Open jeffreyameyer opened 3 months ago
@batpad brought up Titiler as a possible solution for presenting IIIF endpoints as xyz endpoints to editors.
@batpad - can you discuss with @vincentsarago? Using Titiler for COGs would be another interesting use case.
The UX for this might involve 2 different settings: a) a Titiler endpoint (even if this is just in our fork of iD, we should not hard-code this endpoint and could pre-populate it) b) user entry of IIIF endpoints for use in editing
Key question: how to incorporate with an OHM-specific ELI (or something like it)
I thin @batpad was thinking about https://github.com/developmentseed/titiler-image specifically
Allmaps.org has put together MapLibre and Leaflet IIIF map display components.
What's your idea for a cool feature that would help you use OHM better. Many Internet map and satellite imagery providers are moving to supporting either georeferenced IIIF or Cloud Optimized GeoTIFFs (COGs) to improve network and rendering performance for display of their images.
Some map-related sites that have georeferenced IIIF support include Chronoscope (time and IIIF maps!), allmaps.io.
Currently, iD only supports WMS, WMTS, and TMS support in its Custom Background Settings interface.
Implementing this would include modifying the Custom Backgrounds Settings panel, as well as providing a renderer for georeferenced IIIF maps.
Benefits Benefits will be increased access to even more old maps for tracing and vectorizing, as well as providing a higher-performance editing environment. It would also make it easier to launch a JOSM editor with that basemap pre-loaded from external sites like Chronoscope, Library of Congress, Boston Public Library Leventhal Map Center, Old Maps Online, and others.
Current workarounds Some providers have xyz shims for their IIIF-based images, but that defeats the performance benefits of IIIF and is not available everywhere.
Notes Not sure where this should be implemented, but it seems upstream might be better than in our fork, assuming the maintainers are open to it. An ideal solution would be to roll it out alongside support for COGs - see: https://github.com/openstreetmap/iD/issues/8893
Same support for JOSM: #767