<div dir="ltr"><div dir="ltr">Trying to understand. If I read this right you want the router/navigator to replace the target address of a routing request with a different object or location, then start routing, right?<div><br></div><div>Why not simply tag the object_id or other identifier of the replace-destination on the source object (in your terms)? </div><div><div><div dir="ltr" class="gmail_signature"><br></div></div></div><div class="gmail_signature">route_to=<object></div></div><div>with optional suffixes for transport types. </div><div><br></div><div>Wouldn't solve muliple replacement options for one address, but it seems to me that is not a basic requirement. </div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op wo 14 jun 2023 om 09:32 schreef Florian Lohoff <<a href="mailto:f@zz.de">f@zz.de</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Hi,<br>
<br>
Management Summary:<br>
In navigation/routing the point the router is routing to is the nearest<br>
point on the routable network from the poi/address we like to navigate<br>
to. The nearest point may not be a location where the address/poi can be<br>
reached from.<br>
I suggest a navigational aid relation hinting the link between<br>
geocoding and router to use a different point on the routable network.<br>
<br>
<br>
In 2019 i already sketched a problem where the normal "Geocode Address",<br>
"Look for the nearest road" fails miserable for some addresses. There is<br>
a multitude of issues here. Access tag overblocking, huge industrial<br>
complexes, or simply addresses which do not have an easy way for your<br>
mode of transport.<br>
<br>
So i suggest a relation like this<br>
<br>
type=navaid<br>
name=<Name of destination> - Optional<br>
source=<node, way, relation> - Original object we like to reach<br>
destination:motor_vehicle=<node> - Exakt navigation point to get to<br>
<br>
So when the geocoder returns a node, way, relation given in the "source"<br>
of this navaid relation, and our mode of transportation is listed in the<br>
"destination:<modeoftransport>" we replace the location from the<br>
geocoder with the destination from the relation.<br>
<br>
Example 1:<br>
<br>
This is a map i am producing weekly for parts of Germany which shows<br>
addresses on a map when their "nearest road" has a different name. Its<br>
not perfect but you get the idea. (Data bases on the nearest API call in <br>
OSRM)<br>
<br>
<a href="https://osm.zz.de/dbview/?db=addresses-nrw&layer=namemismatch#51.98796,8.57338,17z" rel="noreferrer" target="_blank">https://osm.zz.de/dbview/?db=addresses-nrw&layer=namemismatch#51.98796,8.57338,17z</a><br>
<br>
In this case we have the addresses 114a, and 114b which are behind a<br>
long driveway which somebody tagged as unaccessible. The public road<br>
has a life_gate so there is no real way to get there. But we most likely<br>
want people get to the lift gate. So we would create a navaid relation<br>
for <br>
type=navaid<br>
source=<building way of 114a><br>
source=<building way of 114b><br>
destination=<node of the lift_gate><br>
<br>
Example 2:<br>
<br>
This is the Corporate Fire Brigade within a large industrial compound.<br>
You'll be routed to the next Motorway.<br>
<br>
<a href="https://osm.zz.de/dbview/?db=addresses-nrw&layer=namemismatch#52.00001,8.6192,17z" rel="noreferrer" target="_blank">https://osm.zz.de/dbview/?db=addresses-nrw&layer=namemismatch#52.00001,8.6192,17z</a><br>
<br>
type=navaid<br>
source=<building way of fire_station><br>
destination=<gate of industrial compound><br>
<br>
Possibly adding all POI and Addresses within that compound as source so<br>
all people visiting Mitsubishi Papers in Bielefeld will be routed to the<br>
Gate not some street around.<br>
<br>
<br>
You may pan around the map and find solutions for all those problems.<br>
Sometimes its just the house at the corner - i'd say - okay - no issue.<br>
But sometimes its so utterly broken and people end up on the Motorway, <br>
in the middle of the Woods, on the other side of the Canal etc<br>
with the message "You have reached your destination".<br>
<br>
<br>
I am not really interested in discussions about necessity of this<br>
relation, as it is obvious that this or something similiar is needed and<br>
the problem is unfixable with data manipulation while keeping to<br>
"Ground truth". I am more interested in people Geocoding and Routing<br>
whether this would be a viable way to go, or if anyone can envision <br>
simpler solutions.<br>
<br>
Flo<br>
-- <br>
Florian Lohoff <a href="mailto:f@zz.de" target="_blank">f@zz.de</a><br>
Any sufficiently advanced technology is indistinguishable from magic.<br>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div></div>