Database printout requirements
The database printout file, exported from your CAD system or assembled from data exported from your CAD and RMS systems, must be a CSV file that complies with the specifications in this section.
Some fields are required; some are optional.
Some fields can occur more than once.
Field headings can use underscore characters rather than spaces.
The following table describes the supported fields in a database-printout .csv file which contains only CAD system data:
| Field | Required or Optional | Number of Instances Allowed | Description |
|---|---|---|---|
| Event ID | Required | 1 | The unique ID of the event. The data in the column may reflect INCIDENT#, CADIncidentNumber, or a similar field. |
| Officer Badge ID | Required | 1 | The unique badge ID assigned to the officer. This ID must exactly match the officer badge ID assigned to the Axon camera in Axon Evidence. If badge IDs differ between systems, this must be resolved during the implementation process. |
| Officer Dispatched DateTime | Required | 1 | The start time of the officer event. Used to define the beginning of the time range that the start time of the officer's video evidence file must be within. Dispatched times must be in ISO 8610-compliant format, either using UTC or time zone offset. UTC format example - 2015-11-13T21:35:42Z. Time zone offset format example - 2015-11-13T21:35:42-08:00. The difference between the dispatched and cleared times must to be greater than 0 (zero) but less than 8 hours. |
| Officer Cleared DateTime | Required | 1 | The end time of the officer event. Used to define the end of the time range that the start time of the officer's video evidence file must be within. Cleared times must be in ISO 8610-compliant format, either using UTC or time zone offset. UTC format example - 2015-11-13T21:35:42Z. Time zone offset format example - 2015-11-13T21:35:42-08:00. |
| Call type | Required if available | 1 | The name/ type of event the officer is responding to, this can be in the form of a code or written out. Example — domestic violence or 421 |
| Clearance Code | Required if available | 1 | Disposition of event the type of event officer is responding to after end of call. This describes the action taken as a result of the call for service. This can be in the form of a code or written out. Examples — Gone By Arrival or 1054 |
| Report Number | Optional | 1 | The RMS ID of the report about the CAD event. If no RMS ID is available, this field can be empty. When present this ID becomes the ID for all related videos to an event. If this field is blank, then the Event ID is the ID for videos. |
| Category | Optional | From zero (0) to many | The CAD event type code of the event. Axon Evidence uses the event type provided in this column to determine which retention category is assigned to matching video evidence files. For more information, see Event-Type-to-Category Mapping. Each category must appear as its own column on the .csv file. This is often the same as "Call type" or "Clearance Code", in which case, the data would be written to both columns. There may not be a 1:1 relationship between this section and category, in which case multiple types or codes can map to a single category, this will be configured during implementation. |
| Tag | Optional | From zero (0) to many | Text labels that apply to the event. If you include more than one Tag field, the heading should be "Tag" for each of them. |
| Title | Optional | 0 to 1 | A title for the event. |
| Street | Optional | 0 to 1 | Street address or intersection of the event. This information should be recognizable by Bing Maps; otherwise, location-based Axon Evidence features will be unavailable for video-evidence files matched to the event. |
| City | Optional | 0 to 1 | The full name of the city in which the event occurred. |
| State | Optional | 0 to 1 | State in which the event occurred. |
| ZIP Code | Optional | 0 to 1 | The postal code within which the event occurred. |
The following table shows an example CSV file of metadata exported from a CAD system.
| Event ID | Officer Badge ID | Officer Dispatched DateTime | Officer Cleared DateTime | Call Type | Clearance Code | Report Number | Category | Tag | Title | Street | City | State | ZIP Code |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2016052500132 | 1345 | 2015-10-06T14:30:32Z | 2015-10-06T15:40:02Z | Domestic Violence | 106 | DR1605250334 | Homicide | TagData | Title text | 123 E Minor St | Seattle | WA | 98050 |
| 2016052500137 | 8721 | 2015-10-06T03:30:32Z | 2015-10-06T04:40:02Z | 1054 | 281 | DR1605250317 | Traffic | Tagdata | Title text | ||||
| 2016052500143 | 2962 | 2015-10-06T03:30:32-08:00 | 2015-10-06T04:40:02-08:00 | Cancelled | Gone By Arrival | DR1605250298 | Domestic | Tagdata | Title text |
