#HistoricalGIS
Live, measured metrics for the hashtag #HistoricalGIS from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #historicalgis
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.social (Mastodon public tags API) · fetched 2026-10-15 20:10 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-15 20:10 UTCNo related tags with measured usage found for #historicalgis.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-15 20:10 UTCEverything below is measured over the latest 8 public posts (spanning ~31559 hours).
Posting hours (UTC)
Languages: English (8)
Avg boosts / post: 0.9
Top of the latest posts
Geospatial analysis and modeling is not only about: 1. downloading Copernicus data, 2. generating pretty maps, 3. calling it “analysis”. In reality it often means years of collecting and reconciling heterogeneous data from different eras: d
#DniproHesFlood 🛰️ Dam-break modelling with GRASS GIS I used the r.damflood module in GRASS GIS on a historical scenario: the destruction of the DniproHES dam by Soviet forces in August 1941 during their retreat from Ukraine. I reconstruct
Start and end #dates are very important for a #HistoricalGIS project. We managed to stuff dates into more of the website’s nooks and crannies, so you always know which stage of a boundary or building’s evolution you’re looking at, or whethe
#historicalgis across platforms
every network with a public tag surfaceFollow #historicalgis straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/historicalgis