Hi Frederik,
On Fri, Feb 18, 2011 at 7:57 PM, Frederik Ramm frede...@remote.org wrote:
But I've been thinking: With the the high performance of PBF reading, a
two-pass operation should become possible. Simply read the input file twice,
determining which objects to copy in pass 1, and actually
Igor,
On 02/18/11 11:40, Igor Podolskiy wrote:
just a random thought: what's wrong with using --dataset-bounding-box?
Importing the planet file into a database and doing a bunch of queries
against is equivalent to creating a single disk buffer for all bb tasks
(the database _is_ the disk
Am 18.02.11 12:20, schrieb Frederik Ramm:
ataset-bounding-polygon task for that but that should be possible.
The major problem is finding a database that would be able to import the
data, index it, and fulfil my requests, all within less than 24 hours.
From what I hear, PostGIS takes a week
On Fri, Feb 18, 2011 at 10:20 PM, Frederik Ramm frede...@remote.org wrote:
Igor,
On 02/18/11 11:40, Igor Podolskiy wrote:
just a random thought: what's wrong with using --dataset-bounding-box?
Importing the planet file into a database and doing a bunch of queries
against is equivalent to
Scott,
On 02/18/11 14:15, Scott Crosby wrote:
I used two bitsets for every output file. One indicating which nodes
were already output and another (built when processing ways)
indicating what node ID's were missed and will need to be grabbed on
the next pass. I have another two pair of bitsets
On 2/18/2011 7:24 AM, Frederik Ramm wrote:
Provided that applying a minutely diff (possily even while the
extraction requests are running) does indeed take less than a minute.
Which, I repeat myself, I believe to be unlikely.
Frederik, André,
I have been playing with this lately on a
