#Momepy
Live, measured metrics for the hashtag #Momepy from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #momepy
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 22:19 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 22:19 UTCNo related tags with measured usage found for #momepy.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 22:19 UTCEverything below is measured over the latest 4 public posts (spanning ~1515 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0.5
Top of the latest posts
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
The sx layer in the GeoPKG uses the centre-line track-model overlay on OpenStreetMap #OSM rail data based on minimum point to track distance The ox uses only OSM data for track and meta-data tags TIPLOC and STANOX locations are matched usin
@martinfleis for what it's worth I have updated all of the modules according to your recipe and have a backwardly incompatible #pysal #momepy but Shapely 2.0 "compliant" version on GitHub. This is based on my now-closed pull-request. It pas
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/momepy