Ir al contenido
getgeolens.com

Roadmap

Esta página aún no está disponible en tu idioma.

This page is a high-level view of direction — the themes we’re investing in and the ones we’re exploring. It is intentionally not a dated commitment; priorities shift with real-world usage and community input. For granular, issue-level tracking, follow GitHub.

GeoLens is a complete, self-hosted geospatial catalog. The core platform is stable and in active use:

  • Catalog & discovery — upload Shapefiles, GeoTIFFs, GeoPackages, CSVs, and more; semantic search (pgvector) and fuzzy search (pg_trgm) across metadata.
  • Standards & interop — OGC API Features and Records, plus STAC, consumable natively from QGIS, ArcGIS, and any OGC client.
  • Map Builder — compose vector, raster, and DEM layers; data-driven styling; 3D terrain; secure share and embed tokens.
  • Raster pipeline — Cloud-Optimized GeoTIFF tiling via Titiler, VRT mosaics, hillshade and terrain rendering.
  • Automation — the CLI & manifests and Python / TypeScript SDKs for scripted and CI-driven ingestion.
  • Operations — multi-user RBAC, OAuth/OIDC, API keys, one-command Docker Compose deploy, and a Helm chart for Kubernetes.
  • AI (optional) — embedding-backed semantic search and natural-language map generation, fully optional and provider-agnostic.

These are themes under active investigation. They are candidates, not promises — scope and ordering may change.

  • More 3D — first-class 3D Tiles and Gaussian splat layers on a unified rendering substrate, extending today’s DEM-based 3D terrain.
  • More vector formats — broader ingestion coverage, including the columnar GeoParquet / DuckDB ecosystem and additional GDAL-native formats (FlatGeobuf, File Geodatabase, KML/KMZ).
  • Server-side map thumbnails — generated previews for API- and multi-user-created maps without a browser in the loop.
  • Map Builder extensibility — a cleaner layer-adapter and widget model so the builder and the read-only viewer share one styling pipeline.

To set expectations clearly: GeoLens is built for single-organization, self-hosted deployments — deployed per organization, not sold per seat. Running GeoLens as a shared multi-tenant SaaS is not part of the open platform.

The roadmap is shaped by how people actually use GeoLens. If a theme above matters to you — or one you need is missing — open a discussion or issue. Real use cases move items up the list.