[pgrouting-users] about use of navteq data

[Stephen Woodbridge]

He may have read that I did something like this. I hacked up a version 
of assign_vertex where I stuffed the zlevel of the node into the z value 
of the coordinated, so point(x, y, zlevel) and then computed the 
distance_3d() or whatever the function is called in postgis when 
comparing the vertices. This seems to work fine.

I have attached my sql functions. Feel free to modify this and add it to 
pgRouting as appropriate.

-Steve

On 1/21/2011 6:24 AM, Daniel Kastl wrote:
>
>
> 2011/1/21 Paolo Lubrano <paolo.lubrano at inwind.it
> <mailto:paolo.lubrano at inwind.it>>
>
>     Hi all, hi Charles,
>
>     actually I'm working on a pgrouting graph built on TeleAtlas
>     Multinet data.
>
>     I have problems with Z level, because two streets on different
>     levels are considered as parts of crossroad.
>
>     To explane better my problem this are the data of my network table:
>
>
>     name                             source      target
>     Tangenziale di Napoli    402837    413133
>     Via Giustiniano              402837    388759
>
>
>     I built the graph with assign_vertex function, I have read about a
>     new 3d version but I didn't found anything, where can I get it?
>
>
>
> You read this about PostGIS?
> pgRouting doesn't have a special support for 3D (Dijkstra algorithm even
> doesn't need geometry information).
> If you have two roads crossing each other sharing a node, but they
> actually shouldn't be connected, because they have different z-levels,
> then there shouldn't be shared node. Then the network topology isn't
> correct.
>
> If assign_vertex function produced this topology, then it would be good
> to think about how to identify such a case and add z-level support to
> assign_function. Maybe some extended assign_vertex function could check
> if the road segments are in the same z-level.
>
> Because you're using TeleAtlas data, are you sure you have to build a
> network topology? Doesn't TeleAtlas already contain such an information?
> If you need to run assign_vertex and your data is of good quality, you
> could make the "snapping" tolerance parameter very very slow. But this
> won't help if in your case both roads share exactly the same node.
>
> Daniel
>
>
>
>
>     Thank you very much!
>
>     Paolo
>
>
>     _______________________________________________
>     Pgrouting-users mailing list
>     Pgrouting-users at lists.osgeo.org <mailto:Pgrouting-users at lists.osgeo.org>
>     http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>
>
>
>
> --
> Georepublic UG & Georepublic Japan
> eMail: daniel.kastl at georepublic.de <mailto:daniel.kastl at georepublic.de>
> Web: http://georepublic.de <http://georepublic.de/>
>
>
>
> _______________________________________________
> Pgrouting-users mailing list
> Pgrouting-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: reassign-vertix-ids-3d.sql
Type: text\plain
Size: 8462 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/pgrouting-users/attachments/20110121/80dbc80f/reassign-vertix-ids-3d.pl