[postgis-users] creating topology data is slow
Rémi Cura
remi.cura at gmail.com
Tue Jun 2 12:33:25 PDT 2015
I'm working on a batch way to import topology,
it is not ready yet.
If you now for sure your data is correct, you can skip a lot of testing and
be efficient in a batch way.
You could use grass and the topological export.
Cheers,
Rémi-C
2015-06-02 19:25 GMT+02:00 Marc-André Goderre <magoderre at cgq.qc.ca>:
> Hello all,
>
> I'm creating topology data from almost all world road OSM data ( More than
> 77 Million ways).
>
> Processing the data with postgis topology in one shot is so long than
> that I created a hexagonal grid that let me create topological data from
> only one or many cell of the grid.
>
> Even this way, It' s going to take many month to process the world's data.
>
> Is there a way to make it faster?
>
> This is my function that I use to process data.
>
>
>
> CREATE OR REPLACE FUNCTION cm_update_tile_data(tile_id integer)
>
> RETURNS character varying AS
>
> $BODY$
>
> DECLARE r RECORD;
>
>
>
> BEGIN
>
> FOR r IN SELECT * FROM way, join world_grid on line&& the_geom where
> gid=tile_id and topo_geom is NULL LOOP
>
> BEGIN
>
> UPDATE way
>
> SET topo_geom = topology.toTopoGeom(st_force2d(line), 'way_topo', 1)
>
> WHERE id = r.id;
>
> EXCEPTION
>
> WHEN OTHERS THEN
>
> RAISE WARNING 'Loading of record % failed: %', r.id, SQLERRM;
>
> END;
>
> END LOOP;
>
> UPDATE world_grid set last_update = now() where gid=tile_id;
>
> return 'OK';
>
> END
>
> $BODY$
>
> LANGUAGE plpgsql VOLATILE
>
> COST 100;
>
>
>
> Thanks
>
>
>
> *Marc*
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20150602/4c3839e1/attachment.html>
More information about the postgis-users
mailing list