#pygeos
Live, measured metrics for the hashtag #pygeos from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #pygeos
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-07-28 01:25 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-07-28 01:25 UTCNo related tags with measured usage found for #pygeos.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-28 01:25 UTCEverything below is measured over the latest 2 public posts (spanning ~3361 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1.5
Top of the latest posts
Today I learned that #PyGEOS and #shapely merged in 2021 and that brought ufunc numpy capabilities to shapely. https://shapely.readthedocs.io/en/stable/ #Python #GIS #GEOS #computationalGeometry #Python #numpy
Today's update is #Momepy and #Pysal may give unexpected results due to #PyGeos and #Shapely 2.0 compatibility. The problem is here https://github.com/pysal/momepy/issues/472. Based on the PR comments #473 https://github.com/pysal/momepy/pu
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/pygeos