-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 14 Jun 2023 19:08:11 +0200 Florian Lohoff <f...@zz.de> wrote:
>> Some of the issues could be handled better by the data consumers. >> I.e., matching names of addresses and roads, routing to gates and >> entrances in parks, routing to terminals in airports. > >This is an argument which is coming up all the time and nobody solved >it yet. And IMHO this is unsolvable. There is no "one generalizing >algorithm can solve this". Agree, but there are things that could be generalized. E.g., by using "entrance" tags or something similar on the perimeter. Or route_to_here:motorist=yes, route_to_here:public_transport=yes on nodes on the perimeter. And then fall back to relations when e.g., you have an airport where the terminal is not at the perimeter. >> E.g., when routing from Tårnby to Copenhagen Airport, ORSM still >> routes you away from the airport. (at least what most people would >> consider the airport) >> >> https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=55.6282%2C12.5998%3B55.6091%2C12.6510 > >With this link you already are past the problem. There are >geo-coordinates in them. Now its to late to correct the destination. I know. That is why I mentioned the place names. As far as I know I cannot make an URL with the place names in them. If you go to https://www.openstreetmap.org/ press the "find direction" icon and put in "Tårnby" and "Copenhagen Airport", this is what you get. >The process is > >- Geocode something >- Get a geo coordinate - possibly an object >- Get the "nearest coordinate on the routable network" for that geo > coordinate from the POI >- Route to the geo coordinate on the road network. > >Now - We get a geo coordinate for "Frankfurt Airport" which is the >centroid of the object with the name "Frankfurt Airport" which is the >WHOLE of the collection of the airport. > >Now we call "nearest" and just by pure luck we possibly get a good >geo coordinate on the road network. > >And by Example 2 i posted you see - this breaks all the time at much >simpler setups. And for the corporate fire station there is no "gate" >or "entrance". Yeah - the fire_station has an entrance, but thats >equally broken. It enclosed in an industrial landuse or a >man_made=works. That centroid may also be completely off. > >Try routing to > > >Class poi - Large "Polygon POI" - random location to end up: > >"Frankfurt Airport" (South of Airport on a perimeter Road) >"Flughafen Paderborn" (North of Airport in the Woords) >"Claas, Harsewinkel" (Gate 3, instead Gate 1) >"Miele, Gütersloh" (On a higher class road next to their warehouse, >rail inbetween) "Generalfeldmarschall-Rommel-Kaserne" (Road next to >the fence, 2km from the entrance) "Zoo Berlin" (On the opposite side >of the Zoo than the parking) "Tagebau Garzweiler" (Somewhere on a >track near the big dig) > >Addresses with long distance to the road network. The next road is >basically a dead-end for this address: > >"45883 Gelsenkirchen, Grothusstraße 199" (On the other side of the >Canal) "45357 Essen, Klaumerbruch 40a" (On the other side of the Canal) >"46535 Dinslaken, Am Alten Drahtwerk 27" (On the other side of a rail >track) > > >So take any large polygon POI in your vicinity and try routing there. >80% of them are broken. And this is not algorithmically solvable. > >Flo -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTFiAV7M5dCBbueFnXaxL9tj5Q+NAUCZIrTgwAKCRDaxL9tj5Q+ NIUqAKDQOCJs0Y3gkocDyxV5JjdzRgZUqACgnnLZYrBDYb5zBgu9qr4lRwDbTuQ= =210l -----END PGP SIGNATURE----- _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
