Simplify identify (reverse geocoding) service

[gjn]

Currently, our identify (reverse geocoding) service is quite hard to use. Among other things, 3 parameters are required:

mapExtent (real coordinates), imageDisplay (screen size) and tolerance (in pixel). They are required to calculate a) the tolerance/buffer in meters and b) the resolution.

The resolution itself is only relevant for a limited number of dataset: those that have different data for different resolutions (e.g. swissnames). For all other datasets, it is not relevant at all.

In order to simplify, 2 alternative sets of parameters (instead of the 3 mentioned above) should be allowed:

1. Buffer (in meters) and Resolution (pixel/m) -> for datasets require resolution
2. Buffer (in meters) -> for all datasets that don't require resolution.

This is a lot simpler for API users to specify than the 3 parameters above.

@davidoesch @procrastinatio @loicgasser Thoughts?

Related to #2845

[davidoesch]

Let's solve it like Google does it

https://developers.google.com/maps/documentation/geocoding/intro?hl=en#ReverseGeocoding

Buffer parameter: is optional...

[gjn]

That's the idea. Currently, we are way too complicated.

Also, our documentation does not really mention the real world terms geocoding and reverse geocoding. People looking for it don't find it. This should be improved. We should add a section just for adreess geocoding/reverse geocoding.

[gjn]

It might make sense to have dedicated reverse geocoding service for addresses that is independant of the identify service, which is much broader in its application.

Not to forget is that there seems to be a ech standard for addresses...

[davidoesch]

Current geocoding is cumbersome... But widely used. To change it: we have to plan it well.
Reverse geocoding is a need- once in a while.

Proposal: copy 1:1 the Google or Bing method (afaik esri API does not propose anything)

Ech addresses spec: the Geo part is imho weak and is not referencing ech 0056. Think users first ; how are these days in Switzerland reverse / geocoding set up? Provide an easy switch

[RobertoMinelli]

Any update on this? I believe reverse geocoding is the key to enable a lot of interesting approaces!

To do reverse geocoding, I am doing a very cumbersome detour using Solar Roofs 🤦‍♂

[davidoesch]

Not on short term but midterm 2021

[RobertoMinelli]

Ouch, I am sorry to hear that!

@davidoesch could you be so kind to check this issue? I've just discovered that my client application broke because you changed the result of identify request on Solar Roofs.

[AFoletti]

Ouch, I am sorry to hear that!

@davidoesch could you be so kind to check this issue? I've just discovered that my client application broke because you changed the result of identify request on Solar Roofs.

As stated in the dedicated ticket: we did not change anything. The result you found has always been there. You are simply using the service with another mapscale :)