-
Notifications
You must be signed in to change notification settings - Fork 7
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
Matches against unnamed stop positions #22
Comments
Thanks for reporting this! Usually, the matching prefers In the case of Wörth Berufsschule,
N336080300 is already matched to the higher ranked
I think to remove matches between unnamed bus, ferry and funicular select * from osm_stops o
join matches m on o.osm_id=m.osm_id
join haltestellen_unified h ON m.ifopt_id = h.GlobaleId
where o.match_state!='NO_MATCH'
and public_transport='stop_position'
and o.mode in ('ferry','bus','funicular')
and (not highway='bus_stop' or highway is null)
and linien is null
and o.name is null; Other matches usually indicate data issues in one source or another. They probably should not be imported into Nominatim, though I'd keep them for QA purposes. |
So the match is not completely wrong. Delfi just has a platform more for this stop than OSM. It might make more sense to look at this from the Delfi data perspective and remove the slightly odd platform types if there is a decent platform available for the same stop and it doesn't map at all or maps against a OSM stop_position (with or without name).
You should pretty much always find a |
The final output has a
MATCH
between:de:07334:32431:0:11
While the match is right, the script keeps the wrong OSM object. It references to the unnamed
public_transport=stop_position
instead of the namedhighway=bus_stop
(N336080300).You'd want to prefer the
highway=bus_stop
(orrailway=*
) object as a general rule because Nominatim currently does not indexpublic_transport=*
objects at all (unless you changed the style).The text was updated successfully, but these errors were encountered: