LION

Shapefile

Tags
Transportation, Manhattan, New York, Roads, Streets, Staten Island, Brooklyn, New York City, LION, Bronx, Highway, Richmond, Queens, Kings, transportation, LIONdistricts, Monthly


Summary

The LION file has been maintained as a major component of the Department of City Planning's Geosupport System.

Description

            

LION is a single line representation of New York City streets containing address ranges and other information.

Credits

Department of City Planning

Use limitations

            

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

Scale Range
Maximum (zoomed in)  1:5,000
Minimum (zoomed out)  1:150,000,000

ArcGIS Metadata 

Topics and Keywords 

Themes or categories of the resource  transportation


*Content type  Downloadable Data


Place keywords  Manhattan, New York, Staten Island, Brooklyn, New York City, Bronx, Richmond, Queens, Kings

Theme keywords  Transportation, Roads, Streets, LION, Highway, transportation

Citation 

Title LION
Publication date 12/3/2020 3:52:44 PM
Indeterminate date unknown
Creation date 10/19/2020 3:52:21 PM


Edition 20D


Presentation formats  digital map


Series
Name BYTES of the BIG APPLE
Issue 20D

Citation Contacts 

Responsible party
Organization's name City of New York Department of City Planning
Contact's role  originator


Responsible party
Organization's name New York City Dept. of City Planning
Contact's role  publisher


Contact information
Address
Delivery point New York City



Resource Details 

Dataset languages  English (UNITED STATES)
Dataset character set  utf8 - 8 bit UCS Transfer Format


Status  completed
Spatial representation type  vector


Processing environment Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.3.1.4959


Credits
Department of City Planning

ArcGIS item properties
*Name lion
Location withheld
*Access protocol Local Area Network

Extents 

Extent
Description
ground condition

Geographic extent
Bounding rectangle
West longitude -74.26038
East longitude -73.699206
South latitude 40.485808
North latitude 40.917691

Extent
Geographic extent
Bounding rectangle
Extent type  Extent used for searching
*West longitude -74.260380
*East longitude -73.699206
*North latitude 40.917691
*South latitude 40.485808
*Extent contains the resource Yes

Extent in the item's coordinate system
*West longitude 912287.068792
*East longitude 1067382.508458
*South latitude 116411.371447
*North latitude 273617.843214
*Extent contains the resource Yes

Resource Points of Contact 

Point of contact
Organization's name Department of City Planning
Contact's role  point of contact


Contact information
Address
Type both
Delivery point 120 Broadway, 31st Floor
City New York
Administrative area NY
Postal code 10271
Country US



Resource Maintenance 

Resource maintenance
Update frequency  quarterly


Resource Constraints 

Legal constraints
Other constraints
LION is freely available to the public.

Constraints
Limitations of use
                  

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.


Spatial Reference 

ArcGIS coordinate system
*Type Projected
*Geographic coordinate reference GCS_North_American_1983
*Projection NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet
*Coordinate reference details
Projected coordinate system
Well-known identifier 102718
X origin -120039300
Y origin -96540300
XY scale 9999.9995250255088
Z origin -100000
Z scale 10000
M origin -100000
M scale 10000
XY tolerance 0.00020000000949949029
Z tolerance 0.001
M tolerance 0.001
High precision true
Latest well-known identifier 2263
Well-known text 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]]

Reference system identifier
Value 2263
Codespace EPSG
Version 7.11.2


Spatial Data Properties 

Vector
*Level of topology for this dataset  geometry only


Geometric objects
Feature class name lion
*Object type  composite
*Object count 229873



ArcGIS Feature Class Properties
Feature class name lion
*Feature type Simple
*Geometry type Polyline
*Has topology FALSE
*Feature count 229873
*Spatial index TRUE
*Linear referencing FALSE



Data Quality 

Scope of quality information
Resource level  dataset




Data quality report - Conceptual consistency
Measure description
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.





Data quality report - Absolute external positional accuracy
Dimension horizontal


Measure description
The LION file is spatially aligned with NYCMap aerial photography.





Lineage 

Lineage statement
The dataset is the single line representation of New York City Streets.

Distribution 

Distributor
Contact information
Organization's name New York City Dept. of City Planning
Contact's role  distributor


Contact information
Address
Type both
Delivery point 120 Broadway, 31st Floor
City New York
Administrative area NY
Postal code 10271
Country US





Distribution format
Name Shapefile
Version 16D


Transfer options
Online source
Location https://www1.nyc.gov/site/planning/data-maps/open-data.page

Fields 

Details for object lion 
Type Feature Class
Row count 218349
Definition
Single line representation of New York City streets

Definition source
DCP



Field OBJECTID
 
Alias OBJECTID
Data type OID
Width 4
Precision 0
Scale 0
Field description
Internal feature number.

Description source
Esri

Description of values
Sequential unique whole numbers that are automatically generated.





Field Shape
 
Alias Shape
Data type Geometry
Width 0
Precision 0
Scale 0
Field description
Feature geometry.

Description source
ESRI

Description of values
Coordinates defining the features.





Field Street
 
Alias Street
Data type String
Width 32
Precision 0
Scale 0
Field description
Street or non-street feature name used for labeling.

Description source
DCP



Field SAFStreetName
 
Alias SAFStreetName
Data type String
Width 32
Precision 0
Scale 0
Field description
Special Address Place name



Field FeatureTyp
 
Alias FeatureTyp
Data type String
Width 1
Precision 0
Scale 0
Field description
Feature Type Code

List of values
Value 0
Description Street other than vehicle only street.


Value 1
Description Railroad


Value 2
Description Water Edge / Shoreline


Value 3
Description Census Block Boundary


Value 5
Description 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.


Value 6
Description 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.


Value 7
Description District Boundary: Physically non-existent boundary for a community district, a police precinct, or a fire company.


Value 8
Description Physical Non-Street Boundary: Physically existing un-addressable boundary (such as a rock wall cemetery edge).


Value 9
Description Paper Street and Census/District Boundary: A legally mapped, but unbuilt street that also acts as a census block or district boundary.


Value A
Description Alley: a narrow street or passageway between and behind city buildings.


Value W
Description Path, Non-Vehicular, Addressable: This is a walking path that contains addresses. For example, some boardwalks and some walking paths in housing projects.


Value C
Description 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.


Value F
Description 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.




Field SegmentTyp
 
Alias SegmentTyp
Data type String
Width 1
Precision 0
Scale 0
Field description
Segment Type:  This field is used to define the segment's status in relation to the horizontal topology enhancements first introduced with LION 06A.

List of values
Value B
Description Both: Segment is both generic and roadbed; the center roadbed segment of a divided roadway containing an odd number of roadbeds.


Value C
Description Connector: Segments used to connect adjacent roadbeds of a divided street. Typically these exist to allow traffic flow from one roadbed to another.


Value E
Description Entrance/Exit Ramp: Connects a highway to a different street or highway.


Value F
Description 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.


Value G
Description Generic Segment: An imaginary single line representation of a physically divided street.


Value R
Description Roadbed Segment: Depicts physically separated carriageway segments of a particular street.


Value T
Description Terminator: Used to model situations where a divided section of a street terminates, but the street itself continues.


Value U
Description Undivided Street: All other LION segments that do not fall into any of the above categories.


Value S
Description Suppressed: Undivided segment to be suppressed in a generic view of LION




Field IncExFlag
 
Alias IncExFlag
Data type String
Width 1
Precision 0
Scale 0
Field description
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.

List of values
Value E
Description Segment should be excluded from the NYPD's ETL and from Geosupport cross street generation.




Field RB_Layer
 
Alias RB_Layer
Data type String
Width 1
Precision 0
Scale 0
Field description
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.

List of values
Value R
Description Segment is unique to the Roadbed layer. Comprised of Segment Types R, C, T and S.


Value G
Description Segment unique to the Generic layer. Comprised of Segment Types G and F.


Value B
Description Segment belongs in Both the generic and roadbed layers. Comprised of Segment types U, B and E.


Value N
Description 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.




Field NonPed
 
Data type String
Width 1
Precision 0
Scale 0
*Alias NonPed
Field description
Non-Pedestrian Indicator.

List of values
Value D
Description Pedestrian accessible, but are excluded by the Department of Education in determining walking routes from a pupil's home to their school.


Value V
Description Vehicle-only: primarily roadways, inaccessible to pedestrian usage




Field TrafDir
 
Alias TrafDir
Data type String
Width 1
Precision 0
Scale 0
Field description
Traffic Direction. Code indicating the flow of traffic relative to the street segment's directionality.

List of values
Value W
Description With: One-way street, traffic flows with the segment's directionality, i.e., from the segment's FROM node to the TO node..


Value A
Description Against: One-way street, traffic flows from against the segment's directionality, i.e., from the segment's TO node to the FROM node.


Value T
Description Two-Way: Traffic flows in both directions.


Value P
Description Pedestrian path: Non-vehicular.


Value blank
Description Non-street feature.


Accuracy information
Explanation
Field Verified by the Dept of Transportation (DOT) in 2003 .  DOT supplies regular updates.



Field TrafSrc
 
Alias TrafSrc
Data type String
Width 3
Precision 0
Scale 0
Field description
Indicates the source of information in the Traffic Direction (TrafDir) field.

List of values
Value DCP
Description NYC Department of City Planning


Value DOT
Description NYC Department of Transportation




Field SpecAddr
 
Alias SpecAddr
Data type String
Width 1
Precision 0
Scale 0
Field description
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.

List of values
Value A
Description 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.


Value B
Description Alternative Street Names: Alternative street names that cannot be handled in the usual way.


Value C
Description 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.


Value D
Description 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.


Value E
Description 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.


Value G
Description 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.


Value N
Description 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).


Value O
Description 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.


Value S
Description 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.


Value V
Description 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.


Value X
Description 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."


Value P
Description 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.




Field FaceCode
 
Alias FaceCode
Data type String
Width 4
Precision 0
Scale 0
Field description
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.



Field SeqNum
 
Alias SeqNum
Data type String
Width 5
Precision 0
Scale 0
Field description
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.



Field StreetCode
 
Alias StreetCode
Data type String
Width 6
Precision 0
Scale 0
Field description
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.



Field SAFStreetCode
 
Alias SAFStreetCode
Data type String
Width 6
Precision 0
Scale 0




Field LGC1
 
Alias LGC1
Data type String
Width 2
Precision 0
Scale 0
Field description
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.



Field LGC2
 
Alias LGC2
Data type String
Width 2
Precision 0
Scale 0
Field description
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.



Field LGC3
 
Alias LGC3
Data type String
Width 2
Precision 0
Scale 0
Field description
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.



Field LGC4
 
Alias LGC4
Data type String
Width 2
Precision 0
Scale 0
Field description
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.



Field LGC5
 
Alias LGC5
Data type String
Width 2
Precision 0
Scale 0
Field description
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.



Field LGC6
 
Alias LGC6
Data type String
Width 2
Precision 0
Scale 0
Field description
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.



Field LGC7
 
Alias LGC7
Data type String
Width 2
Precision 0
Scale 0
Field description
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.



Field LGC8
 
Alias LGC8
Data type String
Width 2
Precision 0
Scale 0
Field description
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.



Field LGC9
 
Alias LGC9
Data type String
Width 2
Precision 0
Scale 0
Field description
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.



Field BOE_LGC
 
Alias BOE_LGC
Data type String
Width 1
Precision 0
Scale 0
Field description
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.



Field SegmentID
 
Alias SegmentID
Data type String
Width 7
Precision 0
Scale 0
Field description
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.



Field SegCount
 
Alias SegCount
Data type String
Width 1
Precision 0
Scale 0
Field description
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'.



Field LocStatus
 
Alias LocStatus
Data type String
Width 1
Precision 0
Scale 0
Field description
Segment Locational Status.

List of values
Value H
Description Land-hooked segment, i.e. a segment internal to a Dynamic Block but not a dead end.


Value I
Description Dead end segment


Value X
Description Tract Boundary segment other than a borough boundary


Value 1
Description Segment bordering Manhattan


Value 2
Description Segment bordering The Bronx


Value 3
Description Segment bordering Brooklyn


Value 4
Description Segment bordering Queens


Value 5
Description Segment bordering Staten Island


Value 9
Description Segment on the New York City Boundary




Field LZip
 
Alias LZip
Data type String
Width 5
Precision 0
Scale 0
Field description
Contains the five digit postal zip code for the left side of the street segment.

Accuracy information
Accuracy Low
Explanation
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.



Field RZip
 
Alias RZip
Data type String
Width 5
Precision 0
Scale 0
Field description
Contains the five digit postal zip code for the right side of the street segment.

Accuracy information
Accuracy low
Explanation
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.



Field LBoro
 
Alias LBoro
Data type Integer
Width 9
Precision 9
Scale 0
Field description
This is a 1-digit code identifying the borough in which the left side of the street segment is located.

List of values
Value 1
Description Manhattan


Value 2
Description The Bronx


Value 3
Description Brooklyn


Value 4
Description Queens


Value 5
Description Staten Island




Field RBoro
 
Alias RBoro
Data type Integer
Width 9
Precision 9
Scale 0
Field description
This is a 1-digit code identifying the borough in which the right side of the street segment is located.

List of values
Value 1
Description Manhattan


Value 2
Description The Bronx


Value 3
Description Brooklyn


Value 4
Description Queens


Value 5
Description Staten Island




Field L_CD
 
Alias L_CD
Data type String
Width 3
Precision 0
Scale 0
Field description
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.



Field R_CD
 
Alias R_CD
Data type String
Width 3
Precision 0
Scale 0
Field description
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.



Field LATOMICPOLYGON
 
Alias LATOMICPOLYGON
Data type String
Width 3
Precision 0
Scale 0
Field description
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.



Field RATOMICPOLYGON
 
Alias RATOMICPOLYGON
Data type String
Width 3
Precision 0
Scale 0
Field description
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.



Field LCT2010
 
Alias LCT2010
Data type String
Width 4
Precision 0
Scale 0
Field description
Left 2010 Census Tract.



Field LCT2010Suf
 
Alias LCT2010Suf
Data type String
Width 2
Precision 0
Scale 0
Field description
Left 2010 Census Tract Suffix.



Field RCT2010
 
Alias RCT2010
Data type String
Width 4
Precision 0
Scale 0
Field description
Right 2010 Census Tract.



Field RCT2010Suf
 
Alias RCT2010Suf
Data type String
Width 2
Precision 0
Scale 0
Field description
Right 2010 Census Tract Suffix.



Field LCB2010
 
Alias LCB2010
Data type String
Width 4
Precision 0
Scale 0
Field description
Left 2010 Census Block.



Field LCB2010Suf
 
Alias LCB2010Suf
Data type String
Width 1
Precision 0
Scale 0
Field description
Left 2010 Census Block Suffix.



Field RCB2010
 
Alias RCB2010
Data type String
Width 4
Precision 0
Scale 0
Field description
Right 2010 Census Block.



Field RCB2010Suf
 
Alias RCB2010Suf
Data type String
Width 1
Precision 0
Scale 0
Field description
Right 2010 Census Block Suffix.



Field LCT2000
 
Alias LCT2000
Data type String
Width 4
Precision 0
Scale 0
Field description
Left 2000 Census Tract.



Field LCT2000Suf
 
Alias LCT2000Suf
Data type String
Width 2
Precision 0
Scale 0
Field description
Left 2000 Census Tract Suffix.



Field RCT2000
 
Alias RCT2000
Data type String
Width 4
Precision 0
Scale 0
Field description
Right 2000 Census Tract.



Field RCT2000Suf
 
Alias RCT2000Suf
Data type String
Width 2
Precision 0
Scale 0
Field description
Right 2000 Census Tract Suffix.



Field LCB2000
 
Alias LCB2000
Data type String
Width 4
Precision 0
Scale 0
Field description
Left 2000 Census Block.



Field LCB2000Suf
 
Alias LCB2000Suf
Data type String
Width 1
Precision 0
Scale 0
Field description
Left 2000 Census Block Suffix.



Field RCB2000
 
Alias RCB2000
Data type String
Width 4
Precision 0
Scale 0
Field description
Right 2000 Census Block.



Field RCB2000Suf
 
Alias RCB2000Suf
Data type String
Width 1
Precision 0
Scale 0
Field description
Right 2000 Census Block Suffix.



Field LCT1990
 
Alias LCT1990
Data type String
Width 4
Precision 0
Scale 0
Field description
Left 1990 Census Tract.



Field LCT1990Suf
 
Alias LCT1990Suf
Data type String
Width 2
Precision 0
Scale 0
Field description
Left 1990 Census Tract Suffix.



Field RCT1990
 
Alias RCT1990
Data type String
Width 4
Precision 0
Scale 0
Field description
Right 1990 Census Tract.



Field RCT1990Suf
 
Alias RCT1990Suf
Data type String
Width 2
Precision 0
Scale 0
Field description
Right 1990 Census Tract Suffix.



Field LAssmDist
 
Alias LAssmDist
Data type String
Width 2
Precision 0
Scale 0
Field description
Assembly District for the left side of the street.



Field LElectDist
 
Alias LElectDist
Data type String
Width 3
Precision 0
Scale 0
Field description
Election District for the left side of the street.  Election Districts are unique within an Assembly District.



Field RAssmDist
 
Alias RAssmDist
Data type String
Width 2
Precision 0
Scale 0
Field description
Assembly District for the right side of the street.



Field RElectDist
 
Alias RElectDist
Data type String
Width 3
Precision 0
Scale 0
Field description
Election District for the right side of the street.  Election Districts are unique within an Assembly District.



Field SplitElect
 
Alias SplitElect
Data type String
Width 1
Precision 0
Scale 0
Field description
Split Election District Flag. Indicates when a LION segment is split by more than one Election District.

List of values
Value blank
Description Neither side of segment is split among two or more election districts


Value B
Description Both sides of segment are split among two or more election districts


Value L
Description Left side of segment is split


Value R
Description Right side of segment is split.




Field LSchlDist
 
Alias LSchlDist
Data type String
Width 2
Precision 0
Scale 0
Field description
School District for the left side of the street.



Field RSchlDist
 
Alias RSchlDist
Data type String
Width 2
Precision 0
Scale 0
Field description
School District for the right side of the street.



Field SplitSchl
 
Alias SplitSchl
Data type String
Width 1
Precision 0
Scale 0
Field description
Split School Flag. Indicates when a LION segment is split by more than one School District.

List of values
Value blank
Description Neither side of segment is split among two or more election districts


Value B
Description Both sides of segment are split among two or more election districts


Value L
Description Left side of segment is split


Value R
Description Right side of segment is split




Field LSubSect
 
Alias LSubSect
Data type String
Width 2
Precision 0
Scale 0
Field description
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).



Field RSubSect
 
Alias RSubSect
Data type String
Width 2
Precision 0
Scale 0
Field description
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).



Field SanDistInd
 
Alias SanDistInd
Data type String
Width 1
Precision 0
Scale 0
Field description
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.

List of values
Value L
Description Left: For both sides of the street, the sanitation district is defined using the CD on the left side of the street.


Value R
Description Right: For both sides of the street, the sanitation district is defined using the CD on the right side of the street.


Value blank
Description 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.




Field MapFrom
 
Alias MapFrom
Data type String
Width 3
Precision 0
Scale 0
Field description
DCP Sectional / Zoning Map at the beginning of the segment.



Field MapTo
 
Alias MapTo
Data type String
Width 3
Precision 0
Scale 0
Field description
DCP Sectional / Zoning Map at the end of the segment.



Field BoroBndry
 
Alias BoroBndry
Data type String
Width 1
Precision 0
Scale 0
Field description
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.



Field MH_RI_Flag
 
Alias MH_RI_Flag
Data type String
Width 1
Precision 0
Scale 0
Field description
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.



Field XFrom
 
Alias XFrom
Data type Integer
Width 9
Precision 9
Scale 0
Field description
X (Spatial) coordinate at the 'From' end of a segment.



Field YFrom
 
Alias YFrom
Data type Integer
Width 9
Precision 9
Scale 0
Field description
Y (Spatial) coordinate at the 'From' end of a segment.



Field XTo
 
Alias XTo
Data type Integer
Width 9
Precision 9
Scale 0
Field description
X (Spatial) coordinate at the 'To' end of a segment.



Field YTo
 
Alias YTo
Data type Integer
Width 9
Precision 9
Scale 0
Field description
Y (Spatial) coordinate at the 'To' end of a segment.



Field ArcCenterX
 
Alias ArcCenterX
Data type Integer
Width 9
Precision 9
Scale 0
Field description
X (Spatial) coordinate at the center of the curve.



Field ArcCenterY
 
Alias ArcCenterY
Data type Integer
Width 9
Precision 9
Scale 0
Field description
Y (Spatial) coordinate at the center of the curve.



Field CurveFlag
 
Alias CurveFlag
Data type String
Width 1
Precision 0
Scale 0
Field description
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.

List of values
Value blank
Description LION record represents a straight line segment


Value I
Description LION record represent an irregularly curved segment (not a circular arc)


Value L
Description LION record represents a curved segment consisting of a circular arc lying on the left side of the segment's directed chord.


Value R
Description LION record represents a curved segment consisting of a circular arc lying on the right side of the segment's directed chord.




Field Radius
 
Alias Radius
Data type Integer
Width 9
Precision 9
Scale 0
Field description
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.



Field NodeIDFrom
 
Alias NodeIDFrom
Data type String
Width 7
Precision 0
Scale 0
Field description
Node identifier at the low address end, or beginning of the segment.



Field NodeIDTo
 
Alias NodeIDTo
Data type String
Width 7
Precision 0
Scale 0
Field description
Node identifier at the high address end, or end of the segment.



Field NodeLevelF
 
Alias NodeLevelF
Data type String
Width 1
Precision 0
Scale 0
Field description
Level code indicator vertical topology at the start of the street segment.

List of values
Value A-Z
Description Relative level code on a scale where A is the lowest level of subterranean, M is ground level and Z is highest elevated level.


Value *
Description 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.


Value $
Description Shoreline / water level.




Field NodeLevelT
 
Alias NodeLevelT
Data type String
Width 1
Precision 0
Scale 0
Field description
Level code indicator vertical topology at the end of the street segment.

List of values
Value A-Z
Description Relative level code on a scale where A is the lowest level of subterranean, M is ground level and Z is highest elevated level.


Value *
Description 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.


Value $
Description Shoreline / water level.




Field ConParity
 
Alias ConParity
Data type String
Width 1
Precision 0
Scale 0
Field description
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.

Description source
ESRI

List of values
Value L
Description Odd and Even house number are bothe on the left side of the segment.


Value R
Description Odd and Even house number are bothe on the right side of the segment.




Field Twisted
 
Alias Twisted
Data type String
Width 1
Precision 0
Scale 0
Field description
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).

Description source
ESRI

List of values
Value T
Description 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).




Field RW_TYPE
 
Alias RW_TYPE
Data type String
Width 2
Precision 0
Scale 0
Field description
Roadway Type

List of values
Value 1
Description Street


Value 2
Description Highway


Value 3
Description Bridge


Value 4
Description Tunnel


Value 5
Description Boardwalk


Value 6
Description Path/Trail


Value 7
Description Step Street


Value 8
Description Driveway


Value 9
Description Ramp


Value 10
Description Alley


Value 11
Description Unknown


Value 12
Description Non-Physical Street Segment


Value 13
Description U-Turn


Value 14
Description Ferry Route




Field PhysicalID
 
Alias PhysicalID
Data type Integer
Width 9
Precision 9
Scale 0
Field description
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.



Field GenericID
 
Alias GenericID
Data type Integer
Width 9
Precision 9
Scale 0
Field description
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.



Field NYPDID
 
Alias NYPDID
Data type String
Width 7
Precision 0
Scale 0
Field description
A unique ID assigned for NYPD's use in order to aggregate granular geometry for administrative purposes.



Field FDNYID
 
Alias FDNYID
Data type String
Width 7
Precision 0
Scale 0
Field description
Not currently implemented. A unique ID assigned for FDNY's use in order to aggregate granular geometry for their administrative purposes.

Accuracy information
Accuracy Not currently implemented.


Field LBlockFaceID
 
Alias LBlockFaceID
Data type String
Width 7
Precision 0
Scale 0
Field description
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.



Field RBlockFaceID
 
Alias RBlockFaceID
Data type String
Width 7
Precision 0
Scale 0
Field description
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.



Field LegacyID
 
Alias LegacyID
Data type String
Width 7
Precision 0
Scale 0
Field description
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.

Description source
ESRI

Description of values
Sequential unique whole numbers that are automatically generated.





Field Status
 
Alias Status
Data type String
Width 1
Precision 0
Scale 0
Field description
Refers to the construction status of a street segment.

List of values
Value 1
Description Planned Private


Value 2
Description Constructed


Value 3
Description Paper


Value 4
Description Under Construction


Value 5
Description Demapped


Value 9
Description Paper Street Coincident with Boundary




Field StreetWidth_Min
 
Alias StreetWidth_Min
*Data type Double
*Width 8
*Precision 0
*Scale 0
Field description
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.



Field StreetWidth_Irr
 
Alias StreetWidth_Irr
Data type String
Width 1
Precision 0
Scale 0
Field description
Not currently implemented. Flag indicating whether the street width is consistent along a street segment.

Accuracy information
Accuracy Not currently implemented.


Field BikeLane
 
Alias BikeLane
Data type String
Width 2
Precision 0
Scale 0
Field description
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.

List of values
Value 1
Description Class 1: Separated Greenway


Value 2
Description Class II: Striped Bike Lane


Value 3
Description Class III: Signed Bicycle Route


Value 4
Description Links: Connecting segments.


Value 5
Description Class I, II: Combination of Class I and II


Value 6
Description Class II, III: Combination of Class II and III


Value 7
Description Stairs: Includes step streets, bridge stairs, etc.


Value 8
Description Class I, III: Combination of Class I and III


Value 9
Description Class II, I: Combination of Class II and I


Value 10
Description Class III, I: Combination of Class III and I


Value 11
Description Class III, II: Combination of Class III and II




Field Snow_Priority
 
Alias Snow_Priority
Data type String
Width 1
Precision 0
Scale 0
Field description
DSNY snow removal priority designation.

List of values
Value blank
Description unknown


Value C
Description 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.


Value S
Description 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.


Value H
Description 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).


Value V
Description Non-DSNY




Field Number_Travel_Lanes
 
Alias Number_Travel_Lanes
*Data type String
*Width 2
*Precision 0
*Scale 0
Field description
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.



Field Number_Park_Lanes
 
Alias Number_Park_Lanes
*Data type String
*Width 2
*Precision 0
*Scale 0
Field description
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.



Field Number_Total_Lanes
 
Alias Number_Total_Lanes
*Data type String
*Width 2
*Precision 0
*Scale 0
Field description
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.



Field Carto_Display_Level
 
Alias Carto_Display_Level
*Data type String
*Width 20
*Precision 0
*Scale 0
Field description
Cartographic Display Level:  Select LION segments are flagged as a way to designate major roads for cartographic purposes at various scales.

List of values
Value 10
Description City


Value 20
Description Borough


Value 30
Description Neighborhood




Field FCC
 
Alias FCC
Data type String
Width 2
Precision 0
Scale 0
Field description
Not currently implemented. Federal Classification Code

Accuracy information
Accuracy Not currently implemented.


Field ROW_Type
 
Alias ROW_Type
Data type String
Width 1
Precision 0
Scale 0
Field description
Right-of-Way Type: These refer only to subway and rail segments.

List of values
Value 1
Description Subterranean


Value 2
Description Elevated


Value 3
Description Surface


Value 4
Description Hidden


Value 5
Description Open Cut Depression


Value 6
Description Embankment


Value 7
Description Viaduct


Value 8
Description Subterranean Coincident with Boundary




Field LLo_Hyphen
 
Alias LLo_Hyphen
Data type String
Width 7
Precision 0
Scale 0
Field description
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.

Description source
ESRI

Description of values
Sequential unique whole numbers that are automatically generated.





Field LHi_Hyphen
 
Alias LHi_Hyphen
Data type String
Width 7
Precision 0
Scale 0
Field description
High Value for the hyphenated address range beginning on the left side of the street segment.

Description source
ESRI

Description of values
Sequential unique whole numbers that are automatically generated.





Field RLo_Hyphen
 
Alias RLo_Hyphen
Data type String
Width 7
Precision 0
Scale 0
Field description
Low Value for the hyphenated address range beginning on the right side of the street segment.

Description source
ESRI

Description of values
Sequential unique whole numbers that are automatically generated.





Field RHi_Hyphen
 
Alias RHi_Hyphen
Data type String
Width 7
Precision 0
Scale 0
Field description
High Value for the hyphenated address range beginning on the right side of the street segment.

Description source
ESRI

Description of values
Sequential unique whole numbers that are automatically generated.





Field FromLeft
 
Alias FromLeft
Data type Integer
Width 9
Precision 9
Scale 0
Field description
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).

Description source
ESRI

Description of values
Sequential unique whole numbers that are automatically generated.





Field ToLeft
 
Alias ToLeft
Data type Integer
Width 9
Precision 9
Scale 0
Field description
High Value for the numeric address range beginning on the left side of the street segment.

Description source
ESRI

Description of values
Sequential unique whole numbers that are automatically generated.





Field FromRight
 
Alias FromRight
Data type Integer
Width 9
Precision 9
Scale 0
Field description
Low Value for the numeric address range beginning on the right side of the street segment.

Description source
ESRI

Description of values
Sequential unique whole numbers that are automatically generated.





Field ToRight
 
Alias ToRight
Data type Integer
Width 9
Precision 9
Scale 0
Field description
High Value for the numeric address range beginning on the right side of the street segment.

Description source
ESRI

Description of values
Positive real numbers that are automatically generated.





Field Join_ID
 
Alias Join_ID
Data type String
Width 15
Precision 0
Scale 0
Field description
Identification field used to link LION feature class with Alternative Names table during a geocoding operation.

Description source
ESRI

Description of values
Sequential unique whole numbers that are automatically generated.





Field BIKE_TRAFDIR
 
Alias BIKE_TRAFDIR
Data type String
Width 10
Precision 0
Scale 0
Field description
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.

List of values
Value blank
Description This segment is not part of the bicycle network as defined by the Department of Transportation.


Value FT
Description 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.


Value TF
Description 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.


Value TW
Description Bike traffic is two way. Bicycles travel in both directions.




Field ACTIVE_FLAG
 
Alias ACTIVE_FLAG
Data type String
Width 10
Precision 0
Scale 0
Field description
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.

List of values
Value Y
Description This portion of the subway is active and open.


Value N
Description This portion of the subway is inactive, i.e. either under construction or proposed.


Value NULL
Description This segment does not represent a subway feature.




Field POSTED_SPEED
 
Alias POSTED_SPEED
Data type string
Width 2
Precision 0
Scale 0
Field description
POSTED_SPEED contains the speed limit, in miles per hour, of the paved area.



Field SHAPE_Length
 
Alias SHAPE_Length
Data type Double
Width 19
Precision 0
Scale 0
Field description
Length of feature in internal units.

Description source
Esri

Description of values
Positive real numbers that are automatically generated.





Field StreetWidth_Max
 
*Alias StreetWidth_Max
*Data type Double
*Width 8
*Precision 0
*Scale 0
Field description
The maximum width, in feet, of the paved area of the street.



Field L_PD_Service_Area
 
*Alias L_PD_Service_Area
*Data type String
*Width 1
*Precision 0
*Scale 0
Field description
Left side Police Service Areas (PSAs), which provides the Housing Bureau Police services to a set of housing developments.



Field R_PD_Service_Area
 
*Alias R_PD_Service_Area
*Data type String
*Width 1
*Precision 0
*Scale 0
Field description
Right side Police Service Areas (PSAs), which provides the Housing Bureau Police services to a set of housing developments.



Field TRUCK_ROUTE_TYPE
 
Alias TRUCK_ROUTE_TYPE
Data type String
Width 1
Precision 0
Scale 0
Field description
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.

List of values
Value 1
Description Limited Local


Value 2
Description Local


Value 3
Description Through






Metadata Details 

Metadata language English (UNITED STATES)
Metadata character set  utf8 - 8 bit UCS Transfer Format


Scope of the data described by the metadata  dataset
Scope name* dataset


Last update 2016-02-25


ArcGIS metadata properties
Metadata format ArcGIS 1.0


Created in ArcGIS for the item 2020-12-03 15:56:48
Last modified in ArcGIS for the item 2020-12-03 15:58:19


Automatic updates
Have been performed Yes
Last update 2020-12-03 15:58:19


Metadata Contacts 

Metadata contact
Organization's name Department of City Planning
Contact's role  point of contact


Contact information
Address
Type both
Delivery point 120 Broadway, 31st Floor
City New York
Administrative area NY
Postal code 10271



Metadata Maintenance 

Maintenance
Update frequency  quarterly