Reverse geocode observations to municipality

[peterdesmet]

I wonder how useful it is to show coordinates in the table:

I would show a more meaningful name there, such as the municipality (can always be done) and maybe polygon that is more relevant to RIPARIAS, like rivers subunit, basin, ...

3421061584 | Leuven (Dijle) | 2021-12-02 | Procambarus virginalis 3400341585 | Hofstade (Dijle) | 2021-10-20 | Procambarus virginalis

[niconoe]

Note: since the observations are refreshed every night, that would mean around 50,000 reverse geocode operations per day.

What about costs and time of execution? One possible optimisation for that would be to use the observation "migration/replacement mechanism" to only reverse geocode if the observation is new, or if the coordinates have changed since the last import.

Another one would be to reverse geocode locally (using a local source of municipalities) rather than calling an external web service.