|
if this is a duplicate please link to answers or documentation when closing. 39.862359, -86.122204 is a dual carriage way intersection. I want to make this intersection searchable as a destination, i.e. type in "kessler and keystone" and have it show up as an option. I think this level of convenience is a necessity for open street maps. I assume the way to achieve this is to create some open street map "point". This is how I did it, and I am making this post to ask if I did it correctly because I am still unsure after looking at documentation. I did not want to name a street light node, because I dont like that solution and its not nice and symmetric.
https://nominatim.openstreetmap.org/details.php?osmtype=N&osmid=6371398592&class=junction One issue: After entering all this I am satisfied, except, if I type in "Kessler and Keystone" it shows up fine, however if i enter "Kessler and Keystone, Indianapolis" the search results do not list it. Any advice on where I can work to resolve this? Thank you for your time, Rick relevant documentation: |
|
Hi Rick, I can totally understand your desire to find a junction by stating the two intersecting road names. But it should be up to the search engine to support that. I find it a terribly bad idea to name junctions like this. If a junction had a proper name different from the street names this would be a different case (like in the first link you gave). But in your case you are merely duplicating the information that already exists: the two roads are in fact intersecting (here is a junction) plus the two names (on the intersecting ways) are already there. So what happens if we started mapping all intersections with an additional (or existing tagged) node with the "x and y" naming scheme?
I would argue that "Kessler and Keystone" is not even a name. When you say "let's meet at the pub at Kessler and Keystone", this is merely an abbreviation for saying "let's meet at the pub at the intersection of Kessler and Keystone". There's a long-standing issue to support this in Nominatim, OSM's default geocoder (search), but as yet no-one has stepped up to the plate to implement it: https://github.com/openstreetmap/Nominatim/issues/123 (and dupe https://github.com/openstreetmap/Nominatim/issues/1224)
(01 Apr '19, 18:13)
Richard ♦
1
TZorn I agree with everything in your post. Richard, I am excited to see if I can help resolve the issue you linked to. This is something I have wanted to help implement for a while. Thank both of you for taking the time to read and respond.
(06 Apr '19, 01:20)
OpenMapsRH
@OpenMapsRH: thanks for getting involved in the Nominatim issue resolution.
(12 Apr '19, 09:50)
TZorn
|
It seems that Nominatim (the geocode / search engine) does not know that the junction is in Indianapolis: https://nominatim.openstreetmap.org/details.php?place_id=257785410 The address tag is probably ignored, and it lists the junction in Dawnbury, Marion County
Some questions that have to be answered, are the admin boundaries correct in that area? Is the nearest street (from which the city is taken) passing through Dawnbury?