future-mvt
titiler
| future-mvt | titiler | |
|---|---|---|
| 1 | 6 | |
| 9 | 692 | |
| - | 2.6% | |
| 10.0 | 8.9 | |
| over 1 year ago | 9 days ago | |
| Python | ||
| - | 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.
future-mvt
-
How The Post is replacing Mapbox with open source solutions
> PMTiles aside, this is still Mapbox’s world.
Isn't this is a bit like saying we're still in Google's world because most maps still use Web Mercator? :)
Good tech builds on what came before. Mapbox did a lot of ground-breaking work in building tooling around OSM, but so have many others. The fact that they named it Mapbox Vector Tiles is be genius in hindsight, because even though we may use tons of tooling they didn't create to build and render them, their name is still there.
> The next challenge is to evolve the tech stack to something beyond what Mapbox worked up five/ten years ago.
Agreed, and I think we've seen a lot of iterative work in the open since then. The next challenge is likely building a OSS stack to do proper 3D: open data (including OSM) to pixels, and that work is already beginning across a lot of organizations: https://github.com/nyurik/future-mvt/discussions, Overture Maps, MapLibre, etc.
titiler
-
How The Post is replacing Mapbox with open source solutions
There's a lot to like about GDAL+Rasterio, although I've found having all HTTP requests go through GDAL's C API does result in some limitations on concurrency and multithreading. GDAL's configuration being based entirely on env vars also has its downsides: https://github.com/developmentseed/titiler/issues/186
-
Extending PostGIS with TiMVT/TiFeatures and PgSTAC
TiMVT and TiFeatures, along with TiTiler for raster services, complete a trio of python-FastAPI services. The current roadmap includes merging TiFeatures & TiMVT, the vector-based services, into a single project to reduce code redundancy.
-
Serverless GIS
COGs are great, but from my experience micro services like titiler don't support complex styling logic. Is there a possibility to create a serverless WMS service with complex styling requirements?
-
geotiff mosaic viewer / qgis?
Consider something like titiler if you want to serve the pile of geotiffs out to the web.
-
Configuring >100GB of imagery as raster tiles, TMS / WTMS, AWS S3 storage?
We were able to host 10gb six band rasters as well as 2cm RGB split into 100m tiles on S3 using COGS, mosaic.json and the TiTiler project which is powered by AWS lambda functions
What are some alternatives?
valhalla - Open Source Routing Engine for OpenStreetMap
gdal2tiles-leaflet - Generate raster image tiles for use with leaflet.
go-pmtiles - Single-file executable tool for working with PMTiles archives
mangum - AWS Lambda support for ASGI applications
maputnik - An open source visual editor for the 'MapLibre Style Specification'
rasterio - Rasterio reads and writes geospatial raster datasets
PMTiles - Cloud-optimized + compressed single-file tile archives for vector and raster maps
fastapi-crudrouter - A dynamic FastAPI router that automatically creates CRUD routes for your models
planetiler - Flexible tool to build planet-scale vector tilesets from OpenStreetMap data fast
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
geoserver-rest - Python library for management for geospatial data in GeoServer.
fastapi-microservice-template - A template for a FastAPI based Serverless Framework microservice running on AWS Lambda