Modify ↓
Opened 2 years ago
Last modified 14 months ago
#18726 new enhancement
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 entries
- Remove _apiKey_ support in JMapViewer
- Use {apikey} in all relevant entries:
- Maps/Worldwide
- Bing
- Mapbox
- mapbox_locator_overlay
- Maxar-Premium
- Maxar-Standard
- opencylemap
- tf-landscape
- tf-outdoors
- Maps/Australia
- City_of_Melbourne_Feb_2019
- City_of_Melbourne_May_2018
- Maps/Austria
- geoimage.at
- Maps/Brazil
- IBGE_DF_Addresses
- IBGE_Nomes_Ruas
- IBGE_Salvador_Streets
- Maps/New Zealand
- LINZ_NZ_Aerial_Imagery
- LINZ_NZ_Topo50_Gridless_Maps
- Maps/Norway
- geovekst-nib
- Maps/Sweden
- lantmateriet-orto1960
- lantmateriet-orto1975
- lantmateriet-topowebb
- Maps/USA
- New_and_Misaligned_TIGER_Roads-2013
- US_Forest_Service_roads_overlay
- US-TIGER-Roads-2017
- US-TIGER-Roads-2018
- US-TIGER-Roads-2019
- WSDOT-Roads-2017
- Maps/Worldwide
- Update the apikey workaround/support in ELI-Sync-tool
Attachments (0)
Change History (12)
comment:1 Changed 2 years ago by
Cc: | sommerluk added |
---|
comment:2 Changed 2 years ago by
Description: | modified (diff) |
---|---|
Summary: | Use {apiKey} everywhere → Use {apikey} everywhere |
comment:3 Changed 2 years ago by
Milestone: | Longterm → 20.08 |
---|
comment:4 Changed 2 years ago by
Description: | modified (diff) |
---|
comment:5 follow-up: 7 Changed 2 years ago by
comment:7 Changed 2 years ago by
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 Changed 2 years ago by
Description: | modified (diff) |
---|
comment:9 Changed 2 years ago by
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 Changed 2 years ago by
Milestone: | 20.08 → Longterm |
---|
comment:11 Changed 2 years ago by
Keywords: | apikey mapkey added |
---|
comment:12 Changed 14 months ago by
Owner: | changed from Don-vip to team |
---|---|
Status: | assigned → new |
Note: See
TracTickets for help on using
tickets.
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?