[osmosis-dev] Announcement of the OSMbin file-format

[marcus.wolschon at googlemail.com]

On Thu, 05 Feb 2009 00:02:37 +1100, Brett Henderson <brett at bretth.com>
wrote:
> Good stuff!
> 
> I'd like to play with the dataset support in particular.  A persistence 
> mechanisms that doesn't rely on a full database would be very useful.  
>  From your docs on the Osmosis/DetailedUsage page it looks like you 
> don't have full dataset support yet.  Is that something you plan to add?

Yes I do.
Random access is already working but streaming access is not implemented
yet.
I am still thinking about how to
create a ReleasableIterator that can return all nodes AND ways AND
relations.

Also the reading of a bounding-box is still memory-bound as I need to
know all nodes to know what ways and relations to return. And I need
to keep note on what ways/relations I have already returned to not return
them twice.
Any hints where in osmosis I may look? I guess you had to do similar
bookkeeping in other tasks already.

(For the benefit of the other readers:)
This is only an issue with the unfinished "--dataset-osmbin-0.6" -task
and does not affect the "--write-osmbin-0.6" -task in Osmosis.


> There are so many OSM toys to play with these days I don't know where to 
> begin ...
> 
> Looking at the Osmosis/DetailedUsage wiki page there might be a few 
> typos.  I haven't fixed them because I'm not 100% sure how the tasks
work.
> * The --read-osmbin task says "Write to a directory ...".  I assume it 
> should be reading instead.

Done.

> * The --dataset-osmbin task also says "Write to a directory ...".  If 
> it's the same as other dataset tasks it would be read-only.

It implementes Datasetsink, so It writes and reads.

> * The --dataset-osmbin task has inPipe.0 consuming an entity stream.  
> Should it be producing a dataset?

As a Datasetsink it consumes one stream and produces one dataset.

> * The --read-osmbin task has inPipe.0 but I assume it should be
outPipe.0.

Done



Marcus