Fix broken basemaps and add Carto/Stadia API key support
@jimsafley is already working on this.
Since Sep 3, 2026.
Assessment
This issue has not been assessed yet.
Description
Half the basemaps we offer don't work:
- All six Carto styles are watermarked without an API key, including Voyager, our default.
- The six Stamen styles return 401 on any real domain.
- Esri DeLorme is retired (404).
Because Voyager is the default, most existing sites are showing a watermarked map and probably don't know it. Fixing this means those sites will visibly change to OpenStreetMap, their setting is preserved, so adding a Carto key restores it.
The Stamen problem is easy to miss: those styles moved to Stadia hosting, and Stadia now requires an API key or a registered domain for anything but localhost. They render normally on localhost, so a developer testing locally sees nothing wrong.
Closes #76. Takes over part of #80.
What needs doing:
- Change the default basemap to OpenStreetMap.
- Remove Esri DeLorme and migrate sites using it.
- Update leaflet-providers to v4.0.0, which adds Carto's API key support.
- Add Carto and Stadia API key fields, alongside the existing Mapbox one.
- Tell admins in the config form when their basemap needs a key, and substitute the default where we can do that safely.
- Add a contrast suggestion to the Base Map setting (from #80).
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from omeka/plugin-Geolocation
-
Document: Multiple locations, shapes, and the new browse mapPossibly taken @allanaaa claimed this 18 days ago. Open
omeka/plugin-Geolocation#83 · 1 assignee ·
-
Accessibility: screen reader handling of map zoom level changesPossibly taken @jimsafley claimed this 23 days ago. Opena11y
omeka/plugin-Geolocation#79 · 2 comments · 1 assignee ·
-
a11y
Difficulty 5/5 Over a week Newbie friendliness 25/100
omeka/plugin-Geolocation#75 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
omeka/plugin-Geolocation#55 ·
-
Enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
omeka/plugin-Geolocation#53 ·
All issues in omeka/plugin-Geolocation
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
parse-community/parse-server#10699 · 1 comment ·
Maintainers usually reply within 1 day
-
area: dashboard bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Nitjsefnie-Harness-Commons/daedalus#1179 ·
Maintainers usually reply within 1 day
-
Aframe enhancement javascript
Difficulty 1/5 Under an hour Newbie friendliness 92/100
webarkit/Aframe-nft#17 ·
-
spec-feedback
Difficulty 2/5 1-3 hours Newbie friendliness 75/100