20221129
16474200
1.0
FALSE
LIONGeneric_Clip
002
912287.068792
1067382.508458
113279.346998
273617.843214
1
Projected
GCS_North_American_1983
Linear Unit: Foot_US (0.304801)
NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.0.0'><WKT>PROJCS["NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",984250.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-74.0],PARAMETER["Standard_Parallel_1",40.66666666666666],PARAMETER["Standard_Parallel_2",41.03333333333333],PARAMETER["Latitude_Of_Origin",40.16666666666666],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2263]]</WKT><XOrigin>-120039300</XOrigin><YOrigin>-96540300</YOrigin><XYScale>9999.9995250255088</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.00020000000949949029</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102718</WKID><LatestWKID>2263</LatestWKID></ProjectedCoordinateSystem>
150000000
5000
20221128
12112900
20221128
12112900
New York City Department of City Planning (DCP)
120 Broadway, 31st Floor
New York
NY
10271
DCPopendata@planning.nyc.gov
New York City Department of City Planning (DCP)
The LION file has been maintained as a major component of the Department of City Planning's Geosupport System.
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>LION is a single line representation of New York City streets containing address ranges and other information.</SPAN></P></DIV></DIV></DIV>
Department of City Planning (DCP)
LION
New York City Department of City Planning (DCP)
120 Broadway, 31st Floor
New York
NY
10271
DCPopendata@planning.nyc.gov
New York City Department of City Planning (DCP)
10/21/2022 9:03:53 AM
11/28/2022 9:03:59 AM
22C
BYTES of the BIG APPLE
22C
Streets
Roads
Roadbeds
LION
Transportation
Department of City Planning
DCP
New York City
NYC
LIONdistricts
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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.</SPAN></P></DIV></DIV></DIV>
New York City Department of City Planning (DCP)
120 Broadway, 31st Floor
New York
NY
10271
DCPopendata@planning.nyc.gov
New York City Department of City Planning (DCP)
Esri ArcGIS 13.0.2.36056
1
-74.260380
-73.699206
40.917691
40.477211
lion
Single line representation of New York City streets
DCP
Feature Class
0
OBJECTID
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
OBJECTID
OID
4
0
0
Shape
Feature geometry.
ESRI
Coordinates defining the features.
SHAPE
Geometry
0
0
0
Street
Street or non-street feature name used for labeling.
DCP
Street
String
32
0
0
SAFStreetName
Special Address Place name
SAFStreetName
String
32
0
0
FeatureTyp
Feature Type Code
0
Street other than vehicle only street.
1
Railroad
2
Water Edge / Shoreline
3
Census Block Boundary
5
Paper Street: This is a legally mapped, but unbuilt street. Such streets are common in areas of Staten Island anticipating development. May exist in all boroughs.
6
Private Street: This is a physically existing street which is not owned by the City and is not officially mapped. For example, streets in the Fort Totten and Breezy Point sections of Queens.
7
District Boundary: Physically non-existent boundary for a community district, a police precinct, or a fire company.
8
Physical Non-Street Boundary: Physically existing un-addressable boundary (such as a rock wall cemetery edge).
9
Paper Street and Census/District Boundary: A legally mapped, but unbuilt street that also acts as a census block or district boundary.
A
Alley: a narrow street or passageway between and behind city buildings.
W
Path, Non-Vehicular, Addressable: This is a walking path that contains addresses. For example, some boardwalks and some walking paths in housing projects.
C
CCO (Corporation Counsel Opinion). A CCO is an opinion by the City's Law Department that a street area, not owned by the City, has been dedicated for public use, consistent with the requirements of General City Law, Section 36(2). That allows the City to use public funds for various improvements and services, including paving of the roadway and installing sewers. The request usually relates to planned work by the City's Department of Transportation, Department of Design and Construction, and Department of Environmental Protection.
F
Ferry Route: A schematic representation of a ferry’s passage through a water body. Please note that only selected ferry routes required for the bicycle routing within NYC are included.
FeatureTyp
String
1
0
0
SegmentTyp
Segment Type: This field is used to define the segment's status in relation to the horizontal topology enhancements first introduced with LION 06A.
B
Both: Segment is both generic and roadbed; the center roadbed segment of a divided roadway containing an odd number of roadbeds.
C
Connector: Segments used to connect adjacent roadbeds of a divided street. Typically these exist to allow traffic flow from one roadbed to another.
E
Entrance/Exit Ramp: Connects a highway to a different street or highway.
F
Faux Segment: These are used when a street or ramp physically ends at a roadbed, but connectivity needs to be maintained with the generic segment.
G
Generic Segment: An imaginary single line representation of a physically divided street.
R
Roadbed Segment: Depicts physically separated carriageway segments of a particular street.
T
Terminator: Used to model situations where a divided section of a street terminates, but the street itself continues.
U
Undivided Street: All other LION segments that do not fall into any of the above categories.
S
Suppressed: Undivided segment to be suppressed in a generic view of LION
SegmentTyp
String
1
0
0
IncExFlag
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.
E
Segment should be excluded from the NYPD's ETL and from Geosupport cross street generation.
IncExFlag
String
1
0
0
RB_Layer
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.
R
Segment is unique to the Roadbed layer. Comprised of Segment Types R, C, T and S.
G
Segment unique to the Generic layer. Comprised of Segment Types G and F.
B
Segment belongs in Both the generic and roadbed layers. Comprised of Segment types U, B and E.
N
Segment is neither in the generic or roadbed layer. These are exception cases where divided roadbeds existed in the LION file prior to release 06A.
RB_Layer
String
1
0
0
NonPed
Non-Pedestrian Indicator.
D
Pedestrian accessible, but are excluded by the Department of Education in determining walking routes from a pupil's home to their school.
V
Vehicle-only: primarily roadways, inaccessible to pedestrian usage
NonPed
String
1
0
0
TrafDir
Traffic Direction. Code indicating the flow of traffic relative to the street segment's directionality.
W
With: One-way street, traffic flows with the segment's directionality, i.e., from the segment's FROM node to the TO node..
A
Against: One-way street, traffic flows from against the segment's directionality, i.e., from the segment's TO node to the FROM node.
T
Two-Way: Traffic flows in both directions.
P
Pedestrian path: Non-vehicular.
blank
Non-street feature.
Field Verified by the Dept of Transportation (DOT) in 2003 . DOT supplies regular updates.
TrafDir
String
1
0
0
TrafSrc
Indicates the source of information in the Traffic Direction (TrafDir) field.
DCP
NYC Department of City Planning
DOT
NYC Department of Transportation
TrafSrc
String
3
0
0
SpecAddr
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.
A
Alternate Address Range: Alternative address ranges for the same street name. This can occur where buildings have been renumbered; old numbers will sometimes remain in use. For example, such usage is common in some Queens neighborhoods, including Far Rockaway, Douglaston, Forest Hills and Ridgewood, where non-hyphenated addresses have been replaced by hyphenated addresses.
B
Alternative Street Names: Alternative street names that cannot be handled in the usual way.
C
Handles a unique situation along the Brooklyn-Queens border, where Ruby Street on the Brooklyn side of the street is known as 75 Street in Queens. Some Brooklyn residents use 75 Street in their address; however there is another 75 Street in the Bay Ridge section of Brooklyn, far from the Queens border.
D
Duplicate Addresses: Duplicate addresses for the same street name within the same borough. Currently, there are three New York City streets that have some duplicate addresses: Hillside Avenue and Center Drive in Queens, and Martin Luther King Junior Boulevard in Manhattan. The portion of Hillside Avenue in the Far Rockaway neighborhood has some addresses that are identicdal to addresses in the portion of Hillside Avenue in the Douglaston neighborhood. Hillside Avenue also has some addresses that are duplicated between the Douglaston and Bellerose neighborhoods. Center Drive has some addresses that are duplicated between the Douglaston and Malba neighborhoods. Martin Luther King Junior Boulevard is an alternative name for both East 125 Street and West 125 Street, and therefore has many duplicate addresses.
E
Refers to situations in which the name of a neighborhood can serve as an alternate name for all streets in that neighborhood. The two neighborhoods for which this applies are both in the Bronx: Edgewater Park and Harding Park.
G
This is used for names of complexes (e.g., Lincoln Center). Complexes are non-addressable, and are composed of a number of non-addressable place names. Complexes can include individual buildings or parks that are recognized as a grouped entity (e.g., Lincoln Center, Jefferson Houses, City College). "G" records refer to the complex names (Lincoln Center), while the entities within the complex (Alice Tully Hall, Metropolitan Opera, etc.) are flagged as type "x" records.
N
Non-Addressable Place Name: This is used for non-addressable place names. These are place names that cannot be combined with a house number to form an address. Such place names can include individual buildings (e.g., City Hall, Alice Tully Hall), building complexes (e.g., Columbia University, New York Hospital) and large facilities (e.g., Penn Station, LaGuardia Airport).
O
This is used for out-of-sequence addresses. Such addresses do not follow the logical addressing sequence of the immediately adjacent buildings. For example, address number 62 of a street may exist between addresses 80 and 82, not between 60 and 64 on that blockface (it may also appear on a blockface other than that which contains 60 and 64). Also, the address may be an opposite-parity address, in that its parity (odd/even) is the opposite of the predominant parity on the blockface. For example, address number 62 may appear on the odd side of the street between 63 and 65.
S
Suffix: This refers to situations in which the break in addresses from one block face to the next along a street involves house number suffixes. The "s" flag appears with such records to denote that a suffix exists at either the low or high end of the segment's address range. For example, if the address range on one block is 1 - 13A, and the next block is 15 - 25, the address range on the first block will be shown in LION as 1 - 13, and 13A will be an SAF type "S" record.
V
This is used for "vanity addresses" (i.e. addresses in which the street name refers to a different street than the one on which the referenced building entrance is actually located). For example, 1049 5th Avenue in Manhattan, a vanity address, is actually located on East 86th Street, between 5th Avenue and Madison Avenue.
X
This is used for names of non-addressable, consituent entities of complexes (not the entire complex name itself, which is flagged as type "G"). These are non-addressable place names grouped with other non-addressable place names to form a larger, non-addressable complex. Such non-addressable place name parts of complexes can include individual buildings or parks (e.g., Alice Tully Hall of Lincoln Center, Damrosch Park of Lincoln Center, Jefferson Houses Building 2 of Jefferson Houses, Shepard Hall of City College). To ensure that non-addressable place names are geocoded to the correct side of a street segment, the address range fields of the incorrect side of the street will contain a value of "-99999."
P
Addressable Place Names: An addressable place name is usually the name of an individual building or building complex that can serve the role of a street name in an address, even though there is no actual street with that name. Each of these can combine with address numbers to form addresses, such as 5 Penn Plaza or 13 Confucius Plaza.
SpecAddr
String
1
0
0
FaceCode
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.
FaceCode
String
4
0
0
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.
SeqNum
String
5
0
0
StreetCode
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.
StreetCode
String
6
0
0
SAFStreetCode
SAFStreetCode
String
6
0
0
LGC1
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.
LGC1
String
2
0
0
LGC2
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.
LGC2
String
2
0
0
LGC3
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.
LGC3
String
2
0
0
LGC4
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.
LGC4
String
2
0
0
LGC5
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.
LGC5
String
2
0
0
LGC6
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.
LGC6
String
2
0
0
LGC7
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.
LGC7
String
2
0
0
LGC8
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.
LGC8
String
2
0
0
LGC9
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.
LGC9
String
2
0
0
BOE_LGC
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.
BOE_LGC
String
1
0
0
SegmentID
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.
SegmentID
String
7
0
0
SegCount
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'.
SegCount
String
1
0
0
LocStatus
Segment Locational Status.
H
Land-hooked segment, i.e. a segment internal to a Dynamic Block but not a dead end.
I
Dead end segment
X
Tract Boundary segment other than a borough boundary
1
Segment bordering Manhattan
2
Segment bordering The Bronx
3
Segment bordering Brooklyn
4
Segment bordering Queens
5
Segment bordering Staten Island
9
Segment on the New York City Boundary
LocStatus
String
1
0
0
LZip
Contains the five digit postal zip code for the left side of the street segment.
Low
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.
LZip
String
5
0
0
RZip
Contains the five digit postal zip code for the right side of the street segment.
low
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.
RZip
String
5
0
0
LBoro
This is a 1-digit code identifying the borough in which the left side of the street segment is located.
1
Manhattan
2
The Bronx
3
Brooklyn
4
Queens
5
Staten Island
LBoro
Integer
4
0
0
RBoro
This is a 1-digit code identifying the borough in which the right side of the street segment is located.
1
Manhattan
2
The Bronx
3
Brooklyn
4
Queens
5
Staten Island
RBoro
Integer
4
0
0
L_CD
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.
L_CD
String
3
0
0
R_CD
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.
R_CD
String
3
0
0
LATOMICPOLYGON
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.
LATOMICPOLYGON
String
3
0
0
RATOMICPOLYGON
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.
RATOMICPOLYGON
String
3
0
0
LCT2010
Left 2010 Census Tract.
LCT2010
String
4
0
0
LCT2010Suf
Left 2010 Census Tract Suffix.
LCT2010Suf
String
2
0
0
RCT2010
Right 2010 Census Tract.
RCT2010
String
4
0
0
RCT2010Suf
Right 2010 Census Tract Suffix.
RCT2010Suf
String
2
0
0
LCB2010
Left 2010 Census Block.
LCB2010
String
4
0
0
LCB2010Suf
Left 2010 Census Block Suffix.
LCB2010Suf
String
1
0
0
RCB2010
Right 2010 Census Block.
RCB2010
String
4
0
0
RCB2010Suf
Right 2010 Census Block Suffix.
RCB2010Suf
String
1
0
0
LCT2000
Left 2000 Census Tract.
LCT2000
String
4
0
0
LCT2000Suf
Left 2000 Census Tract Suffix.
LCT2000Suf
String
2
0
0
RCT2000
Right 2000 Census Tract.
RCT2000
String
4
0
0
RCT2000Suf
Right 2000 Census Tract Suffix.
RCT2000Suf
String
2
0
0
LCB2000
Left 2000 Census Block.
LCB2000
String
4
0
0
LCB2000Suf
Left 2000 Census Block Suffix.
LCB2000Suf
String
1
0
0
RCB2000
Right 2000 Census Block.
RCB2000
String
4
0
0
RCB2000Suf
Right 2000 Census Block Suffix.
RCB2000Suf
String
1
0
0
LCT1990
Left 1990 Census Tract.
LCT1990
String
4
0
0
LCT1990Suf
Left 1990 Census Tract Suffix.
LCT1990Suf
String
2
0
0
RCT1990
Right 1990 Census Tract.
RCT1990
String
4
0
0
RCT1990Suf
Right 1990 Census Tract Suffix.
RCT1990Suf
String
2
0
0
LAssmDist
Assembly District for the left side of the street.
LAssmDist
String
2
0
0
LElectDist
Election District for the left side of the street. Election Districts are unique within an Assembly District.
LElectDist
String
3
0
0
RAssmDist
Assembly District for the right side of the street.
RAssmDist
String
2
0
0
RElectDist
Election District for the right side of the street. Election Districts are unique within an Assembly District.
RElectDist
String
3
0
0
SplitElect
Split Election District Flag. Indicates when a LION segment is split by more than one Election District.
blank
Neither side of segment is split among two or more election districts
B
Both sides of segment are split among two or more election districts
L
Left side of segment is split
R
Right side of segment is split.
SplitElect
String
1
0
0
LSchlDist
School District for the left side of the street.
LSchlDist
String
2
0
0
RSchlDist
School District for the right side of the street.
RSchlDist
String
2
0
0
SplitSchl
Split School Flag. Indicates when a LION segment is split by more than one School District.
blank
Neither side of segment is split among two or more election districts
B
Both sides of segment are split among two or more election districts
L
Left side of segment is split
R
Right side of segment is split
SplitSchl
String
1
0
0
LSubSect
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).
LSubSect
String
2
0
0
RSubSect
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).
RSubSect
String
2
0
0
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.
L
Left: For both sides of the street, the sanitation district is defined using the CD on the left side of the street.
R
Right: For both sides of the street, the sanitation district is defined using the CD on the right side of the street.
blank
The sanitation district route for each side of the street is correctly identified using the CD and subsection fields for the corresponding side of the street.
SanDistInd
String
1
0
0
MapFrom
DCP Sectional / Zoning Map at the beginning of the segment.
MapFrom
String
3
0
0
MapTo
DCP Sectional / Zoning Map at the end of the segment.
MapTo
String
3
0
0
BoroBndry
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.
BoroBndry
String
1
0
0
MH_RI_Flag
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.
MH_RI_Flag
String
1
0
0
XFrom
X (Spatial) coordinate at the 'From' end of a segment.
XFrom
Integer
4
0
0
YFrom
Y (Spatial) coordinate at the 'From' end of a segment.
YFrom
Integer
4
0
0
XTo
X (Spatial) coordinate at the 'To' end of a segment.
XTo
Integer
4
0
0
YTo
Y (Spatial) coordinate at the 'To' end of a segment.
YTo
Integer
4
0
0
ArcCenterX
X (Spatial) coordinate at the center of the curve.
ArcCenterX
Integer
4
0
0
ArcCenterY
Y (Spatial) coordinate at the center of the curve.
ArcCenterY
Integer
4
0
0
CurveFlag
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.
blank
LION record represents a straight line segment
I
LION record represent an irregularly curved segment (not a circular arc)
L
LION record represents a curved segment consisting of a circular arc lying on the left side of the segment's directed chord.
R
LION record represents a curved segment consisting of a circular arc lying on the right side of the segment's directed chord.
CurveFlag
String
1
0
0
Radius
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.
Radius
Integer
4
0
0
NodeIDFrom
Node identifier at the low address end, or beginning of the segment.
NodeIDFrom
String
7
0
0
NodeIDTo
Node identifier at the high address end, or end of the segment.
NodeIDTo
String
7
0
0
NodeLevelF
Level code indicator vertical topology at the start of the street segment.
A-Z
Relative level code on a scale where A is the lowest level of subterranean, M is ground level and Z is highest elevated level.
*
Level-less feature associated with node. The asterisk is used to indicate the level-code on non-physical geometry, such as generic roadbed segments. Since these are non-physical, there is no 'real' level code that can be associated.
$
Shoreline / water level.
NodeLevelF
String
1
0
0
NodeLevelT
Level code indicator vertical topology at the end of the street segment.
A-Z
Relative level code on a scale where A is the lowest level of subterranean, M is ground level and Z is highest elevated level.
*
Level-less feature associated with node. The asterisk is used to indicate the level-code on non-physical geometry, such as generic roadbed segments. Since these are non-physical, there is no 'real' level code that can be associated.
$
Shoreline / water level.
NodeLevelT
String
1
0
0
ConParity
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
L
Odd and Even house number are bothe on the left side of the segment.
R
Odd and Even house number are bothe on the right side of the segment.
ConParity
String
1
0
0
Twisted
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
T
Indicates that the address parities along a street have switched since the immediately preceding segment of the same street (i.e., if odd addresses were on the left, they are now on the right).
Twisted
String
1
0
0
RW_TYPE
Roadway Type
1
Street
2
Highway
3
Bridge
4
Tunnel
5
Boardwalk
6
Path/Trail
7
Step Street
8
Driveway
9
Ramp
10
Alley
11
Unknown
12
Non-Physical Street Segment
13
U-Turn
14
Ferry Route
RW_TYPE
String
2
0
0
PhysicalID
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.
PhysicalID
Integer
4
0
0
GenericID
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.
GenericID
Integer
4
0
0
NYPDID
A unique ID assigned for NYPD's use in order to aggregate granular geometry for administrative purposes.
NYPDID
String
7
0
0
FDNYID
Not currently implemented. A unique ID assigned for FDNY's use in order to aggregate granular geometry for their administrative purposes.
Not currently implemented.
FDNYID
String
7
0
0
LBlockFaceID
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.
LBlockFaceID
String
10
0
0
RBlockFaceID
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.
RBlockFaceID
String
10
0
0
LegacyID
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.
LegacyID
String
7
0
0
Status
Refers to the construction status of a street segment.
1
Planned Private
2
Constructed
3
Paper
4
Under Construction
5
Demapped
9
Paper Street Coincident with Boundary
Status
String
1
0
0
StreetWidth_Min
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.
StreetWidth
Double
8
0
0
StreetWidth_Irr
Not currently implemented. Flag indicating whether the street width is consistent along a street segment.
Not currently implemented.
StreetWidth_Irr
String
1
0
0
BikeLane
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.
1
Class 1: Separated Greenway
2
Class II: Striped Bike Lane
3
Class III: Signed Bicycle Route
4
Links: Connecting segments.
5
Class I, II: Combination of Class I and II
6
Class II, III: Combination of Class II and III
7
Stairs: Includes step streets, bridge stairs, etc.
8
Class I, III: Combination of Class I and III
9
Class II, I: Combination of Class II and I
10
Class III, I: Combination of Class III and I
11
Class III, II: Combination of Class III and II
BikeLane
String
2
0
0
Snow_Priority
DSNY snow removal priority designation.
blank
unknown
C
Critical: These routes are comprised of highways (main beds, entrances, exits, interchanges), arterial roadways, main travel thoroughfares (single land and multi-lane), bus routes, that contain emergency services and first responder facilities (Hospitals, EMS, FDNY, NYPD) and schools.
S
Sector: Designed to encompass all streets that are not classified as Critical Streets and are awide enough to accommodate a full size DSNY collection truck with a plow attached.
H
Haulster: Designed to service dead ends and streets that cannot be serviced with a collection truck or salt spreader with a plow attached due to narrow street width or tight turning radius (either entering or exiting the street).
V
Non-DSNY
Snow_Priority
String
1
0
0
Number_Travel_Lanes
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.
Number_Travel_Lanes
String
2
0
0
Number_Park_Lanes
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.
Number_Park_Lanes
String
2
0
0
Number_Total_Lanes
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.
Number_Total_Lanes
String
2
0
0
Carto_Display_Level
Cartographic Display Level: Select LION segments are flagged as a way to designate major roads for cartographic purposes at various scales.
10
City
20
Borough
30
Neighborhood
Carto_Display_Level
String
20
0
0
FCC
Not currently implemented. Federal Classification Code
Not currently implemented.
FCC
String
2
0
0
ROW_Type
Right-of-Way Type: These refer only to subway and rail segments.
1
Subterranean
2
Elevated
3
Surface
4
Hidden
5
Open Cut Depression
6
Embankment
7
Viaduct
8
Subterranean Coincident with Boundary
ROW_Type
String
1
0
0
LLo_Hyphen
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.
LLo_Hyphen
String
7
0
0
LHi_Hyphen
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.
LHi_Hyphen
String
7
0
0
RLo_Hyphen
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.
RLo_Hyphen
String
7
0
0
RHi_Hyphen
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.
RHi_Hyphen
String
7
0
0
FromLeft
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.
FromLeft
Integer
4
0
0
ToLeft
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.
ToLeft
Integer
4
0
0
FromRight
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.
FromRight
Integer
4
0
0
ToRight
High Value for the numeric address range beginning on the right side of the street segment.
ESRI
Positive real numbers that are automatically generated.
ToRight
Integer
4
0
0
Join_ID
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.
Join_ID
String
15
0
0
BIKE_TRAFDIR
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.
blank
This segment is not part of the bicycle network as defined by the Department of Transportation.
FT
Bike traffic is one way. The bike traffic flow is with the direction of increasing addresses, if any. This direction is also known as ‘with’ the segment’s logical direction, i.e. from the FROM node to the TO node.
TF
Bike traffic is one way. The bike traffic flow is against the direction of increasing addresses, if any. This direction is also known as ‘against’ the segment’s logical direction, i.e. from the TO node to the FROM node.
TW
Bike traffic is two way. Bicycles travel in both directions.
BIKE_TRAFDIR
String
2
0
0
ACTIVE_FLAG
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.
Y
This portion of the subway is active and open.
N
This portion of the subway is inactive, i.e. either under construction or proposed.
NULL
This segment does not represent a subway feature.
Active_Flag
String
1
0
0
POSTED_SPEED
POSTED_SPEED contains the speed limit, in miles per hour, of the paved area.
POSTED_SPEED
String
2
0
0
SHAPE_Length
Length of feature in internal units.
Esri
Positive real numbers that are automatically generated.
SHAPE_Length
Double
8
0
0
StreetWidth_Max
The maximum width, in feet, of the paved area of the street.
StreetWidth_Max
Double
8
0
0
L_PD_Service_Area
Left side Police Service Areas (PSAs), which provides the Housing Bureau Police services to a set of housing developments.
L_PD_Service_Area
String
1
0
0
R_PD_Service_Area
Right side Police Service Areas (PSAs), which provides the Housing Bureau Police services to a set of housing developments.
R_PD_Service_Area
String
1
0
0
TRUCK_ROUTE_TYPE
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.
1
Limited Local
2
Local
3
Through
Truck_Route_Type
String
1
0
0
LCT2020
Left 2020 Census Tract.
String
4
LCT2020
0
0
LCT2020Suf
Left 2020 Census Tract Suffix.
String
2
LCT2020Suf
0
0
RCT2020
Right 2010 Census Tract.
String
4
RCT2020
0
0
RCT2020Suf
Right 2010 Census Tract Suffix.
String
2
RCT2020Suf
0
0
LCB2020
Left 2020 Census Block.
LCB2020
String
4
0
0
LCB2020Suf
Left 2020 Census Block Suffix.
String
2
LCB2020Suf
0
0
RCB2020
Right 2020 Census Block.
String
4
RCB2020
0
0
RCB2020Suf
Right 2020 Census Block Suffix.
String
2
RCB2020Suf
0
0
File Geodatabase Feature Class
dataset
EPSG
5.3(9.0.0)
0
Simple
FALSE
0
TRUE
FALSE
20221128