43 products Sparkpulse tracks are shipping around geospatial. The highest-velocity geospatial products right now are GeoServer, Mapnik and MapServer (ranked by Sparkpulse's velocity score). The theme runs across 3 sectors, so the momentum you see here is drawn from products competing in different corners of the market. Their velocity scores span 0.0 to 5.0 out of 10, a spread that shows how unevenly shipping cadence is distributed across the field. Below: every tracked product carrying this theme, updated from release data. Everything on this page is regenerated from verified release data, so the ranking reflects the latest changelogs rather than a static list.
#01GeoServerGeoServer patches three branches at once, with the new work reserved for the 3.0 line5.0alternatives →#02MapnikMapnik is turning a local-file map renderer into a client of remote tile archives2.5alternatives →#03MapServerFive of MapServer's last six releases exist to fix security advisories.2.5alternatives →#04topocastNew R package downscaling coarse climate rasters onto fine terrain, now five times cheaper per call.2.5alternatives →#05geosThe thin GEOS binding for R adds terra interop after three years of compiler triage0.0alternatives →#06GRASS GISGRASS dropped the GIS from its name and gave Python users a real API.0.0alternatives →#07osm2pgsqlosm2pgsql is rebuilding tile expiry so a small edit stops invalidating a whole lake.0.0alternatives →#08libosmiumlibosmium is a stable OSM parsing library whose main work now is shedding old dependencies0.0alternatives →#09ggmapinsetA ggplot2 inset-map extension that is now infrastructure for other packages0.0alternatives →#10leafletleaflet relicensed to MIT and finished migrating off R's retired spatial stack0.0alternatives →#11tidyterratidyterra finished wiring terra objects into the tidyverse, one verb family at a time.0.0alternatives →#12FedDataFedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.0.0alternatives →#13inbospatialA thin R wrapper over Flemish geospatial services, adding one standard at a time0.0alternatives →#14naijRnaijR is assembling the Nigerian reference data R analysts otherwise hand-code every time.0.0alternatives →#15dggridRA discrete global grid generator grew cell traversal and became a usable spatial index.0.0alternatives →#16osmextractosmextract stopped throwing your OpenStreetMap downloads away at the end of every session.0.0alternatives →#17arcgisutilsThe R-ArcGIS plumbing layer grew a portal administration API and geoprocessing job support.0.0alternatives →#18geomanderA redistricting toolkit that grows mostly by wiring in new public data sources0.0alternatives →#19choleraJohn Snow's 1854 cholera map is being rebuilt on real geographic coordinates.0.0alternatives →#20osmapiRosmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.0.0alternatives →#21parzerA coordinate parser whose entire job is surviving how badly humans write latitude and longitude.0.0alternatives →#22geoarrow-rgeoarrow tracks the GeoArrow spec and otherwise just keeps compiling0.0alternatives →#23geopandasGeoPandas bet everything on shapely 2 and Pyogrio, and is now paying down pandas 30.0alternatives →#24rasterpicrasterpic became an S3 generic and picked up stars support; the rest is upkeep0.0alternatives →#25Apache BaremapsBaremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation0.0alternatives →#26raprrapr generalises its Rangeland Analysis Platform API access one endpoint at a time0.0alternatives →#27mapSpainmapSpain's 1.0.0 broke every user cache to get the package onto modern foundations.0.0alternatives →#28hydroloomUSGS puts a type system over its river network toolkit so errors surface at dispatch0.0alternatives →#29geodistgeodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.0.0alternatives →#30geotargetsGeospatial targets grew from two raster helpers into a tiling and multi-backend pipeline layer.0.0alternatives →#31rioxarrayrioxarray is a thin, disciplined seam between rasterio and xarray — and stays that way.0.0alternatives →#32gpkgAn R interface to GeoPackage that keeps sanding down its own API0.0alternatives →#33nswgeoNSW boundary data for R, refreshed as the official sources move0.0alternatives →#34duckspatialduckspatial rebuilt itself around a lazy DuckDB class, then spent four releases filling in the geometry surface0.0alternatives →#35giscoRgiscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.0.0alternatives →#36wkwk spent one release fixing what empty means, then went quiet.0.0alternatives →#37geoboundsgeobounds relicensed to MIT and drew a line between its code and the data it downloads.0.0alternatives →#38osrm.backendosrm.backend stopped trusting upstream binaries and started shipping its own0.0alternatives →#39gtfstoolsgtfstools stopped guarding its own object model and started accepting everyone else's.0.0alternatives →#40ggspatialggspatial finishes its move off raster and onto terra0.0alternatives →
Frequently asked questions about geospatial
Which SaaS tools ship geospatial in 2026?
GeoServer, Mapnik, MapServer, topocast, geos, and 35 more — the geospatial products Sparkpulse tracks, ranked by shipping velocity from verified changelogs.
Which geospatial product has the highest shipping velocity?
GeoServer, with the top velocity score (5.0/10) — Sparkpulse's velocity score is derived from verified release data.
How many products are shipping around geospatial?
Sparkpulse currently tracks 43 products carrying the geospatial theme, updated continuously from verified release data.