geo alternatives and similar packages

Based on the "Geolocation" category.
Alternatively, view geo alternatives based on common mentions on social networks and blogs.

geocoder

7.6 6.9 geo VS geocoder

An Elixir Geocoder/Reverse Geocoder
geolix

7.4 0.0 geo VS geolix

IP information lookup provider

InfluxDB - Power Real-Time Data Analytics at Scale

Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

Promo www.influxdata.com

topo

7.1 3.4 geo VS topo

A Geometry library for Elixir that calculates spatial relationships between two geometries
geocalc

7.0 0.0 geo VS geocalc

Geographic calculations for Elixir
Google Maps

6.9 0.0 geo VS Google Maps

Google Maps API written in Elixir
geoip

6.8 5.7 geo VS geoip

Elixir library to find geo location information given an IP address, hostname or Plug.Conn
distance_api_matrix

4.2 0.0 geo VS distance_api_matrix

Google Distance Matrix API Library for Elixir
geohash

3.9 0.0 geo VS geohash

Geohash encode/decode for Elixir
geonames

3.6 0.0 geo VS geonames

An elixir wrapper around the GeoNames API
ip2location

2.9 0.0 geo VS ip2location

An Elixir library for the IP2Location database
geohax

2.6 0.0 geo VS geohax

Geohash encoding and decoding for Elixir.
wheretz

2.5 4.8 geo VS wheretz

Time zone by geo coordinates lookup
proj

2.5 0.0 geo VS proj

Elixir coordinate conversion library using OSGeo's PROJ.4
ipgeobase

1.5 0.0 geo VS ipgeobase

Find Russian and Ukraine city by IP address and find country for other country Elixir
srtm

1.4 6.9 geo VS srtm

Query locations for elevation data from the NASA Shuttle Radar Topography Mission
segseg

0.8 2.9 geo VS segseg

Segment-segment intersection classifier and calculator for Elixir
geohash_nif

0.4 0.0 geo VS geohash_nif

Elixir NIF for Geohash C Library

Do you think we are missing an alternative of geo or a related project?

Add another 'Geolocation' Package

Popular Comparisons

README

Geo

A collection of GIS functions. Handles conversions to and from well-known test (WKT), well-known binary (WKB), and GeoJSON for the following geometries:

Point
PointZ
PointM
PointZM
LineString
LineStringZ
Polygon
PolygonZ
MultiPoint
MultiPointZ
MuliLineString
MuliLineStringZ
MultiPolygon
MultiPolygonZ
GeometryCollection

Note: If you are looking for the Postgrex PostGIS extension, check out geo_postgis.

Note: If you are looking to do geospatial calculations in memory with Geo's structs, check out topo.

defp deps do
  [
    {:geo, "~> 3.4"}
  ]
end

Examples

Encode and decode WKT and EWKT:

iex(1)> {:ok, point} = Geo.WKT.decode("POINT(30 -90)")
%Geo.Point{ coordinates: {30, -90}, srid: nil}

iex(2)> Geo.WKT.encode!(point)
"POINT(30 -90)"

iex(3)> point = Geo.WKT.decode!("SRID=4326;POINT(30 -90)")
%Geo.Point{coordinates: {30, -90}, srid: 4326}

Encode and decode WKB and EWKB:

iex(1)> {:ok, point} = Geo.WKB.decode("0101000000000000000000F03F000000000000F03F")
%Geo.Point{ coordinates: {1.0, 1.0}, srid: nil }

iex(2)> Geo.WKB.encode!(point)
"00000000013FF00000000000003FF0000000000000"

iex(3)> point = Geo.WKB.decode!("0101000020E61000009EFB613A637B4240CF2C0950D3735EC0")
%Geo.Point{ coordinates: {36.9639657, -121.8097725}, srid: 4326 }

iex(4)> Geo.WKB.encode!(point)
"0020000001000010E640427B633A61FB9EC05E73D350092CCF"

Encode and decode GeoJSON:

Geo only encodes and decodes maps shaped as GeoJSON. JSON encoding and decoding must be done before and after.

# Examples using Jason as the JSON parser

iex(1)> Geo.JSON.encode(point)
{:ok, %{ "type" => "Point", "coordinates" => [100.0, 0.0] }}

iex(2)> point = Jason.decode!("{\"type\": \"Point\", \"coordinates\": [100.0, 0.0] }") |> Geo.JSON.decode
%Geo.Point{ coordinates: {100.0, 0.0}, srid: nil }

iex(3)> Geo.JSON.encode!(point) |> Jason.encode!
"{\"coordinates\":[100.0,0.0],\"type\":\"Point\"}"