Layer: Police Posts (ID:0)

View In: Map Viewer

Name: Police Posts

Display Field: Comment

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: This Post boundary data shows the coverage areas that divide each District and Sector into smaller geographic areas to ensure proper BPD response for calls for service. Addresses in calls for service are geo-verified in the City’s public safety applications, and each address will have Post value assigned based on the geographic location within the Post boundaries. Post boundary names are numerical values consisting of a combination of three numbers: The District number (1-9), plus Sector number (1-3), and Post number. For example, the five Posts within the Central District (District 1) Sector 1 area are named as follows: 111, 112, 113, 114, 115. There is a total of 138 Posts across the City for this 2023 update to these boundaries.Data Dictionary:field_namedescriptiondata_typerange_of_possible_valuesexample_valuessearchable1OBJECTIDThe database’s internal unique identifier for the data table record.Number0 - 9999999994721No2LabelOfficial names for each Police Sector in each District; also used as labeling values for cartographic purposes.Free Text EntryCentral, Eastern, Northern, Southern, Northeastern, Northwestern, Southeastern, Southwestern, Western, Sector 1, Sector 2, Sector 3Central Sector 1, Southern Sector 3Yes3AgencyField used to hold the Baltimore Police ("BP") agency value, used in public safety applications.Free Text EntryBPBPYes4ServiceField used to hold the Police ("P") service value, used in public safety applications.Free Text EntryPPYes5DistrictOfficial names for each Police District.Free Text EntryCentral, Eastern, Northern, Southern, Northeastern, Northwestern, Southeastern, Southwestern, WesternCentral, Eastern, Northern, Southern, Northeastern, Northwestern, Southeastern, Southwestern, WesternYes6SectorOfficial names for each Police Sector in each District.Free Text EntrySector 1, Sector 2, Sector 3Sector 1, Sector 2, Sector 3Yes7AreaOfficial names for each Police Post in each District. Post boundary names are numerical values consisting of a combination of three numbers: The District number (1-9), plus Sector number (1-3), and Post number. For example, the five Posts within the Central District (District 1) Sector 1area are named as follows: 111, 112, 113, 114, 115.Free Text Entry111 - 935111, 215, 315, 425, 521, 636, 733, 825, 916Yes8GroupField used to hold the Police District group abbreviation values ("CD, NW, SD"), used in public safety applications.Free Text EntryCD, ED, ND, SD, NE, NW, SE, SW, WDCD, ED, ND, SD, NE, NW, SE, SW, WDYes9ShapeThe geometry designation of the centerline feature, for GIS purposes.CategoryPolylinePolylineNo10SHAPE_LengthESRI geodatabase internal length field (in feet).Number0 - 99999999910021.59174No11SHAPE_AreaESRI geodatabase internal area field (in square feet).Number0 - 9999999994521077.288No

Copyright Text: BPD Information Technology Division, Data Driven Services Division, BPD GIS. This data is current and has been put into effect in BPD’s and other City public safety operations on July 9, 2023. The data will be updated as needed. All reference to BPD responding Post within Districts and Sectors for 911 call for service data beginning at 7:00 a.m. on 7/9/23 should reference this Post boundary data.

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

{"renderer":{"type":"simple","symbol":{"type":"esriSFS","style":"esriSFSSolid","color":[204,233,252,255],"outline":{"type":"esriSLS","style":"esriSLSSolid","color":[110,110,110,255],"width":0.7}}},"scaleSymbols":true,"transparency":0,"labelingInfo":null}
HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:

OBJECTID (type: esriFieldTypeOID, alias: OBJECTID, SQL Type: sqlTypeOther, length: 0, nullable: false, editable: false)
Comment (type: esriFieldTypeString, alias: Comment, SQL Type: sqlTypeOther, length: 200, nullable: true, editable: true)
Label (type: esriFieldTypeString, alias: Label, SQL Type: sqlTypeOther, length: 80, nullable: true, editable: true)
Agency (type: esriFieldTypeString, alias: Agency, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
Service (type: esriFieldTypeString, alias: Service, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
District (type: esriFieldTypeString, alias: District, SQL Type: sqlTypeOther, length: 20, nullable: true, editable: true)
Sector (type: esriFieldTypeString, alias: Sector, SQL Type: sqlTypeOther, length: 10, nullable: true, editable: true)
Post (type: esriFieldTypeString, alias: Area, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: true)
Group_ (type: esriFieldTypeString, alias: Group, SQL Type: sqlTypeOther, length: 4, nullable: true, editable: true)
Shape__Area (type: esriFieldTypeDouble, alias: Shape__Area, SQL Type: sqlTypeDouble, nullable: true, editable: false)
Shape__Length (type: esriFieldTypeDouble, alias: Shape__Length, SQL Type: sqlTypeDouble, nullable: true, editable: false)

Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 7/22/2025 3:56:36 PM

Schema Last Edit Date: 7/22/2025 3:56:34 PM

Data Last Edit Date: 1/22/2025 11:06:05 PM

Supported Operations: Query Query Pivot Query Top Features Query Analytic Query Bins Generate Renderer Validate SQL Get Estimates ConvertFormat