Provenance
Data and sources
Nothing on this portal is typed by hand. Each dataset below is fetched from the publisher by the ETL in this repository, reduced to the part that concerns Labo, and compiled into a static file the website serves. A refresh replaces the file and records a new retrieval date.
Deferred
1
Named, not yet wired
Local fiscal data compiled and published by the Bureau of Local Government Finance (BLGF), Department of Finance.
Four per-LGU workbooks, one row selected for Labo, Camarines Norte. sha256 is of the Statement of Receipts and Expenditures workbook; bytes is the combined download size.
- Retrieved
- Oct 21, 2026
- Source version
- FY 2024 (Preliminary)
- Rows compiled
- 95
- Downloaded
- 1.8 MB
- Portal dataset
- #9
Produced
- Fiscal sections and figures
- BLGF — FY 2024 Statement of Receipts and Expenditures by LGU (resource 30)
- BLGF — FY 2024 Annual Regular Income and Dependencies by LGU (resource 31)
- BLGF — FY 2024 Special Education Fund Income and Expenditures (resource 44)
- BLGF — FY 2024 Local Disaster Risk Reduction Management Fund by LGU (resource 41)
sha256 e836347e1e5dec7a57a195ba218613c861a65187b0e64554d239f23f45f02715
Infrastructure project data from the official DPWH transparency platform, packaged by BetterGov.ph.
Read from a 248220-row Parquet file (17 of 25 columns projected). 214747 rows carry usable coordinates; 478 fall inside Labo's bounding box, and 309 fall inside a Labo barangay polygon. 203 row(s) name Labo in the description but could not be located, so they are excluded. `location.province` is the implementing District Engineering Office, not a project location.
- Retrieved
- Oct 21, 2026
- Source version
- 2025-11-29
- Rows compiled
- 309
- Downloaded
- 23.2 MB
- Portal dataset
- #19
Produced
sha256 5b411cf3f112fabd1913c70681791e5e2b78b43a8393f489f48bd882f154e123
Municipal Government of Labo, Camarines Norte — official website (labo.gov.ph). Retrieved via the Internet Archive Wayback Machine; each section records its snapshot date.
Not compiled in this run: no task in this run produced it
- Retrieved
- Oct 17, 2026
- Source version
- —
- Rows compiled
- —
- Downloaded
- —
- Portal dataset
- —
Produced
- Nothing — this source was not compiled in the last refresh.
Hazard layers produced by Project NOAH, Department of Science and Technology, Philippines.
Per-province shapefile archives for Camarines Norte, clipped to the Labo municipal outline with a point-in-polygon test. Analysed: flood_5yr (static, 3 features), flood_25yr (static, 3 features), flood_100yr (static, 3 features), landslide (static, 4 features), storm_surge (none-in-area, 0 features).
- Retrieved
- Oct 21, 2026
- Source version
- 2026-04-11
- Rows compiled
- 13
- Downloaded
- 37.9 MB
- Portal dataset
- #22
Produced
- Hazard layer registry
- /data/hazards/labo-flood-5yr.geojson
- /data/hazards/labo-flood-25yr.geojson
- /data/hazards/labo-flood-100yr.geojson
- /data/hazards/labo-landslide.geojson
sha256 8b3fbedbb8027bbea6e8300867dc639d2d2e4616b7b658fedde19249cfee667c
Boundary polygons derived from PSA Philippine Standard Geographic Code snapshots (2023-10-24) and NAMRIA administrative-boundary shapefiles (v2023-11-06), packaged by Manuel Balmeo.
Selected 52 of 42026 national barangay polygons by ADM3_PCODE=PH0501606; geometry simplified at 0.0002°. Areas are the upstream AREA_SQKM values (NAMRIA-derived), not recomputed.
- Retrieved
- Oct 21, 2026
- Source version
- v2026.4.13.0
- Rows compiled
- 52
- Downloaded
- 69.5 MB
- Portal dataset
- #23
Produced
- Barangay boundary polygons
- Municipal outline
- Barangay directory index
sha256 10606e46cd7b4b34a61f4975f3568bb3c11a48fa355cbe3c4d78c3737e0fcfa9
Hazard layers
What is compiled, and what was checked and found empty
Static clipped layers are served from /data/hazards/. A layer marked "none-in-area" was compiled and analysed and genuinely has no Labo coverage — that is a finding, not a gap. A layer marked "remote" is streamed from Project NOAH’s published tile archive by HTTP range request and is not a copy held in this repository.
Flood — 5-year return period
Clipped from 3 province-level features; 0 were dropped after the bounding-box pass. 3 feature(s) fell back to a bounding-box clip because the upstream contour could not be intersected exactly (it self-intersects), so their outer boundary may include a sliver of a neighbouring municipality. 129317 polygon piece(s) whose interior point fell outside the Labo outline were discarded, so hazard belonging to neighbouring municipalities is not shown here. Simplified at 0.0003° tolerance to keep the layer under 8.388608 MB. Hazard classes follow the Project NOAH legend in the per-layer readme PDF that ships inside the province archive.
Flood — 25-year return period
Clipped from 3 province-level features; 0 were dropped after the bounding-box pass. 3 feature(s) fell back to a bounding-box clip because the upstream contour could not be intersected exactly (it self-intersects), so their outer boundary may include a sliver of a neighbouring municipality. 132539 polygon piece(s) whose interior point fell outside the Labo outline were discarded, so hazard belonging to neighbouring municipalities is not shown here. Simplified at 0.0003° tolerance to keep the layer under 8.388608 MB. Hazard classes follow the Project NOAH legend in the per-layer readme PDF that ships inside the province archive.
Flood — 100-year return period
Clipped from 3 province-level features; 0 were dropped after the bounding-box pass. 3 feature(s) fell back to a bounding-box clip because the upstream contour could not be intersected exactly (it self-intersects), so their outer boundary may include a sliver of a neighbouring municipality. 344553 polygon piece(s) whose interior point fell outside the Labo outline were discarded, so hazard belonging to neighbouring municipalities is not shown here. Simplified at 0.0192° tolerance to keep the layer under 8.388608 MB. Hazard classes follow the Project NOAH legend in the per-layer readme PDF that ships inside the province archive.
Rain-induced landslide
Clipped from 4 province-level features; 0 were dropped after the bounding-box pass. 4 feature(s) fell back to a bounding-box clip because the upstream contour could not be intersected exactly (it self-intersects), so their outer boundary may include a sliver of a neighbouring municipality. 323667 polygon piece(s) whose interior point fell outside the Labo outline were discarded, so hazard belonging to neighbouring municipalities is not shown here. Simplified at 0.0192° tolerance to keep the layer under 8.388608 MB. Hazard classes follow the Project NOAH legend in the per-layer readme PDF that ships inside the province archive.
Storm surge (advisory 1)
The Camarines Norte archive was compiled and analysed, and no part of Labo falls inside this layer's hazard zones: all 3 province-level feature(s) were rejected by a point-in-polygon test against the municipal outline. This is a result, not a missing layer.
Named, not yet wired
Fields this portal refuses to guess
Each of these is named in the BetterLabo brief. None has a machine-readable upstream source yet, so the portal shows them as pending and links to the source document instead.
Barangay population
No barangay-level PSA census extract is published on data.bettergov.ph. Place an official PSA Census of Population file at data/sources/psa-population.csv (headers: psgc_code,population,source,year) and re-run `npm run etl barangays` to attach it.
Annual Investment Plan (AIP) line items
The AIP is published per-LGU as a PDF on the LGU website, not as a structured dataset. The FDPP explorer links to the source document instead of transcribing it.
Commission on Audit annual audit report text
data.bettergov.ph dataset 14 indexes COA audit-agency listings as PDFs; the Labo-specific report has not been parsed into structured rows.
Elected and appointed officials
COMPILED — see apps/web/public/data/lgu.json. Source: the Municipality of Labo's own website (labo.gov.ph) via the Wayback Machine, because the live host is behind a Cloudflare challenge. Every section carries the snapshot date it came from, because the current capture names no mayor, vice mayor or councilor.
Ordinance index
No machine-readable source; municipal ordinance PDFs are not published as a dataset.
Reuse
Take the data and check our work
The compiled files are plain JSON and GeoJSON under /data/ and can be fetched directly, e.g. /data/fiscal.json. The ETL that produced them is open source, and npm run etl:verify re-checks every figure against the source workbook. If a number here disagrees with the official record, that is a bug — please report it.