Street Centerline (NG911) [Maryland--Baltimore]
Baltimore City · 2025 Full Details
Tip: Check “Visit Source” link for download options.
| Attribute | Value |
|---|---|
| Click on map to inspect values | |
Full Details
- Title
- Street Centerline (NG911) [Maryland--Baltimore]
- Description
- A spatial data layer containing line geometry features for representing the center line of roadways in Baltimore City, as documented in the City's enterprise GIS database and Department of Transportation right-of-way data sources. The data contains information on street address ranges, speed limits, one-way designations, street types, and many other street related data. The data employs what's referred to as the Next Generation 9-1-1 (NG911) schema/data standard, which has specific attribute field names, field formats, and data standards to support the standardization required by a future public safety NG911 system, as set forth by the National Emergency Number Association (NENA). The data contained in this data layer (number of features, accuracy, locations) will match the data in the other street centerline layer on Open Baltimore ("Street Centerline (Native)"), just the format of the attribute field names and data standards will be different. This data also employs the WGS 1984 projected coordinate system (WKID: 4326). Data is updated on a quarterly basis. Data Dictionary: field_name description data_type range_of_possible_values example_values searchable 1 OBJECTID The database's internal unique identifier for the data table record. Number 0 - 999999999 4721 No 2 DiscrpAgID Agency that receives a Discrepancy Report (DR), should a discrepancy be discovered, and will take responsibility for ensuring discrepancy resolution. This may or may not be the same as the 9-1-1 Authority. This MUST be represented by a domain name that is an Agency Identifier as defined in the NENA Master Glossary [1]. Free Text Entry % (any ID, per NG911 standard) pgcpsc.pgc.md.us.msi911.net (example from PG County, MD) Yes 3 DateUpdate The date and time that the record was created or last modified. This value MUST be populated upon modifications to attributes, geometry, or both. Date 1/1/1990 00:00:00 - 12/31/2100 00:00:00. 8/31/2021 10:04 Yes 4 effective The date and time that the record is scheduled to take effect in a NG911 system. Date 1/1/1990 00:00:00 - 12/31/2100 00:00:00. 8/31/2021 10:04 Yes 5 expire The date and time when the information in the record is no longer considered valid in a NG911 system. Date 1/1/1990 00:00:00 - 12/31/2100 00:00:00. 8/31/2021 10:04 Yes 6 RCL_NGUID 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 "locally unique ID". Free Text Entry % (any name, per NG911 standard) RCL243246@pgcpsc.pgc.md.us.msi911.net (example from PG County, MD) Yes 7 AdNumPre_L 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 alphanumeric characters, punctuation, and spaces preceding the Left FROM Address and Left TO Address. Free Text Entry % (any alphanumeric value), <Null> "101-" in "101-123 Grid Drive"; "N" in "N46999 Holden Road"; "0" in "012 Portland D" Yes 8 AdNumPre_R 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 alphanumeric characters, punctuation, and spaces preceding the Right FROM Address and Right TO Address. Free Text Entry % (any alphanumeric value), <Null> "2N3W-" in "2N3W-124 Township Drive", "S" in "S877 Highway 88" Yes 9 FromAddr_L In a GIS Road Centerlines layer, each feature has a begin point and an endpoint. The FROM Node is the begin point while the TO Node is the endpoint. Each has 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. Number 0 - 9999 400 Yes 10 ToAddr_L In a GIS, each feature has a begin point and an endpoint. The FROM Node is the begin point while the TO Node is the endpoint. Each has 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. Number 0 - 9999 498 Yes 11 FromAddr_R In a GIS Road Centerlines layer, each feature has a begin point and an endpoint. The FROM Node is the begin point while the TO node is the endpoint. Each has 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. Number 0 - 9999 401 Yes 12 ToAddr_R In a GIS Road Centerlines layer, each feature has a begin point andan en dpoint. The FROM Node is the begin point while the TO node is the endpoint. Each has 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. Number 0 - 9999 499 Yes 13 Parity_L The even or odd property of the address number range on the Left side of the road segment relative to the FROM Node. Category E=Even, O=Odd, B=Both, Z=0-0 Address Range or NULL-NULL Even, E Yes 14 Parity_R The even or odd property of the address number range on the Right side of the road segment relative to the FROM Node. Category E=Even, O=Odd, B=Both, Z=0-0 Address Range or NULL-NULL Odd, O Yes 15 St_PreMod 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 field length is currently 15 for existing special cases, but all attempts should be made to follow the domain for this field. Free Text Entry % (any name), <Null> <Null> Yes 16 St_PreDir A word preceding the Street Name element that indicates the direction taken by the road from an arbitrary starting point or line, or the sector where it is located. Category North, South, East, West, Northeast, Northwest, Southeast, Southwest, <Null> North, East Yes 17 St_PreTyp A word or phrase that precedes the Street Name element and identifies a type of thoroughfare in a complete street name. Category NENA defined list, <Null> Access Road, Causeway, "Avenue" in "Avenue A", "Highway" in "Highway 443", "Bypass Highway" in "Bypass Highway 22", "Boulevard" in "Boulevard of the Allies", <Null> Yes 18 St_PreSep A preposition or prepositional phrase between the Street Name Pre Type and the Street Name. This element is defined in CLDXF (NENA-STA-004) [3] as a US specific extension of PIDF-LO per RFC 6848 [6]. Category NENA defined list, <Null> at, de, de la, in the, of the, "of the" in "Avenue of the Stars", <Null> Yes 19 St_Name The official name of the road, usually defined by the lowest jurisdictional authority (e.g., Baltimore City). The street name does not include any street types, directionals, or modifiers. For "Alley" street type centerline segments, an alley naming routine was employed in the legacy database to populate the street name field based on the names of the parallel streets, with the western or northern street listed first (e.g., HICKORY-ROLAND). Alleys that did not have a second parallel street (i.e., alleys that back up to woods, train tracks, etc.) were named with the parallel street name and post type followed by "Rear" (e.g. TUSCANY CT REAR) to prevent potential name duplication. If there were multiple alleys in a single block, they were named as above, then numbered from west to east or north to south (e.g., CHESTNUT-KESWICK 1, CHESTNUT-KESWICK 2). Free Text Entry % (any name) FAYETTE, EASTERN, HICKORY-ROLAND Yes 20 St_PosTyp A word or phrase that follows the Street Name element and identifies a type of thoroughfare in a complete street name. The field length is currently 50 for existing special cases, but new assignments should follow the domain for this field. Category NENA defined list, <Null> Avenue, Street, Terrace, Garth Yes 21 St_PosDir A word following the Street Name element that indicates the direction taken by the road from an arbitrary starting point or line, or the sector where it is located. Category North, South, East, West, Northeast, Northwest, Southeast, Southwest, <Null> North, East Yes 22 St_PosMod A word or phrase that follows and modifies the Street Name element, but is separated from it by a Street Name Post Type or a Street Name Post Directional or both. Always follows and modifies the street name. Free Text Entry % (any name), <Null> <Null> Yes 23 LSt_PreDir The 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. Category N, S, E, W, NE, NW, SE, SW, <Null> N, E, "S" in " S PINE AVE" Yes 24 LSt_Name The street name field as it would appear in the MSAG and legacy database, as assigned by the local addressing authority. For "Alley" street type centerline segments, an alley naming routine was employed in the legacy database to populate the street name field based on the names of the parallel streets, with the western or northern street listed first (e.g., HICKORY-ROLAND). Alleys that did not have a second parallel street (i.e., alleys that back up to woods, train tracks, etc.) were named with the parallel street name and post type followed by "Rear" (e.g. TUSCANY CT REAR) to prevent potential name duplication. If there were multiple alleys in a single block, they were named as above, then numbered from west to east or north to south (e.g., CHESTNUT-KESWICK 1, CHESTNUT-KESWICK 2). Free Text Entry % (any name) FAYETTE, EASTERN, HICKORY-ROLAND Yes 25 LSt_Type 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. The United States Postal abbreviation for the street type. Category AL, AVE, BLVD, CIR, CRES, CT, DR, GLN, GRTH, HWY, LN, LNDG, MALL, MEWS, PASS, PATH, PIKE, PKWY, PL, PLZ, PLZA, PT, RD, RUN, SQ, ST, TER, TERR, WALK, WAY, <Null> AVE, ST, TER, GRTH Yes 26 LSt_PosDir 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. Category N, S, E, W, NE, NW, SE, SW, <Null> N, E, "E" in "KEY HWY E " Yes 27 ESN_L The Emergency Service Number as defined by the associated address points on the left-side directionality of the centerline segment. The Emergency Service Number is actually a 5-digit string, of which this schema is only capturing the last 3. The 3-digit code is prefixed with leading zeros. The ESN is a legacy element used for 10-digt routing. The ESN is also contained within the City MSAG database. Free Text Entry Legacy range of values: 2500 - 2694, 3809 (00500 - 00694 w/ prefixed zeros), <Null> Legacy value: 2502 (or "00502" w/ 2 prefixed zeros), <Null> Yes 28 ESN_R The Emergency Service Number as defined by the associated address points on the right-side directionality of the centerline segment. The Emergency Service Number is actually a 5-digit string, of which this schema is only capturing the last 3. The 3-digit code is prefixed with leading zeros. The ESN is a legacy element used for 10-digt routing. The ESN is also contained within the City MSAG database. Free Text Entry Legacy range of values: 2500 - 2694, 3809 (00500 - 00694 w/ prefixed zeros), <Null> Legacy value: 2502 (or "00502" w/ 2 prefixed zeros), <Null> Yes 29 MSAGComm_L This is not the administrative or postal city designation. This field should contain the MSAG Community Name, assigned by the 9-1-1 authority, which the associated address points on the left-side directionality of the centerline segment are contained within. Free Text Entry BALTIMORE, <Null> BALTIMORE Yes 30 MSAGComm_R This is not the administrative or postal city designation. This field should contain the MSAG Community Name, assigned by the 9-1-1 authority, which the associated address points on the right-side directionality of the centerline segment are contained within. Free Text Entry BALTIMORE, <Null> BALTIMORE Yes 31 Country_L 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. Category United States (US) United States, US Yes 32 Country_R 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. Category United States (US) United States, US Yes 33 State_L The 2-letter abbreviation for the federal state area that the associated address points on the left-side directionality of the centerline segment are contained within. Category Maryland (MD) Maryland, MD Yes 34 State_R The 2-letter abbreviation for the federal state area that the associated address points on the right-side directionality of the centerline segment are contained within. Category Maryland (MD) Maryland, MD Yes 35 County_L The administrative county area that the associated address points on the left-side directionality of the centerline segment are contained within (all records will have the value "Baltimore City"). Category Baltimore City Baltimore City Yes 36 County_R The administrative county area that the associated address points on the right-side directionality of the centerline segment are contained within (all records will have the value "Baltimore City"). Category Baltimore City Baltimore City Yes 37 AddCode_L The Additional Code on the Left side of the road segment relative to the FROM Node. Free Text Entry % (any alphanumeric code), <Null> <Null> Yes 38 AddCode_R The Additional Code on the Right side of the road segment relative to the FROM Node. Free Text Entry % (any alphanumeric code), <Null> <Null> Yes 39 IncMuni_L The officially recognized municipality or other general-purpose local governmental unit as set forth by the United States Postal Service (USPS) the addresses contained in the range for the left side of the centerline feature are located relative to the FROM Node (all records will have the value "Baltimore"). However, use "Unincorporated" if the address is not within an incorporated local government. Category Baltimore Baltimore Yes 40 IncMuni_R The officially recognized municipality or other general-purpose local governmental unit as set forth by the United States Postal Service (USPS) the addresses contained in the range for the right side of the centerline feature are located relative to the FROM Node (all records will have the value "Baltimore"). However, use "Unincorporated" if the address is not within an incorporated local government. Category Baltimore Baltimore Yes 41 UnincCom_L The Unincorporated Community, either within an incorporated municipality or in an unincorporated portion of a county, or both, on the Left side of the road segment relative to the FROM Node. Free Text Entry % (any name), <Null> <Null> Yes 42 UnincCom_R The Unincorporated Community, either within an incorporated municipality or in an unincorporated portion of a county, or both, on the Right side of the road segment relative to the FROM Node. Free Text Entry % (any name), <Null> <Null> Yes 43 NbrhdCom_L The name of an unincorporated neighborhood, subdivision or area, either within an incorporated municipality or in an unincorporated portion of a county or both, on the Left side of the road segment relative to the FROM Node. Free Text Entry % (any name), <Null> Canton, Mount Vernon, Park Heights Yes 44 NbrhdCom_R The name of an unincorporated neighborhood, subdivision or area, either within an incorporated municipality or in an unincorporated portion of a county or both, on the Right side of the road segment relative to the FROM Node. Free Text Entry % (any name), <Null> Canton, Mount Vernon, Park Heights Yes 45 PostCode_L The 5-digit code assigned to the USPS post office servicing the associated address points on the left-side directionality of the centerline segment. Category 21201 - 21287 21202 Yes 46 PostCode_R The 5-digit code assigned to the USPS post office servicing the associated address points on the right-side directionality of the centerline segment. Category 21201 - 21287 21202 Yes 47 PostComm_L A city name for the ZIP Code of an address, as given in the USPS City State Product on the Left side of the road segment relative to the FROM Node. Free Text Entry % (any name), <Null> Baltimore, <Null> Yes 48 PostComm_R A city name for the ZIP Code of an address, as given in the USPS City State Product on the Right side of the road segment relative to the FROM Node. Free Text Entry % (any name), <Null> Baltimore, <Null> Yes 49 RoadClass 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). Category US Census/NENA defined list, <Null> Ramp, Alley, Parking Lot, Tunnel Yes 50 OneWay 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). Category 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, <Null> B, Both, FT, From-To, TF, To-From Yes 51 SpeedLimit Posted Speed Limit in MPH in US or Km/h in Canada. Number 1 - 65, 0 or <Null> (no data) 25, 30, 55 Yes 52 Valid_L Indicates if the address range on the left side of the road segment should be used for civic location validation. A value of "Y" MAY be entered if any Address Number within the address range on the left side of the road segment should be considered by the LVF to be valid. A value of "N" MAY be entered if the Address Number should only be validated using the Site/Structure Address Points layer. If not present, a value of "Y" is assumed. Category Y (Yes), N (No), <Null> Y, <Null> Yes 53 Valid_R Indicates if the address range on the right side of the road segment should be used for civic location validation. A value of "Y" MAY be entered if any Address Number within the address range on the right side of the road segment should be considered by the LVF to be valid. A value of "N" MAY be entered if the Address Number should only be validated using the Site/Structure Address Points layer. If not present, a value of "Y" is assumed. Category Y (Yes), N (No), <Null> Y, <Null> Yes 54 psap_idleft The identification name of the PSAP on the left side of the road segment. Free Text Entry % (any alphanumeric ID), <Null> <Null> Yes 55 psap_idright The identification name of the PSAP on the right side of the road segment. Free Text Entry % (any alphanumeric ID), <Null> <Null> Yes 56 external_nguid The current unique identifier for the centerline feature. Free Text Entry 1 - 999999999 14246 Yes 57 globalid The global unique identifier for the centerline feature. Number {%%%%%%%%-%%%%-%%%%-%%%%-%%%%%%%%%%%%} (any 36 character alphanumeric value) {959A5832-A3B6-470D-A1ED-CC657E16902A} No 58 data_source The name/label of the source of the centerline data. Free Text Entry % (any source name), <Null> <Null> Yes 63 fullrdname The full name of the street, a concatenation of the street name pre-modifier (if exists, St_PreMod field), the street name pre-directional (St_PreDir), the street name pre-type (if exists, St_PreTyp), the street name pre-type separator (if exists, St_PreSep), the street name (St_Name), street name post type (St_PosTyp), the street name post directional (if exists, St_PosDir), and street post modifier (if exists, St_PosMod) fields. Free Text Entry % (any street name in City) EAST FAYETTE STREET Yes 64 feature_status The status of the centerline feature, indicating whether the centerline is an existing or "Active" roadway, "Retired" due to removal or alteration, or "Proposed" future centerline pending a development. Category Active, Proposed, Retired, <Null> Active Yes 65 F_ELEV Connectivity policy value for modeling overpasses and underpasses. From topological network elevation level, required for topological routing data to indicate valid turns. The topological network elevation of the FROM node. Number 0, -1, 1, 2, 3 0, -1 Yes 66 T_ELEV Connectivity policy value for modeling overpasses and underpasses. From topological network elevation level, required for topological routing data to indicate valid turns. The topological network elevation of the TO node. Number 0, -1, 1, 2, 3 0, -1 Yes 67 Shape The geometry designation of the centerline feature, for GIS purposes. Category Polyline Polyline No 68 Shape.STLength() ESRI geodatabase internal length field (in feet). Number 0 - 999999999 355.725225 No To leave feedback or ask a question about this dataset, please fill out the following form: Street Centerline (NG911) feedback form.
- Creator
- Baltimore City
- Temporal Coverage
- Last Modified: 2025-01-27
- Date Issued
- 2023-12-22
- Access Rights
- Public
- Format
- ArcGIS FeatureLayer
- Language
- English
- Date Added
- August 10, 2025
- Provenance Statement
- The metadata for this resource was last retrieved from Open Baltimore on 2025-08-24.
Resource Class
Theme
Place
Local Collection
Cite and Reference
-
Citation
Baltimore City (2023). Street Centerline (NG911) [Maryland--Baltimore]. . https://data.baltimorecity.gov/datasets/baltimore::street-centerline-ng911-1 (web service) -
BTAA Geoportal Link
