> - nodes : with the lat and lng points, category of the road (extracted > from the osm file) and possible other info like elevation that i would > get from other sources
Do you need the road category on the nodes? However, this shouldn't be a big problem > - edges : this would ideally have the from_node to_node fields, > direction (oneway or both) road category, length and road name. Only road name is missing. > - an edges_nodes: this would have a field that identifies the edge. > Also, a from_node and to_node fields that would describe the points that > link the start and end nodes of the edge. I'm not sure to understand this table. If you want the nodes of an edge for a smooth display (but absolutely no influence on routing), I currently keep the coordinates as a text string in the edges table. > As I said i'm starting this work and for what i have read so far this > would be enough information for a routing algorithm to run. Just for routing, the edges tables would actually be enough > Do you have any suggestions on how i could build this tables or at least > export the data to a csv file in excel? Your tool only works in Linux > right? I'm thinking about building a parser myself to do this but i > thought something like this would already be available. Currently csv is a possible output. My tool is opensource and it depends on libs that exist under windows. So you should be able to compile by yourself. _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
