Cloud GIS and Online Mapping Training Course

Participants can prepare spatial datasets that are suitable for reliable web publication.

• Coordinate reference systems, datum transformations and web mapping projection choices
• Geometry validation identifies nulls, duplicates, self-intersections and invalid rings
• Attribute schema design uses domains, aliases, identifiers and coded values
• Data normalisation separates repeated attributes into maintainable related tables
• Source lineage records origin, processing steps, currency and responsible owner
• ISO 19115 metadata elements applied to published spatial datasets

Participants can choose spatial formats and storage approaches for cloud GIS workflows.

• GeoPackage, GeoJSON, GeoParquet and shapefile limitations for web workflows
• PostGIS tables support multiuser editing, indexing and spatial SQL queries
• Raster pyramids, compression and overviews improve imagery delivery performance
• OGC API Features enables standards-based access to vector data
• WMS, WMTS and WFS service capabilities compared for client use
• ETL mapping reconciles field names, types, codes and spatial references

Participants can publish and configure online spatial services for intended users.

• Hosted feature layer publication sets fields, editing and query capabilities
• Tile layers accelerate display of stable, high-volume cartographic content
• Vector tiles separate map styling from source feature geometry
• Service item pages document purpose, owner, tags, credits and limitations
• Editing settings control adds, updates, deletes, attachments and editor tracking
• Generalisation and scale thresholds reduce service payload and visual clutter

Participants can design readable web maps for defined operational and public audiences.

• Visual hierarchy uses contrast, size, order and opacity intentionally
• ColourBrewer schemes support sequential, diverging and categorical thematic mapping
• Scale-dependent rendering prevents inappropriate detail at small map scales
• Classification methods compare natural breaks, quantiles, equal intervals and standard deviation
• Symbol design distinguishes status, priority, uncertainty and asset categories
• Accessible palettes account for colour vision deficiency and contrast requirements

Participants can configure useful web maps with meaningful feature interaction.

• Web map layer order communicates context, priority and operational relevance
• Pop-up design presents concise attributes, calculated values and related records
• Field formatting standardises dates, units, currencies and coded labels
• Search sources target addresses, assets, parcels and named locations
• Bookmarks provide repeatable views for areas, incidents and management zones
• Filters and definition queries create focused views from shared source layers

Participants can configure spatial analyses that support defined operational decisions.

• Buffer analysis identifies assets, populations or facilities within specified distances
• Spatial joins aggregate incidents, beneficiaries or inspections by administrative area
• Overlay methods compare land use, hazards, infrastructure and protected zones
• Suitability models combine weighted criteria using transparent scoring assumptions
• Hotspot analysis identifies statistically significant clusters using Getis-Ord Gi*
• Analysis outputs document parameters, source dates, uncertainty and interpretation limits

Participants can configure dashboards that connect spatial conditions to operational indicators.

• Dashboard requirements define decisions, users, refresh intervals and alert thresholds
• Indicators display counts, rates, targets, variance and current status
• Serial charts reveal trends, seasonality and reporting-period comparisons
• Selectors filter linked maps, charts and tables through common fields
• Spatial extent actions coordinate map views with indicator and chart selections
• Data refresh design distinguishes live feeds, scheduled updates and manual publication

Participants can specify web applications that guide users toward intended tasks.

• User stories define audience tasks, decisions, constraints and success measures
• Application patterns compare public information, operations, reporting and field coordination
• Landing pages explain purpose, data currency, contacts and appropriate use
• Mobile-first layout prioritises essential actions, controls and map content
• Form logic uses conditional visibility, defaults, required fields and validation
• Usability testing records task completion, errors, confusion points and improvements

Participants can design field data workflows that update cloud GIS records reliably.

• Field forms capture location, observations, photographs, status and timestamps
• Offline areas package basemaps and layers for disconnected mobile work
• Global IDs maintain relationships between features, attachments and inspection records
• Contingent values constrain valid attribute combinations during data capture
• Sync workflows reconcile field edits, office review and authoritative updates
• Quality assurance rules flag missing values, impossible dates and location errors

Participants can publish imagery products with suitable performance and interpretation controls.

• Image services publish orthomosaics, elevation models and multiband raster collections
• Raster functions calculate NDVI, band combinations, hillshade and classified outputs
• Mosaic rules control image ordering by date, quality and viewing geometry
• Time-enabled imagery supports change inspection across repeated acquisitions
• Resolution, resampling and compression choices affect visual interpretation and bandwidth
• Imagery metadata records acquisition date, sensor, processing level and cloud cover

Participants can configure temporal map products that communicate change and events.

• Time-aware layers store start dates, end dates and observation timestamps
• Temporal filtering isolates relevant reporting periods, incidents and project phases
• Change detection compares classified rasters, feature versions or repeated observations
• Event layers map service requests, incidents, inspections and sensor readings
• Aggregation periods standardise daily, weekly, monthly and quarterly reporting
• Animation settings communicate progression without obscuring data uncertainty

Participants can apply governance controls to protect and manage online GIS content.

• Role-based access control assigns viewer, editor, publisher and administrator permissions
• Sharing groups separate public, partner, internal and restricted content
• Data classification determines publication suitability, handling controls and retention requirements
• Least-privilege access limits editing and administration to necessary responsibilities
• Content ownership plans address staff changes, project closure and account continuity
• Governance registers record service owner, review date, dependencies and approval status

Participants can diagnose common performance issues and plan service monitoring.

• Service performance depends on geometry complexity, queries, indexes and concurrent users
• Spatial indexes accelerate extent queries, proximity searches and overlay operations
• Pagination, field selection and query limits reduce unnecessary data transfer
• Caching strategies improve basemap and tile delivery for repeated map views
• Availability monitoring tracks response time, failures, usage and storage consumption
• Incident runbooks define triage, escalation, communication and recovery actions

Participants can identify automation opportunities and specify repeatable cloud GIS processes.

• REST APIs expose items, layers, queries, users and administrative operations
• Python scripts automate validation, uploads, updates and metadata checks
• Webhook events trigger notifications from edits, submissions and status changes
• Scheduled jobs refresh datasets from approved source systems and feeds
• Configuration templates standardise layer settings, symbology and sharing permissions
• Automation logs capture execution status, exceptions, timestamps and responsible owner

Participants can plan cloud GIS delivery using measurable requirements and acceptance controls.

• Discovery workshops identify decisions, audiences, data owners and operational constraints
• Requirements matrices link user needs to layers, tools, permissions and outputs
• Data readiness assessments score quality, availability, ownership and update feasibility
• Acceptance criteria specify map behaviour, performance, accessibility and data accuracy
• Release plans sequence pilot, review, production launch and post-launch support
• Product backlogs prioritise fixes, enhancements, technical debt and user requests

Participants can assemble a structured cloud GIS solution design for a realistic case.

• Case requirements translate service problems into measurable spatial information needs
• Stakeholder maps identify data custodians, users, approvers and support responsibilities
• Logical data models define entities, relationships, identifiers and controlled vocabularies
• Publication workflows map preparation, review, approval, release and retirement stages
• Application wireframes specify screens, map tools, filters and information hierarchy
• Risk registers address privacy, quality, availability, misuse and vendor dependency

Participants can build, review and present a complete governed cloud GIS mapping product for a defined operational use case.

• Product scope defines target users, decisions, datasets, constraints and success measures
• Authoritative layers prepared with documented schemas, metadata and quality controls
• Web map configured with purposeful symbology, pop-ups, filters and bookmarks
• Dashboard or application assembled around priority user tasks and indicators
• Peer review tests usability, data interpretation, permissions and acceptance criteria
• Presentation communicates architecture, analysis results, governance controls and implementation roadmap