editor-layer-index icon indicating copy to clipboard operation
editor-layer-index copied to clipboard

Published 20 hours ago • verified publisher icon osmlab

update au/act urls due to server changes

Open andrewharvey opened this issue 3 years ago • 7 comments

andrewharvey avatar Mar 19 '22 04:03 andrewharvey

Further changes are needed here, the ArcGIS server using using MapServer for most of these however requesting tiles in EPSG:3857 is only working for low zooms at high zooms it returns a checkerboard image.

WMTS tiles work for JOSM but these aren't supported in iD due to the projection.

cc @davidhicks

andrewharvey avatar Mar 19 '22 04:03 andrewharvey

Since the ACTmapi imagery was added in 2018, it looks like they've updated the imagery from using EPSG:4326 and EPSG:28355 projections to the new projection of EPSG:7855 (GDA2020). In the process perhaps they've been removing the old projection imagery from data.actmapi.gov.au and placing the new EPSG:7855 projected imagery on data4.actmapi.gov.au instead.

iD Editor doesn't support EPSG:7855 meaning that the imagery layers will be up to 3m misaligned at present. I also couldn't find a published simple approximation (via block shift vector) that could be implemented at https://github.com/openstreetmap/iD/blob/develop/modules/renderer/background_source.js#L139 and I assume a grid transformation approach would only be possible if editor-layer-index bundled some very approximate and simplified grids that are loaded by iD editor alongside each imagery layer needing an approximate/simple transformation of projections.

davidhicks avatar Mar 21 '22 14:03 davidhicks

Since the ACTmapi imagery was added in 2018, it looks like they've updated the imagery from using EPSG:4326 and EPSG:28355 projections to the new projection of EPSG:7855 (GDA2020). In the process perhaps they've been removing the old projection imagery from data.actmapi.gov.au and placing the new EPSG:7855 projected imagery on data4.actmapi.gov.au instead.

Ah that makes sense

iD Editor doesn't support EPSG:7855 meaning that the imagery layers will be up to 3m misaligned at present.

It's more than that, iD can't even use the existing tiles at all, https://data4.actmapi.act.gov.au/arcgis/rest/services/ACT_IMAGERY/imagery2017mga2020/MapServer it can only make a WMS request for the tiles in EPSG:3857 but there is the checkerboard issue per my comment.

I also couldn't find a published simple approximation (via block shift vector) that could be implemented at https://github.com/openstreetmap/iD/blob/develop/modules/renderer/background_source.js#L139 and I assume a grid transformation approach would only be possible if editor-layer-index bundled some very approximate and simplified grids that are loaded by iD editor alongside each imagery layer needing an approximate/simple transformation of projections.

Maybe if https://github.com/openstreetmap/iD/issues/4843 is done then it could all be handled on the iD side, until then it's not looking good for these layers in iD...

andrewharvey avatar Mar 22 '22 05:03 andrewharvey

Hi @tyrasd, what do you think ELI should do here?

grischard avatar Aug 03 '22 15:08 grischard

Isn't the simple solution for OSM Oceania to run a maproxy instance that reprojects the WMS layers?

I would offer the SOSM instance, but it really doesn't make a lot of sense to send everything around half the globe and then back again.

simonpoole avatar Aug 03 '22 17:08 simonpoole

Isn't the simple solution for OSM Oceania to run a maproxy instance that reprojects the WMS layers?

Good suggestion

andrewharvey avatar Aug 04 '22 00:08 andrewharvey

@andrewharvey The services I checked under https://data4.actmapi.act.gov.au/arcgis/rest/services/ACT_IMAGERY seem now to support a "real" WMS server supporting EPSG:4326/CRS:84. E.g. https://data4.actmapi.act.gov.au/arcgis/services/ACT_IMAGERY/imagery2017mga2020/MapServer/WMSServer?request=GetCapabilities&service=WMS

rbuffat avatar Oct 07 '22 12:10 rbuffat