[Openstreetmap] re: turn restrictions

[wabanstar]

  "How about something like a property on a node like
no-turn=a.b,c.e,e.d; where a/b/c/d/e are segment ids for segments
connected to that node, and order matters?  All other combinations are
fair game for routing."
  This would be better than nodes as far as my opinion. Nodes will create clutter as intersections are node intensive if you consider complex multiple intersections at ramped dual carriageways. Nodes also increase storage demands. Related problems are quality control and specifications as you cannot have a consistent turn restriction data specification without consistency in how you vectorize intersections or you will turn up new problem types. Related is who gets to break data and to what purposes and end and how are you going to track those changes going forward? i.e. You may have a good data set I overwrite with a poor one, or my lack of understanding of your turns implementation may result in my breaking your turns ( or you breaking mine, etc.).


		
---------------------------------
Yahoo! Photos
 Ring in the New Year with Photo Calendars. Add photos, events, holidays, whatever.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20060124/df0cf80d/attachment.html>