terracotta
tegola
| terracotta | tegola | |
|---|---|---|
| 4 | 2 | |
| 639 | 1,231 | |
| 1.4% | 1.3% | |
| 6.3 | 7.3 | |
| 8 days ago | 8 days ago | |
| Python | Go | |
| MIT License | MIT License |
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.
terracotta
-
Serverless GIS
One can also do raster calculus between two or more COGs with Terracotta: https://github.com/DHI-GRAS/terracotta/issues/221
-
Which tile server should I use? Terracotta or Geoserver or is there a better one?
I am currently working on setting up a web app using leaflet that can display .tif images along with some polygons and add some filters in the web app to better interact with the data. In the process of implementing this, I came to know that I need to use a tile server because I have large amounts of data and the tile server can help to serve the tiles on the web app. Based on my research, I guess these two are the main tools as of now: 1. Geoserver and 2. Terracotta. I am confused between the two. Can anyone suggest which one would be better for my use case and the pros and cons of both if possible? In case there's a different one that's better than the two mentioned above, it would be great if you can share the tool and your experience. Would be helpful.
-
Hacker News top posts: Jul 26, 2021
Terracotta: Serverless GeoTiff Tile Server\ (12 comments)
- Terracotta: Serverless GeoTiff Tile Server
tegola
-
Self Hosting a Google Maps Alternative with OpenStreetMap
Martin (https://github.com/maplibre/martin) or Tegola (https://github.com/go-spatial/tegola) as the vector tile server
-
Serverless GIS
In case of serverless vector services the cache size is a problem too; especially if you want to create tiles for hight zoom levels and serve them from a storage service like S3. A possible solution would be to use Tegola as an AWS Lambda function to dynamically serve vector tiles for high zoom levels. Lower zoom level tiles could be served from the cache directly, because they are small. But I'm not sure how to set this up and if it makes sense in a production environment.
What are some alternatives?
Zappa - Serverless Python
martin - Blazing fast and lightweight PostGIS, MBtiles and PMtiles tile server, tile generation, and mbtiles tooling.
mapproxy - MapProxy is a tile cache and WMS proxy
openstreetmap-tile-server - Docker file for a minimal effort OpenStreetMap tile server
threeXYZgraphing - 3d xyz graphing using threejs
titiler - Build your own Raster dynamic map tile services
javascript-algorithms - 📝 Algorithms and data structures implemented in JavaScript with explanations and links to further readings
orb - Types and utilities for working with 2d geometry in Golang
BorgBackup - Deduplicating archiver with compression and authenticated encryption.
go-geom - Package geom implements efficient geometry types for geospatial applications.
mbtileserver - Basic Go server for mbtiles
simplefeatures - Simple Features is a pure Go Implementation of the OpenGIS Simple Feature Access Specification