[Imports] Birmingham City Council tree import

[Martin Koppenhoefer]

sent from a phone

> On 12. May 2017, at 14:29, Brian Prangle <brianboruimport at gmail.com> wrote:
> 
> Example imported tree
> 
> http://www.openstreetmap.org/node/4721553869
> 
> natural=tree
> source=bcc_dec_2016
> form=Natural
> age=New Planting
> height=2 to 2.99m
> species=Liquidambar styraciflua 'Worpl
> usrn=2701986
> plot_number=110007
> site_name=LUDGATE HILL
> ward=Ladywood
> constituency=City Centre


You have introduced a lot of new tags with this import and used others in a way that could be questioned:

- source tags usually should go on the changeset 

- form is not an established key, it seems there is no docu about it, not even a proposal. Capitalized values are not common for formal values.

- age is only used for kindergartens so far, and the established tags are min_age and max_age. Again there is no proposal for it, there is a capitalized formal value, and it remains unclear when "new" was.
Are you going to update these age tags frequently? Otherwise I'd suggest a date based system. An established tag for this is start_date.

- height is not a value but a range of values.

- what is usrn? Usually we don't use abbreviations in tags. 

- the address tags are not the established kind with addr:* or is_in. Generally I'm not sure whether you should add them, your local community even decided to not import administrative boundaries, why would they want to import derivative point data?


Cheers,
Martin 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20170513/90d5629e/attachment.html>