[OSM-talk] Wanted feature for API 0.7 ??

[Dave Stubbs]

2009/6/8 Peter Dörrie <peter.doerrie at googlemail.com>:
>
>>
>> as frederik says, it doesn't need to be implemented in the API - all
>> of it can already be done client-side using the appropriate tags*.
>
> Well several Users made the point that this would "break" all applications
> that exist today, as they would be useless in their current state. The
> current JOSM for example would not be able to make out the difference
> between "planned" , "constructed", "live", "disused" and "historic" objects,
> leading to a cluttering of the interface and inflation of the data-amounts.
> The current renderes wouldn't be able to handle it either and forcing 50+
> applications to change would be unappropriate.
>


Which just tells you those aren't the "appropriate tags" of which matt speaks.

Careful selection of tags means that nothing existing needs to change,
unless it's to make life easier for the user by adding filtering
features.

Dave