Hi Mario,<div><br></div><div>I think there is a lot to cleanup. But if you start with devel-2_0 branch probably some work has been done already.</div><div>The MULTILINESTRING probably come from pgDijkstra already. I think MULTILINESTRING is the default geometry type when you run shp2pgsql. </div>
<div><br></div><div>I sent your previous post to the list also to Carsten, the author of osm2po, and he will care about it, he said. It's better (and also correct IMO) to require LINESTRING as geometry type. PostGIS 2.0 also provides topology functions. It's better to be more strict with this geometry stuff.</div>
<div>I'm not sure how difficult it is to change the geometry type of a geometry column, but for a routing network we can (must) assume that all features are LINESTRING. Maybe we can provide a function or script to transform MULTILINESTRING routing tables to LINESTRING.</div>
<div><br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Actually I find this inconsistent since some sql files get the srid<br>
via the above method while others it gets it from the geometry_column<br>
metadata table. Either or is fine though except the latter assumes a<br>
'the_geom' geometry column.<br></blockquote><div><br></div><div>I don't know which is better ... </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
osm2po names its geometry column as 'geom_way' so there is a renaming<br>
that has to be done.<br></blockquote><div><br></div><div>You can just modify the "PgRoutingWriter" plugin:</div><div><a href="https://github.com/pgRouting/pgrouting-contrib/blob/master/plugin-osm2po/PgRoutingWriter.java">https://github.com/pgRouting/pgrouting-contrib/blob/master/plugin-osm2po/PgRoutingWriter.java</a></div>
<div><br></div><div>Usually I renamed the columns as I need them with a VIEW.</div><div><br></div><div><br></div><div>Btw, if you're already looking through the source files, another issues that might not be consistent, is support for "schema".</div>
<div>When I installed PostGIS 2.0 recently I saw that there is a "topology" schema that contains all functions. So it's very easy to maintain, drop and update. I like it and it could be nice to have a "pgrouting" schema as well.</div>
<div>Then we don't need something like this: <a href="https://github.com/pgRouting/pgrouting/pull/40">https://github.com/pgRouting/pgrouting/pull/40</a></div><div><br></div><div>Daniel</div><div><br></div><div><br></div>
<div><br></div></div><div><br></div>-- <br><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse">Georepublic UG & Georepublic Japan<br>eMail: <a href="mailto:daniel.kastl@georepublic.de" style="color:rgb(66,99,171)" target="_blank">daniel.kastl@georepublic.de</a><br>
Web: <a href="http://georepublic.de/" style="color:rgb(66,99,171)" target="_blank">http://georepublic.de</a></span><br>
</div>