Shapefile
Tags
Transportation, Manhattan, New York, Roads, Streets, Staten Island, Brooklyn, New York City, LION, Bronx, Highway, Richmond, Queens, Kings, transportation, LIONdistricts, Monthly
The LION file has been maintained as a major component of the Department of City Planning's Geosupport System.
LION is a single line representation of New York City streets containing address ranges and other information.
Department of City Planning
The Department of City Planning make no representation as to the accuracy of the information or its suitability for any purposes. The Department and the City disclaim any liability for errors that may be contained herein.
Extent
West | -74.260380 | East | -73.699206 |
North | 40.917691 | South | 40.485808 |
Maximum (zoomed in) | 1:5,000 |
Minimum (zoomed out) | 1:150,000,000 |
Department of City Planning
ground condition
LION is freely available to the public.
The Department of City Planning make no representation as to the accuracy of the information or its suitability for any purposes. The Department and the City disclaim any liability for errors that may be contained herein.
A node occurs wherever two or more linear features cross regardless of whether a physical intersection occurs at that point. Duplicate line segments may appear where lines are associated with non-addressable place names such as Grand Army Plaza or where alternate street names exist.
The LION file is spatially aligned with NYCMap aerial photography.
The dataset is the single line representation of New York City Streets.
Single line representation of New York City streets
DCP
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
Feature geometry.
ESRI
Coordinates defining the features.
Street or non-street feature name used for labeling.
DCP
Special Address Place name
Feature Type Code
Segment Type: This field is used to define the segment's status in relation to the horizontal topology enhancements first introduced with LION 06A.
Inclusion/Exclusion Flag: Field formerly used by DCP to identify pre-horizontal topology roadbeds in LION. This field is now used to flag selected pedestrian walkways and greenways for exclusion in the NYPD's ETL process from CSCL.
For cartographic purposes, indicates whether segment is present in the "Roadbed" layer and/or the "Generic" layer. This field is generated by a definition query of Segment Types.
Non-Pedestrian Indicator.
Traffic Direction. Code indicating the flow of traffic relative to the street segment's directionality.
Field Verified by the Dept of Transportation (DOT) in 2003 . DOT supplies regular updates.
Indicates the source of information in the Traffic Direction (TrafDir) field.
Special Address Type Code. These represent special addressing situations. Please note that alternative street names and street codes for Special Addresses other than TYPE = 'A' can be found in the fields "SAFStreetName" and "SAFStreetCode" respectively.
Face Code: A four digit number assigned to any linear geographic feature in LION. This can be either a street or non-street feature (e.g., shoreline, railroad tracks). Also a component field of a unique identifier in LION known as the LIONkey (comprised of Boro, FaceCode and SeqNum.
Sequence Number: A five digit number assigned sequentially to the street segments within a given face code. The sequence number generally increases with the directionality of the street. Also a component field of a unique identifier in LION known as the LIONkey (comprised of Boro, FaceCode and SeqNum.
Street Code is a numeric code that represents the names of New York city streets. The first digit is a borough code; the subsequent five digits are the 5-digit street code.
Local Group Code 1: A Local Group Code (LGC) is a qualifier for DCP's 5 digit street code. Each LGC value represents a group of names for the given street that are valid for that segment.
Local Group Code 2: A Local Group Code (LGC) is a qualifier for DCP's 5 digit street code. Each LGC value represents a group of names for the given street that are valid for that segment.
Local Group Code 3: A Local Group Code (LGC) is a qualifier for DCP's 5 digit street code. Each LGC value represents a group of names for the given street that are valid for that segment.
Local Group Code 4: A Local Group Code (LGC) is a qualifier for DCP's 5 digit street code. Each LGC value represents a group of names for the given street that are valid for that segment.
Local Group Code 5: A Local Group Code (LGC) is a qualifier for DCP's 5 digit street code. Each LGC value represents a group of names for the given street that are valid for that segment.
Local Group Code 6: A Local Group Code (LGC) is a qualifier for DCP's 5 digit street code. Each LGC value represents a group of names for the given street that are valid for that segment.
Local Group Code 7: A Local Group Code (LGC) is a qualifier for DCP's 5 digit street code. Each LGC value represents a group of names for the given street that are valid for that segment.
Local Group Code 8: A Local Group Code (LGC) is a qualifier for DCP's 5 digit street code. Each LGC value represents a group of names for the given street that are valid for that segment.
Local Group Code 9: A Local Group Code (LGC) is a qualifier for DCP's 5 digit street code. Each LGC value represents a group of names for the given street that are valid for that segment.
Board of Elections LGC Pointer (Domain values = 1, 2, 3, 4) indicates which LGC field (LGC1, LGC2, LGC3 or LGC4 respectively) corresponds to the name for this segment that is used for Board of Elections applications.
Segment ID: A seven digit number (right justified, zero filled) that identifies each segment of a street or a non-street feature represented in the LION file. Segment ID differs from the LIONKey (see FaceCode and SeqNum definitions) in that the former identifies a geographic entity, whereas the latter identifies a record in the LION file. In the case of a segment lying along a borough boundary (for example, the Brooklyn-Queens border), there will be two distinct LIONKeys (one for each borough), but the Segment ID in each LION record will be identical since it refers to the same physical geometry.
Coincident Segment Count: Indicates situations where there are double-decker roads and therefore more than one segment for the same geography in LION (as it is maintained in CSCL). An example would be the upper and lower roadways of the George Washington Bridge. In this case, the SegCount would be equal to 2. Most LION segments will have a SegCount of 1. However there will appear to be some anomalies because of the difference in the way LION is maintained, and the way it must be exported. For example, the Department of City Planning maintains an associated Special Address file that links various types of special address records (described further down in this document) to the LION file. In the BYTES version of LION, the only way to include these special address records is by replicating the segment with alternate address information. The result can be multiple records with the same Segment ID while the coincident segment count remains '1'.
Segment Locational Status.
Contains the five digit postal zip code for the left side of the street segment.
LION segments are not split due to zip-code changes - in the event that a LION segment has more than 1 zip code associated to the left or right side, the predominant zip code is used. No zip codes assigned to individual buildings are represented in the LION file.
Contains the five digit postal zip code for the right side of the street segment.
LION segments are not split due to zip-code changes - in the event that a LION segment has more than 1 zip code associated to the left or right side, the predominant zip code is used. No zip codes assigned to individual buildings are represented in the LION file.
This is a 1-digit code identifying the borough in which the left side of the street segment is located.
This is a 1-digit code identifying the borough in which the right side of the street segment is located.
Three-digit Community District code for the left side of the street. The first byte is the Borough Code and the second and third bytes are the Dommunity District Number (right justified, zero filled). For example, Community District 6 in Brooklyn would be represented as 306. There are 59 community districts in the City of New York, as well as 12 Joint Interest Areas (JIAs). The JIAs are major parks and airports that are not contained within any CD. For a full listing, please refer to the 'readme.txt' that is included as part of the LION file download.
Three-digit Community District code for the left side of the street. The first byte is the Borough Code and the second and third bytes are the Dommunity District Number (right justified, zero filled). For example, Community District 6 in Brooklyn would be represented as 306. There are 59 community districts in the City of New York, as well as 12 Joint Interest Areas (JIAs). The JIAs are major parks and airports that are not contained within any CD. For a full listing, please refer to the 'readme.txt' that is included as part of the LION file download.
Left Atomic Polygon: An atomic polygon is a minimal polgon formed by most LION segments (exceptions include paper streets and alleys). "Minimal" means the polygon is not subdivided by LION segments (other than the noted exceptions) into smaller polygons. An atomic polygon can contain segments of various types in its interior: paper street segments (Feature Type = 5), dead end segments (LocStatus = I), land-hooked segments (LocStatus = H) and alley segments (Feature Type = A). Atomic Polygons numbers are unique within 2010 Census Tracts and are used as building blocks for many higher geographies.
Right Atomic Polygon: An atomic polygon is a minimal polgon formed by most LION segments (exceptions include paper streets and alleys). "Minimal" means the polygon is not subdivided by LION segments (other than the noted exceptions) into smaller polygons. An atomic polygon can contain segments of various types in its interior: paper street segments (Feature Type = 5), dead end segments (LocStatus = I), land-hooked segments (LocStatus = H) and alley segments (Feature Type = A). Atomic Polygons numbers are unique within 2010 Census Tracts and are used as building blocks for many higher geographies.
Left 2010 Census Tract.
Left 2010 Census Tract Suffix.
Right 2010 Census Tract.
Right 2010 Census Tract Suffix.
Left 2010 Census Block.
Left 2010 Census Block Suffix.
Right 2010 Census Block.
Right 2010 Census Block Suffix.
Left 2000 Census Tract.
Left 2000 Census Tract Suffix.
Right 2000 Census Tract.
Right 2000 Census Tract Suffix.
Left 2000 Census Block.
Left 2000 Census Block Suffix.
Right 2000 Census Block.
Right 2000 Census Block Suffix.
Left 1990 Census Tract.
Left 1990 Census Tract Suffix.
Right 1990 Census Tract.
Right 1990 Census Tract Suffix.
Assembly District for the left side of the street.
Election District for the left side of the street. Election Districts are unique within an Assembly District.
Assembly District for the right side of the street.
Election District for the right side of the street. Election Districts are unique within an Assembly District.
Split Election District Flag. Indicates when a LION segment is split by more than one Election District.
School District for the left side of the street.
School District for the right side of the street.
Split School Flag. Indicates when a LION segment is split by more than one School District.
Sanitation District Subsection for the left side of the street. These are subareas of Sanitation Districts, which in general coincide with Community Districts, except possibly on a CD boundary (see SanDistInd).
Sanitation District Subsection for the right side of the street. These are subareas of Sanitation Districts, which in general coincide with Community Districts, except possibly on a CD boundary (see SanDistInd).
Sanitation District Boundary Indicator. Normally, sanitation routes are defined by the community district (CD) and sanitation district subsection. For some streets that divide a CD, the same route will service both sides. This indicator defines which CD will service the entire street. The Subsection (LSubSect and RSubSect) is NOT affected by the sanitation district boundary indicator.
DCP Sectional / Zoning Map at the beginning of the segment.
DCP Sectional / Zoning Map at the end of the segment.
Borough Boundary Indicator. When a segment lies along a boundary of two boroughs, it is represented by two separate LION records, one for each borough. The flag indicates which side of the segment is out of the borough.
Marble Hill/Rikers Island Flag. These are two areas of the city that legally are part of one borough, but serviced by another. In each case, these records are flagged to be generated by the alternative borough for Geosupport purposes.
X (Spatial) coordinate at the 'From' end of a segment.
Y (Spatial) coordinate at the 'From' end of a segment.
X (Spatial) coordinate at the 'To' end of a segment.
Y (Spatial) coordinate at the 'To' end of a segment.
X (Spatial) coordinate at the center of the curve.
Y (Spatial) coordinate at the center of the curve.
Indicates whether a LION record represents a straight segment, irregular curve (not a circular arc) or a regular curve (circular arc) segment. If a regular curve segment, indicates which side of the segment the curve is on.
This field contains a value only if the segment is a circular arc (i.e. regular curve), as indicated by an 'L' or an 'R' in the CurveFlag field. The value is the radius of the arc in feet, rounded to the nearest foot.
Node identifier at the low address end, or beginning of the segment.
Node identifier at the high address end, or end of the segment.
Level code indicator vertical topology at the start of the street segment.
Level code indicator vertical topology at the end of the street segment.
Continuous Parity Indicator (Domain Values = L, R). A continuous parity segment has both odd and even addresses on the same side of the segment, and no addresses on the other side. In a LION record that represents a continous parity segment, the odd and even address ranges are stored separately and the 1-byte code indicates on which side of the street the addresses physically exist.
ESRI
Twisted Parity: Occasionally, the address parities along a street switch. If a 'T' value exists in this field, it indicates that the parities have changed since the immediately preceding segment of the same street (i.e., if odd addresses were on the left, now they are on the right).
ESRI
Roadway Type
A unique ID assigned in order to aggregate granular geometry to represent a Physical View of the city's street network. In CSCL, segmentation is very granular in order to accommodate many types of physical and non-physical geometry. The Physical ID is a unique number used to identify a physically existing piece of geometry that may or may not be comprised of several Segment IDs. For example, E 28 Street between 2nd Ave and 3rd Ave in Manhattan would have 1 Physical ID although there are 3 segments defining that block face, with 3 separate Segment IDs.
A unique ID assigned in order to aggregate granular geometry to represent a Generic View of the city's street network. Streets that contain multiple carriageways or roadbeds (such as Queens Boulevard in Queens and Park Ave in Manhattan) are represented by multiple centerlines corresponding to each roadbed as well as an imaginary 'single' generic centerline.
A unique ID assigned for NYPD's use in order to aggregate granular geometry for administrative purposes.
Not currently implemented. A unique ID assigned for FDNY's use in order to aggregate granular geometry for their administrative purposes.
A ten digit number (right justified, zero filled) identifying the block face on the left hand side of a segment. Block Face is defined as one continuous side of a physical block that is intersected on that side by two other physical through streets. Blockface IDs were established by DoITT’s consultants working on the planimetric feature classes for NYC and are not maintained by the Department of City Planning.
A ten digit number (right justified, zero filled) identifying the block face on the right hand side of a segment. Block Face is defined as one continuous side of a physical block that is intersected on that side by two other physical through streets. Blockface IDs were established by DoITT’s consultants working on the planimetric feature classes for NYC and are not maintained by the Department of City Planning.
LION 09C Segment IDs which were migrated for the initial population of the CSCL. This data is captured in order to help users migrate legacy data. New geometry in the CSCL/LION will not have this field populated, however existing CSCL/LION segments will retain the legacy ID when split.
ESRI
Sequential unique whole numbers that are automatically generated.
Refers to the construction status of a street segment.
Formerly known as StreetWidth, this represents the narrowest width, in feet, of the paved area of the street. These values correspond to the StreetWidth field in Geosupport.
Not currently implemented. Flag indicating whether the street width is consistent along a street segment.
Bike Lane: Defines which segments are part of the bicycle network as defined by the Department of Transportation. These values correspond to Bike Lane 2 in Geosupport.
DSNY snow removal priority designation.
The number of lanes in a carriageway (roadway) that are designated for the movement of vehicles traveling from one destination to another. The number of travel lanes were determined by DoITT’s consultants working on the planimetric feature classes for NYC.
The number of lanes in a carriageway (roadway) that are reserved for parallel parking of vehicles. The number of parking lanes were determined by DoITT’s consultants working on the planimetric feature classes for NYC.
The total number of lanes in a carriageway (roadway) including travel lanes and parking lanes. The total number of lanes were determined by DoITT’s consultants working on the planimetric feature classes for NYC.
Cartographic Display Level: Select LION segments are flagged as a way to designate major roads for cartographic purposes at various scales.
Not currently implemented. Federal Classification Code
Right-of-Way Type: These refer only to subway and rail segments.
Low Value for the hyphenated address range beginning on the left side of the street segment. Left and right are defined relative to a street segment's direction. For streets that have addresses, the direction of a DCPLION streeet segment is determined by the direction of increasing address numbers. Note that this direction is unrelated to the street's traffic direction or its orientation relative to the points of the compass. The direction of streets with out address numbers, as well as non-street features, is assigned arbitrarily, but is consistent within the street feature. Direction can usually be determined by observing which way the SeqNum increases. Includes hyphenated addresses.
ESRI
Sequential unique whole numbers that are automatically generated.
High Value for the hyphenated address range beginning on the left side of the street segment.
ESRI
Sequential unique whole numbers that are automatically generated.
Low Value for the hyphenated address range beginning on the right side of the street segment.
ESRI
Sequential unique whole numbers that are automatically generated.
High Value for the hyphenated address range beginning on the right side of the street segment.
ESRI
Sequential unique whole numbers that are automatically generated.
Low Value for the numeric address range beginning on the left side of the street segment. For all hyphanated addresses, the hyphen has been removed. To convert the before hyphen portion of the house number is multiplied by 1000 and then added to the after hyphen portion of the house number (e.g. 101-40 would be converted to 101040).
ESRI
Sequential unique whole numbers that are automatically generated.
High Value for the numeric address range beginning on the left side of the street segment.
ESRI
Sequential unique whole numbers that are automatically generated.
Low Value for the numeric address range beginning on the right side of the street segment.
ESRI
Sequential unique whole numbers that are automatically generated.
High Value for the numeric address range beginning on the right side of the street segment.
ESRI
Positive real numbers that are automatically generated.
Identification field used to link LION feature class with Alternative Names table during a geocoding operation.
ESRI
Sequential unique whole numbers that are automatically generated.
BIKE_TRAFDIR (Bike Traffic Direction) defines bicycle traffic direction on segments that are part of the bicycle network as defined by the Department of Transportation.
ACTIVE_FLAG only applies to LION segments representing subway features. This field is being introduced with the digitization of the 2nd Avenue subway to indicate which portions are open versus under construction or proposed.
POSTED_SPEED contains the speed limit, in miles per hour, of the paved area.
Length of feature in internal units.
Esri
Positive real numbers that are automatically generated.
The maximum width, in feet, of the paved area of the street.
Left side Police Service Areas (PSAs), which provides the Housing Bureau Police services to a set of housing developments.
Right side Police Service Areas (PSAs), which provides the Housing Bureau Police services to a set of housing developments.
Segments that are part of the New York City truck route network designated by Department of Transportation for use by trucks and other commercial vehicles.