Sam Wear — one of New York’s pre-eminent GIS leaders — published a fun interview with me about our mapping work at the CUNY Graduate Center. I’m honored!
The NYC Dept of City Planning only provides an ESRI Geodatabase, which is native to ESRI software, therefore presenting a challenge to people using non-ESRI applications. Although the shapefile format is technically also proprietary to ESRI, it’s become a de facto open format, easily read/consumed by other software packages such as QGIS (from which you can simply “save as…”, for example, to almost any other format you want).
Preferably NYC Planning would provide access to the LION file in this and/or other formats at the Bytes of the Big Apple website (many other data sets are available there in shapefile format and other formats). But until they do, here’s a link to my version of it, converted from geodatabase to shapefile:
Hope this helps!
ORIGINAL POST: Oct. 7, 2015
According to the metadata, “LION is a single line representation of New York City streets containing address ranges and other information.” The centerline GIS data, as well as the “other information” in LION, is pretty impressive, and this blog post highlights some of the really neat nooks and crannies in the data.
LION-the-name is of a piece with TIGER, the US Census Bureau’s massive spatial data set of the nation’s street grid (and other Census statistical areas). Both are kinda (too?) cute “backronyms” – TIGER as shorthand for Topologically Integrated Geographic Encoding and Referencing files. LION stands for Linear Integrated Ordered Network, presumably pieced together to represent an equally fierce jungle animal symbolically showing that NYC’s street centerline data was just as impressive. LION is now part of the city’s newer City Street Centerline (CSCL) project, also an impressive effort but a much tamer string of initials – not even an acronym, and nowhere close to BEARs, which IMHO would’ve been the perfect Oz-like grouping (“LIONs and TIGERs and BEARs, oh my!”).
Anyway, according to a 1996 version of the LION User Guide:
The LION file has been maintained by DCP [NYC Dept of City Planning] as a major component of the Geosupport System. It is a single line representation of New York City streets containing address ranges and other information. The LION file has also been used for automated cartography within DCP. The increasing use of microcomputer-based mapping and geographical information systems within the City’s government has led to the development of the BYTES of the BIG APPLE™ files.
In 1996, the LION dataset was spread over several files occupying 14 MB of disk space. The latest version of LION is available as an ESRI geodatabase occupying almost 130MB of disk space, almost 10 times as large. There were a number of attribute fields in 1996, but nowhere near the more than 100 fields available today.
In this expanded set of attributes lies all sorts of fascinating ways of describing and representing New York City’s street system. Of course LION can be used to just display streets throughout the city. But there’s lots more in the file, not all of which is obvious.
For example, LION has an indicator for curved vs. straight street segments, and whether the curve is “irregular” (i.e, not a circular arc) or if it’s a “circular arc lying on the left [or right] side of the segment’s directed chord.” Wow.
As you might imagine, there aren’t too many curved streets within Manhattan’s grid. But in the middle of Manhattan in Central Park, curved streets are the norm. Here they are in something of an abstract neon light display (rotated 29 degrees from north):
The red lines are “irregularly curved segments”, the green lines are circular arcs — remember that the lines may represent multiple connecting segments, so even though a green line may not look like it’s part of a circle, each segment along the line may be its own circular arc.
Note that you can click on each map image in this post to see a larger version.
The image below is the Mill Basin neighborhood in Brooklyn (rotated about 320 degrees), highlighting the amphitheatre-style street layout:
Prospect Park’s curved streets (rotated about 130 degrees) take the shape of some sort of prehistoric neon species:
And Wards Island (rotated about 303 degrees) looks like … well, you can decide based on your own interpretation:
The LION data can be used to highlight certain types of streets, such as highways/parkways, bridges, and tunnels, as illustrated below (based on the RW_TYPE & NONPED fields, using the filter RW_TYPE in (‘ 3’, ‘ 4’ , ‘ 2’) or nonped = ‘V’):
Also, the white lines above are borough boundaries as indicated by LION segments, based on the LocStatus field (where LocStatus is 1, 2, 3, 4, 5, or 9).
Or, LION can isolate where the city’s pedestrian-only pathways are located, as represented below (based on the TrafDir field where TrafDir = ‘P’, ie., ‘Pedestrian path: Non-vehicular’) – notice the almost complete ring around Manhattan, as well as along much of south Brooklyn’s waterfront:
Or railways – not only the subway lines, but rail lines such as the Conrail freight line in Queens and the Bronx, Metro North, and PATH (based on the FeatureTyp field where 1 is Railroad, and the different colors below are based on “street”, i.e. rail, name groupings):
Light blue are subway lines, yellow is AirTrain, dark blue is the Staten Island Railway, green is PATH, brown are the various LIRR lines in the city (including the Bay Ridge freight line), red is Metro North, and purple is Amtrak/Conrail.
LION can be used to locate “non-addressable place names” (NAPs), or “geographic place names that cannot be combined with a house number to form an address” (per the City Planning Department’s Property Address Directory user guide [PDF]).
Examples of NAPs in the city’s street centerline file include the Empire State Building, Columbia University, or even the Coney Island Cyclone. Even though each of these locations likely has a street address, there’s no “25 Empire State Building” or “350 Columbia University”. The names themselves have been georeferenced by DCP so that the names alone can be used for geocoding and map display.
The way these NAPs are represented in LION is that DCP adds a street name synonym to the closest street segment for each NAP location. The images below give you a sense of how these show up on the map. In other words, the LION file can be used to approximate a database of all sorts of important facilities, cultural icons, housing complexes, schools, etc throughout the city. For the two maps below I used the following filter based on LION attributes:
“FeatureTyp” = ‘2’ or ( “SpecAddr” in ( ‘G’, ‘N’, ‘V’, ‘X’, ‘P’) )
… and I labeled the segments with the SAFStreetName field (described in the LION metadata as a “Special Address Place Name”).
The first image below shows some the mapped NAPs in and around Coney Island (definitely click the image for a larger, clearer view):
The next image shows NAPs in the Lower East Side:
Some of the LION segments in the images above are very precise (such as El Jardin Del Paraiso, represented by a very narrow piece of the street segment along East 5th St). Others extend along an entire city block or more, such as PS 15 or New York Aquarium in the images above.
LION includes more than street segments. It also includes line representations of borough boundaries (as shown in the highway/bridge/tunnel map above), administrative district boundaries (such as Police Precincts or Community Districts), and Census block and tract boundaries.
The LION file also includes some history regarding the Census geography. The latest version of LION includes attribute fields indicating which segments align with Census block and tract boundaries not only in 2010, but also in 2000 and 1990.
By filtering segments where the 2010 Census attribute fields don’t match 2000 (LCT2010 <> LCT2000 or RCT2010 <> RCT2000 — where L stands for the left side of the segment and R the right side), we can see where Census tracts changed in the last decade (yellow-orange in the map below is where the 2010 tract identifiers didn’t match 2000; blue are all the other tract boundaries as represented by LION street segments):
These changes could’ve been simply due to different tract numbers from one decade to another, but also could’ve been the result of tract geometry being split or combined.
There were far fewer changes between 1990 and 2000, represented in red in the map below:
Pretty colors (or, Zoning Sections)
Finally, each LION segment is tagged with its corresponding zoning map ID from the Dept of City Planning’s sectional zoning maps. The image below uses a random color pattern to highlight the zoning sections across the city (otherwise mapped at DCP’s website as a simple grid):
(I was inspired for the zoning section map by these maps by Stephen von Worley of Data Pointed.)
There’s lots more interesting data in LION where these examples came from. Check out LION’s metadata, and hopefully you’ll be able to use the LION file for much more than just streets. (Btw, each map above was made using ArcGIS Desktop mapping software.)
In September 2015, the MTA opened its first new subway station in NYC in decades. I’ve added the new station and extension of the 7 line to the Center for Urban Research’s (CUR’s) maps and underlying GIS data, and we’re making this updated data freely available.
Here’s the post at CUR’s website, and here are the links below with the data:
If you use the data (which I hope you do), please let me know how it works out. If you use the files, please reference the “Center for Urban Research at the Graduate Center/CUNY” especially if you use the layer symbology in any printed maps or online applications. Thanks!
Lately NYC agencies have started to step up the pace in producing an impressive amount of publicly accessible GIS (and other) data. It’s a very good direction (and hopefully one that all agencies will soon follow).
This summer, the big news was that MapPLUTO was all of a sudden available for free. And then ACRIS was opened up (not geospatial, but key to analyzing spatial patterns of property transactions). And before that HPD had posted a large amount of housing data (albeit in a wacky XML format, but nonetheless it was a lot and it was freely available and it was being updated regularly).
But today there’s even more…
… Historical MapPLUTO!
The latest news – spotted by eagle eye GIS star Jessie Braden – is that historical versions of PLUTO and MapPLUTO are now freely available, going back to 2002. Really great.
And City Planning included an important but bittersweet note at the historical download page: sweet because all of us who had to sign licenses to obtain PLUTO data are now absolved from the license restrictions, but bitter because there was no mention of the thousands of dollars each of us have had to spend unnecessarily over the years to obtain that data that is now online for free. Sigh. Here’s the note:
Note to Licensees:
DCP releases all licensees of PLUTO and MapPLUTO versions 02a through 12v2 from all license restrictions.
One thing to point out about the historical PLUTO data is to be careful if you’re hoping to compare and analyze parcels year to year. Our team at the CUNY Graduate Center tried that a few years ago, and it was painful. So many data inconsistencies and related issues. The best we were able to do was display historical land use patterns via the OASISnyc.net website (for example, look at the disappearance of industrial land use in Williamsburg from 2003 to 2010). I’d be glad to explain in more detail if anyone is interested.
Building footprint data too
Other good news for all of us who use the city’s GIS data is that it seems that building footprints are being updated on a more regular basis, and more attribute information is being added (hat tip to Pratt’s Fred Wolf for discovering it). The latest building footprint data is dated September 2013, and includes new attributes such as building height and type, and includes a supplemental data set on “historic” buildings (ie., ones that have been demolished, with date of demolition).
Agency data web portals are a beautiful thing
Thankfully the NYC Dept of City Planning staff are continuing to maintain the Bytes of the Big Apple website, where the PLUTO data is available along with many other spatial and non-spatial planning-related data sets. The Bytes pages provide essential metadata about each data set, easily accessible contact information, and context about the data sets.
All of that is missing from the city’s open data portal, which I think is a major failure with the city’s open data practices. (Someone even commented on the buildings data set noted above, asking great questions about how the building heights were calculated, and about the source of these calculations – essential information that is too often missing from data sets available through the portal, though usually included when you download the data from the agencies directly.)
As long as the data portal doesn’t undermine invaluable agency websites like Bytes of the Big Apple, and more data keeps getting freed and accessible on these agency sites, that’s a great thing. And hopefully more agencies will either continue to maintain their own online data repositories (such as the departments of Buildings, Finance, HPD, Health, and others) or launch new ones (such as MTA did a couple of years ago).
Happy holidays …
… and big kudos to the City Planning department for explicitly posting the historical PLUTO data sets!
Download away! http://www.nyc.gov/html/dcp/html/bytes/applbyte.shtml
This essential corpus of public data is now (finally!) freely accessible. According to the metadata:
Access Constraints: MapPLUTO is freely available to all New York City agencies and the public.
- Jessie Braden at Pratt Institute for pointing it out,
- 596 Acres for pressing the FOIL case with the city (and a similar effort from Muck Rock),
- The New York World for highlighting the irony of charging fees and licenses for this data,
- the NYC Transparency Working Group for pressing the city on all things opendata,
- anyone and everyone in city government who pressed for this change from the inside, and
- thanks to everyone else who helped shine a light on this ongoing failure of the city’s open data efforts — that has now been turned around!
NY1 – New York City’s 24-hour cable news channel – featured the maps in a segment they aired during the Thursday, June 20 segment of the “Road to City Hall”. We’ve posted a link to the video below:
The Graduate Center also posted a news release about the project.
JUNE 10, 2013
Today our Center for Urban Research at the Graduate Center / CUNY joined with the League of Women Voters to launch an online service so anyone can identify their elected officials in New York City.
The idea behind this “Who Represents Me” service is not new (in fact, my old team at NYPIRG’s Community Mapping Assistance Project pioneered it more than a decade ago). But now that redistricting has changed all the legislative boundaries in the city (and the City Council lines will all be new by January 2014) it seemed like the perfect time for a reprise of our Who Represents Me service from 2000, updated with new data and new technology.
How it works
Anyone can enter a street address at the “Who Represents Me” website, or if they’re using a mobile device they can tap the Use My Current Location link. The site displays a list of all city, state, and federal elected representatives (as well as NYC Community Board), an interactive map of the district and all districts nearby, contact information for local offices, and links for more information such as email addresses, individual websites, Twitter feeds, and Facebook pages of elected officials.
Users can also link to candidate information using the League’s VOTE411.org interactive voter guide. And we provide district-specific links to DecideNYC.com’s candidate summaries.
According to Mary Lou Urban, Co-President of the League of Women Voters of the City of New York,
resources like MyGovNYC.org are what it takes to make participation in government appealingly simple and is a logical approach to increasing voter participation.
We believe our Who Represents Me service will be even more popular and helpful than it was over a decade ago.
First, the League of Women Voters is providing up-to-date info for all elected officials across the city. The League keeps this information current through ongoing contact with all officials at all levels of government. Initially the League collected this data for its 2013 They Represent You brochure (which you can order here). And they’ll be providing new info periodically for the online service.
We supplemented the League’s info with data from Sunlight Foundation, the Open States project, and local websites with contact information and photographs of City Council members, state legislators, congressional representatives, and executive branch officials.
One of the best features of the service is that Who Represents Me can be embedded in anyone’s website, blog, etc. So all the advocacy groups, elected officials, media outlets, and others who use the service can widely share it and make it their own.
Anyone can use the service, Tweet about it, post it to Facebook, and/or create and share a location-specific link to the list of representatives. Just click the “LINK / EMBED” option at the top of the page and the link like the one below will automatically display the list of officials for that location:
We used a combination of cartoDB, Google Maps API, and the Twitter Bootstrap framework to add a flexible and helpful interactive map overlay to the service. Just click a thumbnail map of any district, and a new window is displayed that shows all the district boundaries for that location. Hover over the list of districts and each one is highlighted on the map. Double-click on a district in the list, and the map zooms to its extent.
Most important, you can click anywhere on the map and new districts are highlighted for that location. And the list of representatives is automatically updated when you close the map window.
So the maps — combined with the address search and current location feature — enable you to determine elected representatives literally for any and every location in the city.
“Who Represents Me: NYC” has been developed with the generous support of the New York Community Trust.
Geographic data sources for the service include:
- district boundary files for state Senate, Assembly, and Congress from the New York State redistricting task force (LATFOR) website; and
- boundary files for City Council, Community Districts, and boroughs from the NYC Dept of City Planning’s Bytes of the Big Apple website.
The geographic data representing district boundaries is hosted at cartoDB. The overall site design relies on the Twitter Bootstrap framework. We use the Google Maps API for address matching, “typeahead” address search, and basemaps.