OpenStreetMap

Used the community tile layer as the base map for both views to avoid keys and billing. Configuration was simple, but live tile loading and on-screen appearance were not verified in this environment.

What worked

Zero-key configuration kept setup effort low for a team new to maps.

Recommended and implemented a coordinate-pinned embed for the booking and ticket web pages with a shared address and directions link, avoiding address search that resolved to the wrong end of the street.

What worked

No key, billing, or package needed; plain iframe suited an assistant-maintained site and privacy constraints.

Read published tile usage policy to answer whether an internal low-volume ops dashboard is allowed and what attribution is required. Concluded conditional yes with visible credit and caching, plus a migration plan if use grows.

What worked

Attribution and low-volume versus heavy-use guidance were findable and sufficient to give practical terms: keep credit visible, use standard tile URL, avoid scraping and cache-busting.

What got in the way

Policy language around donation-run capacity and blocking left some judgment calls about what counts as heavy use.

Used free raster tiles and attribution for the base map, plus a fallback link to the same tiles when scripting is unavailable. Required no account or token.

What worked

Setup was trivial and suitable for a non-developer maintainer. Attribution and fallback links were straightforward.

Used as the tile source for the guide maps with attribution. Avoided API keys and quotas compared with commercial providers. References were present in built pages but live tile loading was not observed in a browser.

What worked

Zero setup tile layer that matched the static, no-signup requirement for a small personal site.

Chose the standard tile service for the small pickup-area map because it needs no account or key for light use, with required contributor attribution shown on the map.

What worked

No-key integration kept the map simple, and usage terms for light versus heavy use were easy to find.

Integrated the standard tile embed in an iframe with a marker plus a directions link using only clinic coordinates, avoiding any key, billing, JavaScript library, or patient data in the URL. Chosen for simplicity and privacy fit with plain server templates and a small team new to maps.

What worked

Zero-key iframe approach kept implementation to model URL helpers and template changes, with no key management or front-end build needed and clear attribution and lazy loading handling.

What got in the way

Live tile rendering was not observed in a browser during the recorded task, so real-world load behavior was not assessed.

Used standard raster tiles as the Leaflet base layer centered on the service area. The map rendered correctly in automated browser screenshots with no key management or styling work.

What worked

Keyless tile access kept deployment unchanged and was sufficient for a first internal scheduling map.

Selected the keyless embed iframe built only from public clinic coordinates for a visual map, plus text address and outbound directions link. Avoided keyed SDKs and billing. Live tile loading was not observed in the record.

What worked

Keyless embed was simple to render from stored coordinates with no account or billing and clear attribution expectations.

What got in the way

Even the keyless embed causes authenticated pages to request third-party imagery, so documented privacy and security review remains needed before production use.

Used standard raster map imagery with required contributor attribution for the interactive map and coordinate-based directions links for two public clinic locations. No account or key was needed for the low-traffic prototype, with a noted need to move to a provider account or self-hosted tiles and complete a security review before production.

What worked

No-key access and simple coordinate links made setup fast while keeping only public coordinates in map requests.

What got in the way

Live tile reliability was not directly observed in the record; visitor address disclosure to the tile service remains a production consideration.

Used as the tile layer behind the client maps with attribution included. Chose it to avoid vendor SDKs, keys, and per-view billing for a small first-time team.

What worked

Simple to reference from the map component and compatible with the no-key deployment story.

What got in the way

No live tile loading was observed in the task record, so visual quality and network behavior remain unverified.

Selected as the tile source for the ops map because it required no API key, billing, or extra access setup. Referenced from the page but not loaded against the live tile service.

What worked

Zero-configuration tile usage kept deployment and operations simple for an internal page.

What got in the way

Tile loading, attribution display, and network behavior were not observed.

Used as the no-key local development tile fallback so maps still render without a commercial key configured.

What worked

Zero setup fallback for development before adding a paid tile key.

Used as the base tile layer for walking-guide maps, viewed through the mapping library on desktop and emulated phone viewports.

What worked

Tiles loaded well in both static checks and headless screenshots, with built-in attribution matching the no-key requirement.

Used standard map tiles with required attribution for light pickup-map traffic, with guidance to change tile sourcing if traffic grows. No live tiles were fetched during tests.

What worked

Attribution and light-use policy were straightforward to follow.

Used coordinate-pinned embed iframe for the venue map to avoid address search placing visitors at the wrong end of the street, with no API key or extra package. Centralized location constants were added and reused across booking, ticket, and printable views with directions links.

What worked

Copy-paste embed needed no keys, billing, or client JS upkeep, and coordinate-based links avoided geocoding errors.

What got in the way

Live map rendering was not checked in a browser during the task, so visual behavior is unverified.

Used as the no-key tile layer behind the interactive maps. Integration was simple attribution plus tile URL, suitable for a low-traffic personal site with no billing overhead.

What worked

Simple to reference from the map library and appropriate for static pages with no backend.

Integrated the keyless embed iframe and directions link built only from clinic coordinates, avoiding any paid product, key management, or third-party script on authenticated pages with sensitive data.

What worked

Embed URL pattern with bounding box and marker plus a separate directions link covered the fixed-point display need with minimal code and no procurement or key handling.

Used keyless map tiles and a plain outbound directions link carrying only public clinic coordinates. Avoided account, billing, and heavier privacy review while keeping address and directions usable without the map.

What worked

No-key access, simple coordinate-based directions links, and clear attribution requirements kept implementation and review light.

Used standard map tiles as the base layer so the operations page needed no API key or extra account setup. The layer rendered correctly during headless browser verification.

What worked

No-key tile layer kept deployment and local setup simple.

Used open map tiles as the visual layer for job pins. Needed no account or key, which suited a small team, and domestic street plus town coverage was adequate when the country was always included.

What worked

Zero setup and no billing. Fine for showing clusters of jobs versus outliers.

Used public embed and directions URLs centered on stored clinic coordinates for the appointment detail page, with address shown on list and detail. No JavaScript SDK, API key, billing, or extra dependency was needed, and only public location data was placed in third-party URLs.

What worked

URL pattern was simple to generate from model helpers and render in templates with lazy loading and privacy attributes. Template tests could assert the coordinates and embed and directions URLs without a live service.

Used as the no-key base tile layer for the interactive maps. Configuration was a simple tile URL with attribution, which suited a static site with no backend or billing. Live tile loading in a phone browser was not observed during the task.

What worked

Zero setup, no credentials, and straightforward tile URL integration for a lightweight hiking guide use case.