Hello Michael, The 'private' tag is used quite often and will be quite tedious if a user needs to specify what roads he may access as an owner before he can use the system. So from a practical standpoint, it makes sense to treat it as a road tagged with 'destination': A valid route can exit and enter the set of 'destination' roads no more than once of each and, when both occurs, they must occur in that order.
Doing that, will mean that there are some hypothetical cases where for example he wants cross a river and he the nearest bridge is on his property, but the calculated route makes use of the public bridge instead. With a little bit of common sense the driver will ignore the computer and the computer will then catch up as soon as he enters his own property. I haven't considered all these issues last time I looked at my code that handles it and it still interpret 'private' as 'no'. Perhaps the same thing happened to Cloudmade. Or they don't want to take the risk that one of their clients will do something silly, get a fine or get arrested and then face all the legalities and / or bad press. > > access: no > bicycle: yes > created_by: JOSM > foot: yes > highway: service > motorcar: private > name: Munkebotn > note: Middelalder stamvei (ridevei) > old_name: Den Trondheimske postvei > start_date: 1600 > > http://osm.org/go/0Rv01LEg?layers=0B00FTTT > > Is there a problem with the tagging, or with the routing-software? > > -- > Michael Eric Menk > Linkedin: http://no.linkedin.com/in/mikemenk > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk > > _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
