Re: [Imports] Birmingham City Council tree import

On 15 May 2017 at 15:36, Martin Koppenhoefer wrote: >> - 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.

Re: [Imports] Birmingham City Council tree import

I'm proposing to edit the already imported data to improve the height data as suggested in the discussions. This will bring the data into line with the generally accepted format for height tags change existing tag to height:range add height=x where x is nearest whole digit at the upper end of

Re: [Imports] Birmingham City Council tree import

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