[Talk-us] Potential data source: New York City watershed recreation lands

2016-05-22 Thread Kevin Kenny

One-line summary: I want to import the boundaries of New York City
watershed recreation areas.

Side note: This project ties in closely with Paul Norman's
identification of a need to clean up the NYS DEC Lands import.
Many of the NYC DEP watershed lands share borders with the DEC lands,
and performing this import together with or after the DEC Lands
cleanup would yield a topology that is more nearly consistent. (Some
property lines simply are mapped inconsistently in the real world as
well as the digital world, so there will unavoidably be misalignment
of some parcels after the import.)

I welcome comments about any aspects of this proposal. I'm still new
to this game.



PROPOSED IMPORT:
New York City
Department of Environmental Protection
Bureau of Water Supply
Open Recreation Areas and Use Designations
http://www.nyc.gov/html/dep/pdf/recreation/open_rec_areas.pdf

1. OVERVIEW

New York City owns, and makes accessible for public recreational use
(activities such as hiking, fishing, hunting and trapping) about four
hundred parcels of land in the Catskill and Croton watersheds. All of
these lands are outside the boundaries of the city itself. The vast
majority of these parcels do not yet appear in OpenStreetMap.  This
proposal is made to solicit community buy-in for the project of
importing multipolygons giving the boundaries of these reserves.

I expect that this import should be relatively non-controversial. The
data arise from an authoritative source - the agency that manages the
lands in question. They are readily obtainable in no other
way. Cadastre of public parks, nature reserves, and the like has been
imported many times before.

The import is of relatively small scale, comprising fewer than 400
multipolygons and associated tags. The total area of the parcels in
question is roughly 145 square miles (375 km**2).

2. LICENSING

I believe that the data are, by law, in the public domain under New
York City's open data access policy. The OSM community has relied on
ths policy in the past, most notably in the import of the New York
City address and building footprint data. The relevant paragraph is
in the Administrative Code of the City of New York, Chapter 5,
paragraph 23-502, subparagraph d. The text may be found at
http://www1.nyc.gov/assets/doitt/downloads/pdf/nyc_open_data_tsm.pdf,
page 27. The data in question do appear on the single web portal
described in subparagraph a.

3. TECHNICAL DETAILS

The data in question consist of the PDF file
http://www.nyc.gov/html/dep/pdf/recreation/open_rec_areas.pdf, and the
PDF maps to which it links. I've successfully made a script to scrape
the tabular data from the PDF, resulting in a set of 367 distinct
unit names, together with the 'paa', 'hike', 'fish', 'hunt', 'trap'
and 'dua' columns, and the URL's of the corresponding maps.

These maps are all in PDF format. They are fully georeferenced, and
I've been able to work out GDAL scripts to extract the boundaries and
produce well-formed polygons from all but four of them. These four are
the "Day Use Areas" or "Designated Use Areas" (the web site fairly
consistently uses the former phrasing, the posters on the land use the
latter) of Devasego Park, the Ashokan fountains, and the Kensico and
Cross River dams. These are popular areas for walking and picnicking,
but are more of the nature of city parks than of nature reserves.
On the initial import I propose simply to ignore these four, leaving
363 recreation areas to import.

The proposed tagging is as follows:
leisure=nature_reserve
For the benefit of legacy renderers that do not yet comprehend
the details of boundary=protected_area
boundary=protected_area
protect_class=12
protection_object=water
Tailor-made for this data set!
operator='New York City, Department of Environmental Protection,
  Bureau of Water Supply'
website=http://www.nyc.gov/html/dep/html/recreation/index.shtml
name=(obtained from the 'unit' column of the list of sites, with
the word, 'Unit' postpended)
access=yes (if the 'PAA' column is 'Y') or access=license (if the
PAA column is 'N')
access:license=http://www.nyc.gov/html/dep/html/watershed_protection/recreation.shtml
if (access=license)
access:hiking=(value of the 'hike' column, normalized to 'yes' or 'no')
access:fishing=(value of the 'hike' column, normalized to 'yes' or 
'no')
access:hunting=(value of the 'hike' column, normalized to 'yes' or 
'no')

access:trapping=(value of the 'trap' column, normalized to 'yes'
or 'no')
nycdep:version=MMDDHHMMSS
UTC time returned as Date-Modified from the web site. See
below for rationale of retaining this information.

I'm more than open to a different tagging scheme for 'access'. What
the relevant restrictions are:

PAA=Y areas are open to all comers, no p

Re: [Talk-us] TopOSM

2016-05-22 Thread Kevin Kenny

On 05/22/2016 02:39 PM, Lars Ahlzen wrote:

On 05/21/2016 01:54 PM, Clifford Snow wrote:
TopOSM looks like a good candidate for a hack session at SOTM-US. Let 
me know if you are interested so I can find a room for people to meet 
on July 25th.


That's not a bad idea. Sounds like there's some interest in the OSM 
community, and I'd be happy to take a look at it again. I'd say go ahead!


Alas, I'm not going to SOTM, but put me down as someone who's interested 
in the project, with some 'skin in the game' already.


As I already posted privately to Clifford:

I picked up TopOSM's code for my own purposes and added quite a few 
twists of my own. I use the result as a basemap for several of my own 
projects. You can see what it looks like at 
https://kbk.is-a-geek.net/catskills/test3.html.


The 'catskills' in the name is something of a misnomer - it started as a 
Catskill Mountain project, but got out of hand and now covers most of 
the Eastern Seaboard. The 'test' in the name reflects that the page in 
question was intended largely as a demonstration viewer. I mostly use 
the tiles in apps on my phone.


At the moment, it's several months out of date. I've generally brought 
it fully up to date only a few times a year, because I've never troubled 
to get a pipeline going for automatic rendering with a tool such as 
tilestache. Given the limited area that it supports, I do all right 
serving static tiles. It generally takes overnight to produce them all, 
and warms my home office quite nicely when it's running. Clearly, I am 
NOT tooled up to serve it up on a large scale.


It depends on a good many publicly-available data layers with 
ODBL-incompatible terms. Life is full of tradeoffs. I think that a 
'sanitized' version with only ODBL and US Government data wouldn't be 
too difficult to put together.


I'm more than willing to share the code, but it would be a bit of a 
nightmare to set up. I think that the best approach would be to share it 
with a willing apprentice (if you will) in pieces, reworking as we go to 
make sure that each shared piece runs for more than just me and the 
setup is better documented than it is now. I'm willing to put in the 
effort to make such a project succeed, but would find it immensely 
difficult without a guinea pig to try stuff out and provide ongoing 
feedback.


Significant public layers that I include that I believe TopOSM does not 
include:


(1) NLCD, the National Land Cover Database. This provides the base 
colour, atop which is added hillshading. For my personal map, this is 
not something I'm willing to live without. It's important to me, when 
planning an off-trail trip, to know when to expect coniferous forest 
(near me, this is generally dense balsam-and-spruce that slows travel to 
a crawl) and when to expect deciduous forest (which, by contrast, is 
relatively open). It also pretty much obviates the need to use 
NaturalEarth's 1:10million populated areas shading, which is at an 
inappropriately coarse scale for most of our use of it.


In order to do this, I had to replace styles describing land use/land 
cover/cadastre to use shading on the boundaries rather than area fills. 
(I think the appearance in the end is nicer in any case.) I confess to 
colour-blindness and would welcome a more attractive colour scheme.


(2) A fair number of FCODES from NHD (National Hydrographic Dataset) 
that TopOSM ignores. Ignoring these FCODEs loses, for instance, the 
lower Hudson River on TopOSM.


(3) The USFWS National Wetlands Inventory. Most of the marshlands that 
are shown on my map come from there.


There are also a few state-level data sets describing foot trails and 
public land boundaries in my map that I am NOT comfortable including in 
TopOSM without consulting with the issuing agencies. Some of the 
agencies are not amenable to allowing redistribution of their data, even 
when the law requires them to make the data available to the public. 
Most of those are shown on the map in magenta, and serve me as a "things 
to do" list when I'm thinking up ideas for a short hiking trip.





--
73 de ke9tv/2, Kevin


___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] TopOSM

2016-05-22 Thread Lars Ahlzen

On 05/21/2016 01:54 PM, Clifford Snow wrote:
TopOSM looks like a good candidate for a hack session at SOTM-US. Let 
me know if you are interested so I can find a room for people to meet 
on July 25th.


That's not a bad idea. Sounds like there's some interest in the OSM 
community, and I'd be happy to take a look at it again. I'd say go ahead!


- Lars


___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us