Daily Map Events

What is it?

A daily breakdown of OpenStreetMap events affecting Bitcoin-merchant entries on BTCMap, decomposed into three event-type series - Created (green, primary), Updated (blue), Deleted (red) - rendered as vertical event spikes on the left count axis. A BTC price overlay (white line, right USD axis) is added by default for cycle context. The three series together expose the day-by-day pulse of the BTCMap registry: creation activity reflects mapping work, update activity reflects maintenance/verification, and deletion activity reflects cleanup or merchant attrition.

How to read

Read the three event-type spikes on the left Y-axis (compact count scale). The colours match the toolbar legend: Created in green, Updated in blue, Deleted in red. The white BTC line on the right USD axis is context - its scale typically dominates the visual area, so to read the event spikes precisely you may want to either toggle the BTC overlay off in the toolbar or switch the LOG scale (supportsLogScale=true) to compress the BTC axis. Days with one or more very tall coloured bars indicate concentrated activity (a cleanup campaign, a bulk import, a coordinated verification day); long stretches of low-amplitude bars indicate routine background work.

Key zones

This chart carries no drawn threshold lines - the qualitative reading is composition-based, not absolute-level-based. A healthy growing registry typically shows the green Created series dominating in spike height, with a steady carpet of blue Updated activity and modest red Deleted spikes. A red spike that visibly overshoots the other two on a single day is the signature of a cleanup campaign. Long flat stretches across all three series indicate contributor inactivity. Bulk operations (one contributor doing hundreds of events at once) can make a day look exceptionally active without reflecting broad community work.

What to observe

Track the day-by-day balance between the three series rather than absolute peaks. Created consistently above Deleted is an indication of growth; Deleted overshooting Created on isolated days is healthy maintenance, not a contraction. Watch for hot streaks of Updated activity - they often follow conference seasons or major BTCMap announcements. Compare the alignment with the BTC overlay: post-bull-market periods often produce activity waves driven by community enthusiasm.

Historical context

BTCMap's event-by-event tracking matured alongside the platform's API. The earliest days carry sparse coverage and should not be over-interpreted. As the registry grew and contributor tooling stabilized, the mix shifted from creation-heavy (early footprint expansion) toward a more balanced create/update mix typical of a mature community-maintained dataset. Specific historical 'event' days (cleanup campaigns, conference-driven bursts) are not annotated on this chart - they appear as visible spikes that can be cross-referenced against community calendars.

Expert notes

Bulk operations from a single contributor can make a day look exceptionally active without reflecting broad community work. To separate meaningful activity from noise, cross-reference this chart with the active-contributors metric - 100 events from 50 contributors is a healthier indication than 100 events from one contributor. Automated bots, if present, distort the daily series. Time-zone effects also matter: 'daily' is bounded by a UTC cutoff, so contributors active around midnight UTC may have their work split across two displayed days.

Common mistakes to avoid

A day with many Deleted spikes is not a bad day - it often represents important data cleanup that improves dataset quality. A day with many Created spikes is not automatically a good day - bulk imports can inflate the count without representing real merchant adoption. Event count is not merchant-experience quality. Focus on the composition and the multi-day trend, not on individual daily numbers. The BTC price overlay is purely contextual: alignment between event spikes and BTC price moves is not causation.

Programmatic access

REST API

curl -sS \
  'https://api.trinityinsights.io/api/v1/onchain/btcmap-daily-events/history?days=90' \
  -H 'X-API-Key: $TRINITY_API_KEY'

MCP server

{
  "tool": "get_chart_value",
  "metric_id": "btcmap-daily-events",
  "timeframe": "1y"
}

Required tier: pro. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.

Institutional disclaimer

Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.