Source change monitor

Recurring pulls become operational evidence.

The builder records each CKAN and ArcGIS source pull, then computes deltas so the launch team can see whether source counts changed between packet builds. This is source monitoring from public endpoints, not a claim about City production schedules.

7

Recorded source pulls

0

Runs with core count changes

+3,920

ArcGIS Hub view change

2026-06-14T09:36:45.996Z

Latest pull timestamp

Source popularity

The City's existing open data is already in demand

View counts on the City's existing ArcGIS Hub item, captured at each source pull. This is a baseline of public interest in San José's open data today — not a usage metric of this proposed portal.

Change monitor export

The CSV keeps each pull timestamp, observed source counts, count deltas, Hub view delta, and source-pull note together for launch operations review.

Download change monitor CSV

Latest monitor signal

  • Core CKAN and ArcGIS source counts stayed stable on the latest pull.
  • Latest CKAN package count: 170.
  • Latest datastore-backed resource count: 265.
  • Latest ArcGIS layer count: 149.

Refresh-to-refresh deltas

Rows are ordered newest first. Delta columns compare each run to the previous recorded run.

Pull timestampCKAN packagesDeltaDatastore resourcesDeltaArcGIS layersDeltaHub viewsDelta
2026-06-14T09:36:45.996Z 170 0 265 0 149 0 1,776,736 +627
2026-06-14T03:36:38.972Z 170 0 265 0 149 0 1,776,109 +635
2026-06-13T21:36:51.832Z 170 0 265 0 149 0 1,775,474 +549
2026-06-13T15:40:16.471Z 170 0 265 0 149 0 1,774,925 +538
2026-06-13T09:44:29.715Z 170 0 265 0 149 0 1,774,387 +613
2026-06-13T03:40:02.462Z 170 0 265 0 149 0 1,773,774 +958
2026-06-12T21:39:13.715Z 170 0 265 0 149 0 1,772,816 0