<div dir="ltr"><div>I am strenuously in favor of keeping whichever feature ID enables us to know the lineage and provenance of the GNIS point. That bit of metadata can be useful for downstream uses. <br><br>There are instances where the ele tag is useful, even if only as a rough guide, but I don't have strong feelings about it. <br>
<br></div>But I agree with the general sentiment expressed here so far, that the rest of the tags can safely be deleted.<br></div><div class="gmail_extra"><br clear="all"><div>-- SEJ<br>-- twitter: @geomantic<br>-- skype: sejohnson8<br>
<br>There are two types of people in the world. Those that can extrapolate from incomplete data.<br></div>
<br><br><div class="gmail_quote">On Wed, Aug 21, 2013 at 1:19 PM, Apollinaris Schoell <span dir="ltr"><<a href="mailto:aschoell@gmail.com" target="_blank">aschoell@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The ele tag is of unknown accuracy. It can be off by much more for mountains. This is the case when it's a real steep cliff between the sampling of NED data. found one peak where it was off by 300ft this is simply wrong and not useful.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On Aug 21, 2013, at 10:09 AM, Jason Remillard <<a href="mailto:remillard.jason@gmail.com">remillard.jason@gmail.com</a>> wrote:<br>
<br>
> Hi Serge,<br>
><br>
> - If there are two tags for the feature id, we should pick one and<br>
> change the other one.<br>
> - I don't think the ele tag should be renamed just because it is only<br>
> accurate to 60m. Everything in the database is an estimate.<br>
> - I would be ok with removing all of the gnis:* tags except the<br>
> feature id. There is no reason for us to maintain the other data.<br>
> - You might want to keep the ele tags.<br>
><br>
> Thanks<br>
> Jason<br>
><br>
><br>
><br>
><br>
><br>
> On Tue, Aug 20, 2013 at 9:24 PM, Kevin Kenny <<a href="mailto:kkenny2@nycap.rr.com">kkenny2@nycap.rr.com</a>> wrote:<br>
>> On 08/20/2013 04:54 PM, Serge Wroclawski wrote:<br>
>>><br>
>>> In addition, I suggest that we remove two other tags conditionally.<br>
>>><br>
>>> I suggest we remove the "ele" tag unless the tag natural=peak is<br>
>>> present and that we remove "source" if the value for that tag is "USGS<br>
>>> Geonames" (which is just GNIS).penny stove<br>
>><br>
>><br>
>> ele= is certainly meaningful for aeroways. And I suspect that the<br>
>> UUID will be meaningful when trying to cross-reference back to the<br>
>> original data.<br>
>><br>
>><br>
>> On 08/20/2013 06:04 PM, Apollinaris Schoell wrote:<br>
>>><br>
>>> go for it.<br>
>>> actually the ele tag is quite wrong on peaks and should be removed too or<br>
>>> renamed to something like estimated ele<br>
>><br>
>><br>
>> Please don't. If you want to add a tag like ele:status=estimated, that would<br>
>> be a better solution. There's always imprecision in elevations; even GPS<br>
>> usually has considerable vertical dilution of position. An elevation derived<br>
>> from photogrammetric contour lines is better than no elevation at all.<br>
>><br>
>> --<br>
>> 73 de ke9tv/2, Kevin<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Talk-us mailing list<br>
>> <a href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a><br>
>> <a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
><br>
> _______________________________________________<br>
> Talk-us mailing list<br>
> <a href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a><br>
> <a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
<br>
<br>
_______________________________________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
</div></div></blockquote></div><br></div>