<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In the osm2pgrouting source :<br>
<a href="https://github.com/pgRouting/osm2pgrouting/blob/master/src/Export2DB.cpp#L372" target="_blank">https://github.com/pgRouting/osm2pgrouting/blob/master/src/Export2DB.cpp#L372</a><br>
<br>
But the vertices_tmp table remains empty. When running manually SELECT<br>
assign_vertex_id('ways', 0.00001, 'the_geom', 'gid'); I get this :<br>
<br>
NOTICE: CREATE TABLE will create implicit sequence<br>
"vertices_tmp_id_seq" for serial column "<a href="http://vertices_tmp.id" target="_blank">vertices_tmp.id</a>"<br>
CONTEXT: SQL statement "CREATE TABLE vertices_tmp (id serial)"<br>
PL/pgSQL function "assign_vertex_id" line 15 at EXECUTE statement<br>
ERROR: query string argument of EXECUTE is null<br>
CONTEXT: PL/pgSQL function "assign_vertex_id" line 33 at EXECUTE statement<br>
<br>
My "ways" table is in MultiLineString geometry type. Could the problem<br>
come from that ?<br></blockquote><div><br></div><div>Yes, osm2pgrouting creates geometries as "MULTILINESTRING" which is not working anymore with functions like "ST_StartPoint" and ST_EndPoint" in PostGIS 2.0.</div>
<div>Legacy.sql doesn't seem to help here.</div><div><br></div><div>I found out that source and target column remain empty therefor. Best would be to change osm2pgrouting and recompile.</div><div>In case you use the Ubuntu package and don't want to compile, you can alter the geometry type to LINESTRING (I don't think there is any MULTILINESTRING consisting of two lines created) and run assign_vertex_id manually once more.</div>
<div><br></div><div>Daniel</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></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>
Frédéric Bonifas<br>
<br>
2013/3/18 Stephen Woodbridge <<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>>:<br>
<div class="HOEnZb"><div class="h5">> On 3/18/2013 10:48 AM, Frédéric Bonifas wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> I have built PgRouting from the sew-devel-2_0 branch. I am using<br>
>> Postgis 2.0 and PostgreSql 9.1.8<br>
>><br>
>> I have created a database "routing" and created the postgis and<br>
>> pgrouting extensions on it :<br>
>> createdb routing<br>
>> createlang plpgsql routing<br>
><br>
><br>
> You can use "CREATE EXTENSION plpgsql" but I'm not sure it is even needed.<br>
><br>
><br>
>> psql -d routing -c "CREATE EXTENSION postgis;"<br>
>> psql -d routing -c "CREATE EXTENSION pgrouting;"<br>
>><br>
>> I did not run the following lines because I assume that "CREATE<br>
>> EXTENSION pgrouting;" does that but I may be wrong. Anyway, the<br>
>> /usr/share/postlbs/ directory is empty.<br>
>> psql -d routing -f /usr/share/postlbs/routing_core.sql<br>
>> psql -d routing -f /usr/share/postlbs/routing_core_wrappers.sql<br>
>> psql -d routing -f /usr/share/postlbs/routing_topology.sql<br>
><br>
><br>
> Right when you install an extension it loads all the files as part of the<br>
> extension. And I do not install files in /usr/share/postlbs The extension<br>
> installs share/postgresql/extension/pgrouting--1.0.7.sql which contains all<br>
> the SQL concatenated into one file.<br>
><br>
> One problem with the current setup is that tsp and dd are optional and as a<br>
> result probably need to be broken out into separate extensions, but that<br>
> should not be a problem for now.<br>
><br>
><br>
>> Then I run osm2pgrouting, from the georepublic ppa.<br>
>> osm2pgrouting -file "data.osm" -conf<br>
>> "/usr/share/osm2pgrouting/mapconfig.xml" -host localhost -dbname<br>
>> routing -user postgres -clean<br>
>><br>
>> osm2pgrouting seems the end coorectly as I got :<br>
>> size of streets: 41<br>
>> size of splitted ways : 469<br>
>> finished<br>
>><br>
>> But while the "nodes" table is correctly filled, the "ways" and<br>
>> "vertices_tmp" tables remain empty. I suspect this might be related to<br>
>> routing_core.sql, routing_core_wrappers.sql and routing_topology.sql<br>
>> that I did not run.<br>
>> Does someone know what I am doing wrong ?<br>
><br>
><br>
> A couple of thoughts here:<br>
><br>
> 1. you have to run the topology command assign_vertex_id(), which I have<br>
> never used as I wrote my own a long time ago.<br>
><br>
> 2. You might (most likely) will need to load legacy.sql from postgis until I<br>
> have had a chance to review, update and test all the sql code for<br>
> compatibility with postgis 2.x<br>
><br>
><br>
> Thank you for stepping on on the bleed edge and testing this. I look forward<br>
> to here about your success and failures. Hopefully more success than<br>
> failures :)<br>
><br>
> -Steve<br>
><br>
>> Thanks in advance<br>
>><br>
><br>
> _______________________________________________<br>
> Pgrouting-users mailing list<br>
> <a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
<br>
<br>
<br>
</div></div><div class="im HOEnZb">--<br>
Frédéric Bonifas<br>
<a href="tel:%2B33672652807" value="+33672652807">+33672652807</a> skype:fredericbonifas<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
</div></div></blockquote></div><br><br clear="all"><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>