Opened 5 years ago
Closed 12 months ago
#18726 closed enhancement (fixed)
Use {apikey} everywhere
Reported by: | Don-vip | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | Longterm |
Component: | Core imagery | Version: | |
Keywords: | api key apikey mapkey | Cc: | Stereo, stoecker, sommerluk |
Description (last modified by )
Follow-up of #18440:
- Wait for JOSM users to all run r15855+
Replace _apiKey_ by {apikey} in Maxar entriesRemove _apiKey_ support in JMapViewer- Use {apikey} in all relevant entries:
- Maps/Worldwide
BingMapboxmapbox_locator_overlayMaxar-PremiumMaxar-StandardRemovedopencylemaptf-landscapetf-outdoors
- Maps/Australia
City_of_Melbourne_Feb_2019City_of_Melbourne_May_2018
- Maps/Austria
geoimage.at
- Maps/Brazil
IBGE_DF_AddressesIBGE_Nomes_RuasIBGE_Salvador_StreetsRemoved?
- Maps/New Zealand
LINZ_NZ_Aerial_ImageryLINZ_NZ_Topo50_Gridless_Maps
- Maps/Norway
geovekst-nib
- Maps/Sweden
lantmateriet-orto1960lantmateriet-orto1975lantmateriet-topowebblantmateriet-orto-historic
- Maps/USA
New_and_Misaligned_TIGER_Roads-2013US_Forest_Service_roads_overlayUS-TIGER-Roads-2017US-TIGER-Roads-2018US-TIGER-Roads-2019WSDOT-Roads-2017(2017->2021)
- Maps/Worldwide
- Update the apikey workaround/support in ELI-Sync-tool
Attachments (0)
Change History (16)
comment:1 by , 5 years ago
Cc: | added |
---|
comment:2 by , 5 years ago
Description: | modified (diff) |
---|---|
Summary: | Use {apiKey} everywhere → Use {apikey} everywhere |
comment:3 by , 5 years ago
Milestone: | Longterm → 20.08 |
---|
comment:4 by , 5 years ago
Description: | modified (diff) |
---|
follow-up: 7 comment:5 by , 5 years ago
comment:7 by , 5 years ago
Replying to anonyme:
For people who use ELI directly in JOSM
What's the point? JOSM has more entries than ELI, and we check for their validity, so the JOSM dataset is greatly superior both in quantity and quality.
comment:8 by , 5 years ago
Description: | modified (diff) |
---|
comment:9 by , 5 years ago
The workaround if you come across this in JOSM is to upgrade to the latest version. But yeah, like Vincent said, I don't know anyone who uses ELI in JOSM apart from ourselves, the ELI maintainers :).
comment:10 by , 4 years ago
Milestone: | 20.08 → Longterm |
---|
comment:11 by , 4 years ago
Keywords: | apikey mapkey added |
---|
comment:12 by , 4 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
comment:13 by , 2 years ago
Description: | modified (diff) |
---|
comment:14 by , 2 years ago
Description: | modified (diff) |
---|
Added missing apikeys. Update status.
Last point ELI-tools: getUrlStripped() should be adapted to also handle other apikey places like /token/{apikey} which are now much easier to detect.
comment:15 by , 2 years ago
Description: | modified (diff) |
---|
comment:16 by , 12 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
ELI just addded an
{apikey}
value to URLs https://github.com/osmlab/editor-layer-index/pull/548. For people who use ELI directly in JOSMhttps://osmlab.github.io/editor-layer-index/imagery.xml
this now gives a warning/error.Is this ticket tracking support for this?