[Geojson] FW: Features without geometry

[Sean Gillies]

Christopher Schmidt wrote:
> On Tue, Oct 02, 2007 at 12:51:51PM -0600, Sean Gillies wrote:
>> Martin Daly wrote:
>>>> Without a geometry, it's not GeoJSON. It's just another JSON
>>>> serialization. If you want to describe it in terms of GeoJSON, that's
>>>> fine, but for interchange of data, having a geometry means that you know
>>>> what can be done with it.
>>> Unless...
>>>
>>> We could add:
>>>
>>> "geometry": {
>>>    "type": "Empty"
>>> }
>>>
>>> OGC SF has provision for an empty geometry, e.g. the result of the boolean intersection between two non-intersecting LineString-s.
>>>
>>> M
>>>
>> "{}" is JSON's null, no?
> 
> 'null' (no quotes) is JSON's null. {} is probably JSON's empty. I'm not
> really against either type "Empty" or {} or null. type "Empty" seems to
> be more in line with WKT.
> 
> Regards,

Thank you for the correction. I much prefer

   { "geometry": null }

over

   { "geometry": {"type": "Empty", ...} }

Sean