[Feature Request] Configurable reverse geocoding radius

[nicobgr]

Is your feature request related to a problem? Please describe.
Not a bug, but with the new geocoding result dropdown in place, it would be really useful to have more control over reverse geocoding behaviour when using a self-hosted provider like Photon. Specifically, the search radius for reverse geocoding requests appears to be hardcoded (currently radius=0.03), which can't be adjusted through the UI. Additionally, there's currently no way to decline a suggested visit — for example, when travelling by train and the train stops briefly somewhere, that location gets recorded as a visit even though it shouldn't be.

Describe the solution you'd like

• An environment variable (e.g. PHOTON_REVERSE_RADIUS) to configure the radius used for reverse geocoding requests to self-hosted providers
• An option to decline/dismiss a suggested visit from the geocoding result dropdown

Describe alternatives you've considered
Being able to adjust the radius directly in the UI would also work as an alternative to an environment variable.

[dgraf-gh]

HI @nicobgr, thank you for the suggestion.

For Photon I would add this into the reverse geocoder configuration.

Additionally, there's currently no way to decline a suggested visit — for example, when travelling by train and the train stops briefly somewhere, that location gets recorded as a visit even though it shouldn't be.

This affects the visit detection and I see the point. I also have a lot of Visits which I do not like to have. The next release will focus on editing capabilities. We would need to create a no-visit area or something like that, and then the detection should skip that. So the path will be part of the trip but no Visit will be created at this point.