Chapter 2: Modern Geospatial Technology

Modern geospatial technology is the stack that turns observations of the world into searchable, analyzable, visual, and operational software products. The field now spans satellites, mobile devices, drones, sensors, spatial databases, distributed analytics, web maps, cloud-native file formats, and AI-assisted interpretation.

Learning Goals

• Explain the modern geospatial stack from sensing to decision support.
• Compare desktop, web, cloud, mobile, and edge geospatial systems.
• Identify when tiles, APIs, spatial databases, object storage, and streams are appropriate.
• Understand how modern systems combine vector, raster, 3D, temporal, and model outputs.

Theory

Modern geospatial systems are built around a loop: observe, locate, structure, analyze, communicate, and act. Observations may come from satellites, phones, vehicles, surveys, or public records. The software challenge is to preserve spatial meaning while transforming raw data into products.

The central abstractions are layers, features, coverages, tiles, indexes, services, catalogs, and workflows. A layer organizes spatial information by theme. A feature combines geometry and attributes. A coverage stores values across space, often as a raster. Tiles partition space for scalable rendering. Indexes make spatial search fast. Services expose data and operations through APIs. Catalogs make data discoverable. Workflows make processing reproducible.

Research and Standards Foundations

Modern geospatial technology is increasingly shaped by open, web-native standards and cloud-native data layouts. OGC API standards provide modular building blocks for web APIs; OGC API - Features focuses on feature-level discovery and query operations. STAC gives Earth observation and other spatiotemporal assets a catalog pattern that software can crawl and search. Cloud-Optimized GeoTIFF makes large rasters practical over HTTP range requests, while GeoParquet brings geospatial columns into analytical lakehouse workflows.

The research lesson for engineers is that modern geospatial systems are not only map servers. They are distributed data systems with spatial semantics. A design should make explicit where geometry is stored, where CRS assumptions live, how metadata is preserved, how data is indexed, and what parts of a workflow are authoritative, derived, cached, or experimental.

Math

Modern geospatial math includes coordinate transformations, spatial indexing, tiling math, raster sampling, graph theory, time-series analysis, statistics, and optimization. Web maps rely on tile pyramids, where each zoom level subdivides the world into predictable x/y tile addresses. Routing relies on weighted graphs. Earth observation relies on grids, spectral bands, calibration, and resampling.

Equation companion: Math and Algorithms Reference

Tools of the Trade

• Spatial databases: PostGIS, DuckDB Spatial, BigQuery GIS, Snowflake, SpatiaLite.
• File formats: GeoJSON, GeoPackage, GeoParquet, Cloud-Optimized GeoTIFF, Zarr, NetCDF.
• Processing tools: GDAL, PROJ, GEOS, QGIS, GeoPandas, Shapely, rasterio, xarray, Dask.
• Web tools: MapLibre GL JS, Leaflet, OpenLayers, vector tiles, tile servers.
• Catalogs and APIs: STAC, OGC API - Features, OGC API - Tiles, WMS, WMTS, WFS.
• Cloud and operations: object storage, containers, queues, serverless functions, Kubernetes, observability tools.

Examples of Real-World Solutions

• A city publishes zoning, parcels, street centerlines, and flood maps as public web services.
• A logistics platform combines real-time vehicle positions, routing graphs, traffic data, and geofences.
• An agriculture platform combines satellite imagery, weather, soil, and field boundaries.
• A disaster response team uses satellite imagery, mobile reports, and road accessibility layers.
• A telecom team models coverage, assets, permits, and maintenance crews in one operational map.

Working Practice Examples

1. Draw a reference architecture for a web map that serves parcel data from PostGIS through vector tiles.
2. Convert a GeoJSON dataset to GeoParquet and explain the storage and analytics tradeoffs.
3. Design a streaming geofence alert service for moving vehicles. Include ingestion, indexing, state, and alert delivery.
4. Compare a desktop GIS workflow with a cloud-native pipeline for the same analysis.

Common Failure Modes

• Treating latitude and longitude as planar x/y coordinates.
• Publishing large raw features directly to browsers without tiling or simplification.
• Losing CRS metadata during conversion.
• Mixing authoritative, crowd-sourced, and derived datasets without lineage.
• Building beautiful maps that cannot be reproduced or audited.

Works Cited

"Cloud Optimized GeoTIFF." Cloud Optimized GeoTIFF, https://www.cogeo.org/. Accessed 9 May 2026.

"GeoParquet Specification." GeoParquet, https://geoparquet.org/. Accessed 9 May 2026.

"OGC API Standards." Open Geospatial Consortium, https://ogcapi.ogc.org/. Accessed 9 May 2026.

"OGC API - Features Standard." Open Geospatial Consortium, https://www.ogc.org/publications/standard/ogcapi-features/. Accessed 9 May 2026.

"SpatioTemporal Asset Catalog Specification." STAC, https://stacspec.org/. Accessed 9 May 2026.

Butler, Howard, et al. "The GeoJSON Format." RFC 7946, Internet Engineering Task Force, 2016, https://www.rfc-editor.org/rfc/rfc7946. Accessed 9 May 2026.

Ramsey, Paul. PostGIS in Action. 3rd ed., Manning, 2021.

---