[HOT] damage as a tag - not docu,

[Donal Hunt]

I would agree with the view that such statuses should be managed outside of
the OSM datastore. Organisations with interest of doing this may already be
using products that rely on GIS data from various sources.

For those designing apps, they can track things like damage, repairs, etc
and tie that meta data to a OSM node / way / relation ID.

Is there an existing policy regarding data types that should not be added
to OSM but tracked separately? Are there tools to support teams needing to
so this?

Donal

On Thu, 6 Feb 2020, 10:06 Russell Deffner, <russell.deffner at hotosm.org>
wrote:

> Just a quick note; HOT does not formally do damage tagging, mainly because
> no tagging schema exists. In the past, members of HOT tried various tagging
> but results for remote damage assessment were poor.
>
> I personally would be glad to see a community driven tagging schema
> developed but if not we (HOT) will need to document what we come up with
> for usage in disaster response and recovery.
>
> One glaring issue has been that typically the tags persist much longer
> than the damage.
>
> =Russ
>
> > On Feb 6, 2020, at 12:49 PM, Warin <61sundowner at gmail.com> wrote:
> >
> > Hi.
> >
> > It looks like HOT is using the tag 'damage' for something. It is not
> documented as to what it means. Further is this information kept current or
> just added and forgotten? In at least one case the tag goes back to 2011.
> >
> >
> > When will HOT start to document what tags they are using, and what they
> are used for on the OSM wiki? This is not good behavior for HOT in OSM.
> >
> >
> > _______________________________________________
> > HOT mailing list
> > HOT at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/hot
>
> _______________________________________________
> HOT mailing list
> HOT at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/hot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/hot/attachments/20200206/62e1bdae/attachment.htm>