{"action":"create","ckan_id":null,"date_created":"Sat, 14 Mar 2026 20:40:03 GMT","date_finished":null,"harvest_job_id":"f9e30a5f-6df0-4a44-8219-6bb17207dbcf","harvest_source_id":"abba255d-4153-4d75-89dc-14b63138fe6b","id":"b7d6e127-c1ae-47dc-a7a5-0632c7061afd","identifier":"https://www.arcgis.com/home/item.html?id=6454e7137e6943ca9c7984d0ab1eb4d4&sublayer=0","parent_identifier":null,"source_hash":"5820fcd08f2e7c996b1db4358cb3bee504798e326cd5d842e77912a1d117003e","source_raw":"{\"@type\": \"dcat:Dataset\", \"accessLevel\": \"public\", \"contactPoint\": {\"@type\": \"vcard:Contact\", \"fn\": \"baltimore_city\", \"hasEmail\": \"mailto:gis@baltimorecity.gov\"}, \"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 (\\u201cStreet Centerline (Native)\\u201d), 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:


\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
 field_namedescriptiondata_typerange_of_possible_valuesexample_valuessearchable
1OBJECTIDThe database\\u2019s\\n internal unique identifier for the data table record.Number0 - 9999999994721No
2DiscrpAgIDAgency that\\n receives a Discrepancy Report (DR), should a
\\n discrepancy be discovered, and will take responsibility for ensuring\\n discrepancy resolution. This may or may not be the same as the 9-1-1\\n Authority. This MUST be represented by a domain name that is an Agency\\n Identifier as defined in the NENA Master Glossary [1].		Free Text Entry% (any ID, per\\n NG911 standard)pgcpsc.pgc.md.us.msi911.net\\n (example from PG County, MD)Yes
3DateUpdateThe date and\\n time that the record was created or last modified. This value MUST be\\n populated upon modifications to attributes, geometry, or both.Date1/1/1990\\n 00:00:00 - 12/31/2100 00:00:00.8/31/2021 10:04Yes
4effectiveThe date and\\n time that the record is scheduled to take effect in a NG911 system.Date1/1/1990\\n 00:00:00 - 12/31/2100 00:00:00.8/31/2021 10:04Yes
5expireThe date and\\n time when the information in the record is no longer considered valid in a\\n NG911 system.Date1/1/1990\\n 00:00:00 - 12/31/2100 00:00:00.8/31/2021 10:04Yes
6RCL_NGUIDThe NENA\\n Globally Unique ID for each Road Centerline. Each record in the Road\\n Centerlines layer MUST have a globally unique ID. When coalescing data from\\n other local 9-1-1 Authorities into the ECRF and LVF, this unique ID MUST\\n continue to have only one occurrence. One way to accomplish this is to append\\n the 9-1-1 Authority\\u2019s domain to the end of the \\u201clocally unique ID\\u201d.Free Text Entry% (any name,\\n per NG911 standard)RCL243246@pgcpsc.pgc.md.us.msi911.net  (example from PG\\n County, MD)Yes
7AdNumPre_LAn extension of\\n the Address Number that precedes it and further identifies a location along a\\n thoroughfare or within a defined area, on the Left side of the road segment\\n relative to the FROM Node. It contains any alphanumeric characters,\\n punctuation, and spaces preceding the Left FROM Address and Left TO Address.Free Text Entry% (any\\n alphanumeric value), <Null>\\\"101-\\\"\\n in \\u201c101-123 Grid Drive\\u201d; \\u201cN\\u201d in \\u201cN46999 Holden Road\\u201d; \\u201c0\\u201d in \\u201c012 Portland D\\u201dYes
8AdNumPre_RAn extension of\\n the Address Number that precedes it and further identifies a location along a\\n thoroughfare or within a defined area, on the Right side of the road segment\\n relative to the FROM Node. It contains any alphanumeric characters,\\n punctuation, and spaces preceding the Right FROM Address and Right TO\\n Address.Free Text Entry% (any\\n alphanumeric value), <Null>\\\"2N3W-\\\"\\n in \\u201c2N3W-124 Township Drive\\u201d, \\u201cS\\u201d in \\u201cS877 Highway 88\\u201dYes
9FromAddr_LIn a GIS Road\\n Centerlines layer, each feature has a begin point and an endpoint. The FROM\\n Node is the begin point while the TO Node is the endpoint. Each has a left\\n side and a right side relative to a begin node and an end node. The Left FROM\\n address is the address number on the Left side of the road segment relative\\n to the Left FROM Node.Number0 - 9999400Yes
10ToAddr_LIn a GIS, each\\n feature has a begin point and an endpoint. The FROM Node is the begin point\\n while the TO Node is the endpoint. Each has a left side and a right side\\n relative to a begin node and an end node. The Left TO address is the address\\n number on the Left side of the road segment relative to the Left TO Node.Number0 - 9999498Yes
11FromAddr_RIn a GIS Road\\n Centerlines layer, each feature has a begin point and an endpoint. The FROM\\n Node is the begin point while the TO node is the endpoint. Each has a left\\n side and a right side relative to a begin node and an end node. The Right\\n FROM address number is the address number on the Right side of the road\\n segment relative to the Right FROM Node. Number0 - 9999401Yes
12ToAddr_RIn a GIS Road\\n Centerlines layer, each feature has a begin point andan en dpoint. The FROM\\n Node is the begin point while the TO node is the endpoint. Each has a left\\n side and a right side relative to a begin node and an end node. The Right TO\\n address number is the address number on the Right side of the road segment\\n relative to the Right TO Node.Number0 - 9999499Yes
13Parity_LThe even or odd\\n property of the address number range on the Left side of the road segment\\n relative to the FROM Node.CategoryE=Even, O=Odd,\\n B=Both, Z=0-0 Address Range or NULL-NULLEven, EYes
14Parity_RThe even or odd\\n property of the address number range on the Right side of the road segment\\n relative to the FROM Node.CategoryE=Even, O=Odd,\\n B=Both, Z=0-0 Address Range or NULL-NULLOdd, OYes
15St_PreModA\\n word or phrase that precedes and modifies the Street Name element but is\\n separated from it by a Street Name Pre Type or a Street Name Pre Directional\\n or both. The field length is currently 15 for existing special cases, but all\\n attempts should be made to follow the domain for this field.Free\\n Text Entry%\\n (any name), <Null><Null>Yes
16St_PreDirA\\n word preceding the Street Name element that indicates the direction taken by\\n the road from an arbitrary starting point or line, or the sector where it is\\n located.CategoryNorth,\\n South, East, West, Northeast, Northwest, Southeast, Southwest, <Null>North,\\n EastYes
17St_PreTypA\\n word or phrase that precedes the Street Name element and identifies a type of\\n thoroughfare in a complete street name.CategoryNENA\\n defined list, <Null>Access\\n Road, Causeway, \\u201cAvenue\\u201d in \\u201cAvenue A\\u201d, \\u201cHighway\\u201d in \\u201cHighway 443\\u201d, \\u201cBypass\\n Highway\\u201d in \\u201cBypass Highway 22\\u201d, \\u201cBoulevard\\u201d in \\u201cBoulevard of the Allies\\u201d,\\n <Null>Yes
18St_PreSepA\\n preposition or prepositional phrase between the Street Name Pre Type and the\\n Street Name. This element is defined in CLDXF (NENA-STA-004) [3] as a US\\n specific extension of PIDF-LO per RFC 6848 [6].CategoryNENA\\n defined list, <Null>at,\\n de, de la, in the, of the, \\u201cof the\\u201d in \\u201cAvenue of the Stars\\\", <Null>Yes
19St_NameThe\\n official name of the road, usually defined by the lowest jurisdictional\\n authority (e.g., Baltimore City). The street name does not include any street\\n types, directionals, or modifiers. For \\\"Alley\\\" street type\\n centerline segments, an alley naming routine was employed in the legacy\\n database to populate the street name field based on the names of the parallel\\n streets, with the western or northern street listed first (e.g.,\\n HICKORY-ROLAND). Alleys that did not have a second parallel street (i.e.,\\n alleys that back up to woods, train tracks, etc.) were named with the\\n parallel street name and post type followed by \\u201cRear\\u201d (e.g. TUSCANY CT REAR)\\n to prevent potential name duplication. If there were multiple alleys in a\\n single block, they were named as above, then numbered from west to east or\\n north to south (e.g., CHESTNUT-KESWICK 1, CHESTNUT-KESWICK 2).Free\\n Text Entry%\\n (any name)FAYETTE,\\n EASTERN, HICKORY-ROLANDYes
20St_PosTypA\\n word or phrase that follows the Street Name element and identifies a type of\\n thoroughfare in a complete street name. The field length is currently 50 for\\n existing special cases, but new assignments should follow the domain for this\\n field.CategoryNENA\\n defined list, <Null>Avenue,\\n Street, Terrace, GarthYes
21St_PosDirA\\n word following the Street Name element that indicates the direction taken by\\n the road from an arbitrary starting point or line, or the sector where it is\\n located.CategoryNorth,\\n South, East, West, Northeast, Northwest, Southeast, Southwest, <Null>North,\\n EastYes
22St_PosModA\\n word or phrase that follows and modifies the Street Name element, but is\\n separated from it by a Street Name Post Type or a Street Name Post\\n Directional or both. Always follows and modifies the street name.Free\\n Text Entry%\\n (any name), <Null><Null>Yes
23LSt_PreDirThe\\n leading street direction prefix as it previously existed prior to the\\n adoption of the NG9-1-1 Data Model as assigned by the local addressing\\n authority.CategoryN,\\n S, E, W, NE, NW, SE, SW, <Null>N,\\n E, \\u201cS\\u201d in \\u201cS PINE AVE\\u201dYes
24LSt_NameThe\\n street name field as it would appear in the MSAG and legacy database, as\\n assigned by the local addressing authority. For \\\"Alley\\\" street type\\n centerline segments, an alley naming routine was employed in the legacy\\n database to populate the street name field based on the names of the parallel\\n streets, with the western or northern street listed first (e.g.,\\n HICKORY-ROLAND). Alleys that did not have a second parallel street (i.e.,\\n alleys that back up to woods, train tracks, etc.) were named with the\\n parallel street name and post type followed by \\u201cRear\\u201d (e.g. TUSCANY CT REAR)\\n to prevent potential name duplication. If there were multiple alleys in a\\n single block, they were named as above, then numbered from west to east or\\n north to south (e.g., CHESTNUT-KESWICK 1, CHESTNUT-KESWICK 2).Free\\n Text Entry%\\n (any name)FAYETTE,\\n EASTERN, HICKORY-ROLANDYes
25LSt_TypeThe\\n valid street abbreviation as it previously existed prior to the adoption of\\n the NG9-1-1 Data Model as assigned by the local addressing authority. The\\n United States Postal abbreviation for the street type.CategoryAL,\\n AVE, BLVD, CIR, CRES, CT, DR, GLN, GRTH, HWY, LN, LNDG, MALL, MEWS, PASS,\\n PATH, PIKE, PKWY, PL, PLZ, PLZA, PT, RD, RUN, SQ, ST, TER, TERR, WALK, WAY,\\n <Null>AVE,\\n ST, TER, GRTHYes
26LSt_PosDirThe\\n trailing street direction suffix as it previously existed prior to the\\n adoption of the NG9-1-1 Data Model as assigned by the local addressing\\n authority.CategoryN,\\n S, E, W, NE, NW, SE, SW, <Null>N,\\n E, \\u201cE\\u201d in \\u201cKEY HWY E\\u201dYes
27ESN_LThe\\n Emergency Service Number as defined by the associated address points on the\\n left-side directionality of the centerline segment. The Emergency Service\\n Number is actually a 5-digit string, of which this schema is only capturing\\n the last 3. The 3-digit code is prefixed with leading zeros. The ESN is a\\n legacy element used for 10-digt routing. The ESN is also contained within the\\n City MSAG database.Free\\n Text EntryLegacy\\n range of values: 2500 - 2694, 3809 (00500 - 00694 w/ prefixed zeros),\\n <Null>Legacy\\n value: 2502 (or \\\"00502\\\" w/ 2 prefixed zeros), <Null>Yes
28ESN_RThe\\n Emergency Service Number as defined by the associated address points on the\\n right-side directionality of the centerline segment. The Emergency Service\\n Number is actually a 5-digit string, of which this schema is only capturing\\n the last 3. The 3-digit code is prefixed with leading zeros. The ESN is a\\n legacy element used for 10-digt routing. The ESN is also contained within the\\n City MSAG database.Free\\n Text EntryLegacy\\n range of values: 2500 - 2694, 3809 (00500 - 00694 w/ prefixed zeros),\\n <Null>Legacy\\n value: 2502 (or \\\"00502\\\" w/ 2 prefixed zeros), <Null>Yes
29MSAGComm_LThis\\n is not the administrative or postal city designation. This field should\\n contain the MSAG Community Name, assigned by the 9-1-1 authority, which the\\n associated address points on the left-side directionality of the centerline\\n segment are contained within.Free\\n Text EntryBALTIMORE,\\n <Null>BALTIMOREYes
30MSAGComm_RThis\\n is not the administrative or postal city designation. This field should\\n contain the MSAG Community Name, assigned by the 9-1-1 authority, which the\\n associated address points on the right-side directionality of the centerline\\n segment are contained within.Free\\n Text EntryBALTIMORE,\\n <Null>BALTIMOREYes
31Country_LThe\\n name of the Country on the Left side of the road segment relative to the FROM\\n Node, represented by its two-letter ISO 3166-1 English
\\n country alpha-2 code elements in capital ASCII letters.		CategoryUnited\\n States (US)United\\n States, USYes
32Country_RThe\\n name of the Country on the Right side of the road segment relative to the\\n FROM Node, represented by its two-letter ISO 3166-1 English country alpha-2\\n code elements in capital ASCII letters.CategoryUnited\\n States (US)United\\n States, USYes
33State_LThe\\n 2-letter abbreviation for the federal state area that the associated address\\n points on the left-side directionality of the centerline segment are\\n contained within.CategoryMaryland\\n (MD)Maryland,\\n MDYes
34State_RThe\\n 2-letter abbreviation for the federal state area that the associated address\\n points on the right-side directionality of the centerline segment are\\n contained within.CategoryMaryland\\n (MD)Maryland,\\n MDYes
35County_LThe\\n administrative county area that the associated address points on the\\n left-side directionality of the centerline segment are contained within (all\\n records will have the value \\u201cBaltimore City\\u201d).CategoryBaltimore\\n CityBaltimore\\n CityYes
36County_RThe\\n administrative county area that the associated address points on the\\n right-side directionality of the centerline segment are contained within (all\\n records will have the value \\u201cBaltimore City\\u201d).CategoryBaltimore\\n CityBaltimore\\n CityYes
37AddCode_LThe\\n Additional Code on the Left side of the road segment relative to the FROM\\n Node.Free\\n Text Entry%\\n (any alphanumeric code), <Null><Null>Yes
38AddCode_RThe\\n Additional Code on the Right side of the road segment relative to the FROM\\n Node.Free\\n Text Entry%\\n (any alphanumeric code), <Null><Null>Yes
39IncMuni_LThe\\n officially recognized municipality or other general-purpose local\\n governmental unit as set forth by the United States Postal Service (USPS) the\\n addresses contained in the range for the left side of the centerline feature\\n are located relative to the FROM Node (all records will have the value\\n \\u201cBaltimore\\u201d). However, use \\\"Unincorporated\\\" if the address is not\\n within an incorporated local government.CategoryBaltimoreBaltimoreYes
40IncMuni_RThe\\n officially recognized municipality or other general-purpose local\\n governmental unit as set forth by the United States Postal Service (USPS) the\\n addresses contained in the range for the right side of the centerline feature\\n are located relative to the FROM Node (all records will have the value\\n \\u201cBaltimore\\u201d). However, use \\\"Unincorporated\\\" if the address is not\\n within an incorporated local government.CategoryBaltimoreBaltimoreYes
41UnincCom_LThe\\n Unincorporated Community, either within an incorporated municipality or in an\\n unincorporated portion of a county, or both, on the Left side of the road\\n segment relative to the FROM Node.Free\\n Text Entry%\\n (any name), <Null><Null>Yes
42UnincCom_RThe\\n Unincorporated Community, either within an incorporated municipality or in an\\n unincorporated portion of a county, or both, on the Right side of the road\\n segment relative to the FROM Node.Free\\n Text Entry%\\n (any name), <Null><Null>Yes
43NbrhdCom_LThe\\n name of an unincorporated neighborhood, subdivision or area, either within an\\n incorporated municipality or in an unincorporated portion of a county or\\n both, on the Left side of the road segment relative to the FROM Node.Free\\n Text Entry%\\n (any name), <Null>Canton,\\n Mount Vernon, Park HeightsYes
44NbrhdCom_RThe\\n name of an unincorporated neighborhood, subdivision or area, either within an\\n incorporated municipality or in an unincorporated portion of a county or\\n both, on the Right side of the road segment relative to the FROM Node.Free\\n Text Entry%\\n (any name), <Null>Canton,\\n Mount Vernon, Park HeightsYes
45PostCode_LThe\\n 5-digit code assigned to the USPS post office servicing the associated\\n address points on the left-side directionality of the centerline segment.Category21201\\n - 2128721202Yes
46PostCode_RThe\\n 5-digit code assigned to the USPS post office servicing the associated\\n address points on the right-side directionality of the centerline segment.Category21201\\n - 2128721202Yes
47PostComm_LA\\n city name for the ZIP Code of an address, as given in the USPS City State\\n Product on the Left side of the road segment relative to the FROM Node.Free\\n Text Entry%\\n (any name), <Null>Baltimore,\\n <Null>Yes
48PostComm_RA\\n city name for the ZIP Code of an address, as given in the USPS City State\\n Product on the Right side of the road segment relative to the FROM Node.Free\\n Text Entry%\\n (any name), <Null>Baltimore,\\n <Null>Yes
49RoadClassThe\\n general description of the type of road. The Road Classifications used in\\n this document are derived from the US Census MAF/TIGER Feature Classification\\n Codes (MTFCC), which is an update to the now deprecated Census Feature Class\\n Codes (CFCC).CategoryUS\\n Census/NENA defined list, <Null>Ramp,\\n Alley, Parking Lot, TunnelYes
50OneWayThe\\n direction of traffic movement along a road in relation to the FROM node and\\n TO node of the line segment representing the road in the GIS data. The\\n one-way field has three possible designations: B (Both), FT (From-To) and TF\\n (To-From).CategoryB\\n \\u2013 Travel in both directions allowed, FT \\u2013 One-way traveling from FROM node to\\n TO node, TF \\u2013 One way traveling from TO node to FROM node, <Null>B,\\n Both, FT, From-To, TF, To-FromYes
51SpeedLimitPosted\\n Speed Limit in MPH in US or Km/h in Canada.Number1\\n - 65, 0 or <Null> (no data)25,\\n 30, 55Yes
52Valid_LIndicates\\n if the address range on the left side of the road segment should be used for\\n civic location validation. A value of \\u201cY\\u201d MAY be entered if any Address\\n Number within the address range on the left side of the road segment should\\n be considered by the LVF to be valid. A value of \\u201cN\\u201d MAY be entered if the\\n Address Number should only be validated using the Site/Structure Address\\n Points layer. If not present, a value of \\u201cY\\u201d is assumed.CategoryY\\n (Yes), N (No), <Null>Y,\\n <Null>Yes
53Valid_RIndicates\\n if the address range on the right side of the road segment should be used for\\n civic location validation. A value of \\u201cY\\u201d MAY be entered if any Address\\n Number within the address range on the right side of the road segment should\\n be considered by the LVF to be valid. A value of \\u201cN\\u201d MAY be entered if the\\n Address Number should only be validated using the Site/Structure Address\\n Points layer. If not present, a value of \\u201cY\\u201d is assumed.CategoryY\\n (Yes), N (No), <Null>Y,\\n <Null>Yes
54psap_idleftThe\\n identification name of the PSAP on the left side of the road segment.Free\\n Text Entry%\\n (any alphanumeric ID), <Null><Null>Yes
55psap_idrightThe\\n identification name of the PSAP on the right side of the road segment.Free\\n Text Entry%\\n (any alphanumeric ID), <Null><Null>Yes
56external_nguidThe\\n current unique identifier for the centerline feature.Free\\n Text Entry1\\n - 99999999914246Yes
57globalidThe\\n global unique identifier for the centerline feature.Number{%%%%%%%%-%%%%-%%%%-%%%%-%%%%%%%%%%%%}\\n (any 36 character alphanumeric value){959A5832-A3B6-470D-A1ED-CC657E16902A}No
58data_sourceThe\\n name/label of the source of the centerline data.Free\\n Text Entry%\\n (any source name), <Null><Null>Yes

63fullrdnameThe\\n full name of the street, a concatenation of the street name pre-modifier (if\\n exists, St_PreMod field), the street name pre-directional (St_PreDir), the\\n street name pre-type (if exists, St_PreTyp), the street name pre-type\\n separator (if exists, St_PreSep), the street name (St_Name), street name post\\n type (St_PosTyp), the street name post directional (if exists, St_PosDir),\\n and street post modifier (if exists, St_PosMod) fields.Free\\n Text Entry%\\n (any street name in City)EAST\\n FAYETTE STREETYes
64feature_statusThe\\n status of the centerline feature, indicating whether the centerline is an\\n existing or \\\"Active\\\" roadway, \\\"Retired\\\" due to removal or\\n alteration, or \\\"Proposed\\\" future centerline pending a development.CategoryActive,\\n Proposed, Retired, <Null>ActiveYes
65F_ELEVConnectivity\\n policy value for modeling overpasses and underpasses. From topological\\n network elevation level, required for topological routing data to indicate\\n valid turns. The topological network elevation of the FROM node.Number0,\\n -1, 1, 2, 30,\\n -1Yes
66T_ELEVConnectivity\\n policy value for modeling overpasses and underpasses. From topological\\n network elevation level, required for topological routing data to indicate\\n valid turns. The topological network elevation of the TO node.Number0,\\n -1, 1, 2, 30,\\n -1Yes
67ShapeThe\\n geometry designation of the centerline feature, for GIS purposes.CategoryPolylinePolylineNo
68Shape.STLength()ESRI\\n geodatabase internal length field (in feet).Number0\\n - 999999999355.725225No


To leave feedback or ask a question about this dataset, please fill out the following form:
Street Centerline (NG911) feedback form.\", \"distribution\": [{\"@type\": \"dcat:Distribution\", \"accessURL\": \"https://data.baltimorecity.gov/api/download/v1/items/6454e7137e6943ca9c7984d0ab1eb4d4/csv?layers=0\", \"format\": \"CSV\", \"mediaType\": \"text/csv\", \"title\": \"CSV\"}, {\"@type\": \"dcat:Distribution\", \"accessURL\": \"https://data.baltimorecity.gov/api/download/v1/items/6454e7137e6943ca9c7984d0ab1eb4d4/geojson?layers=0\", \"format\": \"GeoJSON\", \"mediaType\": \"application/vnd.geo+json\", \"title\": \"GeoJSON\"}, {\"@type\": \"dcat:Distribution\", \"accessURL\": \"https://data.baltimorecity.gov/api/download/v1/items/6454e7137e6943ca9c7984d0ab1eb4d4/kml?layers=0\", \"format\": \"KML\", \"mediaType\": \"application/vnd.google-earth.kml+xml\", \"title\": \"KML\"}, {\"@type\": \"dcat:Distribution\", \"accessURL\": \"https://data.baltimorecity.gov/api/download/v1/items/6454e7137e6943ca9c7984d0ab1eb4d4/shapefile?layers=0\", \"format\": \"ZIP\", \"mediaType\": \"application/zip\", \"title\": \"Shapefile\"}, {\"@type\": \"dcat:Distribution\", \"accessURL\": \"https://data.baltimorecity.gov/datasets/baltimore::street-centerline-ng911-1\", \"format\": \"Web Page\", \"mediaType\": \"text/html\", \"title\": \"ArcGIS Hub Dataset\"}, {\"@type\": \"dcat:Distribution\", \"accessURL\": \"https://egis.baltimorecity.gov/egis/rest/services/Address_Points/Road_Centerline_NG911/FeatureServer/0\", \"format\": \"ArcGIS GeoServices REST API\", \"mediaType\": \"application/json\", \"title\": \"ArcGIS GeoService\"}], \"identifier\": \"https://www.arcgis.com/home/item.html?id=6454e7137e6943ca9c7984d0ab1eb4d4&sublayer=0\", \"issued\": \"2023-12-22T21:28:12.000Z\", \"keyword\": [\"City Government\", \"City Services\", \"Geo Spatial\", \"Geographic\", \"Public Safety\", \"Street\", \"Transportation\"], \"landingPage\": \"https://data.baltimorecity.gov/datasets/baltimore::street-centerline-ng911-1\", \"license\": \"\", \"modified\": \"2026-01-26T20:50:40.000Z\", \"publisher\": {\"name\": \"Baltimore City\"}, \"spatial\": \"-76.7122,39.1992,-76.5286,39.3728\", \"theme\": [\"geospatial\"], \"title\": \"Street Centerline (NG911)\"}","source_transform":null,"status":"error"}