#overpass
Live, measured metrics for the hashtag #overpass from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #overpass
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 09:53 UTC0 uses by 0 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 09:53 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:53 UTCEverything below is measured over the latest 40 public posts (spanning ~5102 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (27) · German (4) · French (2)
Avg boosts / post: 2
Top of the latest posts
#Overpass is such a powerful #OpenStreetMap tool, but it has the strangest version numbers ever. Latest release is v0.7.62.4 4 levels of version number! v0.7.0 was released more than 10 years ago... Cripes, just do a “version one release” �
I've built a small web tool to generate #GeoJSON from #OpenStreetMap public transport route relations. https://openstreetmap.tools/public_transport_geojson/ Supports bus, tram, train, subway, light rail, trolleybus, monorail, ferry and funi
I am REALLY FRIKKEN MAD now that the PBF→Spatialite conversion of #OSM data loses all of the relationships made by the relations in the data. I had to give up on #overpass queries because hey nobody can run an API any more without drowning
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/overpass