3 ms·
Better idea - save the data to a server, make an API (free), and let engineershelp visualize where the violence is occuring / predict where it will occur based
by misiti3780 13y ago
Better idea - save the data to a server, make an API (free), and let engineershelp visualize where the violence is occuring / predict where it will occur based on date/time
- sliverstorm 13y agoSo, basically, you want someone else to do all the legwork and give you access to their data for free. Cool, we'll get right on that.
- mparlane 13y agoThanks.
- misiti3780 13y agoby leg work, you mean saving this 'shared information' to a database ? - ya get on it
- sliverstorm 13y agoIt's so easy to dismiss considerable amounts of work as trivial when you don't have to do it, isn't it? Yes doctor, you just hit the "save to SQL database" right here on your plastic clipboard...
- misiti3780 13y agoalso - "their data" is public information anyways (or at least should be) - is basic crime statistics
- sliverstorm 13y agoI'm not claiming it's secret information that they own. But this is like the FOIA. Some smartass comes along, hears about FOIA, and declares "Well they should just digitize the entire archive, make it available in a queriable SQL database, and be done with it". The problem is, while the public has a right to the information, the representation, the storage of that data has issues. Digitizing millions of pages of records is not an afternoon's work (triply so if you want OCR). The reason we don't have such a database is not because John Spook is too lazy to spend thirty minutes doing it. When you put hundreds of thousands of man-hours into digitizing an archive, there's essentially a cost/value-add. If there wasn't a value-add, why would you want this hypothetical database anyway? The crime information is public, why don't you just go compile it yourself!