GIS Monitoring Systems Training Course

Participants can design a geodatabase structure for monitored features, observations and events.

• Feature classes structured for assets, sites, boundaries, events and observations
• Entity relationship diagrams define keys, cardinality and temporal records
• Unique identifiers maintain traceability between field records and mapped features
• Domains, subtypes and coded values prevent inconsistent attribute entry
• Observation tables separate repeated measurements from static asset attributes
• Versioned records preserve historical condition, status and inspection changes

Participants can select coordinate reference systems and assess positional fitness for monitoring data.

• Geographic and projected coordinate reference systems selected for measurement purposes
• Datum transformations documented when combining datasets from different sources
• Positional accuracy assessed against monitoring tolerances and intended decisions
• GNSS error sources include multipath, canopy, atmospheric delay and geometry
• Scale, resolution and minimum mapping units matched to monitoring requirements
• Topology rules detect gaps, overlaps, dangles and invalid feature relationships

Participants can create spatial indicator definitions that support repeatable monitoring and reporting.

• Indicator definitions specify numerator, denominator, unit, geography and frequency
• Baselines established using dated datasets, documented methods and acceptance criteria
• Thresholds distinguish normal variation, early warning and escalation conditions
• Disaggregation rules define reporting by location, asset type and population
• Data dictionaries record field names, formats, sources and permitted values
• Indicator ownership assigns collection, validation, approval and response responsibilities

Participants can specify reliable mobile workflows for inspections, surveys and incident reporting.

• Mobile forms capture geometry, attributes, photographs, timestamps and collector identity
• Required fields, skip logic and constraints enforce valid inspection records
• Offline synchronization procedures manage disconnected locations and delayed submissions
• Sampling plans define coverage, revisit intervals, sample frames and selection methods
• Field protocols standardize observations, photographs, severity ratings and safety checks
• Supervisor review queues identify incomplete, duplicate and suspicious submissions

Participants can establish quality controls for spatial, attribute and temporal monitoring data.

• Completeness checks compare submitted records against planned monitoring coverage
• Accuracy assessments distinguish positional, thematic, temporal and attribute errors
• Validation rules test ranges, mandatory values, relationships and duplicate identifiers
• Quality flags classify accepted, corrected, rejected and pending observation records
• Audit trails record editor, change date, reason and approval status
• Acceptance sampling sets inspection rates for large field-data submissions

Participants can select suitable earth observation data for defined monitoring questions.

• Spatial resolution matched to target size, boundary precision and mapping scale
• Spectral resolution selected for vegetation, water, soil and built surfaces
• Temporal resolution assessed against change frequency, cloud cover and reporting cycles
• Radiometric resolution considered when detecting subtle reflectance differences
• Passive optical, thermal and radar sensors compared for monitoring tasks
• Image acquisition plans document seasonality, revisit dates and acceptable cloud thresholds

Participants can prepare imagery for comparison, classification and monitoring analysis.

• Radiometric correction reduces sensor noise and atmospheric reflectance effects
• Geometric correction aligns imagery with reference data and map coordinates
• Cloud masking removes cloud, haze and shadow contamination from analyses
• Mosaicking combines adjacent scenes using consistent projection and color balancing
• Band combinations reveal vegetation vigor, water extent and urban surfaces
• Normalized Difference Vegetation Index supports vegetation condition monitoring

Participants can apply image classification and change-detection methods to monitoring questions.

• Supervised classification uses labelled training samples and class signatures
• Unsupervised classification groups pixels before analyst interpretation and labelling
• Confusion matrices measure producer, user and overall classification accuracy
• Post-classification comparison identifies transitions between dated land-cover maps
• Image differencing detects change using pixel values from aligned scenes
• Change maps filtered using minimum mapping units and verification samples

Participants can plan integration of sensor observations with GIS monitoring data.

• Sensor metadata records device type, calibration, location and measurement units
• Time-series data linked to spatial assets through persistent identifiers
• Telemetry ingestion rules manage frequency, latency, missing values and duplicates
• Calibration schedules maintain confidence in water, air and infrastructure sensors
• Alert logic combines sensor thresholds, duration rules and spatial context
• Data retention policies distinguish raw telemetry from summarized monitoring records

Participants can join operational records to GIS features while preserving data lineage.

• Master data identifiers align work orders, inspections, complaints and assets
• Geocoding converts addresses, place names and facilities into mapped locations
• Join rules document matching keys, cardinality and unmatched record treatment
• Data lineage records origin, extraction date, transformation and responsible owner
• Privacy controls limit exposure of personal, health and sensitive location data
• Update schedules reconcile operational systems with monitoring geodatabases

Participants can use spatial analysis to rank locations for inspection, response and investment.

• Buffer analysis identifies assets and populations within defined proximity zones
• Overlay analysis combines hazards, exposure, condition and service coverage layers
• Hot spot analysis identifies statistically significant concentrations of incidents
• Kernel density surfaces show incident intensity beyond administrative boundaries
• Multi-criteria decision analysis weights spatial factors for priority ranking
• Network analysis estimates travel time, service areas and response accessibility

Participants can identify meaningful trends and exceptions in monitored spatial time series.

• Time-enabled layers display observation sequences, durations and status changes
• Trend analysis separates sustained change from short-term measurement variation
• Rolling averages smooth volatile sensor readings and operational service indicators
• Control charts distinguish common-cause variation from actionable process signals
• Seasonal baselines prevent false alerts from predictable annual patterns
• Early warning thresholds combine magnitude, persistence and affected-area criteria

Participants can specify dashboard and alert products for operational monitoring decisions.

• Decision dashboards organize indicators by priority, geography, status and owner
• Map symbology communicates severity through tested color, size and classification rules
• Drill-down paths connect summary indicators to records, imagery and evidence
• Alert messages state trigger, location, affected asset and required response
• Service-level targets measure acknowledgement, investigation and closure performance
• Dashboard refresh schedules match data latency and management review cycles

Participants can specify data-sharing services and exchange controls for GIS monitoring systems.

• OGC Web Map Service publishes rendered maps for shared viewing
• Web Feature Service supports controlled access to vector monitoring features
• Application programming interfaces exchange observations with operational information systems
• Metadata profiles document dataset purpose, extent, lineage and usage restrictions
• Service agreements define availability, update frequency, ownership and support responsibilities
• Schema mapping resolves field differences between partner monitoring datasets

Participants can establish governance controls for secure and accountable GIS monitoring operations.

• Data governance assigns stewardship, custodianship, access approval and retention duties
• Role-based access control restricts editing, viewing and administrative permissions
• Sensitive locations protected through aggregation, masking and controlled publication
• Personal data minimization limits collection to documented monitoring purposes
• Incident response procedures address unauthorized access, loss and data corruption
• Ethical review identifies surveillance risks, bias and potential community harm

Participants can plan ongoing operation, maintenance and improvement of a GIS monitoring system.

• Standard operating procedures document collection, validation, publication and escalation steps
• Maintenance schedules cover datasets, forms, services, dashboards and sensor inventories
• System performance metrics track uptime, latency, completeness and user adoption
• Change control evaluates proposed schema, indicator and workflow modifications
• Business continuity plans protect critical monitoring data and reporting services
• Implementation roadmaps sequence pilots, rollout, training, support and review

Participants can build, review and present a complete GIS monitoring system design for a defined operational case.

• Monitoring problem framed with users, decisions, indicators and response actions
• Geodatabase schema documents assets, observations, identifiers and data relationships
• Collection workflow specifies forms, validation rules, sampling and review stages
• Remote-sensing or sensor component justified against monitoring requirements and constraints
• Dashboard specification presents thresholds, map views, alerts and accountability
• Governance plan defines quality controls, access rules, maintenance and implementation milestones