Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decimal degrees coordinates ingored, showing only the nearest object #4

Open
int-ua opened this issue Apr 23, 2015 · 3 comments
Open

Comments

@int-ua
Copy link

int-ua commented Apr 23, 2015

To reproduce: paste any decimal degrees coordinates under which there are no objects in OSM to the location field. 49.415248, 26.957707 for example.

Expected result: pointer put directly on these coordinates.

Actual result: pointer put on the nearest object (road, town) that can be several kilometres away.

I think it should be addressed in the django-osm-field because Nominatim's function is just different.

And _lat, _lon fields changes are ignored on the map in my case, is that a bug?

@MarkusH
Copy link
Owner

MarkusH commented Apr 24, 2015

@netAction Do you have any input on this?

@int-ua
Copy link
Author

int-ua commented Apr 24, 2015

After deleting the display:none style from location_lat and location_lon fields the problem is less serious. Now it's just that map is not updated after coordinates are pasted. But it would be still much better if in case of raw coordinates input Nominatim wasn't touched at all. It looks more logical: if user pasted or typed in numbers he/she obviously wanted the pointer put on that place, not to search some nearest object.

@blag
Copy link
Collaborator

blag commented Jun 13, 2016

I will try to take a look into this in a few days and fix it - please ping me if I forget.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants