On Fri, Jun 12, 2009 at 7:25 AM, Joe Early<[email protected]> wrote: > It seems to be ignored by most (web, GPS units) routing systems though. > So OSM has a chance to outdo the competition here. :P
Is it REASONABLE to route thru it as if it were a bridge? Any Ferry needs quite a penalty on routing ... this 'Bridge' included. How much volume can it handle? How long is the backup at rush hour? Is it usable for thru-traffic, or only used for traffic originating/terminating near one end? Is tagging for the router morally superior to tagging for the renderer? In neither case is there one true implementation, let alone with a transparent immutable spec. Cloudmade can competitively improve their renderer to route over this quasibridge quasiferry quassiaerialway however we decide to tag it and its N for small N operating cousins, if we do it well and don't change it. The other routers have the same option. But given the needed penalty and the surprise factor and the scarcity, I wouldn't blame a router for ignoring these N quassiunique features. As to abstraction, I'd say while this is architecturally a bridge, operationally and highway-wise it's a ferry, the asphalt is not end-to-end even though the beam is. -- Bill [email protected] [email protected] _______________________________________________ newbies mailing list [email protected] http://lists.openstreetmap.org/listinfo/newbies
