[OSM-dev] Chopped of ways. New flag for OSM XML?
jochen at remote.org
Thu Aug 14 15:53:45 BST 2008
On Fri, Aug 15, 2008 at 12:28:14AM +1000, Brett Henderson wrote:
> Karl Newman wrote:
>> On Thu, Aug 14, 2008 at 12:47 AM, Brett Henderson <brett at bretth.com
>> <mailto:brett at bretth.com>> wrote:
>> Jochen Topf wrote:
>> But people *want* to use the data they get from some kind of
>> process to base decisions upon. And they should be able to.
>> Not all the
>> data is invalidated by an extraction, only some of it. It
>> makes sense
>> to mark those parts invalid that are, so that an automated
>> process can
>> decide what it uses and what not.
>> Sure. If I stop mangling ways then I can't think of a particular
>> case where this would be useful for osmosis processing ... but
>> that's not to say one doesn't exist.
>> I'll keep quiet and let those more impacted by the topic resume
>> normal discussions ;-)
>> How about Dave Stubb's new tag transform plugin? And the other example
>> I mentioned, tile cutting, where ways are intentionally mangled to end
>> exactly on the tile border?
> I didn't explain myself very well. In the case of these transform tasks
> you could simply mark the whole file as unsuitable for upload, I
> couldn't see a case where you'd need to know which entities have been
> mangled and which haven't. But again, perhaps I just haven't considered
> a case where it might be useful.
I think its better to mark each individual object as complete or
incomplete. Most of the file is ok, so if you mark the whole file,
people will look at it and say: "That looks ok to me, I'll just go ahead."
If you mark individual objects its clearer where exactly the problem
That beeing said, an *additional* marker at the file level saying: Some
things in this file might be incomplete, might be good.
If you only have the marker at the file level, the file can't be
"cleaned up", because you don't know which data to trust and which not
to trust. If you have markers at all incomplete objects a file is
trivial to clean.
Jochen Topf jochen at remote.org http://www.remote.org/jochen/ +49-721-388298
More information about the dev