A collection of GIS functions for Elixir, handling conversions between WKT, WKB, and GeoJSON formats.
Geo is an Elixir library that provides a collection of GIS functions for handling spatial data. It solves the problem of converting between common geospatial formats like Well-Known Text (WKT), Well-Known Binary (WKB), and GeoJSON, enabling developers to work with geometries such as points, lines, and polygons in Elixir applications.
Elixir developers building applications that require geospatial data processing, such as mapping tools, location-based services, or GIS integrations.
Developers choose Geo for its pure Elixir implementation, comprehensive support for GIS standards, and seamless integration with the Elixir ecosystem, offering a lightweight and efficient way to handle spatial data conversions.
A collection of GIS functions for Elixir
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports WKT, WKB (including EWKT/EWKB with SRID), and GeoJSON conversions, enabling seamless interoperability between common GIS standards as shown in the README examples.
Handles a wide range of geometries including Points, LineStrings, Polygons, and their multi-variants, covering essential GIS data structures for spatial processing.
Built entirely in Elixir with idiomatic APIs, offering lightweight integration and no external dependencies, making it ideal for Elixir-centric projects.
Provides reliable format conversions without bloat, as emphasized in its philosophy, allowing efficient data handling for specific tasks like web mapping integrations.
The README explicitly points to the 'topo' library for spatial operations, meaning Geo only handles format conversions and lacks built-in functions for calculations like distances or intersections.
Designed for converting data in memory, it doesn't offer native support for spatial database integrations or large-scale batch processing, requiring additional tools for such use cases.
As a pure Elixir library, it may not match the speed of C-based GIS libraries for intensive computations, which could be a bottleneck in high-throughput applications.