Title:New York City Truck Routes
Abstract:
The New York City Truck Routes GIS file is a line file representing Local and Through Truck Routes in New York City, created by the New York City Department of Transportation. It was created from the LION streets file, available from the New York City Department of City Planning. LION is a single line representation of New York City streets containing address ranges and other information.
  1. How should this data set be cited?

    City of New York Department of Transportation, September, 2009, New York City Truck Routes:, New York City Department of Transportation, New York City.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -74.256483
    East_Bounding_Coordinate: -73.699234
    North_Bounding_Coordinate: 40.911464
    South_Bounding_Coordinate: 40.502662
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: September, 2009
    Currentness_Reference: publication date
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • String (37826)
    2. What coordinate system is used to represent geographic features?

      The map projection used is Lambert Conformal Conic.

      Projection parameters:
      Standard_Parallel: 40.666667
      Standard_Parallel: 41.033333
      Longitude_of_Central_Meridian: -74.000000
      Latitude_of_Projection_Origin: 40.166667
      False_Easting: 984250.000000
      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000000
      Ordinates (y-coordinates) are specified to the nearest 0.000000
      Planar coordinates are specified in survey feet

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Resolution: 0.000100
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    New York City Truck Routes
    *Attribute in ESRI GeoDatabase Only; **Attribute in MapInfo Table Only
    ToRight
    High Value for the numeric address range beginning on the right side of the street segment.
    FID
    Low Value for the numeric address range beginning on the right side of the street segment. (Source: ESRI)
    Sequential unique whole numbers that are automatically generated.
    OBJECTID
    Internal feature number. (Source: ESRI)
    Sequential unique whole numbers that are automatically generated.
    Join_ID
    Identification field used to link LION feature class with Alternative Names table during a geocoding operation. (Source: ESRI)
    Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: ESRI)
    Coordinates defining the features.
    Street
    Street name used for labeling (in MapInfo and ESRI versions) and geocoding (in MapInfo Version).
    HideLabel
    Flag used by DCP to suppress labeling of LION segments based on Borough and FaceCode.
    FeatureTyp
    Feature Type Code
    Value Definition
    0 Street other than vehicle only street.
    1 Railroad
    2 Water Edge / Shoreline
    3 Census Block Boundary
    4 Other Non-Street Feature: Physically existing, addressable boundary, such as a street segment that has been closed off (inaccessible at both ends).
    5 Paper Street: This is a legally mapped, but not built 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 A paper street that falls along a census block boundary.
    A Alley.
    W Path, Non-Vehicular, Addressable: This is a walking path. For example, some boardwalks and some walking paths in housing projects.
    SegmentTyp
    Feature Type Code
    Value Definition
    B Both: Part of a multple roadbed but also used as a generic segment.
    C Connector: Small street segments that connect two roadbeds.
    E Entrance or Exit.
    F Faux Street: Used to extend an exit to the gereric centerline.
    G Generic: Centerline of street.
    R Roadbed.
    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.
    T Terminator: Brings together 2 roadbeds at an intersection when multple roadbeds give way to an undivided street.
    U Undivided Street.
    IncExFlag
    Inclusion/Exclusion Flag
    Value Definition
    E Segment should be excluded in the generic view of LION.
    I Segment should be included in the generic view of LION.
    RB_Layer
    For cartographic purposes, indicates whether segment is present in the "Roadbed" layer and/or the "Generic" layer.
    Value Definition
    R Street segment is present only in the "Roadbed" layer.
    G Street segment is present only in the "Generic" layer.
    B Street segment is present the "Generic" and "Roadbed" layers.
    N Street segment is not present in either the "Generic" or "Roadbed" layers.

    NonPed
    NonPedestrian Code.

    Value Definition
    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

    TrafDir
    Traffic Direction. Code indicating the flow of traffic relative to the street segment's address range.

    Value Definition
    w With: Traffic flows from low to high house numbers.
    a Against: Traffic flows from high to low house numbers.
    t Two-Way: Traffic flows from high to low house numbers.
    p Pedestrian: No vehicles allowed.
    blank Non-street feature.
    TrafSrc
    Indicates the source of information in the Traffic Direction (TrafDir) field.
    Value Definition
    DCP NYC Department of City Planning
    DOT NYC Department of Transportation
    SpecAddr
    Special Address Type Code
    Value Definition
    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 Alternate Street Names: Alternate 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. This is primarily restricted to two situations: 1. Hillside Avenue in Queens- there are two Hillside Avenues, one in Far Rockaway, another in Douglaston; and 2. Dr. Martin Luther King, Jr. Blvd. in Manhattan. This street name is an alternative name for both E 125 St. and W 125 St. As a result, there are numerous duplicate addresses along this street.
    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. Because of restrictions imposed by MapInfo's address matching, the user must include a "0" as a house number to successfully match a non-addressable place name. For example, "0 Lincoln Center" will match to the correct side of the street for that location.
    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). Because of restrictions imposed by MapInfo's address matching, the user must include a "0" as a house number to successfully match a non-addressable plance name. For example, "0 City Hall" will match to the correct side of the street for that location.
    p 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 This refers to situations in which the break in addresses from one block face to the next along a street involves house number suffixes. These suffix addresses are not included in MapInfo LION. 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.
    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 Fifth Avenue in Manhattan, a vanity address, is actually located on East 86th Street, between Fifth Avenue and Madison Avenue.
    x This is used for names of non-addressable parts 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). Because of restrictions imposed by MapInfo's address matching, the user must include a "0" as a house number to successfully match a non-addressable place name. For example, "0 Alice Tully Hall" will match to the correct side of the street for that location.
    FaceCode
    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).
    SeqNum
    A five digit number assigned sequentially to the street segments within a given face code. The sequence number generally increases with the direction of the street.
    StreetCode
    Boro & 5-Digit Street Code
    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.
    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.
    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.
    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.
    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.
    SegmentID
    A number of up to seven digits that identifies each segment of a street or a non-street feature represented in the LION file. Segment-ID differs from the LION Key in that the former identifies a segment, a geographic entity, whereas the latter identifies a record in the LION file. In the case of a segment lying along a borough boundary, say one that lies along the Brooklyn-Queens border, both the Brooklyn and Queens DCPLION files will have a record representing that segment; the LION Keys of those two records are distinct, but the Segment-ID's are identical.
    SegCount
    Coincident Segment Count indicates situations where there are double-decker roads and therefore more than one segment for the same geography in LION. An example would be the upper and lower roadways of the George Washington Bridge. In this case, the SegCount would be = 2. Most LION segments will have a SegCount of 1.
    LocStatus
    Segment Locational Status.
    Value Definition
    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
    LZip
    Contains the five digit postal zip code for the left side of the street segment.
    RZip
    Contains the five digit postal zip code for the right side of the street segment.
    LBoro
    This is a 1-digit code identifying the borough in which the left side of the street segment is located.
    Value Definition
    1 Manhattan
    2 The Bronx
    3 Brooklyn
    4 Queens
    5 Staten Island
    RBoro
    This is a 1-digit code identifying the borough in which the right side of the street segment is located.
    Value Definition
    1 Manhattan
    2 The Bronx
    3 Brooklyn
    4 Queens
    5 Staten Island
    L_CD
    Three-digit Community District code for the left side of the street.
    R_CD
    Three-digit Community District code for the right side of the street.
    LDynBlock
    Left Dynamic Block. A dynamic block is a minimal polygon formed by most LION file 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. A dynamic block 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). Dynamic block numbers are unique within 2000 Census Tracts and are used as building blocks for many higher geographies.
    RDynBlock
    Right Dynamic Block.
    LCT2000
    Left 2000 Census Tract.
    LCT2000Suf
    Left 2000 Census Tract Suffix.
    RCT2000
    Right 2000 Census Tract.
    RCT2000Suf
    Right 2000 Census Tract Suffix.
    LCB2000
    Left 2000 Census Block.
    LCB2000Suf
    Left 2000 Census Block Suffix.
    LCT2000Suf
    Left 2000 Census Tract Suffix.
    RCB2000
    Right 2000 Census Block.
    RCB2000Suf
    Right 2000 Census Block Suffix.
    LCT1990
    Left 1990 Census Tract.
    LCT1990Suf
    Left 1990 Census Tract Suffix.
    RCT1990
    Right 1990 Census Tract.
    RCT1990Suf
    Right 1990 Census Tract Suffix.
    LAssmDist
    Assembly District for the left side of the street.
    LElectDist
    Election District for the left side of the street.
    RAssmDist
    Assembly District for the right side of the street.
    RElectDist
    Election District for the right side of the street.
    SplitElect
    Split Election Flag. Indicates when a LION segment is split by more than one Election District.
    LSchlDist
    School District for the left side of the street.
    RSchlDist
    School District for the right side of the street.
    SplitSchl
    Split School Flag. Indicates when a LION segment is split by more than one School District.
    SchlCount
    School Count (for DCP internal use for Dept. of Education processing)
    LSubSect
    Sanitation District Subsection for the left side of the street.
    RSubSect
    Sanitation District Subsection for the right side of the street.
    SanDistInd
    Sanitation District 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 indicator.
    Value Definition
    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.
    MapFrom
    DCP Sectional / Zoning Map at the beginning of t e segment.
    MapTo
    DCP Sectional / Zoning Map at the end of the segment.
    NearBQ
    Near Brooklyn/Queens. Indicates segments that are within 1.7 miles of the Brooklyn-Queens boundary for special processing done for the Department of Education.
    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.
    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.
    XFrom
    X (Spatial) coordinate at the 'From' end of a segment.
    YFrom
    Y (Spatial) coordinate at the 'From' end of a segment.
    XTo
    X (Spatial) coordinate at the 'To' end of a segment.
    YTo
    Y (Spatial) coordinate at the 'To' end of a segment.
    ArcCenterX
    X (Spatial) coordinate at the center of the curve.
    ArcCenterY
    Y (Spatial) coordinate at the center of the curve.
    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.
    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.
    NodeIDFrom
    Node identifier at the low address range of the segment.
    NodeIDTo
    Node identifier at the high address range of the segment.
    NodeLevelF
    Level code indicator vertical topolgy at the start of the street segment.
    Value Definition
    Y Third elevated geography.
    U Second elevated geography.
    Q First elevated geography.
    M Ground level.
    I First subterranean geography.
    E Second subterranean geography.
    A Third subterranean geography..
    NodeLevelT
    Level code indicator vertical topolgy at the end of the street segment.
    Value Definition
    Y Third elevated geography.
    U Second elevated geography.
    Q First elevated geography.
    M Ground level.
    I First subterranean geography.
    E Second subterranean geography.
    A Third subterranean geography..
    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.
    Value Definition
    L Odd and Even house number are both on the left side of the segment.
    R Odd and Even house number are both on the right side of the segment.
    Twisted
    Twisted Parity
    Value Definition
    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).
    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 street 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.
    LHi_Hyphen
    High Value for the hyphenated address range beginning on the left side of the street segment.
    RLo_Hyphen
    Low Value for the hyphenated address range beginning on the right side of the street segment.
    FromRight
    Feature geometry. (Source: ESRI)
    Coordinates defining the features.
    RHi_Hyphen
    High Value for the hyphenated address range beginning on the right side of the street segment.
    FromLeft
    Low Value for the numeric address range beginning on the left side of the street segment. For all hyphenated addresses, the hyphen has been removed. To convert the before hypen 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).
    ToLeft
    High Value for the numeric address range beginning on the left side of the street segment.
    TruckRoute
    'Y' Indicates that this segment is a Truck Route
    RouteType
    Indicates the type of Truck Route: Through, Local or Limited Local
    Value Definition
    Through Trucks having neither an origin nor a destination in this Borough shall restrict operation of their vehicle to those street segments designated as Through Truck Routes
    Local Trucks having an origin or destination for purpose of delivery, loading or servicing within this Borough shall restrict operation of their vehicle to those street segments designated as Local Truck Routes, except that an operator may operate on a street not designated as a truck route for the purpose of leaving his/her origin or arriving at his/her destination.
    Limited Local Same restrictions as the Local Truck Routes except that no trucks with 3 or more axles can operate on Limited Local Truck Routes
    Descriptio
    Description of Truck Route and Borough
    NYC_Reg
    Section of NYCDOT Traffic Rules explaining Truck Route regulations for that particular Borough and Route Type
    ThruExwy
    'Y' indicates that the segment is a Through Truck Route on an expressway
    LocalBrg
    'Y' indicates that the segment is a Local Truck Route on a bridge
    LocalTunl
    'Y' indicates that the segment is a Local Truck Route in a tunnel
    ThruBrg
    'Y' indicates that the segment is a Through Truck Route on a bridge
    ThruTunl
    'Y' indicates that the segment is a Through Truck Route in a tunnel
    Join_Count
    SHAPE_Leng
    Restrictio
    Describes any restrictions such as vertical clearance, vehicle weight, vehicle width, vehicle length

Who produced the data set?
  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
  2. Who also contributed to the data set?

    New York City Department of Transportation, New York City Department of City Planning

  3. To whom should users address questions about the data?

    New York City Department of Transportation
    Office of Freight Mobility
    55 Water Street, 9th Floor
    New York, NY 10041
    USA

    212.839.6670 (voice)
    jfreight@dot.nyc.gov


Why was the data set created?
The New York City Truck Routes GIS file is meant to provide a geographic dataset of truck routes for use by truck drivers, trucking companies, GPS companies, mapping companies and the general public. The LION file has been maintained as a major component of the Department of City Planning's Geosupport System.

How was the data set created?
  1. From what previous works were the data drawn?
    (source 1 of 1)
  2. How were the data generated, processed, and modified?
    (process 1 of 23)
    (process 2 of 23)
    Dataset copied.

    Data sources used in this process:

    • Server=reade7; Service=5151; Database=sde; User=dcpgis; Version= sde.DEFAULT
    (process 3 of 23)
    Metadata imported.

    Data sources used in this process:

    • C:\temp\metadata.xml
    (process 4 of 23)
    Dataset copied.

    Data sources used in this process:

    • Server=reade7; Service=5151; Database=sde; User=dcpgis; Version= sde.DEFAULT
    (process 5 of 23)
    Dataset copied.

    Data sources used in this process:

    • Server=reade7; Service=5151; Database=sde; User=dcpgis; Version= sde.DEFAULT
    (process 6 of 23)
    Metadata imported.

    Data sources used in this process:

    • G:\GIS\Metadata\04C\xml\lion.xml
    (process 7 of 23)
    Dataset copied.

    Data sources used in this process:

    • Server=reade7; Service=5151; Database=sde; User=dcpgis; Version= sde.DEFAULT
    (process 8 of 23)
    Metadata imported.

    Data sources used in this process:

    • D:\lion04c_finals\metadata.xml
    (process 9 of 23)
    Metadata imported.

    Data sources used in this process:

    • D:\04d\lion\precise\lion04d_metadata.xml
    (process 10 of 23)
    Metadata imported.

    Data sources used in this process:

    • M:\ESRI\Product\Metadata\lion\nyc_lion.shp.xml
    (process 11 of 23)
    Dataset copied.

    Data sources used in this process:

    • \\NYCDOT-2BD2NG1\C$\John\Truck_Map\LION_Files\nyc_lion08bav\lion.gdb
    (process 12 of 23)
    Dataset copied.

    Data sources used in this process:

    (process 13 of 23)
    Dataset copied.

    Data sources used in this process:

    Date: 09-Jun-2009 (process 14 of 23)
    Dataset copied.

    Data sources used in this process:

    • V:\Office of Freight Mobility\Truck_Routes_Shapefile\New_Truck_Routes\SHAPEFILES
      \Truck_Routes_Bronx
    Date: 07-Jul-2009 (process 15 of 23)
    Dataset copied.

    Data sources used in this process:

    Date: 14-Jul-2009 (process 16 of 23)
    Dataset copied.

    Data sources used in this process:

    Date: 07-Aug-2009 (process 17 of 23)
    Dataset copied.

    Data sources used in this process:

    Date: 10-Aug-2009 (process 18 of 23)
    Dataset copied.

    Data sources used in this process:

    Date: 11-Aug-2009 (process 19 of 23)
    Dataset copied.

    Data sources used in this process:

    Date: 18-Aug-2009 (process 20 of 23)
    Dataset copied.

    Data sources used in this process:

    Date: 24-Aug-2009 (process 21 of 23)
    Dataset copied.

    Data sources used in this process:

    Date: 04-Sep-2009 (process 22 of 23)
    Dataset copied.

    Data sources used in this process:

    • \\dot.nycnet\dfs\UserHomeDrives\JKarras\My Documents\Truck_Map\GIS_Truck_Routes
      \Truck_Routes_Bronx_8_25_2009_Final_Copy
    Date: 09-Sep-2009 (process 23 of 23)
    Dataset copied.

    Data sources used in this process:

  3. What similar or related data should the user be aware of?

How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?
  2. How accurate are the geographic locations?

    The LION file is spatially aligned with NYCMap aerial photography.

  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the observations, including topology?

    A node occurs where ever two or more line segments cross regardless of whether a physical intersection occurs at that point. Duplicate lines may appear where lines are associated with non-addressable place names such as Grand Army Plaza or where alternate street names exist.


Access_Constraints:
New York City Truck Routes is freely available to the public. LION is freely available to the public.
Use_Constraints:
The Department of Transportation makes 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.
  1. Who distributes the data set? (Distributor 1 of 1)
New York City Department of Transportation
55 Water St
New York, NY 10041
USA
  1. What's the catalog number I need to order this data set?

Downloadable Data

  1. What legal disclaimers am I supposed to read?
  2. How can I download or order the data?

Who wrote the metadata?
Dates:
Last modified: 15-Sep-2009
Metadata author:
New York City Department of Transportation
Office of Freight Mobility
55 Water St
New York, NY 10041

212.839.6670 (voice)

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:

Generated by mp version 2.9.6 on Tue Sep 15 09:44:36 2009