[Talk-us] Trails (was: OpenStreetMap US update)

[Mike Thompson]

I find it very hypocritical that land managers are complaining about
OpenStreetMap trail data when their own data is full of inaccuracies.
Perhaps Utah is different, but just around the area where I live in
Colorado I have found hundreds of errors in government trail data,
including cases of:

1) Trails being mislocated by up to a third of a mile.
2) Trails that do not exist, or are in such poor shape as to not be
considered trails, in the government data.  https://youtu.be/YUfrD1vPtHM
3) Official trails (as evidenced by signs and other government documents)
that do exist, but which are not in the government data, e.g.
https://youtu.be/ib7oXELgNFU
4) Trails whose on the ground signage as to name, and number do not match
the government data. e.g. https://youtu.be/jxKZZwQh1wA
4) Trails whose on the ground signage as to allowed usage do not match the
government data.
5) Duplicate trails e.g. https://youtu.be/WcPHcoYagb4
6) Topological issues in government trail data, e.g. two trails that are
connected in reality, but are not in the government data.
7) Government data including trails that are posted "no trespassing"

In some cases the government trail data is over ten years out of date!
e.g. https://youtu.be/m6okmIJXt4k

Unless we are very careful, attempts to "improve" OSM with government data
is likely to lead to a degradation of the quality of OSM!

There seems to be a reluctance on the part of land managers to admit they
have a problem, or do anything about it.

The problem is so bad that a local television station did an investigative
report on it:
https://www.cbsnews.com/colorado/news/colorado-preferred-trail-app-cotrex-own-flaws/

I gave a presentation at GIS in the Rockies on the matter:
https://youtu.be/_sUVKA_C6Q8

Mike


On Mon, Oct 23, 2023 at 11:42 AM Nellie Blair <nellie at openstreetmap.us>
wrote:

> The OpenStreetMap US team is sharing the following updates this week:
>
> 1) With the support of volunteers and land managers, the OpenStreetMap US
> Trails Stewardship Initiative is launching our first statewide campaign
> aiming to update trail information on 60,000+ miles of trails in
> OpenStreetMap across Utah public lands. Learn more in our latest blog post:
> https://openstreetmap.us/news/2023/10/trails-utah-campaign/
>
> 2) Join us online for Mapping USA on January 19 & 20, 2024. Registration
> is free! Sign up here:
> https://openstreetmap.app.neoncrm.com/np/clients/openstreetmap/eventRegistration.jsp?event=77
>
>
> The call for proposals is now open! We are calling on all members of the
> OpenStreetMap US community to share your ideas and session proposals. The
> Mapping USA program will include space for short talks, workshops, birds of
> a feather sessions, plus room for improvisational sessions, editing/mapping
> parties, and other ideas you might have. We’re particularly interested in
> highlighting projects and tool developments that foster our local
> communities in the United States and virtual collaboration across
> geographic divides. Submit your session ideas before the October 31st
> deadline:
> https://docs.google.com/forms/d/e/1FAIpQLSeHXJ_SnAJUqwQDiDmgBjwOHwGXhyjI0ZrYa
> <https://docs.google.com/forms/d/e/1FAIpQLSeHXJ_SnAJUqwQDiDmgBjwOHwGXhyjI0ZrYaY7gFeaZeH2zDg/viewform>
>
> 3) OpenStreetMap US members: save the date for our first virtual Brown Bag
> on November 9th at noon ET. This brown bag event will showcase our Trails
> Stewardship Initiative with a deep dive and demo on improving trails in
> OpenStreetMap. Current members will find an invite in your inbox and the
> member portal. If you're not currently a member, it's easy to join:
> https://openstreetmap.app.neoncrm.com/forms/individual_membership
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20231023/00a6d06a/attachment.htm>