Upon running netconvert on a given OSM-retrieved bounding box / geographical area, SUMO does a great job of converting it into a usable road network.
However, I need to do some pretty heavy post-processing of the XML file(s) themselves (not using python), including, for example, the routing file and the floating car data FCD file. The definition of lanes in sumo <http://sumo.dlr.de/wiki/Networks/SUMO_Road_Networks#Lanes> seems pretty straight forward--the first sequence of numbers indicates the edge/way/road, and the number after an underscore indicates the lane id, starting at the right-most lane. However upon close inspection, I've had trouble identifying the exact semantics of each attribute associated with a lane id. For example, I typically come across the following types of lanes in either the FCD output file format: -21373823#1_0 485925832#2_0 229800762_0_0 444985371_0 :cluster_230036451_3844062512_0_0 :cluster_4424562773_4551197076_4551197077_3_0 I'm aware the ':' prefix indicates an internal lane, where such lanes are of the form <NODE_ID>_<EDGE_ID>, however the semantics of the other types elude me. >From reading online, I've gathered that the first number after the '#' is sometimes used to indicate the lane id as well as when there's an underscore, making them seem interchangeable, but what is the second number? Direction, where 0 is north? I assume a cluster is formed from attempting to join edges from OSM? And what does the minus sign indicate at the beginning of the edge id? -- Matt Piekenbrock Graduate Research Assistant - WSU / Kno.e.sis WaCS lab Email: [email protected], [email protected] Cell: (937) 269-8582 Web Page: mattpiekenbrock.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
