[mkgmap-dev] Problem with routing to a destination at oneway
From Robert Vollmert rvollmert-lists at gmx.net on Wed Feb 18 14:42:37 GMT 2009
On Feb 18, 2009, at 15:25, Mark Burton wrote: >> What's dirindicator supposed to do, anyway? I'm thinking that maybe >> the dirindicator and one-way flags shouldn't be treated as >> independent >> flags, just that some applications check NET for oneway-ness, while >> others check NOD. > > This is what the cGPSMapper doc says about it: > > DirIndicator=# Direction indicator, only for streets, highways, > etc. > 0 no direction > 1 the GPS will show direction of the road > (calculated > internally by GPS) > Default = 0 > > When I originally read that, I thought that it was saying something > about > how the gps displayed the road, rather than affecting the routing > logic. Yes, that's what I thought, too. It turns out we're writing direction info in three places: 1. a flag in RGN (Polyline.FLAG_DIR) 2. a flag in NET (RoadDef.FLAG_DIR_INDICATOR) 3. a flag in Table A in NOD (RoadDef.TABA_FLAG_ONEWAY) Maybe I got the DirIndicator<->NET connection wrong, and DirIndicator should just be set on the polyline. Since the polyline is what's rendered, that would make a lot of sense. Then 2. and 3. would both be oneway-ness. I'll make the change. Cheers Robert
- Previous message: [mkgmap-dev] Problem with routing to a destination at oneway
- Next message: [mkgmap-dev] Problem with routing to a destination at oneway
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list