Since you are in the process of migrating to git, I thought I would
share with you my modification of osm2pgrouting that I use for
www.ridethecity.com.
It adds the following features:
1. Creates and populates a way_tag table, maintaining the 1:N
relationship between ways and tags. The use case for Ride the City is
that sometimes we have to adjust the cost of a way based on the
presence of two or more tags e.g. surface=* and cycleway=*, or
highway=footway and bicycle=yes. This permits more sophisticated cost
calculations.
2. Creates and populates a relations table and a relation_ways table.
Ride the City also needs to be aware of relations for cost
calculations -- mostly as they relate to local, regional and national
bike routes. In the future, we would also want to incorporate turn
restrictions from OSM relations. (Note that the way_id in the
relation_ways table is actually the osm_id of the way -- not the id
that was assigned by osm2pgrouting to the splitted ways.)
3. Adds a new command line parameter called -skipnodes. If this is
set, the program will not load the nodes into the nodes table. This
can be a time-consuming step and is really not crucial for routing
(for us anyway). By default, the nodes table will still be filled as
usual.
Thank you very much!
One of the reasons to move to Git was actually to make it easier for you (and others) to apply changes like you sent me this summer already.
osm2pgrouting was originally written by Daniel Wendt and we offered him to host the source code together with pgRouting.
But it doesn’t belong to the library itself, that’s why I made an extra repository now on GitHub.
I think a lot of users would appreciate if osm2pgrouting would get some improvements. Anton an I don’t have much time to work on it, so we’re happy if anyone is willing to help.
You’re welcome to take the lead with osm2pgrouting. Let me know your GitHub account name. Then I can add you the list of committers.
I think it would be easiest if you could create a branch and apply you changes to the repository yourself. I wouldn’t have the time at the moment to do this.
Since you are in the process of migrating to git, I thought I would
share with you my modification of osm2pgrouting that I use for www.ridethecity.com.
It adds the following features:
Creates and populates a way_tag table, maintaining the 1:N
relationship between ways and tags. The use case for Ride the City is
that sometimes we have to adjust the cost of a way based on the
presence of two or more tags e.g. surface=* and cycleway=*, or
highway=footway and bicycle=yes. This permits more sophisticated cost
calculations.
Creates and populates a relations table and a relation_ways table.
Ride the City also needs to be aware of relations for cost
calculations – mostly as they relate to local, regional and national
bike routes. In the future, we would also want to incorporate turn
restrictions from OSM relations. (Note that the way_id in the
relation_ways table is actually the osm_id of the way – not the id
that was assigned by osm2pgrouting to the splitted ways.)
Adds a new command line parameter called -skipnodes. If this is
set, the program will not load the nodes into the nodes table. This
can be a time-consuming step and is really not crucial for routing
(for us anyway). By default, the nodes table will still be filled as
usual.