[GeoJSON] Aligning implementations

[Tim Schaub]

Chris Holmes wrote:
> I definitely have a set of users who want to be able to serve up data 
> even if it doesn't have a geometry.

Ok, I still like

     geometry: {
         type: null,
         data: []
     }

better than

     geometry: null

or no sign of geometry at all.

> [multiple geometries]
> what do I do?  

Not that hard to say that the data structure should be (for each feature):

{
     id: string,
     geometry: array,
     properties: object
}

Though I wonder if people would complain about having to do geometry[0] 
(or equivalent) most of the time.

You got me curious about all these people who want to serve up 
geographic features with no geometry.  I wonder if you just mean null or 
broken geometry - or if there really is a world where people deal in 
geography without geometry.

Tim