[osmosis-dev] planet import time

Hello, how much time does an import of the whole OSM planet into a PostgreSQL/PostGIS database, including bbox and linestrings, require on modern hardware? Osmosis seems to get stuck at computing bounding boxes, i.e. this query: UPDATE ways SET bbox = (SELECT Envelope(Collect(geom)) FROM

Re: [osmosis-dev] planet import time

Hello, Frederik Ramm schrieb: Jens, Jens Lehmann wrote: UPDATE ways SET bbox = (SELECT Envelope(Collect(geom)) FROM nodes JOIN way_nodes ON way_nodes.node_id = nodes.id WHERE way_nodes.way_id = ways.id) How long will this query take? Is there a way to monitor its progress? Why isn't

Re: [osmosis-dev] planet import time

Hi, Jens Lehmann wrote: A solution would be to include it in the planet or provide it as a separate file, which can be loaded into the database. Well it isn't even in our central database so it would have to be computed at the time we dump the planet file which already is an expensive

[osmosis-dev] Osmosis34 JDBC Connection Error

When i use --read-apidb i get following error Could not open JDBC connection for transaction. How can i fix this. ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev

[OSM-dev] OSM - POI files?

Is there some application that extracts a list of POIs from an OSM file, e.g. as GPX or whatever? It would need to collapse each polygon down into one central point, so that the output is just a list of points. ___ dev mailing list

Re: [OSM-dev] OSM - POI files?

I have some script I use to get the POIs from the Romanian extract and create a SQL query. Unfortunately the code needs some cleanup and most of the comments are in Romanian, but it might help you: http://github.com/cipt2001/OpenMap.ro/blob/master/update_scripts/generate-pois.py --Ciprian On