Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Format Data into JSON #2

Open
mjcarroll opened this issue Mar 28, 2015 · 4 comments
Open

Format Data into JSON #2

mjcarroll opened this issue Mar 28, 2015 · 4 comments

Comments

@mjcarroll
Copy link
Contributor

This is the data format for ChattCrimes. There was some discussion to see if we need an actual DB backend, or if the flatfile is more than enough.

https://data.chattlibrary.org/resource/crime-data.json

I think for a hack, the flat file is fine, but I think that the DB part would be kind of nice for the longer-ish term.

@git-madhav
Copy link
Contributor

if we want to use heat maps available already, it may be easy with JSON or some other DB. Will look into it more.

@mjcarroll
Copy link
Contributor Author

I think for now we could use Spatialite, which is pretty easy and standalone (Based on SQLite).

We could definite move to something like PostGIS (PostGRES + GIS).

GIS extensions allow easier querying by geographic information.

@git-madhav
Copy link
Contributor

I got the heatmap working using simple HTML5, Java Script, JQuery and Google heat map API. This is done all at the client end. This is not the most sophisticated way of a doing, but you can see heat map. I have uploaded the html file. if you want to see the map, just download html file and latest .csv file. after loading html in browser, you need to load csv file using browse button, then press update Map Data button. You should see the heatmap, you may have to press "changeMaxIntensity" button to see redspots.

@git-madhav
Copy link
Contributor

Next I will work on filtering the data based on "Year", "Shift", and "Incident Type" At a later time, we can think of using server pages. Currently this is all done at client machine side, no web server is required for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants