Arcs representing center of right-of-way and easements throughout Pierce County. Data is gps'd, acquired from orthophotos, or digitized using LIDAR according to "source" field. Additionally, data is acquired from other jurisdictions so currentness may vary between jurisdictions. Address ranges and full street names are included. Duplicate arcs are included on jurisdictional boundaries where they do not share the same street name. A supplemental street name alias table is used to aid in geocoding and for routing processes. The street name alias table can be downloaded here (https://matterhorn.piercecountywa.gov/OpenData/SupplementalData/StreetAliasTable/Street_Name_Alias_Table.zip). Please see the Roads metadata (https://matterhorn.piercecountywa.gov/GISmetadata/pdbis_roads.html) and Street Name Alias metadata (https://matterhorn.piercecountywa.gov/OpenData/SupplementalData/StreetAliasTable/streetnamealias.html) for additional information. Any use or data download constitutes acceptance of the Terms of Use (https://matterhorn.piercecountywa.gov/disclaimer/PierceCountyGISDataTermsofUse.pdf).

A vector line file of public/private streets compiled from orthoimagery and other sources that is attributed with street names, addresses, route numbers, routing attributes, and includes a related table of alternate/alias street names. A map service of the NYS Streets is available here: https://gisservices.its.ny.gov/arcgis/rest/services. Streets Data Dictionary: https://gis.ny.gov/system/files/documents/2023/07/streets_data_dictionary.pdf. If the purpose of using NYS Streets is for geocoding, the New York State Office of Information Technology Services (NYS ITS) has a publicly available geocoding service which includes the NYS Streets along with other layers. For more information about the geocoding service, please visit https://gis.ny.gov/address-geocoder. For more information about the SAM Program, please visit: https://gis.ny.gov/streets-addresses. Please contact NYS ITS Geospatial Services at nysgis@its.ny.gov if you have any questions.Publication Date: See Update Frequency. Current as of Date: 2 business days prior to Publication Date. Update frequency: Second and fourth Friday of each month This map service is available to the public.

Spatial Reference of Source Data: NAD_1983_UTM_Zone_18N.

Spatial Reference of Map Service: WGS 1984 Web Mercator Auxiliary.

This street centerline lines feature class represents current right of way in the City of Los Angeles. It shows the official street names and is related to the official street name data. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Street Centerline layer was created in geographical information systems (GIS) software to display Dedicated street centerlines. The street centerline layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. City of LA District Offices use Street Centerline layer to determine dedication and street improvement requirements. Engineering street standards are followed to dedicate the street for development. The Bureau of Street Services tracks the location of existing streets, who need to maintain that road. Additional information was added to Street Centerline layer. Address range attributes were added make layer useful for geocoding. Section ID values from Bureau of Street Services were added to make layer useful for pavement management. Department of City Planning added street designation attributes taken from Community Plan maps. The street centerline relates to the Official Street Name table named EASIS, Engineering Automated Street Inventory System, which contains data describing the limits of the street segment. A street centerline segment should only be added to the Street Centerline layer if documentation exists, such as a Deed or a Plan approved by the City Council. Paper streets are street lines shown on a recorded plan but have not yet come into existence on the ground. These street centerline segments are in the Street Centerline layer because there is documentation such as a Deed or a Plan for the construction of that street. Previously, some street line features were added although documentation did not exist. Currently, a Deed, Tract, or a Plan must exist in order to add street line features. Many street line features were edited by viewing the Thomas Bros Map's Transportation layer, TRNL_037 coverage, back when the street centerline coverage was created. When TBM and BOE street centerline layers were compared visually, TBM's layer contained many valid streets that BOE layer did not contain. In addition to TBM streets, Planning Department requested adding street line segments they use for reference. Further, the street centerline layer features are split where the lines intersect. The intersection point is created and maintained in the Intersection layer. The intersection attributes are used in the Intersection search function on NavigateLA on BOE's web mapping application NavigateLA. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. Note that there are named alleys in the BOE Street Centerline layer. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley , the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name stored in the STNAME and STSFX fields.List of Fields:SHAPE: Feature geometry.OBJECTID: Internal feature number.STNAME_A: Street name Alias.ST_SUBTYPE: Street subtype.SV_STATUS: Status of street in service, whether the street is an accessible roadway. Values: • Y - Yes • N - NoTDIR: Street direction. Values: • S - South • N - North • E - East • W - WestADLF: From address range, left side.ZIP_R: Zip code right.ADRT: To address range, right side.INT_ID_TO: Street intersection identification number at the line segment's end node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.SECT_ID: Section ID used by the Bureau of Street Services. Values: • none - No Section ID value • private - Private street • closed - Street is closed from service • temp - Temporary • propose - Proposed construction of a street • walk - Street line is a walk or walkway • known as - • numeric value - A 7 digit numeric value for street resurfacing • outside - Street line segment is outside the City of Los Angeles boundary • pierce - Street segment type • alley - Named alleySTSFX_A: Street suffix Alias.SFXDIR: Street direction suffix Values: • N - North • E - East • W - West • S - SouthCRTN_DT: Creation date of the polygon feature.STNAME: Street name.ZIP_L: Zip code left.STSFX: Street suffix. Values: • BLVD - BoulevardADLT: To address range, left side.ID: Unique line segment identifierMAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.STNUM: Street identification number. This field relates to the Official Street Name table named EASIS, to the corresponding STR_ID field.ASSETID: User-defined feature autonumber.TEMP: This attribute is no longer used. This attribute was used to enter 'R' for reference arc line segments that were added to the spatial data, in coverage format. Reference lines were temporary and not part of the final data layer. After editing the permanent line segments, the user would delete temporary lines given by this attribute.LST_MODF_DT: Last modification date of the polygon feature.REMARKS: This attribute is a combination of remarks about the street centerline. Values include a general remark, the Council File number, which refers the street status, or whether a private street is a private driveway. The Council File number can be researched on the City Clerk's website http://cityclerk.lacity.org/lacityclerkconnect/INT_ID_FROM: Street intersection identification number at the line segment's start node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.ADRF: From address range, right side.

A list of street segments and intersections sorted by street name and ascending address number. This data set is based on the City's GIS basemap and contains CNN id numbers for each record. If you are looking for a geometric field for each street, please refer to Streets - Active and Retired (https://data.sfgov.org/Geographic-Locations-and-Boundaries/Streets-Active-and-Retired/3psu-pn9h)

This map presents transportation data, including highways, roads, railroads, and airports for the world.

The map was developed by Esri using Esri highway data; Garmin basemap layers; HERE street data for North America, Europe, Australia, New Zealand, South America and Central America, India, most of the Middle East and Asia, and select countries in Africa. Data for Pacific Island nations and the remaining countries of Africa was sourced from OpenStreetMap contributors. Specific country list and documentation of Esri's process for including OSM data is available to view.

Streets data includes: Arterial Classification, Street Names, Block Number, Direction, One-way, Surface Width, Surface Type, Pavement Condition, Speed Limit, Percent Slope. From the Hansen Asset Management System:The linework is from the SND(Street Network Database) which can be found at our open data site - https://data-seattlecitygis.opendata.arcgis.com/datasets/street-network-database-snd. | Attribute Information: https://www.seattle.gov/Documents/Departments/SDOT/GIS/Seattle_Streets_OD.pdf | Update Cycle: Weekly| Contact Email: DOT_IT_GIS@seattle.gov--- Common SDOT queries and data downloads | Arterial Classification: of Seattle StreetsARTCLASS IN(1,2,3,4)| Transit Classification: of Seattle StreetsTRANCLASS IN(1,2,3,4,5,6)

Street name is the common name given to a piece of roadway. It usually matches the signed roadway name. Only county roads, state aid routes, and highways can have different street names along the same Route_ID. For other route systems each street name gets a separate Route_ID. Legacy data transferred from old Transportation Information System (TIS) may be exceptions to this rule.

Check other metadata records in this package for more information on Street Names Information.


Link to ESRI Feature Service:

Street Names in Minnesota: Street Names

Road segments representing centerlines of all roadways or carriageways in a local government. Typically, this information is compiled from orthoimagery or other aerial photography sources. This representation of the road centerlines support address geocoding and mapping. It also serves as a source for public works and other agencies that are responsible for the active management of the road network.

This dataset represents the centerline of all streets, roads and highways in Fulton County. Each record represents a street segment between at-grade intersections. Attributes include street name elements, odd and even address ranges, feature type, zip code (left and right) and highway number.The municipalities of Chattahoochee Hills, College Park, East Point, Fairburn, Hapeville, Palmetto, South Fulton, Union City, as well as the Fulton Industrial District (FID) are actively maintained by the Fulton County GIS Division. The data for Johns Creek, Milton, Alpharetta, Sandy Springs, and Roswell are obtained from the respective cities data portal or REST endpoint and incorporated into this countywide data. For questions or issues concerning these cities, please contact the owner of the respective data directly.

This line layer contains centerlines of all paved and unpaved roads, ramps, and bridges in the City of Cambridge. Each centerline segment contains attributes including street name, street type, address ranges, and one-way designations.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription ID type: Stringwidth: 40precision: 0 Unique identifier for each street segment

ROADWAYS type: Stringwidth: 1precision: 0 Divided street designation

ValueDescription TDivided FNot divided

Street type: Stringwidth: 40precision: 0 Full street name with street type

Street_Name type: Stringwidth: 30precision: 0 Street name only

Street_Type type: Stringwidth: 10precision: 0 Street type

Street_ID type: Doublewidth: 8precision: 38 Street ID number from master address database

Alias type: Stringwidth: 50precision: 0 Alternate street name

L_From type: Integerwidth: 4precision: 10 Left side address range 'from'

L_To type: Integerwidth: 4precision: 10 Left side address range 'to'

R_From type: Integerwidth: 4precision: 10 Right side address range 'from'

R_To type: Integerwidth: 4precision: 10 Right side address range 'to

FromNode type: Doublewidth: 8precision: 38 New 'from node' number

ToNode type: Doublewidth: 8precision: 38 New 'to node' number

Direction type: Stringwidth: 5precision: 0 One-way designation

ValueDescription 0Two-way street segment 1One-way street in same direction as street segment -1One-way street in opposite direction of street segment

Restriction type: Stringwidth: 1precision: 0 Truck restriction designation

Label type: Stringwidth: 50precision: 0 Street name field for labels when mapping

MajorRoad type: SmallIntegerwidth: 2precision: 5 Major road designation

ZIP_Left type: Stringwidth: 8precision: 0 Left side zip code

ZIP_Right type: Stringwidth: 8precision: 0 Right side zip code

EditDate type: Stringwidth: 4precision: 0 Date of last edit

Potential_L_From type: Integerwidth: 4precision: 10 Potential left side address range 'from'

Potential_L_To type: Integerwidth: 4precision: 10 Potential left side address range 'to'

Potential_R_From type: Integerwidth: 4precision: 10 Potential right side address range 'from'

Potential_R_To type: Integerwidth: 4precision: 10 Potential right side address range 'to'

Potentail_Range_Done type: SmallIntegerwidth: 2precision: 5 Potential range researched and populated

created_date type: Datewidth: 8precision: 0

last_edited_date type: Datewidth: 8precision: 0

Statewide Download (FGDB) (SHP)Users can also download smaller geographic areas of this feature service in ArcGIS Pro using the Copy Features geoprocessing tool. The New Jersey Office of Information Technology, Office of GIS (NJOGIS), in partnership with several local GIS and public safety agencies, as well as the NJ Department of Transportation, has built a comprehensive statewide NG9-1-1 database meeting and exceeding the requirements of the National Emergency Number Association (NENA) 2018 NG9-1-1 GIS Data Standard (NENA-STA-006.1-2018). The previous New Jersey statewide road segment data (Tran_road_centerline_NJ), which included the road name alias information, has been transformed into the NENA data model to create the street name alias table.The existing road centerlines were loaded into New Jersey's version of the NENA NG9-1-1 data model using Extract, Transform and Load (ETL) procedures created with Esri's Data Interoperability Extension. The data subsequently have been updated and corrected.The road centerlines no longer contain any linear referencing information. The linear referencing will only be maintained by the NJ Department of Transportation as part of the NJ Roadway Network.***NOTE*** For users who incorporate NJOGIS services into web maps and/or web applications, please sign up for the NJ Geospatial Forum discussion listserv for early notification of service changes. Visit https://nj.gov/njgf/about/listserv/ for more information.

This table of street names is based on the street directory maintained by the Department of Public Works & Parks (DPW&P) of the City of Worcester, MA. For labeling purposes, the unique name identifier, Street Name ID (NEW_NM_ID), corresponds with appropriate road centerline segments in the separate Street Centerlines dataset. To view the Street Directory visit the City of Worcester Street Directory.Informing Worcester is the City of Worcester's open data portal where interested parties can obtain public information at no cost.

Formerly known as the Massachusetts Highway Department (MHD) Roads, then the Executive Office of Transportation - Office of Transportation Planning (EOT-OTP) Roads, the MassGIS-MassDOT Roads layer includes linework from the 1:5,000 road and rail centerlines data that were interpreted as part of the 1990's Aerial Imagery project. The Massachusetts Department of Transportation - Office of Transportation Planning, which maintains the primary source for this layer, continues to add linework from municipal and other sources and update existing linework using the most recent aerial ortho imagery as a base. The attribute table includes many "road inventory" fields maintained in MassDOT's linear referencing system.The current MassGIS-MassDOT hybrid data layer was first published in November 2018, based on the MassDOT 2017 year-end Road Inventory layer and results of a 2014-2015 MassDOT-Central Transportation Planning Staff project to conflate street names and other attributes from MassGIS' "base streets" to the MassDOT Road Inventory linework. The base streets are continually maintained by MassGIS as part of the NextGen 911 and Master Address Database (MAD) projects. MassGIS staff reviewed the conflated layer and added many base street arcs digitized after the completion of the conflation work. MassGIS added several fields to support legacy symbology and labeling. Other edits included modifying some linework in areas of recent construction and roadway reconfiguration to align to 2017-2018 Google ortho imagery, and making minor fixes to attributes and linework. MassGIS continues to modify the layer as needed, modifying the linework using the latest aerial imagery and adding line features from the base street arcs.From this data layer MassGIS extracted Major Roads and Major Highway Routes layers.See full metadata

Road segments representing centerlines of all roadways or carriageways in a local government. Typically, this information is compiled from orthoimagery or other aerial photography sources. This representation of the road centerlines support address geocoding and mapping. It also serves as a source for public works and other agencies that are responsible for the active management of the road network. (From ESRI Local Government Model "RoadCenterline" Feature)**This dataset was significantly revised in August of 2014 to correct for street segments that were not properly split at intersections. There may be issues with using data based off of the original centerline file. ** The column Speed Limit was updated in November 2014 by the Transportation Intern and is believed to be accurate** The column One Way was updated in November of 2014 by core GIS and is believed to be accurate.[MAXIMOID] A unique id field used in a work order management software called Maximo by IBM. Maximo uses GIS CL data to assign locations to work orders using this field. This field is maintained by the Transportation GIS specialists and is auto incremented when new streets are digitized. For example, if the latest digitized street segment MAXIMOID = 999, the next digitized line will receive MAXIMOID = 1000, and so on. STREET NAMING IS BROKEN INTO THREE FIELDS FOR GEOCODING:PREFIX This field is attributed if a street name has a prefix such as W, N, E, or S.NAME Domain with all street names. The name of the street without prefix or suffix.ROAD_TYPE (Text,4) Describes the type of road aka suffix, if applicable. CAPCOG Addressing Guidelines Sec 504 U. states, “Every road shall have corresponding standard street suffix…” standard street suffix abbreviations comply with USPS Pub 28 Appendix C Street Abbreviations. Examples include, but are not limited to, Rd, Dr, St, Trl, Ln, Gln, Lp, CT. LEFT_LOW The minimum numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 101.LEFT_HIGH The largest numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 201.LOW The minimum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 100.HIGHThe maximum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 200.ALIAS Alternative names for roads if known. This field is useful for geocode re-matching. CLASSThe functional classification of the centerline. For example, Minor (Minor Arterial), Major (Major Arterial). THIS FIELD IS NOT CONSISTENTLY FILLED OUT, NEEDS AN AUDIT. FULLSTREET The full name of the street concatenating the [PREFIX], [NAME], and [SUFFIX] fields. For example, "W San Antonio St."ROWWIDTH Width of right-of-way along the CL segment. Data entry from Plat by Planning GIS Or from Engineering PICPs/ CIPs.NUMLANES Number of striped vehicular driving lanes, including turn lanes if present along majority of segment. Does not inlcude bicycle lanes. LANEMILES Describes the total length of lanes for that segment in miles. It is manually field calculated as follows (( [ShapeLength] / 5280) * [NUMLANES]) and maintained by Transportation GIS.SPEEDLIMIT Speed limit of CL segment if known. If not, assume 30 mph for local and minor arterial streets. If speed limit changes are enacted by city council they will be recorded in the Traffic Register dataset, and this field will be updating accordingly. Initial data entry made by CIP/Planning GIS and maintained by Transportation GIS.[YRBUILT] replaced by [DateBuilt] See below. Will be deleted. 4/21/2017LASTYRRECON (Text,10) Is the last four-digit year a major reconstruction occurred. Most streets have not been reconstructed since orignal construction, and will have values. The Transportation GIS Specialist will update this field. OWNER Describes the governing body or private entity that owns/maintains the CL. It is possible that some streets are owned by other entities but maintained by CoSM. Possible attributes include, CoSM, Hays Owned/City Maintained, TxDOT Owned/City Maintained, TxDOT, one of four counties (Hays, Caldwell, Guadalupe, and Comal), TxState, and Private.ST_FROM Centerline segments are split at their intersections with other CL segments. This field names the nearest cross-street in the From- direction. Should be edited when new CL segments that cause splits are added. ST_TO Centerline segments are split at their intersections with other CL segments. This field names the nearest cross-street in the To- direction. Should be edited when new CL segments that cause splits are added. PAV_WID Pavement width of street in feet from back-of-curb to back-of-curb. This data is entered from as-built by CIP GIS. In January 2017 Transportation Dept. field staff surveyed all streets and measured width from face-of-curb to face-of-curb where curb was present, and edge of pavement to edge of pavement where it was not. This data was used to field calculate pavement width where we had values. A value of 1 foot was added to the field calculation if curb and gutter or stand up curb were present (the face-of-curb to back-of-curb is 6 in, multiple that by 2 to find 1 foot). If no curb was present, the value enter in by the field staff was directly copied over. If values were already present, and entered from asbuilt, they were left alone. ONEWAY Field describes direction of travel along CL in relation to digitized direction. If a street allows bi-directional travel it is attributed "B", a street that is one-way in the From_To direction is attributed "F", a street that is one-way in the To_From direction is attributed "T", and a street that does not allow travel in any direction is attibuted "N". ROADLEVEL Field will be aliased to [MINUTES] and be used to calculate travel time along CL segments in minutes using shape length and [SPEEDLIMIT]. Field calculate using the following expression: [MINUTES] = ( ([SHAPE_LENGTH] / 5280) / ( [SPEEDLIMIT] / 60 ))ROWSTATUS Values include "Open" or "Closed". Describes whether a right-of-way is open or closed. If a street is constructed within ROW it is "Open". If a street has not yet been constructed, and there is ROW, it is "Cosed". UPDATE: This feature class only has CL geometries for "Open" rights-of-way. This field should be deleted or re-purposed. ASBUILT field used to hyper link as-built documents detailing construction of the CL. Field was added in Dec. 2016. DateBuilt Date field used to record month and year a road was constructed from Asbuilt. Data was collected previously without month information. Data without a known month is entered as "1/1/YYYY". When month and year are known enter as "M/1/YYYY". Month and Year from asbuilt. Added by Engineering/CIP. ACCEPTED Date field used to record the month, day, and year that a roadway was officially accepted by the City of San Marcos. Engineering signs off on acceptance letters and stores these documents. This field was added in May of 2018. Due to a lack of data, the date built field was copied into this field for older roadways. Going forward, all new roadways will have this date. . This field will typically be populated well after a road has been drawn into GIS. Entered by Engineering/CIP. ****In an effort to make summarizing the data more efficient in Operations Dashboard, a generic date of "1/1/1900" was assigned to all COSM owned or maintained roads that had NULL values. These were roads that either have not been accepted yet, or roads that were expcepted a long time ago and their accepted date is not known. WARRANTY_EXP Date field used to record the expiration date of a newly accepted roadway. Typically this is one year from acceptance date, but can be greater. This field was added in May of 2018, so only roadways that have been excepted since and older roadways with valid warranty dates within this time frame have been populated.

Roadways (streets and highways) for the San Francisco Bay Region. Feature set was assembled using all roads county-based 2021 TIGER/Line shapefiles by the Metropolitan Transportation Commission.The All Roads shapefiles includes all features within the Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB) Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.The feature set contains multiple overlapping road segments where a segment is associated with more than one road feature. For example, if a road segment is associated with US Route 36 and State Highway 7 and 28th Street, the route will contain three spatially coincident segments, each with a different name. The roadway feature set contains the set of unique road segments for each county, along with other linear features.Primary roads are generally divided limited-access highways within the Federal interstate highway system or under state management. Interchanges and ramps distinguish these roads, and some are toll highways.Secondary roads are main arteries, usually in the U.S. 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. They often have both a local name and a route number.

Feature layer of Streets.

Download In State Plane Projection Here. ** The Street Centerline feature class now follows the NG911/State of Illinois data specifications including a StreetNameAlias table. The download hyperlink above also contains a full network topology for use with the Esri Network Analyst extension ** These street centerlines were developed for a myriad of uses including E-911, as a cartographic base, and for use in spatial analysis. This coverage should include all public and selected private roads within Lake County, Illinois. Roads are initially entered using recorded documents and then later adjusted using current aerial photography. This dataset should satisfy National Map Accuracy Standards for a 1:1200 product. These centerlines have been provided to the United States Census Bureau and were used to conflate the TIGER road features for Lake County. The Census Bureau evaluated these centerlines and, based on field survey of 109 intersections, determined that there is a 95% confidence level that the coordinate positions in the centerline dataset fall within 1.9 meters of their true ground position. The fields PRE_DIR, ST_NAME, ST_TYPE and SUF_DIR are formatted according to United States Postal Service standards. Update Frequency: This dataset is updated on a weekly basis.

This list is a work-in-progress and will be updated at least quarterly. This version updates column names and corrects spellings of several streets in order to alleviate confusion and simplify street name research. It represents an inventory of official street name spellings in the City of New Orleans. Several sources contain various spellings and formats of street names. This list represents street name spellings and formats researched by the City of New Orleans GIS and City Planning Commission.Note: This list may not represent what is currently displayed on street signs. City of New Orleans official street list is derived from New Orleans street centerline file, 9-1-1 centerline file, and CPC plat maps. Fields include the full street name and the parsed elements along with abbreviations using US Postal Standards. We invite your input to as we work toward one enterprise street name list.Status: Current: Currently a known used street name in New Orleans Other: Currently a known used street name on a planned but not developed street. May be a retired street name.

The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.