Re: [OSM-dev] osm2pgsql and bbox imports

2012-10-15 Thread Peter Wendorff
Danke. Ich hab wohl zu wenig imports bisher durchgeführt und hatte das einfach als gegeben hingenommen ;) Danke fürs untersuchen und dokumentieren. Gruß Peter Am 15.10.2012 00:11, schrieb Stephan Knauss: On 12.10.2012 18:38, Peter Wendorff wrote: Am 12.10.2012 18:12, schrieb Stephan Knauss:

Re: [OSM-dev] osm2pgsql and bbox imports

2012-10-14 Thread Stephan Knauss
On 12.10.2012 18:38, Peter Wendorff wrote: Am 12.10.2012 18:12, schrieb Stephan Knauss: Peter Wendorff writes: osm2pgsql has to store nodes outside the bbox because geometries that overlap the borders etc. should be included in the result, too. how certain are you regarding this? It's only

[OSM-dev] osm2pgsql and bbox imports

2012-10-12 Thread Stephan Knauss
Hi, I'm doing a slim mode bbox import for rendering. What is supposed to be in the planet_osm_nodes table? All nodes of my import source file or only the nodes contained in the bbox? I used this bbox: --bbox 97.3,5.6,109.6,23.4 and planet_osm_nodes contains for example this: id;lat;lon

Re: [OSM-dev] osm2pgsql and bbox imports

2012-10-12 Thread Peter Wendorff
Hi Stephan. osm2pgsql has to store nodes outside the bbox because geometries that overlap the borders etc. should be included in the result, too. If osm2pgsql would skip nodes outside while parsing nodes, but before parsing the more complex geometries (ways, relations), these nodes would be

Re: [OSM-dev] osm2pgsql and bbox imports

2012-10-12 Thread Stephan Knauss
Peter Wendorff writes: osm2pgsql has to store nodes outside the bbox because geometries that overlap the borders etc. should be included in the result, too. depends on the cutting algorithm used. I could live with osm2pgsql doing a hard cut as I made my bbox large enough to have some buffer.

Re: [OSM-dev] osm2pgsql and bbox imports

2012-10-12 Thread Lynn W. Deffenbaugh (Mr)
I recently switched to --flat-nodes on my osm2pgsql import and am pleasantly impressed with the improved update speed. Of course, I had to re-create the database and re-import the plane, to make the switch, but I was going to the new license and 64bit IDs at the same time, so all was well.

Re: [OSM-dev] osm2pgsql and bbox imports

2012-10-12 Thread Stephan Knauss
Peter Wendorff writes: osm2pgsql has to store nodes outside the bbox because geometries that overlap the borders etc. should be included in the result, too. how certain are you regarding this? in parse-primitive.c::EndElement() I see a call to node_wanted() which only returns true if the

Re: [OSM-dev] osm2pgsql and bbox imports

2012-10-12 Thread Peter Wendorff
Am 12.10.2012 18:12, schrieb Stephan Knauss: Peter Wendorff writes: osm2pgsql has to store nodes outside the bbox because geometries that overlap the borders etc. should be included in the result, too. how certain are you regarding this? It's only based on my observations and short comments