On Tue, 07 Apr 2009 12:46:45 +0200, <[email protected]> wrote: > Update: > > I get the TABCD from group 3A-messages (if y14 and y15 are 0, > then bit y11-y6 contain the tabcd). However that is useless unless > I have the CID=countryID too.
I think I found some way but it's a mess. http://wiki.openstreetmap.org/wiki/TMC/TMC_Import_Germany#TMC:Point The CCID is the first 4 bits of the PI (PI=block1). In each LocationCodeTable you find a mapping of the CCID to the CID for that one country. (I collected some in the wiki) However the CCID is NOT UNIQUE. You need to know at what geographic location the message has been received to choose the correct CID and thus correctly parse it. (Else a traffic-jam in hamburg/Germany may show up on some dust-road in either Lybia or Serbia.) Thank god TMC-messages are usually empedded in NMEA except if you use a GoPal and that gives NMEA and binary-TMC on 2 different serial- ports at the same time. So...should I prefix the tag for TMC LocationCodes in OSM with the CID(unique) or the CCID(not unique but that is what you receive)? Marcus _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
