Similarly, I parse route_ref to identify which stops are served by a particular bus route. Maperitive can't pick out the nodes from the relation directly, so I was glad of the "alternative/duplicate" method.
On Fri, May 31, 2013 at 4:44 PM, Jo <winfi...@gmail.com> wrote: > When standing in front of a bus stop, it's easy to see which bus lines are > served by it. I add this information to > > route_ref > > This enables me to check later on when trying to add the stop to the > proper route relations. > > In the mean time I have a database file with all the bus stops in the > region and which buses pass by at what time . The script which creates an > OSM file based upon this also populates route_ref. > > It is then very easy to find all stops served by a given line: > > RR route_ref="(^|.+;)17(;.+|$)" inview > > This is a regular expression search. > > Jo > > > 2013/5/31 Jochen Topf <joc...@remote.org> > >> Hi! >> >> We have had an informal convention for a long time to use a semicolon >> (;) in tag values to separate multiple values, for instance >> "ref=I 70; US 40" to denote that there are two numbered roads on a way. >> But most software out there doesn't actually interpret this in any >> special way. >> >> If you know of any software that actually does interpret this specially, >> please tell me. I am trying to get an idea where and how this is used in >> the real world. You can answer here on the list or write to me >> privately, I'll summarize for the list later. Thanks! >> >> Jochen >> -- >> Jochen Topf joc...@remote.org http://www.jochentopf.com/ >> +49-721-388298 >> >> _______________________________________________ >> talk mailing list >> talk@openstreetmap.org >> http://lists.openstreetmap.org/listinfo/talk >> > > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk > >
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
