Hi Dominik,
thanks for your detailed explanations. Great to hear you were able to
reproduce it and that you plan to address this issue.
well, if someone will actually commit my upcoming patch, that is ;) I'll
try my best.
I think your line of thought here sounds good.
thanks, that's good to know :)
I am not sure whether other tools like the tile splitter need a
bounding box or whether they can recreate it themselves. So in that
sense, I am not sure whether "throwing away any bounds" is safe.
It's at least safer than writing out a wrong one...
A command line option to throw away and recompute the bounds would be
good in some cases, to be on the safe side. I have no idea how
expensive it is to recalculate. If it's put to the documentation that
this is an expensive process, it could still be useful in some
cases.
IMHO if we want to do this, it should be a separate task like
"--compute-bounding-box". It could be an use case in its own right,
after all. So I'd leave the recomputation out of the merge stuff.
You will know better about any implications or complexity of
implementation. You may consider this rather a wish list. Any quick
fix would already be great,
I'll see what I can do - it's great to have that much input from the
users :) Thanks!
Greetings
Igor
_______________________________________________
osmosis-dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/osmosis-dev
