#atmosphericCorrection
Live, measured metrics for the hashtag #atmosphericCorrection from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #atmosphericcorrection
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.online (Mastodon public tags API) · fetched 2026-10-02 04:40 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.online (Mastodon public search API) · fetched 2026-10-02 04:40 UTCNo related tags with measured usage found for #atmosphericcorrection.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-02 04:40 UTCEverything below is measured over the latest 4 public posts (spanning ~32825 hours).
Posting hours (UTC)
Languages: English (3) · French (1)
Avg boosts / post: 0.8
Top of the latest posts
Enhancements To The USGS Landsat Level 2 Surface Temperature And Emissivity Product For Collection3 Reprocessing -- https://doi.org/10.1016/j.rse.2026.115563 <-- shared paper -- H/T @terry Sohl | USGS EROS Science Branch Chief “HIGHLIGHTS:
Integrated Topographic Corrections Improve Forest Mapping Using Landsat Imagery -- https://doi.org/10.1016/j.jag.2022.102716 <-- shared 2022 paper -- “HIGHLIGHTS: • [They] evaluated the impacts of topographic correction on forest mapping in
@lavergnetho @trappmartin yeah, this is the sort of thing I had in mind. We have a recent paper on #AtmosphericCorrection (https://gmd.copernicus.org/articles/15/7933/2022/), where the uncertainty considerations were the hardest thing to ju
#atmosphericcorrection across platforms
every network with a public tag surfaceFollow #atmosphericcorrection 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/atmosphericcorrection