Optimize GeoJSON

[abettermap]

• Remove unneeded fields (e.g. SHAPE_LEN, etc.)
• Simplify (reduce number of vertices)
• Reduce precision (e.g. 40.374187379751248 to 40.3742)
• Minify

Closes #27

[coveralls]

Coverage remained the same at 100.0% when pulling 35addfe on abettermap:27.slim-geojson into b567415 on CodeForFoco:master.

[abettermap]

@deidyomega

The geojson is about 10% of its original size and should suffice, but mainly I just want to make sure:

• The GeoJSON still works, looks good enough overall, and is not missing any required fields.
• From a general perspective, the shell script looks ok. Any advice/tips are appreciated as I'm still learning the basics!

You can't really test the actual script unless you install ogr2ogr (could use Docker too I guess), but I don't imagine it is something we will use very often anyway.

[abettermap]

@deidyomega

Even though we probably won't use it again and it's pretty basic, any advice on that shell script? For something that simple do you typically make functions and allow more arguments to be passed, or just make it quick and dirty and global like I did? I threw in some parameters and set some defaults for input and output files, but that's about it.

[deidyomega]

Au contraire, the geojson updates from the state from time to time, so I imagine it will be run again.

As for the code itself, that's pretty standard shell scripting. It was and is designed to be a script. Not a full object oriented language.

I may have had a comment about where to install the program you were using, but other than that, it looks good