FALSE
1.0
20170117
10000400
North American Profile of ISO19115 2003
NGRoad_Centerlines
002
-5120900.000000
827832.431800
1900.000000
896862.277900
1
Projected
GCS_North_American_1983
Linear Unit: Foot (0.304800)
NAD_1983_StatePlane_Arizona_West_FIPS_0203_Feet_Intl
<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/10.5'><WKT>PROJCS["NAD_1983_StatePlane_Arizona_West_FIPS_0203_Feet_Intl",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["Transverse_Mercator"],PARAMETER["False_Easting",700000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-113.75],PARAMETER["Scale_Factor",0.9999333333333333],PARAMETER["Latitude_Of_Origin",31.0],UNIT["Foot",0.3048],AUTHORITY["EPSG",2224]]</WKT><XOrigin>-5120900</XOrigin><YOrigin>1900</YOrigin><XYScale>10000</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2224</WKID><LatestWKID>2224</LatestWKID></ProjectedCoordinateSystem>
20181211
13075100
20181211
13075100
Road centerlines represent the estimated centerline of a real world roadway. GIS road centerline arc-node topology is associated with attribute data containing information on street names, address ranges, jurisdictional boundaries, and other attributes. The Road Centerline layer is an integral part of any public safety GIS due to its versatility and its use for: • Querying and geocoding of civic addresses based on dual address ranges • Tactical map display • Map and attribute viewing • Map production • Location and driving directions • Integration of network topology to allow vehicle routing, drive time analysis • Integration of spatially related attributes for advanced applications including those focused on public safety, assets management, planning, utilities, and public works.
ROAD CENTERLINES
X-Ray
NaN
NaN
NaN
NaN
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
SHAPE
Shape
Geometry
4
0
0
Feature geometry.
Esri
Coordinates defining the features.
AddCode_L
Additional Code Left
String
6
0
0
Description: The Additional Code on the Left side of the road segment relative to the FROM Node. Domain: See Additional Code Example: See Additional Code
AddCode_R
Additional Code Right
String
6
0
0
Description: The Additional Code on the Right side of the road segment relative to the FROM Node. Domain: See Additional Code Example: See Additional Code
AdNumPre_L
Left Address Number Prefix
String
15
0
0
Description: An extension of the Address Number that precedes it and further identifies a location along a thoroughfare or within a defined area, on the Left side of the road segment relative to the FROM Node. It contains any alpha-numeric characters, punctuation, and spaces preceding the Left FROM Address and Left TO Address. Domain: None Example: 101- in “101-123 Grid Drive”; “N” in “N46999 Holden Road”; “0” in “012 Portland D
AdNumPre_R
Right Address Number Prefix
String
15
0
0
Description: An extension of the Address Number that precedes it and further identifies a location along a thoroughfare or within a defined area, on the Right side of the road segment relative to the FROM Node. It contains any alpha-numeric characters, punctuation, and spaces preceding the Right FROM Address and Right TO Address. Domain: None Example: 2N3W- in “2N3W-124 Township Drive”, “S” in “S877 Highway 88
Country_L
Country Left
String
2
0
0
Description: The name of the Country on the Left side of the road segment relative to the FROM Node, represented by its two-letter ISO 3166-1 English country alpha-2 code elements in capital ASCII letters. Domain: Restricted to the two-letter designations provided in ISO 3166-1. Example: US for the United States of America; CA for Canada
Country_R
Country Right
String
2
0
0
Description: The name of the Country on the Right side of the road segment relative to the FROM Node, represented by its two-letter ISO 3166-1 English country alpha-2 code elements in capital ASCII letters. Domain: Restricted to the two-letter designations provided in ISO 3166-1. Example: US for the United States of America; MX for Mexico
County_L
County Left
String
40
0
0
Description: The name of a County or County-equivalent on the Left side of the road segment relative to the FROM Node. A county (or its equivalent) is the primary legal division of a state or territory. Domain: See County Example: Saint Louis; Adams County
County_R
County Right
String
40
0
0
Description: The name of a County or County-equivalent on the Right side of the road segment relative to the FROM Node. A county (or its equivalent) is the primary legal division of a state or territory. Domain: See County Example: DeSoto County; Doña Ana County
DateUpdate
Date Updated
Date
8
0
0
Description: The UTC date and time that the record was created or last modified. This value SHOULD be populated upon modifications to attributes, geometry, or both. Domain: Restricted to ISO 8601 compliant values in Coordinated Universal Time (UTC). Values are not allowed to be in the future. Example: 2010-12-19T20:01:29-05 (representing a record updated on December 19, 2010 at 8:01 and 29 seconds PM US Eastern Standard Time)
Effective
Effective Date
Date
8
0
0
Description: The UTC date and time that the record is scheduled to take effect. Domain: Timestamp as defined in NENA-STA-010 that in turn conforms to W3C dateTime. Example: 2010-10-09T13:01:35-04 (representing a record that will become active on October 9, 2010 at 1:01 and 35 seconds PM US Eastern Daylight Time); 2010-02-18T02:30:00-05 (representing a record that will become active on February 18, 2010 at 2:30 and 0 seconds AM US Eastern Standard Time) NOTE: This field is used when time and date of a change is known. For example, the time and date an annexation takes effect.
ESN_L
ESN Left
String
5
0
0
Description: The Emergency Service Number (ESN) on the Left side of the road segment relative to the FROM Node. Domain: Characters from 000 to 99999 Example: 5422; 124; 005
ESN_R
ESN Right
String
5
0
0
Description: The Emergency Service Number (ESN) on the Right side of the road segment relative to the FROM Node. Domain: Characters from 000 to 99999 Example: 5423; 125; 007
Expire
Expiration Date
Date
8
0
0
Date when the information in the record is no longer considered valid. Domain: TimeStamp as defined in NENA-STA-010 that in turn conforms to W3C dateTime. Example: 2010-10-09T13:01:35-04 (representing a record will expire and no longer be valid on October 9, 2010 at 1:01 and 35 seconds PM US Eastern Daylight Time); 2010-02-18T02:30:00-05 (representing a record that will expire and no longer be valid on February 18, 2010 at 2:30 and 0 seconds AM US Eastern Standard Time). NOTE: This field is used when the time and date of a change is known. For example, the time and date an annexation takes effect and the previous boundary is retired.
FromAddr_L
Left FROM Address
Integer
4
10
0
Description: In a GIS, each line segment has a begin point and an endpoint. The FROM Node is the begin point of the linestring while the TO Node is the endpoint. Line segments have a left side and a right side relative to a begin node and an end node. The Left FROM address is the address number on the Left side of the road segment relative to the Left FROM Node of the linestring. Note: This address can be higher than the Left TO Address. Domain: Whole numbers from 1 to 9,999,999
FromAddr_R
Right FROM Address
Integer
4
10
0
Description: In a GIS, each line segment has a begin point and an endpoint. The FROM Node is the begin point of the linestring while the TO node is the endpoint. Line segments have a left side and a right side relative to a begin node and an end node. The Right FROM address number is the address number on the Right side of the road segment relative to the Right FROM Node of the linestring. Note: This address can be higher than the Right TO Address. Domain: Whole numbers from 1 to 9,999,999
IncMuni_L
Incorporated Municipality Left
String
100
0
0
Description: The name of the Incorporated Municipality or other general-purpose local governmental unit, on the Left side of the road segment relative to the FROM Node. Domain: None; however use Unincorporated if the address is not within an incorporated local government. Example: Lexington; Columbus; Unincorporated
IncMuni_R
Incorporated Municipality Right
String
100
0
0
Description: The name of the Incorporated Municipality or other general-purpose local governmental unit, on the Right side of the road segment relative to the FROM Node. Domain: None; however use Unincorporated if the address is not within an incorporated local government. Example: Tampa; Yonkers; Unincorporated
LSt_Name
Legacy Street Name
String
75
0
0
Description: The street name field as it previously existed prior to the adoption of the NG9 1 1 Data Model as assigned by the local addressing authority. Domain: None Example: “STATE” in “STATE ST”; “ELMWOOD” in “N ELMWOOD AVE” NOTE: Legacy Street Name and the additional Legacy Street Name Parts (Legacy Street Name Post Directional, Legacy Street Name Pre Directional, and Legacy Street Name Type), are included in the GIS Data Model to provide backward compatibility with legacy map displays and CAD systems. These fields should be used to reflect attribute parsing that ensures the continuing function of existing systems.
LSt_PreDir
Legacy Street Name Pre Directional
String
2
0
0
Description: Leading street direction prefix as it previously existed prior to the adoption of the NG9 1 1 Data Model as assigned by the local addressing authority. Domain: N, S, E, W, NE, NW, SE, SW Example: “S” in “S PINE AVE”
LSt_Type
Legacy Street Name Type
String
5
0
0
Description: The valid street abbreviation as it previously existed prior to the adoption of the NG9 1 1 Data Model as assigned by the local addressing authority. Domain: As it existed prior to the adoption of the NG9 1 1 Data Model; MAY be blank Example: “ST” for “STREET”; “STR” for “STREET”; “BLVD” for “BOULEVARD”; “AVE” for “AVENUE”; “TRACE” for “TRACE
LSTPosDir
Legacy Street Name Post Directional
String
2
0
0
Description: The trailing street direction suffix as it previously existed prior to the adoption of the NG9 1 1 Data Model as assigned by the local addressing authority. Domain: N, S, E, W, NE, NW, SE, SW Example: “E” in “CHURCH ST E”
MSAGComm_L
MSAG Community Name Left
String
30
0
0
Description: The existing MSAG Community Name on the Left side of the road segment relative to the FROM Node. Domain: None Example: Harris County
MSAGComm_R
MSAG Community Name Right
String
30
0
0
Description: The existing MSAG Community Name on the Right side of the road segment relative to the FROM Node. Domain: None Example: Crystal City
NbrhdCom_L
Neighborhood Community Left
String
100
0
0
Description: The name of an unincorporated neighborhood, subdivision or area, either within an incorporated municipality or in an unincorporated portion of a county, on the Left side of the road segment relative to the FROM Node. Domain: None Example: East Harlem; Cypress Meadows Subdivision
NbrhdCom_R
Neighborhood Community Right
String
100
0
0
Description: The name of an unincorporated neighborhood, subdivision or area, either within an incorporated municipality or in an unincorporated portion of a county, on the Right side of the road segment relative to the FROM Node. Domain: None Example: Edgewater Park; The Meadows
OneWay
One-Way
String
2
0
0
Description: The direction of traffic movement along a road in relation to the FROM node and TO node of the line segment representing the road in the GIS data. The one-way field has three possible designations: B (Both), FT (From-To) and TF (To-From). B – Travel in both directions allowed FT – One-way traveling from FROM node to TO node TF – One way traveling from TO node to FROM node Domain: B, FT, TF
Parity_L
Parity Left
String
1
0
0
Description: The even or odd property of the address number range on the Left side of the road segment relative to the FROM Node. Domain: O=Odd, E=Even, B=Both, Z=Address Range 0-0 or Address Range NULL-NULL Example: O; E; B; Z
Parity_R
Parity Right
String
1
0
0
Description: The even or odd property of the address number range on the Right side of the road segment relative to the FROM Node. Domain: O=Odd, E=Even, B=Both, Z=Address Range 0-0 or Address Range NULL-NULL Example: O; E; B; Z
PostCode_L
Postal Code Left
String
7
0
0
Description: The Postal Code on the Left side of the road segment relative to the FROM Node. Domain: See Postal Code Example: 44114 (Postal Code for Cleveland, OH); H3B 3B0 (Canadian Post for Montreal, QC)
PostCode_R
Postal Code Right
String
7
0
0
Description: The Postal Code on the Right side of the road segment relative to the FROM Node. Domain: See Postal Code Example: 84101 (Postal Code for Salt Lake City, UT); R3C 3Z0 (Canadian Post for Winnipeg, MB)
PostComm_L
Postal Community Name Left
String
40
0
0
Description: The Postal Community Name on the Left side of the road segment relative to the FROM Node. Domain: See Postal Community Name Example: Dublin; Magnolia
PostComm_R
Postal Community Name Right
String
40
0
0
Description: The Postal Community Name on the Right side of the road segment relative to the FROM Node. Domain: See Postal Community Name Example: Wicket; Zanesville
RCL_NGUID
Road Centerline NENA Globally Unique ID
String
100
0
0
The NENA Globally Unique ID for each Road Centerline. Each record in the Road Centerlines layer MUST have a globally unique ID. When coalescing data from other local 9 1 1 Authorities into the ECRF and LVF, this unique ID MUST continue to have only one occurrence. One way to accomplish this is to append the 9 1 1 Authority’s domain to the end of the internally calculated feature ID. Domain: None Example: Feature ID 6237 in the Road Centerline layer would be represented as RCL6237@911Authority_domain.state.us
RoadClass
Road Class
String
15
0
0
Description: The general description of the type of road. The Road Classifications used in this document are derived from the US Census MAF/TIGER Feature Classification Codes (MTFCC), which is an update to the now deprecated Census Feature Class Codes (CFCC). Domain: Primary, Secondary, Local, Ramp, Service, Vehicular Trail, Walkway, Alley, Private, Parking Lot, Trail, Other Example: Ramp NOTE: The Road Class is completely spelled out in the attribute fields. Road Classification is based on Revised Census road classification found in the MAF/TIGER Feature Classification Codes (MTFCC) Attachment D. The values are taken from the S series information in this document which provided the classification scheme for surface roads and can be found at: https://www.census.gov/rdo/pdf/AttD_MAF_TIGER_Feature_Classification_Codes.pdf • Primary roads are generally divided, limited-access highways within the interstate highway system or under state management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. • Secondary roads are main arteries, usually in the US Highway, State Highway, or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not be divided, and usually have at-grade intersections with many other roads and driveways. • Local roads are generally a paved non-arterial street, road, or byway that usually has a single lane of traffic in each direction. Roads in this classification include neighborhood, rural roads and city streets. • Ramp designates a road that allows controlled access from adjacent roads onto a limited access highway, often in the form of a cloverleaf interchange. Ramps typically do not have address ranges. • Service Drives, which provide access to structures along the highway, usually parallel a limited access highway. If these roads are named and addressed they may be considered local roads. • Vehicular Trail (4WD, snowmobile) is an unpaved trail or path where a four-wheel-drive vehicle, snowmobile, or similar vehicle is required. • Walkway (Pedestrian Trail, Boardwalk) is a path that is used for walking, being either too narrow for or legally restricted from vehicular traffic. • Alley is generally a service road that does not generally have associated addressed structures and is usually unnamed. It is located at the rear of buildings and properties. • Private (service vehicles, logging, oil fields, ranches, etc.) is a road within private property that is privately maintained for service, extractive, or other purposes. These roads are often un-named. • Parking Lot is the main travel route for vehicles through a paved parking area. • Trail (Ski, Bike, Walking/Hiking Trail) is generally a path used by human powered modes of transportation. • Other is any road or path type that does not fit into the above categories. Some 9 1 1 Authorities may include un-named and/or un-addressed trails, paths, and similar “roads” in their GIS data. It is recommended that these not be included with the named and addressed roads for provisioning into the ECRF and the LVF databases. Conversely the Road Classification SHOULD be populated so these “roads” can be selected for exclusion and not be part of the data provisioned or updated to the ECRF and the LVF.
Source
Source of Data
String
75
0
0
Description: Agency that last updated the record, usually the name of the 9 1 1 Authority. This MAY be represented by the domain name of the agency. Domain: None Example: Metropolitan Regional Addressing Authority; Vermont911.st.us.gov
SpeedLimit
Speed Limit
SmallInteger
2
5
0
Description: Posted Speed Limit in MPH in US or Km/h in Canada Domain: Whole numbers from 1 to 999 Example: 35; 55; 70
St_PosDir
Street Name Post Directional
String
9
0
0
Description: A word following the Street Name that indicates the direction taken by the road from an arbitrary starting point or line, or the sector where it is located. Domain: North, South, East, West, Northeast, Northwest, Southeast, Southwest Example: “North” in “Elm Avenue North
St_PosMod
Street Name Post Modifier
String
25
0
0
Description: A word or phrase that follows and modifies the Street Name, but is separated from it by a Street Name Post Type or a Street Name Post Directional or both. Domain: None Example: “Alternate” in “State Route 281 Alternate” “Extension” in “Main Street Extension
St_PosTyp
Street Name Post Type
String
15
0
0
Description: A word or phrase that follows the Street Name element and identifies a type of thoroughfare in a complete street name. Domain: Restricted to values found in the “NENA Registry of Street Name Pre Types and Street Name Post Types” or combinations thereof.http://technet.nena.org/nrs/registry/StreetNamePreTypesAndStreetNamePostTypes.xml Example: “Parkway” in “Ocean Parkway”
St_PreDir
Street Name Pre Directional
String
9
0
0
Description: A word preceding the Street Name that indicates the direction taken by the road from an arbitrary starting point or line, or the sector where it is located. Domain: North, South, East, West, Northeast, Northwest, Southeast, Southwest Example: “South” in “South Congress Avenue
St_PreMod
Street Name Pre Modifier
String
15
0
0
Description: A word or phrase that precedes and modifies the Street Name element but is separated from it by a Street Name Pre Type or a Street Name Pre Directional or both. The use of the Street Name Pre Modifier is at the discretion of the local addressing authority.
St_PreSep
Street Name Pre Type Separator
String
20
0
0
Description: A preposition or prepositional phrase between the Street Name Pre Type and the Street Name. This element is defined in CLDXF as a US specific extension of PIDF LO per RFC 6848. Doman: Restricted to values found in the “NENA Registry of Street Name Pre Type Separators.” http://technet.nena.org/nrs/registry/StreetNamePreTypeSeparators.xml Example: “of the” in “Avenue of the Stars
St_PreTyp
Street Name Pre Type
String
25
0
0
Description: A word or phrase that precedes the Street Name element and identifies a type of thoroughfare in a complete street name. Use of this field is at the discretion of the local addressing authority naming conventions. Domain: Restricted to values found in the “NENA Registry of Street Name Pre Types and Street Name Post Types” or combinations thereof.http://technet.nena.org/nrs/registry/StreetNamePreTypesAndStreetNamePostTypes.xml Example: “Avenue” in “Avenue A” “State Highway” in “State Highway 443” “Boulevard” in “Boulevard of the Allies
State_L
State Left
String
2
0
0
Description: The two character abbreviation for the name of the State on the Left side of the road segment relative to the FROM Node. Domain: ISO 3166-2 or USPS Publication 28, Appendix B for the US Example: LA; OK
State_R
State Right
String
2
0
0
Description: The two character abbreviation for the name of the State on the Right side of the road segment relative to the FROM Node. Domain: ISO 3166-2 or USPS Publication 28, Appendix B for the US Example: PA; KY
StreetName
Street Name
String
60
0
0
Description: The legal name of the road, usually defined by the lowest jurisdictional authority, e.g., city. The street name does not include any street types, directionals, or modifiers. Domain: None Example: “Fifth” in “Fifth Avenue
ToAddr_L
Left TO Address
Integer
4
10
0
Description: In a GIS, each line segment has a begin point and an endpoint. The FROM Node is the begin point of the linestring while the TO Node is the endpoint. Line segments have a left side and a right side relative to a begin node and an end node. The Left TO address is the address number on the Left side of the road segment relative to the Left TO Node of the linestring. Note: This address can be lower than the Left FROM Address. Domain: Whole numbers from 1 to 9,999,999
ToAddr_R
Right TO Address
Integer
4
10
0
Description: In a GIS, each line segment has a begin point and an endpoint. The FROM Node is the begin point of the linestring while the TO node is the endpoint. Line segments have a left side and a right side relative to a begin node and an end node. The Right TO address number is the address number on the Right side of the road segment relative to the Right TO Node of the linestring. Note: This address can be lower than the Right FROM Address. Domain: Whole numbers from 1 to 9,999,999
UnincCom_L
Unincorporated Community Left
String
100
0
0
Description: The Unincorporated Community on the Left side of the road segment relative to the FROM Node. Domain: None Example: Latham (NY); Moose (WY)
UnincCom_R
Unincorporated Community Right
String
100
0
0
Description: The Unincorporated Community on the Right side of the road segment relative to the FROM Node. Domain: None Example: Mountain View (GA); Palmer (MI)
NGRoad_Centerlines
Feature Class
16514
ELEV_FROM
Elevation FROM
SmallInteger
2
5
0
ELEV_TO
Elevation TO
SmallInteger
2
5
0
LRS_FIX
LRS_FIX
String
6
0
0
FullStreetName
FullStreetName
String
75
0
0
GlobalID
GlobalID
GlobalID
38
0
0
NGUID
NGUID
String
100
0
0
CREATION_DATE
CREATION_DATE
Date
8
0
0
CREATION_USER
CREATION_USER
String
50
0
0
MODIFY_DATE
MODIFY_DATE
Date
8
0
0
MODIFY_USER
MODIFY_USER
String
50
0
0
C1_EXCEPTION
C1_EXCEPTION
Integer
4
10
0
NO_MSAG
NO_MSAG
Integer
4
10
0
FIRE_L
FIRE_L
String
60
0
0
FIRE_R
FIRE_R
String
60
0
0
LAW_L
LAW_L
String
60
0
0
LAW_R
LAW_R
String
60
0
0
MED_L
MED_L
String
60
0
0
MED_R
MED_R
String
60
0
0
PSAP_L
PSAP_L
String
60
0
0
PSAP_R
PSAP_R
String
60
0
0
TravelTime
TravelTime
Double
8
38
8
Shape.STLength()
Shape.STLength()
Double
0
0
0
Esri ArcGIS 10.5.1.7333
NGRoad_Centerlines
1
-132.395193
-113.330834
33.465321
29.718751
Feature Class
dataset
EPSG
5.3(9.0.0)
16514
Simple
FALSE
16514
TRUE
FALSE
20181211