[osmosis-dev] API 0.6 and unique keys

[marcus.wolschon at googlemail.com]

On Thu, 29 Jan 2009 22:01:08 +1100, Brett Henderson <brett at bretth.com>
wrote:
> Actually I misread your initial email.  I thought you wanted to replace 
> the current Collection of Tags with a Map of Tags keyed by the name.  I 
> didn't realise you wanted to replace Tag entirely although I should have 
> realised because you'd suggested it once before.  Having thought about 
> this some more I'm getting more uncomfortable with it.

That's fine with me.
It was just a suggestion.

> rubbish) but I think it's worth seriously considering.  Add support for 
> a new type of entity to the pipeline (probably as a plugin ...).  Create 
> a new set of entity types that look exactly how you want them to look.  
> They can store tags as Maps, add extra optional fields such as way 
> geometries, and anything else that you wish to experiment with.  Create 
> a new Sink and Source interface that deals with those types, and new 
> Manager objects (such as SinkManager, SourceSinkManager, 
> RunnableSourceManager, etc) to deal with them.  Then write two tasks to 
> convert from existing entities to the super entities and back again.  At 

Sounds interesting.
I may write 2 such tasks after I got my version 1.0 rolled out.
At the moment I have support for Nodes and Ways being a special
subclass in my own code and they contain WayIDs and RelationIDs
of ways/relations referencing the given object (this is code that
is only usefull for myself in my own application.). I guess I
could refactor things on my end to not use your entity-classes
at all and have 2 converter-tasks at the points where I use
osmosis-tasks for file-loading and area-downloads.
It will require some adaption in the little used database-code
where I interface with osmosis-code too but that yould be managable.

Marcus