20190207 16431200 1.0 FGDC CSDGM Metadata FALSE MukilteoStreets_OFFICIAL_1 002 1274392.951130 1285456.451313 322351.184163 350634.550496 1 Projected GCS_North_American_1983 Linear Unit: Foot_US (0.304801) NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.7'><WKT>PROJCS["NAD_1983_StatePlane_Washington_North_FIPS_4601_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",1640416.666666667],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-120.8333333333333],PARAMETER["Standard_Parallel_1",47.5],PARAMETER["Standard_Parallel_2",48.73333333333333],PARAMETER["Latitude_Of_Origin",47.0],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2285]]</WKT><XOrigin>-117104300</XOrigin><YOrigin>-99539600</YOrigin><XYScale>3048.0060960121928</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102748</WKID><LatestWKID>2285</LatestWKID></ProjectedCoordinateSystem> 20220217 10470100 20260330 13535000 500000 5000 ItemDescription Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 MukilteoStreets_OFFICIAL Next Generation 911 Street Model Robert Thurston Snohomish County Enhanced 911 GIS Analyst The OFFICAL Street Network for the City of Mukilteo. Originally derived from Call Routing via Washington State ESINET layer, Snohomish County reformatted and the City of Mukilteo downloaded the GIS layer in 2013. Storage of City Policy data is maintained in this GIS layer. Contains <DIV STYLE="text-align:Left;"><DIV><DIV>This dataset contains the street centerline data for Snohomish County. It follows the Washington State NG 911 Model for use in emergency call routing. Any other use of this data is not directly supported by Snohomish County.Field: Functional_Class - 2024 City Comp Plan Transportation Chapter Roadway Network Map (Fig 37) with Annexation update from City EngineerField: Ownership - Official ownership of the roadwayField: Snow_Removal - Priority 1 - City-focused Main Arterials clearing, Priority 2 - Main Collector roads and critical hills, Priority 3 - Other Secondary/Collector roads Field: DeIcing - De-Icing Route Yes/NoField: Street_Sweeper - Street sweeping routesField: Sole_Access_for_COF - Routes important for Critical Facility access in emergency eventsField: Width - Average Pavement Width (from Street Saver)</DIV></DIV></DIV> Snohomish County Enhanced 911 Office 911, street centerline Snohomish County, Washington State Robert Thurston Snohomish County Enhanced 911 GIS Analyst Robert Thurston 1 -122.327099 -122.279790 47.952091 47.873989 Streets General Plan WSDOT Arterial Collector Roads File Geodatabase Feature Class dataset EPSG 5.3(9.0.0) 0 Simple FALSE 0 TRUE FALSE MukilteoStreets_OFFICIAL_1 Feature Class 0 WA NG911 Data Model OBJECTID OBJECTID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Source Source of Data String 75 0 0 5.104 Source of Data 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 WA NG911 Data Model DateUpdate Date Updated Date 8 0 0 5.37 Date Updated 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) WA NG911 Data Model Effective Effective Date Date 8 0 0 5.39 Effective Date 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) NOTE: This field is used when time and date of a change is known. For example, the time and date an annexation takes effect. WA NG911 Data Model Expire Expiration Date Date 8 0 0 5.46 Expiration Date Description: 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) NOTE: This field is used when time and date of a change is known. For example, the time and date an annexation takes effect and the previous boundary is retired. WA NG911 Data Model RCL_NGUID Road Centerline NENA Globally Unique ID String 100 0 0 5.93 Road Centerline NENA Globally Unique ID Description: The 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@9-1-1Authority_domain.state.us WA NG911 Data Model AdNumPre_L Left Address Number Prefix String 15 0 0 5.57 Left Address Number Prefix 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” WA NG911 Data Model AdNumPre_R Right Address Number Prefix String 15 0 0 5.90 Right Address Number Prefix 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” WA NG911 Data Model FromAddr_L Left FROM Address Double 6 0 0 5.58 Left FROM Address 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 WA NG911 GIS Data Model ToAddr_L Left TO Address Double 6 0 0 5.59 Left TO Address 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 Example: See Figure 7 above NOTE: Many CAD systems assume addresses are increasing in the FROM TO Node direction. Some geocoding applications assume addresses are increasing in the FROM TO Node direction. Many entities are moving to this so they can create one set of base data that can be used for 9-1-1, Engineering, Planning, Taxation, and Transportation Departments. WA NG911 GIS Data Model FromAddr_R Right FROM Address Double 6 0 0 5.91 Right FROM Address 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 WA NG911 GIS Data Model ToAddr_R Right TO Address Double 6 0 0 5.92 Right TO Address 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 WA NG911 GIS Data Model Parity_L Parity_L String 1 0 0 5.80 Parity Left 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 WA NG911 GIS Data Model Parity_R Parity_R String 1 0 0 5.81 Parity Right 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 WA NG911 GIS Data Model St_PreMod Street Name Pre Modifier String 15 0 0 5.115 Street Name Pre Modifier 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. Domain: None Example: “Bypass” in “Bypass State Route 281” “Old” in “Old North Church Street” WA NG911 GIS Data Model St_PreDir Street Name Pre Directional String 9 0 0 5.114 Street Name Pre Directional 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” WA NG911 GIS Data Model North North WA NG911 GIS Data Model South South WA NG911 GIS Data Model East East WA NG911 GIS Data Model West West WA NG911 GIS Data Model Northeast Northeast WA NG911 GIS Data Model Northwest Northwest WA NG911 GIS Data Model Southeast Southeast WA NG911 GIS Data Model Southwest Southwest WA NG911 GIS Data Model St_PreTyp St_PreTyp String 25 0 0 5.116 Street Name Pre Type 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” Street Name Pre Type St_PreSep Street Name Pre Type Seperator String 20 0 0 5.117 Street Name Pre Type Separator 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 RFC6848. 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” WA NG911 GIS Data Model StreetName Street Name String 60 0 0 5.110 Street Name 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” WA NG911 GIS Data Model St_PosTyp Street Name Post Type String 15 0 0 5.113 Street Name Post Type 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” WA NG911 GIS Data Model St_PosDir Street Name Pst Directional String 9 0 0 5.111 Street Name Post Directional 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” WA NG911 GIS Data Model St_PosMod Street Name Post Modifier String 25 0 0 5.112 Street Name Post Modifier 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” WA NG911 GIS Data Model LSt_PreDir Legacy Street Name Pre Directional String 2 0 0 5.62 Legacy Street Name Pre Directional 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” WA NG911 GIS Data Model LSt_Name Legacy Street Name String 75 0 0 5.60 Legacy Street Name 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 backwards 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. WA NG911 GIS Data Model LSt_Type Legacy Street Name Type String 5 0 0 5.63 Legacy Street Name Type 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” WA NG911 GIS Data Model LStPosDir Legacy Street Name Post Directional String 2 0 0 5.61 Legacy Street Name Post Directional 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” WA NG911 GIS Data Model ESN_L ESN Left String 5 0 0 5.43 ESN Left: 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 WA NG911 GIS Data Model ESN_R ESN Right String 5 0 0 5.44 ESN Right: 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 WA NG911 GIS Data Model MSAGComm_L MSAG Community Name Left String 30 0 0 5.73 MSAG Community Name Left Description: The existing MSAG Community Name on the Left side of the road segment relative to the FROM Node. Domain: None Example: Harris County NOTE: Used in Legacy Systems and is not used in a full NG9-1-1 implementation. WA NG911 GIS Data Model MSAGComm_R MSAG Community Name Right String 30 0 0 5.74 MSAG Community Name Right Description: The existing MSAG Community Name on the Right side of the road segment relative to the FROM Node. Domain: None Example: Crystal City NOTE: Used in Legacy Systems and is not used in a full NG9-1-1 implementation. Country_L Country Left String 2 0 0 5.31 Country Left 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 WA NG911 GIS Data Manual Country_R Country Right String 2 0 0 5.32 Country Right 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 WA NG911 GIS Data Model State_L State Left String 2 0 0 5.107 State Left 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 WA NG911 GIS Data Model State_R State Right String 2 0 0 5.108 State Right 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: SO 3166-2 or USPS Publication 28, Appendix B for the US Example: PA; KY WA NG911 GIS Data Model County_L County Left String 40 0 0 5.34 County Left 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 WA NG911 GIS Data Model County_R County Right String 40 0 0 5.35 County Right 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 WA NG911 GIS Data Model AddCode_L Additional Code Left String 6 0 0 5.2 Additional Code Left 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 WA NG911 GIS Data Model AddCode_R Additional Code Right String 6 0 0 5.3 Additional Code Right 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 WA NG911 GIS Data Model IncMuni_L Incorporated Municipality Left String 100 0 0 5.49 Incorporated Municipality Left 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: Lexington; Columbus; Unincorporated WA NG911 GIS Data Model IncMuni_R Incorporated Municipality Right String 100 0 0 5.50 Incorporated Municipality Right 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 WA NG911 GIS Data Model UnincCom_L Unincorporated Community Left String 100 0 0 5.121 Unincorporated Community Left Description: The Unincorporated Community on the Left side of the road segment relative to the FROM Node. Domain: None Example: Latham (NY); Moose (WY) WA NG911 GIS Data Model UnincCom_R Unincorporated Community Right String 100 0 0 5.122 Unincorporated Community Right 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) WA NG911 GIS Data Model NbrhdCom_L Neighborhood Community Left String 100 0 0 5.76 Neighborhood Community Left 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 WA NG911 GIS Data Model NbrhdCom_R Neighborhood Community Right String 100 0 0 5.77 Neighborhood Community Right 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 WA NG911 GIS Data Model PostCode_L Postal Code Left String 7 0 0 5.85 Postal Code Left 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) WA NG911 GIS Data Model PostCode_R Postal Code Right String 7 0 0 5.86 Postal Code Right 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) WA NG911 GIS Data Model PostComm_L Postal Community Left String 40 0 0 5.88 Postal Community Name Left 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 WA NG911 GIS Data Model PostComm_R Postal Community Right String 40 0 0 5.89 Postal Community Name Right 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 WA NG911 GIS Data Model RoadClass Road Class String 15 0 0 5.94 Road Class 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 depreciated 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 includes 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.) - A road within private property that is privately maintained for service, extractive, or other purposes. These roads are often unnamed. • 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 unaddressed 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 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. WA NG911 GIS Data Model OneWay One-Way String 2 0 0 5.79 One-Way 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 WA NG911 GIS Data Model SpeedLimit Speed Limit SmallInteger 2 0 0 5.105 Speed Limit Description: Posted Speed Limit in MPH in US or Km/h in Canada Domain: Whole numbers from 1 to 120 Example: 35; 55; 70 WA NG911 GIS Data Model FL_STRTNM FL_STRTNM String 100 0 0 L_STRTNM L_STRTNM String 100 0 0 GC_Exception GC_Exception String 100 0 0 ST_CLASS ST_CLASS String 50 0 0 TRAVEL_TIME TRAVEL_TIME Double 8 0 0 UNIQUEID UNIQUEID Integer 4 0 0 SHAPE Shape Geometry 0 0 0 Feature geometry. Esri Coordinates defining the features. ALTERNATE_ ALTERNATE_ String 60 0 0 Ownership Ownership String 50 0 0 PCI_Join PCI_Join String 100 0 0 Street_Width Street_Width Single 4 0 0 Street_Width_Buffer Street_Width_Buffer Single 4 0 0 Shape_Length Shape_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. Functional_Class Functional_Class String 100 0 0 PCI_2007 PCI_2007 Double 8 0 0 PCI_2014 PCI_2014 Double 8 0 0 PCI_2016 PCI_2016 Double 8 0 0 PCI_2018 PCI_2018 Double 8 0 0 Truck_Route Truck_Route String 5 0 0 Snow_Removal Snow_Removal String 10 0 0 DeIcing De-Icing? String 10 0 0 Sole_Access_for_COF Sole_Access_for_COF String 10 0 0 Street_Sweeper Street Sweeping? String 10 0 0 20260330 Robert Thurston Snohomish County Enhanced 911 GIS Analyst Robert Thurston 3000 Rockefeller Ave M/S 406 Everett WA 98201 robert.thurston@snoco.org 425-388-3886 M-F 8:00 to 5:00 <DIV STYLE="text-align:Left;"><DIV><DIV>Snohomish County GIS Data and Map DisclaimerThis is for use with the shared GIS data sets that are provided by the Snohomish County Enhanced 9-1-1 Office. All partners with the E9-1-1 Office should understand the street centerline data and address point data are dynamic data sets that are in constant change and revision. The express intention for sharing these is to improve the accuracy and reliability of the data sets that directly support the 9-1-1 call taking business functions of the Snohomish County Public Safety Answering Point (PSAP’s). Further, Snohomish County disclaims any warranty of merchantability or warranty of fitness of this data (or map) for any particular purpose, either express or implied. No representation or warranty is made concerning the accuracy, currency, completeness or quality of data depicted. Any user of this data (or map) assumes all responsibility for use thereof, and further agrees to hold Snohomish County harmless from and against any damage, loss, or liability arising from any use of this data (or map). </DIV></DIV></DIV>