You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With wagtail==4.0.4 and wagtailgeowidget==6.2.0, I have setup linked address and position fields as in the docs, and tested with both Google Maps and Leaflet + Nominatim.
When I change the address, the pin moves on the map as expected.
However, if I move the pin, the address does not update. Is it supposed to, ie. is reverse geocoding supported?
If it isn't, it would be great to have an option to either prevent the user from moving the pin (so the map would just be a 'read-only' confirmation of the address), or to empty the address field if the pin is moved - so as to prevent situations where the address and position are out of sync.
The text was updated successfully, but these errors were encountered:
However, if I move the pin, the address does not update. Is it supposed to, ie. is reverse geocoding supported?
This is the expected behavior, we do not have reverse geocoding from lat/long to string.
The reason is that I have never seen this requirement, it might also result in a lot of costly requests against the geocoding API.
If it isn't, it would be great to have an option to either prevent the user from moving the pin (so the map would just be a 'read-only' confirmation of the address), or to empty the address field if the pin is moved - so as to prevent situations where the address and position are out of sync.
I think having a read-only map is a good idea, contributions are welcome!
With
wagtail==4.0.4
andwagtailgeowidget==6.2.0
, I have setup linked address and position fields as in the docs, and tested with both Google Maps and Leaflet + Nominatim.When I change the address, the pin moves on the map as expected.
However, if I move the pin, the address does not update. Is it supposed to, ie. is reverse geocoding supported?
If it isn't, it would be great to have an option to either prevent the user from moving the pin (so the map would just be a 'read-only' confirmation of the address), or to empty the address field if the pin is moved - so as to prevent situations where the address and position are out of sync.
The text was updated successfully, but these errors were encountered: