[OSGeo-Discuss] Data format frustration - too general!

[berryman]

Hello,

I am hope to use GIS for a traffic analysis program that I am involved with. 
After having looked at a couple weeks worth of GIS resources, I still feel
like I haven't found what I'm looking for and it's time to get some human
input.

The main source of my frustration is that all of the standard data formats
seem to be too general for my purpose.  Common formats provide the ability
to encode points, lines, polylines, and polygons (where the locations are
unitless).  But I need the ability to encode the geographic location (e.g.
lat/long, NAD83) of high-level constructs.  For instance, I'm not just
interested in the location of streets, I'm interested in the location of
each lane.  I also need to know how street topology and traffic direction so
that I can make path planning determinations.  Finally, it would even be
ideal if I could encode the location of traffic signals, stop signs,
bus-only lanes, etc.

I know that these types of encoding must exist somewhere , because my Garmin
GPS understands the rules of the streets and can anticipate things coming
up.  For instance, it might tell me "stay in the right lane."  Are there
standard data formats for encoding this information?  Or is the ability to
encode this a non-public extension of some more generic standard?  If so,
then how do I go about extending some other standard for my application?

Thanks all!
-- 
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Data-format-frustration-too-general-tp5370620p5370620.html
Sent from the OSGeo Discuss mailing list archive at Nabble.com.