jmacura

> Well this is kinda insane.... our 4087 def is just wrong. No idea how. It should not be > > ``` > proj4.defs( > 'EPSG:4087', > '+proj=cea +lon_0=0 +lat_ts=0...

Thanks for investigating this, @FilipLeitner ! I wil try to look at that.

> > What would be really interesting is a git-like workflow...: You could potentially have layers, and merging down layers is a fairly standard operation, but you could also signal...

> Idea for clustering all removal actions (see also [#2289](https://github.com/OpenOrienteering/mapper/pull/2289)) in the edit menu without making it too extensive (...) The "Cleanup" menu item reminds me the magical "optimize /...

> I suggest to place the action in the Map menu, e.g. as "Cleanup object tags...". That feels even more ocadish ("Map" -> "Optimize / repair"). I wonder if your...

Considering the explanation by @dl3sdo , I am hardly finding any relation to the other tools in the "Map" menu. Placing it below the "Find" and "Find next" options in...

If we adhere to the [Usage Policy](https://operations.osmfoundation.org/policies/nominatim/), why not? It shall not be hard to implement -- adding a new parser in the components/search.service shall be sufficient. It can be...

There are also commercial alternatives. Most of them have a free tier which may be suitable for us in like 99 % cases. See https://www.geoapify.com/pricing/ or https://rapidapi.com/GeocodeSupport/api/forward-reverse-geocoding/pricing . An app...

Dear @mavery1763 , read again this line by @dg0yt : > We are talking about the user-facing string (a "display name") which was never meant to be directly interpreted in...

So if I try to sum up... The issue request is actually to prevent "Map Georeferencing" dialog to show "valid" until there is "N" or "S" filled in the "UTM...