docker-postgis
geomesa
| docker-postgis | geomesa | |
|---|---|---|
| 5 | 3 | |
| 1,314 | 1,391 | |
| 1.6% | 0.9% | |
| 5.2 | 9.1 | |
| 16 days ago | 5 days ago | |
| Dockerfile | Scala | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-postgis
- [GeoDjango] - Can someone explain the difference between PostgreSQL and PostGIS?
- Help for database: connecting to port of postgis/postgis docker container - "no such host", even though telnet says otherwise?
-
Looking for PostGIS repo with Postgresql13 compatible version on SLES 15
Other than the repos, there's also a docker image: https://github.com/postgis/docker-postgis
- Arch Linux - Postgis Extension
- PostGIS – Spatial and Geographic Objects for PostgreSQL
geomesa
- GeoMesa
-
Cool Dockerization Ideas
you could help dockerizing geomesa with/on Cassandra https://www.geomesa.org/ Currently its only dockerized with accumulo
-
PostGIS – Spatial and Geographic Objects for PostgreSQL
If you really need to scale beyond what Postgres/PostGIS can handle, then you might want to check out GeoMesa[1], which is (very loosely) "PostGIS for HBase, Cassandra, or Google BigTable".
That being said, you may not need it, because Postgres/PostGIS can scale vertically to handle larger datasets than most people realize. I recommend loading your intended data (or your best simulation of it) into a Postgres instance running on one of the extremely large VMs available on your cloud provider, and running a load test with a distribution of the queries you'd expect. Assuming the deliberately over-provisioned instance is able to handle the queries, you can then run some experiments to "right-size" the instance to find the right balance of compute, memory, SSD, etc. If it can handle the queries but not at the QPS you need, then read replicas may also be a good solution.
[1] https://github.com/locationtech/geomesa
What are some alternatives?
plpgsql_check - plpgsql_check is a linter tool (does source code static analyze) for the PostgreSQL language plpgsql (the native language for PostgreSQL store procedures).
geometry-api-java - The Esri Geometry API for Java enables developers to write custom applications for analysis of spatial data. This API is used in the Esri GIS Tools for Hadoop and other 3rd-party data processing solutions.
docker-node - Official Docker Image for Node.js :whale: :turtle: :rocket:
open-data - Free football data from StatsBomb
stud - Cartography 2019
sample-data - Metrica Sports sample tracking and event data