[Imports] Birmingham City Council tree import

Brian Prangle brianboruimport at gmail.com
Mon May 15 11:11:18 UTC 2017


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
*This is news to me - there are currently over 5 million instances of this
tag in the UK*

- 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.
Is this a problem? *Not aware that using a tag requires all this.  If it's
a problem then I can substitute tree_form which is more explicit*

- 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. *Not aware
that in order to use a tag there has to be a proposal. The use and content
of age as data seems pretty self-explanatory.*
* The source tag contains the date of the data so the age can be related to
that, so "new" and all other values are current at the source of the data:
dec 2016. Could I also suggest that the age tag for kindergartens as you
describe it doesn't relate to the object tagged but to the children
attending?*
Are you going to update these age tags frequently? * Already addressed in
the original post - we can only update as frequently as the data owner
refreshes the published data. *
Otherwise I'd suggest a date based system. An established tag for this is
start_date. *Good idea but we don't have this data*

- height is not a value but a range of values. *Already addressed in the
original post with a proposal to improve this*

- what is usrn? Usually we don't use abbreviations in tags.  *Already
explained in the original post: Unique Street Reference Number. Suggestions
have been to use ref:usrn*

- 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?* see reply from Colin Smale*


On Sat, May 13, 2017 at 10:30 PM, Martin Koppenhoefer <
dieterdreist at gmail.com> wrote:

>
>
> 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 <https://wiki.openstreetmap.org/wiki/Key:natural>=tree
> <https://wiki.openstreetmap.org/wiki/Tag:natural%3Dtree>source
> <https://wiki.openstreetmap.org/wiki/Key:source>=bcc_dec_2016form
> <https://wiki.openstreetmap.org/w/index.php?title=Key:form&action=edit&redlink=1>
> =Naturalage
> <https://wiki.openstreetmap.org/w/index.php?title=Key:age&action=edit&redlink=1>=New
> Plantingheight <https://wiki.openstreetmap.org/wiki/Key:height>=2 to 2.99m
> species <https://wiki.openstreetmap.org/wiki/Key:species>=Liquidambar
> styraciflua 'Worplusrn
> <https://wiki.openstreetmap.org/w/index.php?title=Key:usrn&action=edit&redlink=1>
> =2701986plot_number
> <https://wiki.openstreetmap.org/w/index.php?title=Key:plot_number&action=edit&redlink=1>
> =110007site_name
> <https://wiki.openstreetmap.org/w/index.php?title=Key:site_name&action=edit&redlink=1>=LUDGATE
> HILLward
> <https://wiki.openstreetmap.org/w/index.php?title=Key:ward&action=edit&redlink=1>
> =Ladywoodconstituency
> <https://wiki.openstreetmap.org/w/index.php?title=Key:constituency&action=edit&redlink=1>=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/20170515/5b00720e/attachment.html>


More information about the Imports mailing list