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

Searching using coordinates is useless as markers will be put with a large error margin #419

Open
piiskop opened this issue Jul 9, 2020 · 6 comments

Comments

@piiskop
Copy link

piiskop commented Jul 9, 2020

Tonight, I participated on an adventure game. We knew ahead the coordinates of six control points. So I wanted to use my new toy Nextcloud Maps for that. As I was running already, it turned out that almost all of these six pair of coordinates showed up incorrect results. For instance: 59.39736,24.29106. The marker will be set to Merenuka in the forest near a road. Actually, that point is like half a kilometer South. I fulfilled with that information my story on setting up FOSS-directions where you can see screenshots, too.

@tacruc
Copy link
Collaborator

tacruc commented Jul 9, 2020

I guess the curtial infromation is that a search for 59.39736,24.29106 leads to marker at "lat":"59.4012388","lon":"24.2897721"

@piiskop
Copy link
Author

piiskop commented Jul 9, 2020 via email

@tacruc
Copy link
Collaborator

tacruc commented Jul 9, 2020

Are you a developer or just somebody that guesses?

Right now I'm just somebody that guesses. If this turns out to be a nice conversation, and it turns out that I understand whats your problem, It might be, that I'm the guy who uses his free time to fix you problem.

So right now I'm trying to understand what you want, without reading 4 pages about how to install stuff.

So in short you search for: 59.39736,24.29106
and the marker result is not as expected at 59.39736,24.29106, but "lat":"59.4012388","lon":"24.2897721"

Or did I miss anything?

@piiskop
Copy link
Author

piiskop commented Jul 9, 2020 via email

@piiskop
Copy link
Author

piiskop commented Jul 10, 2020

As I'm kind of calmed down meanwhile, I gave myself a try to reread your response. You made a grammatical mistake with the word curtial that doesn't exist. So I understood that you meant curtail and that your guess was on the software. However, now I understand that you meant crutial and therefore your guess was on my report not the software.

Meanwhile a Nominatim specialist mtmail explained what Nominatim is for - it's for getting names as the name of the software is. So this issue is directly related to Nextcloud Maps.

@Spartachetto
Copy link

@tacruc given the specific behaviour of Nominatim, there are three possibilities, I think. The first one is to maintain the current behaviour; the second one is to select the exact coordinates if the user inputs them; the third one is to provide the user an option (something like "do you want to select the exact coordinates or the nearest named place?"). It is clear that you could choose to change the selected behaviour according to the input (something like "if there are enough decimal digits pick the exact location, otherwise ask"). This is something related to the preferred UI, as I know that in general Nextcloud prefers not to provide unnecessary options.... @jancborchardt could maybe provide some input on this issue.

@piiskop your aggressive behaviour risks to deter contributors to develop open source software, and is not tolerated in several communities (as mtmail already clearly explained in the linked issue of Nominatim). Could you please try to have a kinder and more constructive approach?

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

No branches or pull requests

3 participants