Hey gang. I’ve been working on text-based (turn by turn) driving directions. I noticed a couple days ago that OSM data stores information about motorway junctions in the node tags… things like junction reference and exit text, which would allow me to add more detail to the directions (ie, “take exit 1A towards yada…”). I modified osm2pgrouting to pull this data so I could apply it to the ways, but it’s not working out very well so far. It’s probably a flaw in my logic, so I wanted to run it by you guys. Right now, when the ways are being split I checkall the nodes to see if one is a junction, and I check the way to see if it’s a motorway_link and if they are I populate the two columns I added to ways: junction_reference and exit_text. Then, when constructing the directions, if I have either of these I can print “take exit” instead of “turn right” or whatever.
It doesn’t seem to be populating the data for all the appropriate ways. Do you see any flaws in the way I’m approaching this?
Thanks,
JD
Hi
Sounds good.
I create a separate "crossing table" for that.
Since I store all kinds off crossing "attributes
e.g. roundabout enter and exit, crossing lights a.s.o.
This table is popoulated after parsing in a separate
postprocessing step.
It contains the crossing node as the key and all the
needed attributes.
When calculating a route the attributes are assigned
by following the calculated route over all its crossings
They can then be used for e.g. route description
or displaying on a map.
I dont use osm2pgrouting because I use a sqlite DB
and a "selfmade" osm parser.
Can you idenitfy under wich circumstances the data
is not in the table as expected? Are you sure all the
"motorway junction" data is already added when you try
to assing it to the ways?
Regards
max
On Sat, 26 May 2012 14:19:30 -0500
John Williams <jdwilliams1982@gmail.com> wrote:
Hey gang. I've been working on text-based (turn by turn) driving
directions. I noticed a couple days ago that OSM data stores
information about motorway junctions in the node tags... things like
junction reference and exit text, which would allow me to add more
detail to the directions (ie, "take exit 1A towards yada..."). I
modified osm2pgrouting to pull this data so I could apply it to the
ways, but it's not working out very well so far. It's probably a flaw
in my logic, so I wanted to run it by you guys. Right now, when the
ways are being split I checkall the nodes to see if one is a
junction, and I check the way to see if it's a motorway_link and if
they are I populate the two columns I added to ways:
junction_reference and exit_text. Then, when constructing the
directions, if I have either of these I can print "take exit" instead
of "turn right" or whatever.
It doesn't seem to be populating the data for all the appropriate
ways. Do you see any flaws in the way I'm approaching this?
Thanks,
JD