Ben Balter
@benbalter
@benbalter
The GeoJSON spec would be so much easier if everything were just a FeatureCollection. Why have 4 ways to represent the same geometry?
❗ Heads up! This Tweet is archived and here for historical purposes. It may no longer be accurate or reflect my views. Proceed at your own risk.
If you enjoyed this tweet, you might also enjoy:
- Why everything should have a URL http://bit.ly/1MoMnQI
- Idea: GeoJSON-lite. A subset of the GeoJSON spec where all geometry is s...
- Why would anyone use blogger? (no really, why?)
- OH: "There are two ways to parse HTML -- as XML, or the wrong way. We're...
- Just had my first real-life #pediconference. Was everything I dreamed it...
- Why do I have to bring my lease to the electric company with a photo ID?...
- How to convert Shapefiles to GeoJSON for use on GitHub (and why you real...
- #goosebumps RT @CaliforniaKara @GitHub and UX and UI, oh my! Why I chose...
- If you were writing the White House's government-wide open source policy...
- Why the way the new healthcare .gov was built matters via @digiphile. ht...
- Starting to think that law school would be much more enjoyable if we had...