[Tagging] Estimated values for height

marc marc marc_marc_irc at hotmail.com
Sun Nov 11 15:12:43 UTC 2018


taginfo only count the old/ugly schema with the source
on objects in stead of changest. for a source tag,
it's a count a bad pratice :)

don't forget that :
- tree is growing, so next year, the information that the measurement 
was made by a laser with the accuracy of the device will all be out
of date.
- they are also outdated as soon as a mapper changes the tag height 
without changing the other x tags, which is the case for most contributors.

so putting these tags on the source, the accuracy of the source, etc. on 
the object are useless, they are also searchable via the history on the 
changeset, and at least they are no longer modifiable after closing the 
changeset, which allows to have a real source instead of having a 
"source without any certainty because you still have to read the history 
of the object to see if the last modification of the height was made at 
the same time as the addition of the source tag


Le 11. 11. 18 à 12:15, Sergio Manzi a écrit :
> Hello everybody,
> 
> I'm the one who, in the Italian mailing list, first brought out the 
> issue about how to tag estimated heights (/in our context it was about 
> trees height/).
> 
> My first proposal has been to use a new sub-key in which to store 
> estimated values, as in "height:estimated=10".
> 
> Then I saw, here, the proposal of using "source:height=estimated", which 
> is in use (/1543 entries, mostly applied to ways: see: /[1]), which I 
> thought was a better solution then the one I originally conceived.
> 
> Now I see that there is a different solution in use, 
> "height:source=estimated", which is less used (/149 entries, mostly 
> applied to ways: see: /[2]), but *makes even more sense to me, from a 
> syntactical point of view*.
> 
> Someone also proposed to use "height:accuracy=*" if the accuracy is 
> known, but I think this could be used for an estimated value too 
> (height:accuracy=estimated). On the other hand this doesn't seems to be 
> in use anywhere even though it might be considered an even better 
> solution both syntactically and semantically (/I think "source" should 
> be used to identify "who" is the originator of the information/).
> 
> In any case I think the various est_(width|length|height|whatever) keys 
> should be deprecated and a new universal solution to identify estimated 
> values  should be adopted, taken from the ones described above (/or a 
> new one I'm not thinking of//at this time/)/./
> 
> Regards,
> 
> Sergio
> 
> [1] https://taginfo.openstreetmap.org/tags/source%3Aheight=estimated
> [2] https://taginfo.openstreetmap.org/tags/height%3Asource=estimated
> 
> 
> On 2018-11-11 10:07, bkil wrote:
>> Yes, that sounds reasonable. Also there's height:accuracy if you know 
>> your error.
>>
>> On Fri, Nov 9, 2018 at 11:42 AM Dave Swarthout 
>> <daveswarthout at gmail.com <mailto:daveswarthout at gmail.com>> wrote:
>>
>>     You can also use height=* for both and add a
>>     "source:height=estimated / measured" tag with that to have a value
>>     that is usable by the apps and tools but still keeping the
>>     information that it was only estimated ! ;-)
>>
>>     An excellent solution, Lionel
>>
>>     On Fri, Nov 9, 2018 at 5:06 PM marc marc
>>     <marc_marc_irc at hotmail.com <mailto:marc_marc_irc at hotmail.com>> wrote:
>>
>>         look at the current values in height, you understand from their
>>         round values that they are massively estimated.
>>
>>         my preference is therefore to use height and make 2 changset
>>         to put a changeset tag related to the source
>>         of the measurement: measured <> estimated
>>
>>         Le 09. 11. 18 à 10:57, Lionel Giard a écrit :
>>         > You can also use height=* for both and add a
>>         "souce:height=estimated /
>>         > measured" tag with that to have a value that is usable by
>>         the apps and
>>         > tools but still keeping the information that it was only
>>         estimated ! ;-)
>>         >
>>         >
>>         > Lionel
>>         >
>>         >
>>         >
>>         > Le ven. 9 nov. 2018 à 10:19, Dave Swarthout
>>         <daveswarthout at gmail.com <mailto:daveswarthout at gmail.com>
>>         > <mailto:daveswarthout at gmail.com
>>         <mailto:daveswarthout at gmail.com>>> a écrit :
>>         >
>>         >     There is already an est_width tag (Taginfo 77,000). I
>>         see no reason
>>         >     why you couldn't use est_height, which has over 1000
>>         instances in
>>         >     Taginfo.
>>         >
>>         >     Dave
>>         >
>>         >     On Fri, Nov 9, 2018 at 3:58 PM Cascafico Giovanni
>>         >     <cascafico at gmail.com <mailto:cascafico at gmail.com>
>>         <mailto:cascafico at gmail.com <mailto:cascafico at gmail.com>>> wrote:
>>         >
>>         >         I'm going to import a small dataset of trees. Some
>>         tree heights
>>         >         are defined as "measured", some as "estimated".
>>         >
>>         >         About estimated values, I've found a wiki definition
>>         only for
>>         >         width [1]: shall I
>>         >         derive an est_height tag,
>>         >         go for most popular taginfo solutions,
>>         >         simply assign an estimated value to height tag?
>>         >
>>         >
>>         >
>>         >         [1] https://wiki.openstreetmap.org/wiki/Key:est_width
>>         >  _______________________________________________
>>         >         Tagging mailing list
>>         > Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
>>         <mailto:Tagging at openstreetmap.org
>>         <mailto:Tagging at openstreetmap.org>>
>>         > https://lists.openstreetmap.org/listinfo/tagging
>>         >
>>         >
>>         >
>>         >     --
>>         >     Dave Swarthout
>>         >     Homer, Alaska
>>         >     Chiang Mai, Thailand
>>         >     Travel Blog at http://dswarthout.blogspot.com
>>         >     _______________________________________________
>>         >     Tagging mailing list
>>         > Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
>>         <mailto:Tagging at openstreetmap.org
>>         <mailto:Tagging at openstreetmap.org>>
>>         > https://lists.openstreetmap.org/listinfo/tagging
>>         >
>>         >
>>         >
>>         > _______________________________________________
>>         > Tagging mailing list
>>         > Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
>>         > https://lists.openstreetmap.org/listinfo/tagging
>>         >
>>
>>         _______________________________________________
>>         Tagging mailing list
>>         Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
>>         https://lists.openstreetmap.org/listinfo/tagging
>>
>>
>>
>>     -- 
>>     Dave Swarthout
>>     Homer, Alaska
>>     Chiang Mai, Thailand
>>     Travel Blog at http://dswarthout.blogspot.com
>>     _______________________________________________
>>     Tagging mailing list
>>     Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
>>     https://lists.openstreetmap.org/listinfo/tagging
>>
>>
>> _______________________________________________
>> Tagging mailing list
>> Tagging at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/tagging
> 
> 
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
> 



More information about the Tagging mailing list