UPDATE to the SpotCrime Open Crime Standard (SOCS)!

After speaking with CIO’s, IT departments, open data advocates and the like, we’re making an update to SOCS! We’ve been pretty lucky to have so many people across the country give us their feedback.

The first update we’re making an obvious one we should’ve included in the roll out. We will now be breaking out lat/long coordinates into two separate blocks.
Data Type
RequiredPermitted valuesExampleDetails
LatitudeYesGeographic coordinate system39.399262Geo-coding accuracy. Not displayed by SpotCrime.
LongitudeYesGeographic coordinate system-76.602990Geo-coding accuracy. Not displayed by SpotCrime.

Another change we’ve made to SOCS is more of a clarification than a change. In the original layout, we list the file types accepted by SOCS. We also listed examples of file types not accepted under the Open Data definition and mentioned they are still accepted under the SpotCrime Standard. 

SpotCrime will still map these formats, however, they are not considered an acceptable format under SOCS. 

Revised table:
Machine readable formats that fall under the Open Data definition and are accepted under SOCS:
Formats that do not fall under the Open Data definition and are not accepted under SOCS:
XML
PDF
RSS feed
HTML
CSV
DOC(X)
RDF
Anything Scanned
JSON
Anything Faxed
TXT
Anything typed in an email
XLS(X)

KML


If you are police agency sending us data in one of these formats, thanks for being transparent, however, we recommend you move to the open data formats listed in the left side of the table above.

Finally, we’ve added the Albuquerque open data feed to the list of examples. They recently rolled out an open data feed available in multiple machine readable formats for consumption. Great job ABQ!


Comments

Popular posts from this blog

SpotCrime Weekly Reads: AI, police conduct, transparency

SpotCrime Weekly Reads: Transparency, gun violence, crime data

SpotCrime Weekly Reads: Violent crime, AI tech, transparency