CORE SYSTEM 3 OF 6

GIS

Geographic Information System

A web-based geospatial platform that enables PDRRMO to visualize hazards, plan evacuations, track critical facilities, and analyze risk patterns across the Province of Zambales — all on a single interactive map interface.

Hazard Mapping Evacuation Planning Spatial Analysis Asset Tracking Public Map Portal

System Overview

01

Layer Management

Create, edit, organize, and publish thematic map layers for hazards, infrastructure, demographics, and administrative boundaries.

02

Spatial Analysis

Run buffer queries, intersection analysis, distance measurement, and population-at-risk calculations directly on the map.

03

Public Portal

Citizen-facing map portal showing approved hazard zones, evacuation centers, and disaster preparedness information.

Demo Accounts

Use these credentials in the staging environment to explore role-specific features.

All demo accounts share the same password: P@ssw0rd123

Role Username Department / Position
SuperAdminadminIT Administrator
GIS AdministratorgisadminGIS Division Head
PDRRMO Head (DRRM)drrm.headPDRRMO Officer
DRRM Operationsdrrm.opsOperations Section Chief
Provincial Health (PHO)pho.headProvincial Health Officer
Epidemiology Staffpho.epiEpidemiology Officer (PHO)
PSWDO Headpswdo.headProvincial Social Welfare Officer
Evacuation Coordinatorpswdo.evacEvacuation Center Manager (PSWDO)
Provincial Engineer (PEO)peo.headProvincial Engineer
Roads & Bridges Staffpeo.roadsRoads Section (PEO)
PENRO Headpenro.headEnvironmental Officer
Provincial Agriculturistpagro.headPAGRO Head
PPDO Headppdo.headPlanning & Development Officer
Tourism Officertourism.headProvincial Tourism Officer
Provincial AssessorassessorProvincial Assessor
Read-only ViewerviewerRead-only access
Public Citizenpublic1Public map portal only (citizen@gmail.com)
Note: Demo credentials are seeded by the database initializer. Production credentials are issued upon system handover.

Roles & Permissions Matrix

Capability Admin Officer Viewer Surveyor Public
View public hazard maps✓✓✓✓✓
View internal/draft layers✓✓✓✓—
Create / edit map layers✓✓———
Publish layers to public✓————
Capture geo-tagged field data✓✓—✓—
Run spatial analysis tools✓✓———
Manage users & roles✓————
Export reports & maps✓✓✓—PDF
Approve / archive layers✓————

End-to-End Workflows

Master Workflow — Hazard Map Lifecycle

From raw geospatial data to publicly accessible hazard map.

flowchart TD A([Raw Spatial Data Source]) --> B[GIS Officer Logs In] B --> C{Data Type?} C -->|Vector| D[Upload Shapefile / GeoJSON] C -->|Raster| E[Upload Imagery / Elevation] C -->|Field Capture| F[Mobile Geo-tagging by Surveyor] D --> G[Layer Configuration] E --> G F --> G G --> H[Apply Symbology & Labels] H --> I[Set Visibility & Permissions] I --> J[Submit for Review] J --> K{Admin Approval} K -->|Reject| L[Return with Comments] L --> G K -->|Approve| M[Publish to Internal Layer] M --> N{Publish to Public?} N -->|No| O([Internal Use Only]) N -->|Yes| P[Push to Public Portal] P --> Q([Citizens Access via Web/Mobile]) style A fill:#E8EEF6,stroke:#1F4E79 style Q fill:#D1FAE5,stroke:#065F46 style O fill:#FEF3C7,stroke:#92400E

Workflow A — New Layer Creation

GIS Officer publishes a new flood hazard layer for Subic Bay area.

flowchart LR A[Login as Officer] --> B[Open Layer Manager] B --> C[Click 'New Layer'] C --> D[Fill Metadata
Name, Category, Source] D --> E[Upload Boundary File] E --> F[Configure Style
Color, Opacity, Labels] F --> G[Preview on Map] G --> H{Looks Correct?} H -->|No| F H -->|Yes| I[Save as Draft] I --> J[Submit for Approval] style A fill:#E8EEF6 style J fill:#D1FAE5

Step-by-Step Procedure

1
Login using GIS Officer credentials at the staging URL.
2
Navigate to Map Manager → Layers → New Layer.
3
Fill in metadata: Layer Name, Category (Hazard / Infrastructure / Boundary / Other), Source Agency, Date Captured.
4
Upload boundary file (supported formats: SHP, KML, GeoJSON). The system auto-detects coordinate system.
5
Configure styling: choose fill color, outline weight, labels, and zoom-level visibility.
6
Preview the layer rendered on the live map. Adjust until satisfactory.
7
Save as Draft for further editing, or Submit for Approval to send to GIS Administrator.

Workflow B — Spatial Query (Population at Risk)

PDRRMO Officer identifies how many residents fall within a flood-prone zone.

flowchart TD A[Open Spatial Analysis Panel] --> B[Select Hazard Layer
e.g. Flood Zone 5-Year] B --> C[Select Reference Layer
e.g. Household Points] C --> D[Choose Operation
Intersect / Buffer / Within] D --> E[Set Distance / Threshold] E --> F[Execute Query] F --> G[System Computes Result] G --> H[Display Count + Highlight on Map] H --> I{Export?} I -->|Yes| J[Generate PDF / CSV Report] I -->|No| K[Save Query for Reuse] style A fill:#E8EEF6 style J fill:#D1FAE5 style K fill:#D1FAE5

Workflow C — Field Data Capture (Mobile)

Field Surveyor records evacuation centers and critical facilities.

flowchart LR A[Surveyor Opens Mobile App] --> B[Login] B --> C[Select Capture Form
Evac Center / Critical Facility] C --> D[Capture GPS Coordinates] D --> E[Take Photos] E --> F[Fill Attributes
Capacity, Owner, Condition] F --> G{Online?} G -->|Yes| H[Sync to Server Immediately] G -->|No| I[Save Offline] I --> J[Auto-Sync When Online] J --> H H --> K[Pending Review by Officer] K --> L[Officer Verifies & Publishes] style A fill:#E8EEF6 style L fill:#D1FAE5

Use Case Scenarios

SCENARIO 1

Pre-Typhoon Risk Assessment

Three days before a typhoon makes landfall, PDRRMO needs to identify barangays with high flood exposure and senior-citizen populations.

  1. Officer overlays Storm Surge Hazard layer + Household Points
  2. Filter households by "65+ residents present"
  3. Run intersect query → returns 1,247 households across 18 barangays
  4. Export prioritized evacuation list to PDF
  5. Share with Mayor's Office and BDRRMC
SCENARIO 2

Evacuation Center Capacity Planning

DRRMO plans evacuation routing for a coastal barangay during storm surge alerts.

  1. Open Evacuation Centers layer with capacity attributes
  2. Buffer 3 km around affected barangay
  3. Identify 4 nearest evacuation centers within buffer
  4. Cross-check capacity against expected evacuee count
  5. Generate routing map with primary + backup centers
SCENARIO 3

Post-Disaster Damage Mapping

After flooding, field surveyors document affected structures using the mobile app.

  1. Surveyors capture damage photos + GPS + severity rating
  2. Data syncs automatically to GIS
  3. Officer reviews and verifies entries
  4. Damage Heat Map auto-generated
  5. Report sent to OCD and DSWD for relief allocation
SCENARIO 4

Public Citizen Lookup

A resident wants to verify whether their address is within a flood-prone zone.

  1. Citizen opens Public Map Portal (no login required)
  2. Searches their address or pins location on map
  3. System shows overlapping hazard zones with classification
  4. Lists nearest evacuation centers
  5. Citizen can download a personalized Risk Profile PDF

System Outputs

REPORT
Hazard Exposure Report
Population & assets within hazard zones, by barangay
MAP
Printable Hazard Maps
A0/A1/A4 layouts with legend & scale
DATA
Layer Export
Shapefile, GeoJSON, KML formats
DASHBOARD
Risk Dashboard
Province-wide risk indicators at a glance

Frequently Asked Questions

Can GIS work offline?

The mobile companion supports offline data capture; entries auto-sync when connectivity is restored. The web interface requires an internet connection.

What spatial data formats are supported?

Shapefile (SHP), GeoJSON, KML/KMZ, GPX, and standard raster formats (GeoTIFF). The system auto-reprojects to the working coordinate system.

How are public layers different from internal layers?

Internal layers are visible only to authenticated PDRRMO users. Public layers are pushed to the citizen portal after Administrator approval, ensuring sensitive draft data is not exposed.

Does GIS integrate with the other 4 systems?

Yes. GIS shares authentication and data with ESM (incident geo-tagging), CBMS (household location), and Project Management (project sites).

Is there a limit on layer count or data size?

No fixed cap; the platform scales with your needs. Layers are automatically tiled and cached for performant rendering.