[pgrouting-dev] OSM processing erases some nodes?

Hi, guys.

Simple question. Can anyone tell me if the osm2pgrouting procedure removes any nodes from the osm when processing the OSM file, i.e., does it cut nodes that may be uninteresting?

I calculated a route with Dijkstra, but when I plot it on a map, there are some nodes missing, i.e., the route does not always follow the road.

Thanks in advance. Best,

Paulo Figueiras <paf@uninova.pt>



cid:image002.jpg@01C8AEC7.2F6E45A0







UNINOVA, Centre of Technology and Systems
Campus da Caparica, Quinta da Torre
2829-516 Monte Caparica, PORTUGAL

Phone: (+351) 212948312 | Fax: (+351) 212957786 | Website: http://www.uninova.pt/

Hello Sir ,

I too have the same problem when I developed a web application few months back. I loaded the data using osm2pgrouting & used pgDijkstra Algorithm to get the route. I have attached screenshots of that errors. But when I load this using QGIS its showing perfectly. So I thought data which is in database is perfect and there is some error with my application. Am I right :?

Regards

Manikanta

B.Tech & MS in Computer Science,

Lab for Spatial Informatics,

IIIT Hyderabad

image001.jpg

xyz.jpg

···

On Wed, Jan 29, 2014 at 11:03 PM, Paulo Figueiras <paf@uninova.pt> wrote:

Hi, guys.

Simple question. Can anyone tell me if the osm2pgrouting procedure removes any nodes from the osm when processing the OSM file, i.e., does it cut nodes that may be uninteresting?

I calculated a route with Dijkstra, but when I plot it on a map, there are some nodes missing, i.e., the route does not always follow the road.

Thanks in advance. Best,

Paulo Figueiras <paf@uninova.pt>



cid:image002.jpg@01C8AEC7.2F6E45A0







UNINOVA, Centre of Technology and Systems
Campus da Caparica, Quinta da Torre
2829-516 Monte Caparica, PORTUGAL

Phone: (+351) 212948312 | Fax: (+351) 212957786 | Website: http://www.uninova.pt/


pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev

On Thu, Jan 30, 2014 at 3:48 AM, Manikanta Kondeti
<mani.iiit123@gmail.com>wrote:

Hello Sir ,

            I too have the same problem when I developed a web application
few months back. I loaded the data using osm2pgrouting & used pgDijkstra
Algorithm to get the route. I have attached screenshots of that errors.
But when I load this using QGIS its showing perfectly. So I thought data
which is in database is perfect and there is some error with my
application. Am I right :?

Regards

Manikanta

B.Tech & MS in Computer Science,

Lab for Spatial Informatics,
IIIT Hyderabad

On Wed, Jan 29, 2014 at 11:03 PM, Paulo Figueiras <paf@uninova.pt> wrote:

Hi, guys.

Simple question. Can anyone tell me if the osm2pgrouting procedure
removes any nodes from the osm when processing the OSM file, i.e., does it
cut nodes that may be uninteresting?

I calculated a route with Dijkstra, but when I plot it on a map, there
are some nodes missing, i.e., the route does not always follow the road.

osm2pgrouting ignores OSM tags, which are not specified in the
configuration file:
https://github.com/pgRouting/osm2pgrouting/blob/master/mapconfig.xml

Not sure this is the problem though, but might be.

Daniel

--
Georepublic UG & Georepublic Japan
eMail: daniel.kastl@georepublic.de
Web: http://georepublic.de

Hello Daniel, Manikandra.

image001.jpg

···

I’m quite sure that’s not the problem, because I had to complete your configuration file (mapconfig.xml) to not only catch all the highway and road types (for car, walking, bike), but I also added the train and subway tags, all corresponding to OSM WAYS.

I tried several routing engines, and most of them do some kind of pre-processing of the OSM nodes and ways, in order to cut off groups of nodes, for instance, because they form a straight line, and there is no need to have a way with so many nodes. This node cleansing also aids in terms of performance.

Do you perform any kind of node cleansing in your algorithms? I think not, but I wanted to make sure :slight_smile:

I noticed that, when running osm2pgrouting, the algorithm divides OSM ways that have more than one OSM node into several arcs, or individual ways, with only two nodes, so probably it is not cutting the nodes.

Maybe the way I used to check the route was not the greatest ever :slight_smile: I did a query to get all y1,x1 coordinates of the edges resulting from a Dijkstra’s route. Then, I copied the coordinates in GPX format into http://openrouteservice.org/ and checked the result.

When inside cities, the route is always on the road, but when the route continues to highways and motorways between urban agglomerates, the route off the road issue starts to be more frequent.

Do you have any ideas on this? Is it my fault :slight_smile: ?

Thanks in advance. Cheers,

Paulo Figueiras <paf@uninova.pt>



cid:image002.jpg@01C8AEC7.2F6E45A0







UNINOVA, Centre of Technology and Systems
Campus da Caparica, Quinta da Torre
2829-516 Monte Caparica, PORTUGAL

Phone: (+351) 212948312 | Fax: (+351) 212957786 | Website: http://www.uninova.pt/

osm2pgrouting ignores OSM tags, which are not specified in the configuration file: https://github.com/pgRouting/osm2pgrouting/blob/master/mapconfig.xml

Not sure this is the problem though, but might be.