mismatching bounds at french imagery entries

[Klumbumbus]

The bounds of an imagery entry must match the shape. Could you please review your edits? Thanks!

* Bounds do not match shape (is 41.3136241,-5.3525496,51.1761675,9.6356823, calculated <bounds min-lat='41.27688' min-lon='-6.3' max-lat='51.32937' max-lon='9.8'>): [FR] BANO - http://{switch:a,b,c}.layers.openstreetmap.fr/bano/{zoom}/{x}/{y}.png
* Bounds do not match shape (is 41.3136241,-5.3525496,51.1761675,9.6356823, calculated <bounds min-lat='41.27688' min-lon='-6.3' max-lat='51.32937' max-lon='9.8'>): [FR] Route 500™©® - http://{switch:a,b,c}.tile.openstreetmap.fr/route500/{zoom}/{x}/{y}.png
* Bounds do not match shape (is -21.496511,-178.577276,51.1761675,55.9657599, calculated <bounds min-lat='-21.496511' min-lon='-178.577276' max-lat='51.32937' max-lon='55.9657599'>): [FR] BDOrtho IGN - https://proxy-ign.openstreetmap.fr/bdortho/{zoom}/{x}/{y}.jpg
* Bounds do not match shape (is 41.3136241,-5.3525496,51.1761675,9.6356823, calculated <bounds min-lat='41.27688' min-lon='-6.3' max-lat='51.32937' max-lon='9.8'>): [FR] Cadastre - http://tms.cadastre.openstreetmap.fr/*/tout/{zoom}/{x}/{y}.png
* Bounds do not match shape (is 41.3136241,-5.3525496,51.1761675,9.6356823, calculated <bounds min-lat='41.27688' min-lon='-6.3' max-lat='51.32937' max-lon='9.8'>): [FR] BD Carthage - http://{switch:a,b,c}.tile.openstreetmap.fr/route500hydro/{zoom}/{x}/{y}.png

(from ImageryCompare)

(The plugin ​imagery-xml-bounds helps at creating the shape and bounds.)

[Stereo]

Thank you! I didn't know about that plugin, I'll remember it if I ever edit those bounds again.

[Stereo]

Thank you for catching the remaining one, stoecker.

[stoecker]

Replying to Stereo:

Thank you for catching the remaining one, stoecker.

We admins see a warning until all issues are solved ;-)

[Klumbumbus]

@Stereo: You added some explicit max-zoom attributes. However this is automatically detected correct by JOSM in most cases. If this works then please don't add max-zoom. The reason is that the imagery provider may change the max-zoom in the future and we don't notice and then we may miss the best resolution of the tiles.

[Stereo]

Sure, I can remove those. Should I also change the documentation at https://josm.openstreetmap.de/wiki/Maps#Documentation to say that it's now an anti-pattern?

[stoecker]

@Klumbumbus:

For WMS. This was for TMS.

[Klumbumbus]

My experience is that autodetection of the max zoom level works for TMS too.

[stoecker]

Causing lots of useless requests to the TMS. That's not recommended!

[Klumbumbus]

OK. And for WMS this is derived from the GetCapabilities?

[Klumbumbus]

@Stereo, could you please review these two differences of ELI and JOSM database:

* License URL differs ('https://data.public.lu/en/datasets/lidar-projet-pilote-dun-releve-3d-du-territoire-luxembourgeois/' != 'https://data.public.lu/en/datasets/bd-l-ortho-webservices-wms-et-wmts/'): [LU] geoportail.lu LIDAR prototype Nordstad 2017 - http://{switch:wmts1,wmts2}.geoportail.lu/opendata/wmts/ortho_10cm_proto_lidar/GLOBAL_WEBMERCATOR_4_V3/{zoom}/{x}/{y}.jpeg
* Attribution URL differs ('https://act.public.lu/fr/cartographie/lidar/' != 'https://data.public.lu/en/datasets/bd-l-ortho-webservices-wms-et-wmts/'): [LU] geoportail.lu LIDAR prototype Nordstad 2017 - http://{switch:wmts1,wmts2}.geoportail.lu/opendata/wmts/ortho_10cm_proto_lidar/GLOBAL_WEBMERCATOR_4_V3/{zoom}/{x}/{y}.jpeg

(I think it is wrong in JOSMs database)

[stoecker]

Replying to Klumbumbus:

OK. And for WMS this is derived from the GetCapabilities?

No. WMS has not really zoom-steps. Request are based on a free sections of the world. Max-Zoom there is a kind of workaround for bad servers.

[Stereo]

Replying to Klumbumbus:

@Stereo, could you please review these two differences of ELI and JOSM database:

Fixed, thank you.

So I should leave the max-zoom then?

[Klumbumbus]

Replying to Stereo:

So I should leave the max-zoom then?

Yes.