Hey Charles, Yes, TIGER data is planar. OSM data derived from TIGER is of course planar, but OSM data is not technologically limited to representing planar road networks. Fixing this problem was one of the main motivations for importing TIGER to OSM, at least for me. After the TIGER import I just got to work fixing nonplanar intersections by hand. In any given city there aren't _that_ many nonplanar intersections. You can probably fix a whole city in an evening.
Or you could wait for the census to publish overpasses in TIGER data. Might wait a long time, though. -B On Wed, Dec 3, 2008 at 2:55 PM, Charley Hughes <[EMAIL PROTECTED]> wrote: > I was thinking of using openstreetmap as a data source for a routing > application but found that most of the data in my area is imported from the > Tiger census data. This data does not distinguish between overpasses and > intersections. Some future iteration of the tiger data may include > information about overpasses and underpasses, but for now, every line that > crosses another has a node joining them, even if they are different types of > lines, roads, railways, rivers. This data is in the openstreetmap database > in this same form. > > I suppose one could look at the type of line to keep from routing a car down > a railway, but the under and overpasses look like routable elements when > there is no way to actually traverse them. Has anyone encountered and > solved this? > > > _______________________________________________ > Routing mailing list > Routing@openstreetmap.org > http://lists.openstreetmap.org/listinfo/routing > > _______________________________________________ Routing mailing list Routing@openstreetmap.org http://lists.openstreetmap.org/listinfo/routing
