geo icon indicating copy to clipboard operation
geo copied to clipboard

A collection of GIS functions for Elixir

Results 16 geo issues
Sort by recently updated
recently updated
newest added

The following valid GeoJSON cannot be decoded: ![image](https://github.com/felt/geo/assets/3856560/f5db146d-1de5-4504-b347-2b0742fce91a) It fails with the following error: ** (Geo.JSON.Decoder.DecodeError) GeometryCollection is not a valid type code: geom = Jason.decode!(json) |> Geo.JSON.decode!() It appears...

Adds a conditions to the Geo.JSON.Decoder module and a corresponding unit test to support Feature objects with a geometry of type GeometryCollection.

Hi, Lovely lirary but we are having an issue with MULTILINESTRINGs where it includes "EMPTY" in it similar to: ``` SRID=4326;MULTILINESTRING((17.3184738535347 60.7864700694704,17.3180661577644 60.7874544933595),EMPTY,EMPTY) ``` It would then throw this error:...

The GeoJSON spec supports "unlocated" Feature objects where the "geometry" member is a JSON null value. The Geo library simply ignores Features of this kind, even if they have their...

Per [the discussion on #171](https://github.com/felt/geo/pull/171#issuecomment-1106870881), there's an existing bug in our handling of Z and M coordinates in the GeoJSON decoder. GeoJSON does not recognize any such geometry type as...

When creating a new integration a co-worker of mine sent coordinates as strings in the GeoJSON format. The spec is not really clear in defining the concrete JSON type required,...

Ref: https://github.com/bryanjos/geo/pull/166#issuecomment-974624214 There's a _ton_ of deprecation warnings when running `wkb_test.exs` which I can't get to at the moment. If someone would like to go ahead and fix those, that'd...

I am trying to do a `select st_envelope(...)::box2d` and I get the error: ``` * (Postgrex.QueryError) type `box2d` can not be handled by the types module Test.PostgresTypes ```

It seems that the SRID of a geometry parsed from geojson is not set to the default of 4326, [as defined by the spec](https://tools.ietf.org/html/rfc7946#section-4). I've run into this issue because...