[Imports-us] USNPS, Great Smoky Mountains Bulk Import In Progress

Thomas Colson thomas_colson at nps.gov
Sun May 19 19:54:53 UTC 2013


We feel we did our due diligence in informing the community of this import
in advance of the activity, including posting in the appropriate Wiki pages,
import-us, and talk-us. We got lots of feedback through the mailing list and
via direct email and reached out to some users that we identified were using
the data commercially. As we could not identify any "local community" Wiki
page or mailing list specifically relevant to the mountain region of east
TN/west NC, we reviewed item histories to see who the "power mappers" within
the park footprint were (and communicated with the one we did find), and
exchanged email with one of you directly regarding a component of our
proposed import, which lead to us dropping streams from our initial import.
For the most part, community feedback was incorporated in our planning where
we are legally allowed to do so, including use of a dedicated import

If there is a formal path for approval of a proposed import, we'd love to
hear about it. This is a pilot project which will hopefully entice other
National Parks to do the same, and we plan on putting a lot of effort into
maintaining a Wiki page for NPS imports. If a NPS Park updating OSM data
results in this type of reaction, we'd like to get in front of it so the
next park doesn't get such a hostile response. The goal is to encourage park
GIS managers to be active participants in the OSM community, and hopefully
there will be many more NPS park imports hitting the "street". 

As we plan on continuing with importing/updating the park footprint
throughout the summer, we look forward to a meaningful dialogue which allow
that process to move smoothly. 

-----Original Message-----
From: Jason Remillard [mailto:remillard.jason at gmail.com] 
Sent: Sunday, May 19, 2013 3:10 PM
To: Thomas Colson
Subject: Re: [Imports-us] USNPS, Great Smoky Mountains Bulk Import In

Hi Thomas,

It might help posting the URL to the import project wiki, and the change set
url. Going forward, you should do this for every update to the email lists.
It would help give everybody context. There are lots of imports going on, so
it is hard for everybody to keep track of them.

I did end up finding the wiki, Honestly, the it is a bit confusing.
Lots of different kinds of changes. A sample OSM file posted to the list
would probably have been a better for everybody to look at.


On Sun, May 19, 2013 at 11:22 AM, Thomas Colson <thomas_colson at nps.gov>
> We have completed "seeding" a portion of Great Smoky Mountains 
> National Park OSM data this weekend. We focused on the Cades Cove 
> section of the park, which contains a complete sample of the types of 
> features that are of relevance to visitor services and how they can be
depicted in OSM.
> The parking icons and labels are a bit obtrusive in the default OSM 
> renderer, as are the building labels. I'll likely remove some parking 
> node tags as well as building labels, really not necessary to label 
> every shed and generator building (this is what came out of our 
> default facilities data). Parking ways are also named, so I don't see 
> a problem with not labeling every single parking node.
> The only import issues were related to connecting a few roads to roads 
> we weren't updating, JOSM Editor caught those smoothly.
> The update rendered in the ESRI OSM Tile Service within a few minutes, 
> which was very cool, and also allowed for rapid QA against our Raw GIS
> Nate and Mamata will be presenting our work at State of the Map in a 
> few weeks, and will incorporate feedback into the remainder of the park
> Changesets are linked on the GRSM Wiki Page.
> _______________________________________________
> Imports-us mailing list
> Imports-us at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/imports-us

More information about the Imports-us mailing list