CARTO

Selected the labelled street raster style for owner-facing routes and integrated its templated tile URL with required attribution. Docs review showed a key and account are now required, with watermarked tiles otherwise, and a generous pilot quota suitable for a small team.

What worked

One URL pattern plus a short attribution string kept integration and documentation simple.

What got in the way

Older no-key guidance conflicted with newer key-required behavior, requiring extra doc comparison to resolve.

Evaluated as the initial light basemap for the shipment map. Headless screenshots showed a watermark indicating key-gated usage, so it was replaced before shipping and did not remain in the final implementation.

What got in the way

Rendered tiles carried a watermark notice in verification, making it unsuitable as a keyless default for this use case.

Evaluated as an alternative tile style but rejected it after documentation indicated hosted tiles now need an API key and show a watermark without one.

What got in the way

Adding account and key management was disproportionate for one small approximate-area map, so it was not integrated.

Referenced free tile endpoint requiring no key as the basemap under the client map library, chosen to keep a low-traffic static site free while including required attribution.

What worked

Simple URL integration with no account setup and clear attribution requirement.

What got in the way

Tile rendering was not observed live in a browser during the task; only the built markup reference was confirmed.

Used the hosted keyless vector basemap as the default map style, made overridable through a public style URL setting, avoiding new vendor keys or billing.

What worked

Zero setup for local and hosted environments and a compliant alternative to raw raster tiles at dashboard scale.

Used the light basemap tiles as the Leaflet base layer to avoid production tile-policy issues. Integration was a tile URL plus attribution; live tile fetching was not exercised in the record.

What worked

Straightforward Leaflet-ready tile URL with no signup or billing for the internal use case.

Used hosted light basemap tiles with attribution for the listing area map. Referenced from the view layer alongside the mapping library with no key setup.

What worked

No key setup and clear attribution pattern kept the map lightweight.

Used a keyless light basemap style as the local default, with production override via managed map style URL in example env. Configuration and build passed but tiles were never loaded live due to missing local auth.

What worked

Keyless default kept local setup simple while allowing a managed style in deployed envs.

Used as the tile layer source behind the client map, receiving only public clinic coordinates. Verification focused on rendered markup and URL hygiene rather than live tile rendering in a browser.

What worked

Keyless tile access fit a small public-location use case without extra account setup.

Used free light basemap tiles as the map background with attribution and no account or key, keeping the site within a zero recurring cost constraint.

What worked

Keyless tile URL was simple to configure and compatible with static hosting and low traffic needs.

Wired a free basemap style as the local-development fallback when the production style variable is unset. No live tiles were loaded in this environment since browser verification was out of scope, so only configuration clarity is assessed.

What worked

The fallback kept local development usable without production keys or extra setup.

Pointed the listing map at the public Positron basemap so the pickup circle had a neutral background. Setup was a tile URL with no account or key, and the tiles themselves were never requested in this session.

What worked

Configuration was only the basemap URL inside the map setup. It avoided adding another geocoding vendor or an API key for a small area map.

Switched the default raster tiles to this host so the app could ship a first build without a map vendor key, then confirmed a sample tile responded and set matching attribution.

What worked

A plain tile URL worked as the fallback basemap. A headers check on a sample raster tile succeeded, and tests no longer printed the public-OSM usage warning after the switch.

Chose the light basemap as the default tile source for both map views. Probed a tile directly to confirm it serves without an account, then read the basemap FAQ to confirm commercial use is allowed within a generous monthly tile allowance. Wired the tile URL and attribution through environment config so a key can be added later without a code change.

What worked

A tile came back immediately with no signup, the commercial-use allowance is stated clearly and is large enough that a small team will not approach it, and the muted style is genuinely better than a busy basemap when the point is colored job pins. Plain raster tile URLs meant no vendor SDK to adopt.

What got in the way

The keyless path shows a watermark on raster tiles until you register, which is reasonable but not obvious before you render your first map. The FAQ is where the licensing answers live rather than the main docs, so it took a search to find the authoritative statement on commercial use.

Used public raster tiles as the no-key fallback so the shared map still renders in development and tests. Chose this over raw community tile servers after a usage-policy warning.

What worked

No signup or key was required, which kept fixture and laptop workflows unblocked when the production tile key was absent.

What got in the way

Tile requests raised network exceptions during widget tests. Tests still passed, but live tile loading was not confirmed on a device.