#gdal
Live, measured metrics for the hashtag #gdal from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #gdal
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 07:19 UTC2 uses by 2 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 07:19 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:19 UTCEverything below is measured over the latest 40 public posts (spanning ~2089 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (33) · German (5) · Catalan (1) · French (1)
Avg boosts / post: 2.3
Top of the latest posts
Three #GDAL t-shirts in #foss4ge2026 @EvenRouault @michikommader
Running a large Open Source project is tough and expensive, good to see GDAL v3.13.0+ calling out Cloud Providers who profit off gdal, but no longer support the project: https://github.com/OSGeo/gdal/pull/14313 #OpenSource #GDAL #AWS #Azure
GDAL can fix invalid geometries in a few different ways, depending on what you want to preserve. The main options are a “linework” approach that sticks closely to the original input, and a “structure” approach that prioritises clean, valid
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/gdal