[pgrouting-users] about use of navteq data
cgalpin at lhsw.com
Fri Jan 7 10:46:01 EST 2011
I am using navteq data and would be happy to help, but I am about to take a week long vacation tomorrow morning so hopefully you are not in a rush.
The short answer is
- assign_vertex does a good job of generating the source/target nodes using 0.00001 for me
- for speed, I found I needed to limit the amount of data presented to the routing engine. One was is to reduce the data set (ie remove/limit the func_class 4 roads you don't need). The other is I create a rectangle around the start and the end point and some percentage of the distance between the points as the width and limit the data to that. The narrower the rectangle the less data the routing engine uses, but if you have large arching roads you have to increase this (I use about 70%). Either way it helps speed up the routing for me.
- For z levels search the archives but both Steven Woodbridge and I posted our versions of a 3d assign_vertex.
I'd be happy to answer any specific questions, and look forward to seeing your progress.
On Jan 7, 2011, at 4:31 AM, Emre Koc wrote:
> I am new to pgRouting and trying to figure out how to use it with navteq data. I used pgRouting with osm data and it worked perfect but for navteq data i tried to use ref_in_id and nref_in_id but it turned out that pgRouting found the path very slow when I used these for source and target. How can I calculate a correct topology for pgRouting by taking z levels into consideration ? Shall define geometry as 3D with z levels embedded or is it possible to use 2d multilinestring with additional z level column ?
> Since I am new to pgRouting these questions are very hard for me to solve, but after I figure out how to use pgRouting I would be more than happy to contribute to project.
> Thanks in advance,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pgrouting-users