Awesome! This is excellent work Elliott. Very cool to see the county parks loaded up into OSM. A few thoughts. There is a growing community including Code for America, Open Street Map, the National Parks and Recreation Association, Strava, AllTrails, and many others that have released a new open data standard for park and recreation information, OpenTrails. See below for a few links that will provide some background. The primary focus of OpenTrails is to improve visitor use applications so it is focused on lands that are open to the public. The end goal is to provide public agencies with a mechanism to open up their data and publish their data so it can easily be consumed by third party outdoor applications as well as integrated into popular base maps, most critical being OSM and Google.
OpenTrails at CfA <http://www.codeforamerica.org/specifications/trails/> All things OpenTrails - http://www.opentraildata.org/ Outside Magazine article about OpenTrails <http://www.outsideonline.com/outdoor-adventure/the-current/footprint/Strava-is-Just-the-Start-The-Promise-of-Open-Trail-Data.html> OpenTrails course for public agencies <http://www.opentraildata.org/course/> Feel free to get in touch, would be happy to discuss how OpenTrails might be useful for aggregating standardized Maryland park data so it can be easily integrated into OSM. Best, Ryan On Mon, Dec 1, 2014 at 9:01 AM, Elliott Plack <[email protected]> wrote: > Greetings, > > I finally completed the import over the weekend when I had some free time. > The data looks great and adds some color to the map where there wasn't any. > Have a look at a few areas: > > Eastern Shore: http://www.openstreetmap.org/#map=11/38.3158/-75.9087 > Western Md: http://www.openstreetmap.org/#map=10/39.5348/-78.8956 > Patapsco: http://www.openstreetmap.org/#map=14/39.2404/-76.7529 > > Hooray! > > Now, there is some data on County owned parks in the data that I want to > ask the community about. This data shows all county owned land that is set > aside for recreation or preservation. There are many gaps in the state and > federal parks that are covered by county parks, where having that data > would be immensely valuable. > > Conversely, the data includes many small "Local Open Space" or "Drainage > and Utility" properties. These tracts are set aside during the land > subdivision process to preserve a certain % of the land for non-development > uses. There is value in having this data on OSM, such as for geocachers. > Technically the land is public and open. However, I'd only use the > leisure=park when the land is specifically a park, whereas > leisure=nature_reserve would apply to preserved land that isn't > specifically for recreation. Look at Baltimore.geojson or > Montgomery.geojson in the data below for these small properties. > > Here are some geoJSON files that you can visualize on Github on top of an > OSM basemap (by Mapbox): > https://github.com/talllguy/maryland-dnr-osm-import/tree/master/dataWGS84/County%20Lands/byCounty > > Thoughts on the small county properties? > > Elliott > > > On Fri Apr 18 2014 at 3:16:39 PM Elliott Plack <[email protected]> > wrote: > >> Greetings Import Community, >> >> *Firstly, pardon the duplicate message. The original was sent in error >> without a subject.* >> >> After SOTMUS, I have decided to resurrect the import of Maryland Dept. of >> Natural Resources land boundary data. This import will take public domain >> Maryland polygon data that represents the official boundaries of state >> parks and protected areas and will bring them into OSM using a variety of >> tags. I have documented this in the link below, complete with tables, >> diagrams, examples, and a link to the data on GitHub. >> >> *Brief Summary*: Maryland has made this data public domain. The plan is >> to import this data in *manual mode* only. Local editors will examine >> the data on an individual basis and then upload it when it meets tagging >> standards. The tagging will be fairly comprehensive. We'll either use >> leisure=park or leisure=nature_reserve depending on the data dictionary >> on the wiki. We'll also use the boundary=protected scheme and I have >> written a key for each state land type and corresponding protect_class >> type. >> >> *Benefits:* This data in OSM will be fantastic for basemaps, as parks >> and natural protected land boundaries are often hard to discern based >> solely on imagery. Local surveys are impractical given the immense size of >> some of these areas. Coupled with trails surveyed by other local mappers, >> or using the new Strava slide tool, the OSM map can often outperform the >> official state maps in terms of accuracy and informational content. >> >> http://wiki.openstreetmap.org/wiki/Maryland_State_Parks >> >> >> https://github.com/talllguy/maryland-dnr-osm-import/tree/master/dataWGS84/DNR%20Lands%20and%20Conservation%20Easements >> >> Looking forward to any comments. >> >> Thanks, >> >> -- >> Elliott Plack >> http://about.me/elliottp >> > > _______________________________________________ > Imports-us mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/imports-us > > -- Ryan Branciforte Cofounder & CEO @ www.TrailheadLabs.com <http://www.trailheadlabs.com/> ***2014 Code for America Accelerator Company***
_______________________________________________ Imports-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports-us
