API Access
Access dataset files directly from scripts, code, or AI agents.
Browse dataset files
API Access
Access dataset files directly from scripts, code, or AI agents.
Dataset Files
Each file has a stable URL (r-link) that you can use directly in scripts, apps, or AI agents. These URLs are permanent and safe to hardcode.
/core/seismic-bumps/
https://datahub.io/core/seismic-bumps/_r/-/README.md
https://datahub.io/core/seismic-bumps/_r/-/UPDATE_SCRIPT_MAINTENANCE_REPORT.md
https://datahub.io/core/seismic-bumps/_r/-/data/seismic-bumps.csv
https://datahub.io/core/seismic-bumps/_r/-/datapackage.json
Key Files
Start with these files — they give you everything you need to understand and access the dataset.
datapackage.json— metadata & schema
https://datahub.io/core/seismic-bumps/_r/-/datapackage.json
README.md— documentation
https://datahub.io/core/seismic-bumps/_r/-/README.md
Typical Usage
- 1. Fetch datapackage.json to inspect schema and resources
- 2. Download data resources listed in datapackage.json
- 3. Read README.md for full context
Data Files
Explore with AIseismic-bumps
| Field | Type | Format | Description |
|---|---|---|---|
| seismic | string | default | result of shift seismic hazard assessment in the mine working obtained by the seismic method (a - lack of hazard, b - low hazard, c - high hazard, d - danger state) |
| seismoacoustic | string | default | result of shift seismic hazard assessment in the mine working obtained by the seismoacoustic method |
| shift | string | default | information about type of a shift (W - coal-getting, N -preparation shift) |
| genergy | integer | default | seismic energy recorded within previous shift by the most active geophone (GMax) out of geophones monitoring the longwall |
| gpuls | integer | default | a number of pulses recorded within previous shift by GMax |
| gdenergy | integer | default | a deviation of energy recorded within previous shift by GMax from average energy recorded during eight previous shifts |
| gdpuls | integer | default | a deviation of a number of pulses recorded within previous shift by GMax from average number of pulses recorded during eight previous shifts |
| ghazard | string | default | result of shift seismic hazard assessment in the mine working obtained by the seismoacoustic method based on registration coming form GMax only |
| nbumps | integer | default | the number of seismic bumps recorded within previous shift |
| nbumps2 | integer | default | the number of seismic bumps (in energy range [10^2,10^3)) registered within previous shift |
| nbumps3 | integer | default | the number of seismic bumps (in energy range [10^3,10^4)) registered within previous shift |
| nbumps4 | integer | default | the number of seismic bumps (in energy range [10^4,10^5)) registered within previous shift |
| nbumps5 | integer | default | the number of seismic bumps (in energy range [10^5,10^6)) registered within the last shift |
| nbumps6 | integer | default | the number of seismic bumps (in energy range [10^6,10^7)) registered within previous shift |
| nbumps7 | integer | default | the number of seismic bumps (in energy range [10^6,10^7)) registered within previous shift |
| nbumps89 | integer | default | the number of seismic bumps (in energy range [10^6,10^7)) registered within previous shift |
| energy | integer | default | the number of seismic bumps (in energy range [10^6,10^7)) registered within previous shift |
| maxenergy | integer | default | the maximum energy of the seismic bumps registered within previous shift |
| class | integer | default | the decision attribute - "1" means that high energy seismic bump occurred in the next shift ("hazardous state"), "0" means that no high energy seismic bumps occurred in the next shift ("non-hazardous state") |
Download
Download CSVAbout
- Last updated
- 9 February 2026
- Total rows
- ...
- Format
- CSV
- File size
- 128 kB
About this dataset
Update Script Maintenance Report
Date: 2026-03-04
- Ran updater:
python scripts/main.py. - Root cause: repository had no workflow automation despite having a working script.
- Fixes made: added first monthly + manual workflow with explicit
contents: writepermission and commit-if-changed guard. - Validation summary: updater executes successfully in current environment.