The installations map on the Dataverse website has an overlay saying "API key required"

[DieuwertjeBloemen]

Just noticed that the map on https://dataverse.org/ is showing "API key required" all over the map. Maybe something to look into?

[jggautier]

Ooo, thanks for pointing this out!

The url in that watermark, https://carto.com/basemaps/apikey, points to a page that makes it seem that this service is still free, but we'd need to request an API key, and there are usage limits.

Pinging @pdurbin who worked on this map.

[pdurbin]

@DieuwertjeBloemen yes, thanks for pointing this out at #docs > ✔ issue with Dataverse installation map on dataverse.org @ 💬

Bah, I'm seeing the same thing on my meetup site at https://bostonopen.dev

I'll assign this to myself but we're trying to get 6.12 out and probably won't have time to work on it in the short term.

Pull requests welcome! Maybe someone can try the vanilla OpenStreetMap layers. Here's an an example switch (in the opposite direction):

• switch map from default OSM tiles to Carto Voyager bostonopen/bostonopen.github.io#21

[youseihuayu-wonderful]

@pdurbin
I reproduced the current issue locally from main at
86c72d62bbd82a2717a278de8d28f0431d8510a3 using Chrome 151 on macOS 26.3.1. The CARTO
tile requests return HTTP 200, but the PNG tiles contain the “API KEY REQUIRED”
watermark.

I tested two key-free, drop-in raster alternatives using the same map center, zoom,
viewport, and installation data.

Option 1: OpenStreetMap Standard

• No API-key watermark
• All 150 markers loaded
• Popup, zoom, pan, attribution, map.html, and index.html worked
• Simple, neutral style that keeps the installation markers prominent
• Few labels appear at the default world zoom
• The public tile service is best-effort and subject to the OSMF tile usage
  policy

Option 2: OpenTopoMap

• No API-key watermark
• The same marker and interaction checks passed
• Rich terrain detail, but it competes visually with the installation markers
• Attribution is considerably longer
• maxZoom must be reduced from 19 to 17
• The upstream
  README notes
  that its raster tiles are being deprecated as the project moves toward vector tiles

My recommendation is OpenStreetMap Standard because it is the simplest key-free,
drop-in change and its neutral style keeps the installation markers prominent. The
trade-off is that the OSMF public tile service is best-effort, so this assumes the
site’s traffic complies with the OSMF tile usage policy.

If this direction looks acceptable, I can prepare a small PR.

[pdurbin]

My recommendation is OpenStreetMap Standard

I agree! Please make a PR! Thanks, @youseihuayu-wonderful!