Commits on Nov 1, 2022

1. Support null feature geometries …

   [Per RFC 7946](https://www.rfc-editor.org/rfc/rfc7946#section-3.2), a Feature object's `"geometry"` member can be either a Geometry object or a JSON null value.
   
   Prior to this patch, you would get a `BadMapError` if you attempted to decode GeoJSON that included a feature with null geometry; with this change, that feature will be filtered out of a FeatureCollection, or in the case of a standalone Feature, it will be converted to `nil`.
   
   I'm not entirely convinced this is the right implementation—the GeoJSON RFC seems to indicate there may be some value in having an "unlocated" feature (I guess for its `properties`?). However, it seemed like a much bigger, scarier, and frankly less consistent change to introduce a non-located type into `Geo.GeometryCollection` or `Geo.geometry()`. (After all, these are explicitly about _geometries_, so the unlocated feature doesn't seem to fit into the abstraction at all.)

   

   s3cur3 committed Nov 1, 2022
   Configuration menu

   • View commit details
   • Copy full SHA for e36d74f
   • Browse repository at this point

   Copy the full SHA

   e36d74f View commit details

   Browse the repository at this point in the history