The age key is described in terms of "mature" "semi-mature" "young" "newly planted" etc. and so cannot be updated mathematically as, to repeat an earlier post, we don't have a date of planting in the data to be imported. Moreover this system of descriptive values is better, having a sufficient range to obviate the necessity for constant updating which is presumably why the data owner used these values in the first place. I fail to see why this tag cannot be used given that's the data format we have and it is a good description of the age and one that anyone can readily understand in relation to the trees to which it relates. It's a valuable, and valid, piece of data about the trees and one we don't want to omit. regards
Brian On Tue, May 16, 2017 at 9:44 AM, Martin Koppenhoefer <[email protected] > wrote: > > 2017-05-15 23:36 GMT+02:00 Andy Mabbett <[email protected]>: > >> > the point is, while a mapper can use any tags he wants, an import >> shouldn't >> > introduce any new tags but rather use established tags in a way they are >> > already defined. >> >> Where was this "rule" agreed and where is that documented? What is the >> justification for it? >> > > > > it is part of the import guidelines: https://wiki.openstreetmap. > org/wiki/Import/Guidelines#Use_the_right_tags > > > > >> >> > "min_age" relates to the min_age of the people attending the feature. >> > It is defined like this. >> >> Since no people "attend" trees, this would appear to be a wholly >> unnecessary distinction. >> > > > > yes, the point was: don't use "age" as you would have to update this every > instant, use a date based tag like the well established start_date which > allows to calculate the age when you need it. > > > > >> >> >> - 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 >> > >> > IMHO there shouldn't be an abbreviation in the tag name, generally, >> there >> > shouldn't even be a foreign key at all. >> >> If "usrn" is the name used for the ID by the source, it seems >> perfectly reasonable to use the same name in OSM. > > > > actually the name appears to be "Unique Street Reference Number" and usrn > is just an abbreviation for it. This is a tag that codifies an address (the > street where a tree is located) into a new OSM tag, which is rather > pointless, as we already have a spatial reference to the position of the > tree. These reference numbers might be useful to attach to the highway (if > the british comunity decides so), but it doesn't seem to make a lot of > sense adding them to trees. > > Cheers, > Martin > > _______________________________________________ > Imports mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/imports > >
_______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
