[osmosis-dev] Announcement of the OSMbin file-format
marcus.wolschon at googlemail.com
marcus.wolschon at googlemail.com
Thu Feb 5 07:45:02 GMT 2009
Hello Brett.
I just implemented the --read-osmbin-0.6 without support for
bounding-boxes.
I need to test it but it should work.
So I can implement the method to get all nodes+ways+relations with no
bounding-box of --dataset-osmbin-0.6 and will have a look at the
classes you mentioned to implement the bounding-box -version later.
Marcus
>> Look at the IdTracker interface (core.filter.common) and see how it's
>> used in the AreaFilter task (core.filter.v0_6).
> Another class to checkout is
> org.openstreetmap.osmosis.core.customdb.v0_6.impl.DatasetStoreReader
> which provides the dataset implementation for my customdb storage. It
> inherits much of its functionality from
> org.openstreetmap.osmosis.core.filter.v0_6.impl.BaseDatasetReader (I
> don't know why I put it in that package ...). As Karl suggests it uses
> IdTracker instances to keep track of all the ids in the bbox. The
> customdb storage uses a quadtile mechanism for identifying nodes, and
> either quadtiles or node_way relations to identify ways. That side
> worked reasonably well from memory. The real performance problems with
> it came when trying to stream out the data associated with the ids.
> Pulling out the data associated with each id required a lot of disk
> seeking which never performed well. I'm hoping that the osmbin
> implementation will work better there.
>
> Brett
>
More information about the osmosis-dev
mailing list