<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Talk-us] Ferries</title></head><body>
<div>OK, Clifford, I take your point very well. It may not be
one-off, but when routing algorithms chase data in this way, we CAN
say it comes close to "tagging for the algorithm" and is
therefore to be discouraged. But this might be considered a
sharpening up of the data in a perfectly valid way which also supports
routing algorithms.</div>
<div><br></div>
<div>How about a sane tagging scheme that will capture
highway=ferry_link similar to highway=motorway_link? That's
off-the-cuff, but might be enough. I think there was talk of
this (or something similar) earlier, I'd have to go back in the
threads and look.</div>
<div><br></div>
<div>Concomitantly, routing algorithms can and should pay attention to
said tagging scheme.</div>
<div><br></div>
<div>SteveA</div>
<div>California</div>
<div><br></div>
<div><br></div>
<blockquote type="cite" cite>On Thu, Nov 7, 2013 at 8:49 AM, stevea <<a
href="mailto:steveaOSM@softworkers.com">steveaOSM@softworkers.com</a>>
wrote:<br>
<blockquote>A very big +1 to this. "Posing a challenge"
to the construction of an accurate routing algorithm is a poor excuse
to propose rippling through data changes for what would essentially be
a one-off convenience. Greg Troxel's suggestion about
regular->service->regular and regular->service->ferry
sounds perfectly reasonable and can certainly be made to work for this
particular case. Inside of a routing algorithm is exactly where
this sort of decision-making belongs, not by making data changes that
are more convenient for it.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
I disagree that we are making one-off change. What we are doing is
making the map more useful. When adding an access ramp to a motorway
we call it a motorway link. The waiting area for ferries is a similar
feature of a ferry route. It certainly isn't a service road except in
a broad sense. There was agreement to tag the service=ferry to solve
the problem. That wasn't my first choice but it works.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>There is a push in OSM to include
addresses. One of the big advantages we gain is the ability to route
from door to door. For that we need ferry routing. Living in an area
with one of the largest ferry systems in the world[1], I appreciate
efforts to solve the problem. <br>
</blockquote>
<blockquote type="cite" cite>[1] <a
href="http://en.wikipedia.org/wiki/Washington_State_Ferries"
>http://en.wikipedia.org/wiki/Washington_State_Ferries</a></blockquote
>
<blockquote type="cite" cite>--<br>
</blockquote>
<blockquote type="cite" cite>Clifford</blockquote>
</body>
</html>