Pull incident reports from SF Open Data and display results using Mapbox.

Universities and colleges are required by a federal law, the Jeanne Clery Act, to report crime statistics on specific crimes that happened within ~500 feet of anywhere their student population went. The SFPD fields about 2,500 requests per year from universities and colleges for information about those crimes, which take between 20-40 minutes to fulfill... per request, which is about ~156.25 8-hour days. They need to do a radial search around a specific address (or list of addresses), as provided by the universities or colleges.

This application does exactly that. It performs a radial search of variable size around an address provided by the user, and then offers the datapoints (crimes, in this case) for download.

At the moment, the application is 100% browser-based. No servers at all. Just API calls, HTML, CSS, and JavaScript. It's likely that the immediately pending version can stay this way... not necessarily as likely for the "Wouldn't it be cool if..." version.

Satisfy SFPD crime reporting needs, as well as other interested parties, including watch dog groups, organizations with reporting requirements (like universities), and civic hackers, while ensuring an easily maintainable product.

(Note: that this comes after Vision #1 is complete, so the rest of the README doesn't address this vision.) Create a single place for all universities and colleges in the United States to collect the data for their Clery Act reporting requirements, incorporating data from as many police departments in the country as possible.

• Front-end developer! Yup. Self-explanatory if you read the above paragraph. Bonus points if you love APIs and are up for the challenge of keeping the whole project browser-based... even the coming versions.
• Copywriter! The site needs more and easily understandable information on it. Zero coding required.
• User Researcher! Can you reach out to a university's crime data reporting team, understand their needs (without biasing them), and take notes as they test this application? Zero coding required.
• Future project lead! If you're interested managing in this project, come check it out asap and get up to speed... then build it out so any police department in the country can use it. Time savings in the multiple thousands of workdays across the entire U.S.

Note: this repository takes advantage of ZenHub. If you haven't added it to your Github yet, it's recommended to better understand how issues are prioritized.

• Attend a Code for San Francisco orientation
• Get on Slack
  • Add prj-sf-crime-data as a channel
• Get on GitHub
  • Find sfbrigade/sf-crime-data
• Add ZenHub plug-in to GitHub
  • Review how ZenHub works
• Review issues on ZenHub boards (within GitHub: sfbrigade/sf-crime-data)
• Clone the site to your dev machine and get it running locally
  • See readme.md "Running Codebase Locally"
  • See readme.md "Working in Github"
  • Alternately use your GitHub account's hosting option for gh-pages
• Visit SF OpenData
  • Review SFPD available data
  • Review how to call the API (Export)
• Visit Mapbox.com
  • Review their map offerings
  • Review how to call the API
• Read the Wiki on GitHub sfbrigade/sf-crime-data
• If you want to contribute to the code base...
  • Set up a "public hosting" location like GitHub pages or Firebase
    • This will be used to share your changes for team testing and code reviews
  • Comment on the issue you would like to work on
  • Continue to collaborate and code using Slack and GitHub
• If "life happens" and you won't have time to finish an issue due to new demands, do let us know, so we can re-assign.

If you want to contribute to this project please follow these instructions:

• fork the repository in to your account
• open terminal, cd to a folder you want your files saved in.
• clone from your repository: git clone https://github.com/youraccount/sf-crime-data
• setup upstream to main repository: git remote add upstream https://github.com/sfbrigade/sf-crime-data
• make sure your upstream and origin are correct: git remote -v
• make edits in gh-pages branch: git checkout gh-pages
• make changes from your local folder. Everytime you work on it make sure to pull any updates: git pull upstream gh-pages
• When you are ready to submit changes:

  git add <changed file names>
  git commit -m "type your message here"
  git push origin gh-pages

• go to your git hub account in your browser and make a pull request from there. The dropdown should look like Main Repo/gh-pages to Forked Repo/gh-pages.

If you want to download the github repository and run the code locally on your Apple machine,

• open terminal
• go to the folder directory
• run 'python -m SimpleHTTPServer'
• go to a browser and type in localhost:"PORT_NUMBER"

1. You have worked an issue and resolved it. Great!
2. It works on your local web server. Great!
3. Do a regression test to make sure nothing else broke.
   • Use the test script at: https://drive.google.com/open?id=1AAy7PV08czDWLs1aG9ch5WvLqLZCWKWN8deguUiuv1Q
4. Publish your changes to your personal public hosting location like GitHub pages or Firebase.
5. Post a note on Slack channel #prj-sf-crime-data with your personal public hosting URL and ask the team to test.
   • We need at least one other teammate to approve moving forward.
6. Submit a pull request.
   • Do not "pretty up" the code. That makes it super difficult to do a code review.
   • Change only the lines that need to change to resolve the Issue.
7. A team member will review the pull request, do a code review and perform the merge (or advise with any changes needed).

The following are among the libraries and extensions used:

Bootstrap – "a sleek, intuitive, and powerful mobile first front-end framework for faster and easier web development"

• Bootstrap 3 Typeahead
• Date Range Picker

jQuery - "The Write Less, Do More, JavaScript Library"

• URI.js – "URI.js offers simple, yet powerful ways of working with query string, has a number of URI-normalization functions and converts relative/absolute paths"
• DataTables
  • Buttons
  • colVis
  • FixedHeader

Leaflet – "An open-source JavaScript library for mobile-friendly interactive maps"

• Mapbox - "The location platform for developers and designers APIs for maps, geocoding, driving directions, and more"
• Leaflet.markercluster – "Provides Beautiful Animated Marker Clustering functionality"
• Leaflet.draw - "Adds support for drawing and editing vectors and markers"
• Leaflet.Sleep – "Prevent unwanted scroll capturing; let your map sleep"

Moment.js – "Parse, validate, manipulate, and display dates and times in JavaScript"

noUiSlider – "JavaScript Range Slider"

After speaking with the Crime Data Analysis Unit at the SFPD on 5/6/16 for initial user research, the current prototype satisfies their minimum needs. They plan to direct future inquiring universities and colleges directly to [http://sfcrimedata.org]. Great!

However, the prototype has a few things that could be greatly improved (also listed as issues), which were discovered during initial user testing. Specifically:

• Columns displayed on the desktop version of the data table are insufficient (posted in an issue)
• Would be great for a "Clery Act"-specific report
• Display the source of the data and when it was last updated

When prompted to think about other uses for this web app, the SFPD crime data analysts asked for the following:

• Ability to overlay data layers, such as PD district laters, sector layers (police beats), political jurisdictions, plots (9sq block areas), and national/state/local parks.
• Why? Police captains want to see what is going on in their jurisdiction, cops want to see what happened on their beats while they were off duty, the Mayor's Office wants to know what's going on in a particular area, and SFPD in general wants to know what's going on on their turf (hence the park layer). The Crime Data Analysis Team runs regular (weekly) reports for nearly all of these folks and the team could save even MORE time by sharing this web app with the entire SFPD, who could run their own reports by themselves.
• Ability to see crime data over time (add beginning and ending time period filter).
• Why? Every single captain of every single district (and anyone else who has to report to constituents) wants to know if they're up or down on crime over a specific period of time.