-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Adopt crosshairs feature #6173
Comments
I really don't like this idea, since the location people searched for is usually just the area they want to edit in, not an exact location. I don't see any use for this feature. |
Works great if there is a certain different colored house that you can remember when you finally move the pointer to where the numbers all match up to what you want. But if we want to put an object at an exact known X,Y, well there is an assumption that we must not really know the exact X,Y or else we would be using JOSM. Or that we can always base our edits on some satellite photo's nearby features. |
(Related: #4218.) |
OK, today I tried it. So in fact often must be the case where one cannot indeed place a point at an exact coordinate with iD in its current state. Due to pixel size issues, often the exact X or Y one is trying to input is not available. Let's go back and see (with a steady wrist) how precise we can get here 24.1317882,
So we are forced to place our point upon a lattice of 6.7cm spaced dots. |
So we observe that no matter what zoom level, any pixel-based solution, including crosshairs, will still often be inadequate in the case where the user simply wants to get a pair of coordinates directly into the database intact. I propose a simple dialog box, that upon right-clicking on a point, would open up and ask the user what are the coordinates he now wants to move this point to. See also https://commons.wikimedia.org/wiki/Commons:Geocoding#Precision |
This crosshair brings much confidence to the website: |
Here https://gis.swcb.gov.tw/ has a crosshairs in center of the screen feature we could adopt,

E.g., when activated there would be no doubt where e.g., searching for the point "24,121"
https://www.openstreetmap.org/edit#map=19/24.00000/121.00000
actually lies upon the screen.
The text was updated successfully, but these errors were encountered: