Name: Police_Calls_for_Service
Display Field:
Type: Table
Is View: true
Is Updatable View: true
Source Schema Changes Allowed: true
Sources
Description: <div><span style>This dataset has been published by the Virginia Beach Police Department, data.virginiabeach.gov The mission of data.virginiabeach.gov is to provide timely and accurate City information to increase government transparency and access to useful and well organized data by the general public, non-governmental organizations, and City of Virginia Beach employees. Any questions about this dataset or request for information, please contact the data owner - Virginia Beach Police Department at - </span>vbpdpublicaffairs@vbgov.com or 757-385-4097 - <a href="https://www.vbgov.com/government/departments/police/chiefs-office/Pages/publicaffairs.aspx" target="_blank">VBPD Public Affairs Office</a><div>The following five priority codes are assigned to each call for service depending on the severity of the incident. <br /></div></div><div><br /></div><div>Priority 1 - Life threatening situations in progress or which have just occurred and where an immediate response is necessary to preserve property and crime scenes or to prevent the situation from escalating. Examples include accidents with injuries, burglaries in progress, and violent domestics.</div><div>Priority 2 - Life threatening situations in progress or which have just occurred and where an immediate response is necessary to preserve property and crime scenes or to prevent the situation from escalating. Examples include accidents with injuries, burglaries in progress, and violent domestics.</div><div>Priority 3 - Misdemeanors in progress or that have just occurred. Examples include accidents with no injuries, burglar alarms, suspicious persons, domestics with no weapons, prowler.</div><div>Priority 4 - Cold crimes that require reporting and other situations that would not be impacted by delayed response. Examples include reports taken by telephone in the Telephone Reporting Unit, abandoned autos, nuisance calls, pick-up prisoner, found property.</div><div>Priority 5 - Situations where no reportable offense has occurred. </div><div><br /></div><div><br /></div><div><p style="margin-bottom:0in;"><b><span style="font-size:14pt;">Access constraints</span></b></p><p style="margin-bottom:0in;">The data is publicly available and accessible.</p><p style="margin-bottom:0in;"><br /></p><p style="margin-bottom:0in;"><b><span style="font-size:14pt;">Use constraints</span></b><br /></p><p style="margin-bottom:0in;">By using data made available through this site the user agrees to all the conditions stated in the following paragraphs, as well as the terms and conditions described in the “Terms of Use” on the “About this Site” page.</p><p style="margin-bottom:0in;"><br /></p><p style="margin-bottom:0in;">The City of Virginia Beach makes no claims as to the completeness, accuracy, timeliness, or content of any data contained in this application; makes any representation of any kind, including, but not limited to, warranty of the accuracy or fitness for a particular use; nor are any such warranties to be implied or inferred with respect to the information or data furnished herein. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the site is being used at one’s own risk. Applications using data supplied by this site must include the following disclaimers on their sites:</p><p style="margin-bottom:0in;"><br /></p><p style="margin-bottom:0in;">“The data made available here has been modified for use from its original source, which is the City of Virginia Beach. Neither the City of Virginia Beach nor the Office of the Chief Information Officer (CIO) makes any claims as to the completeness, timeliness, accuracy or content of any data contained in this application; makes any representation of any kind, including, but not limited to, warranty of the accuracy or fitness for a particular use; nor are any such warranties to be implied or inferred with respect to the information or data furnished herein. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the web feed is being used at one’s own risk.” As found in the “Terms of Use” on the “About this Site” page.</p></div><div><br /></div>
Copyright Text:
Max Record Count: 2000
Supported query Formats: JSON, geoJSON, PBF
Use Standardized Queries: True
HasZ: false
HasM: false
Has Attachments: false
Has Geometry Properties: false
HTML Popup Type: esriServerHTMLPopupTypeNone
Object ID Field: OBJECTID
Unique ID Field:
IsSystemMaintained : True
Global ID Field:
Type ID Field:
Fields:
- IncidentNumber (type: esriFieldTypeString, alias: IncidentNumber, SQL Type: sqlTypeOther, length: 17, nullable: true, editable: true)
- ReportNumber (type: esriFieldTypeString, alias: ReportNumber, SQL Type: sqlTypeOther, length: 13, nullable: true, editable: true)
- Call_Type (type: esriFieldTypeString, alias: Call_Type, SQL Type: sqlTypeOther, length: 40, nullable: true, editable: true)
- Block_Address (type: esriFieldTypeString, alias: Block_Address, SQL Type: sqlTypeOther, length: 4000, nullable: true, editable: true)
- CityName (type: esriFieldTypeString, alias: CityName, SQL Type: sqlTypeOther, length: 150, nullable: true, editable: true)
- State (type: esriFieldTypeString, alias: State, SQL Type: sqlTypeOther, length: 2, nullable: true, editable: true)
- Zone (type: esriFieldTypeString, alias: Zone, SQL Type: sqlTypeOther, length: 3, nullable: true, editable: true)
- Case_Disposition (type: esriFieldTypeString, alias: Case_Disposition, SQL Type: sqlTypeOther, length: 512, nullable: true, editable: true)
- Priority (type: esriFieldTypeString, alias: Priority, SQL Type: sqlTypeOther, length: 1, nullable: true, editable: true)
- Subdivision (type: esriFieldTypeString, alias: Subdivision, SQL Type: sqlTypeOther, length: 150, nullable: true, editable: true)
- Call_Date_Time (type: esriFieldTypeDate, alias: Call_Date_Time, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: true)
- Entry_Date_Time (type: esriFieldTypeDate, alias: Entry_Date_Time, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: true)
- Dispatch_Date_Time (type: esriFieldTypeDate, alias: Dispatch_Date_Time, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: true)
- EnRoute_Date_Time (type: esriFieldTypeDate, alias: EnRoute_Date_Time, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: true)
- OnScene_Date_Time (type: esriFieldTypeDate, alias: OnScene_Date_Time, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: true)
- Close_Date_Time (type: esriFieldTypeDate, alias: Close_Date_Time, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: true)
- OBJECTID (type: esriFieldTypeOID, alias: OBJECTID, SQL Type: sqlTypeOther, length: 0, nullable: false, editable: false)
- Officer_Id (type: esriFieldTypeString, alias: Officer_ID, SQL Type: sqlTypeOther, length: 4, nullable: true, editable: true)
Is Data Versioned: false
Has Contingent Values: false
Supports Rollback On Failure Parameter: true
Last Edit Date: 11/29/2025 9:30:11 AM
Schema Last Edit Date: 8/6/2025 8:12:04 PM
Data Last Edit Date: 11/29/2025 9:30:11 AM
Supported Operations:
Query
Query Pivot
Query Top Features
Query Analytic
Query Bins
Generate Renderer
Validate SQL
Get Estimates
ConvertFormat