*DBH:* is one of the most common dendrometric measurements. https://en.wikipedia.org/wiki/Diameter_at_breast_height
*Ref:* These trees are tagged & stamped by the City of Ottawa for tracking purposes. *Operator: *The City of Ottawa does maintain these trees. *Source: *Has been removed and can be placed in the Changeset comment. Words of encouragement on imports should not be discouraged. +1 this import *~~~~~~* *Denis Carriere* *GIS Software & Systems Specialist* On Wed, Jun 28, 2017 at 3:21 AM, Christoph Hormann <[email protected]> wrote: > On Wednesday 28 June 2017, Kyle Nuttall wrote: > > You are correct to assume that I did not research each tree > > individually, but I also did not create a table while I was working > > on this dataset. I went ahead and created one and it is now available > > on the wiki page > > https://wiki.openstreetmap.org/wiki/Canada:Ontario:Ottawa/Import/Tree > >s#Common_and_Latin_names > > That is a good start, if you could beef up this table with the > leaf_type/leaf_cycle and genus tags that would be what i had in mind. > Both creating this and verifying that this is actually consistent in > the data can be done with a simple GROUP BY query on the data. > > > As for the verification, the data was collected by the City of Ottawa > > Forestry Services using GPS software on computers. Even if I surveyed > > each tree individually, the tools I have are much less accurate. I'd > > argue that the background imagery should be aligned to these trees > > and not the other way around. I'm not sure how to satisfy your > > question when the tools used by my government are far greater than my > > cell phone. > > You probably misunderstood me then - i was not questioning the accuracy > of the data (although with a survey date of 2013 there are probably > some trees removed for building stuff in the meantime), i was worried > about mismatches with the existing data in OSM. It is quite possible > that resolving those usually needs to modify the existing data rather > than the trees but you should have a solid plan for handling this kind > of problem. Just dumping the data and hoping that mappers will sort > out problems later is not the way to go. > > -- > Christoph Hormann > http://www.imagico.de/ > > _______________________________________________ > Imports mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/imports >
_______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
