[osmosis-dev] Switch to API 0.6 and interfaces

marcus.wolschon at googlemail.com marcus.wolschon at googlemail.com
Tue Jan 27 06:51:39 GMT 2009


Hello everyone,

I am currently trying to switch the codebase of Traveling Salesman
to API 0.6 and since I need to change all the v0_5 to v0_6 I was
wondering if there was any reason we could not have an interface
Node/Way/Relation and V5Node/V6Node, ...
90% of the code does not care about the version but:
* much code is dublicated and
* replacing the entity-classes requires you to copy all of
  the planet when piping your own implementations of entity-classes
  into or out of osmosis-tasks. (e.g. exporting map-data, downloading,...)

So... how is everyone thinking about having an interface
v0_6.Node/Relation/Way and maybe even have the v0_6.Node
extend the interface v0_5.Node to ease the transition.
Since a v0.6-node has everything a v0.5-node has with unchanged
semantics. The only thing that changed was to add version-numbers
and make relation-members ordered (But any ordered list implicitely
still has the semantic of the v0.5 unordered, unmodifiable list).

Marcus




More information about the osmosis-dev mailing list