Web GIS and Online Mapping Training Course

Participants can prepare and validate coordinate reference systems for reliable web map display.

• Coordinate reference systems, datums and transformations reviewed for publication
• Web Mercator limitations assessed for distance, area and thematic mapping
• Reprojecting vector layers while preserving geometry and attribute integrity
• Raster resampling methods selected for imagery and elevation products
• Axis order errors identified in service requests and API responses
• Scale-dependent visibility configured using appropriate map resolution ranges

Participants can assess source data suitability and define governance controls before web publication.

• Authoritative source identification documented for each published spatial layer
• Metadata records capture lineage, currency, licensing and usage restrictions
• Data classification separates public, internal, confidential and restricted layers
• Publication criteria check completeness, positional accuracy and attribute quality
• Retention rules defined for historical snapshots and superseded datasets
• Named data owners approve changes, access rights and release schedules

Participants can create clean, efficient vector datasets suited to browser-based mapping.

• Geometry validation finds self-intersections, duplicates, gaps and invalid polygons
• Attribute schemas simplified for display, filtering, search and downloads
• Generalisation methods reduce vertex counts while retaining meaningful shapes
• Field aliases and coded values improve readable public-facing information
• Multipart features reviewed against expected map interaction behaviour
• GeoJSON export settings tested for coordinate precision and file size

Participants can prepare imagery and raster-derived products for effective web delivery.

• Raster pyramids accelerate multi-scale display of aerial imagery
• Compression formats selected for photographs, classified rasters and transparency
• Band combinations prepared for natural colour, false colour and indices
• Cloud-optimised raster principles applied to large imagery collections
• Colour ramps designed for elevation, temperature, risk and vegetation outputs
• NoData handling prevents misleading edges and empty-value artefacts

Participants can structure spatial tables and write queries that support web map functions.

• PostGIS geometry types selected for points, lines, polygons and collections
• Spatial indexes created to improve bounding-box and proximity searches
• SQL filters retrieve features by status, date, category and jurisdiction
• ST_Intersects queries support map-window selection and overlay requests
• ST_Buffer analysis identifies assets within specified operational distances
• Database views expose controlled fields without duplicating source tables

Participants can design readable online maps that support defined user tasks.

• Visual hierarchy assigns prominence through colour, size, contrast and order
• Scale-dependent styling prevents clutter at national, regional and local scales
• Colour schemes checked for colour-vision deficiency and print interpretation
• Labels prioritised using feature rank, collision rules and zoom thresholds
• Basemap selection evaluated against operational task and thematic contrast
• Legend, attribution and uncertainty statements placed for clear interpretation

Participants can configure a functional web map prototype with structured layers and interaction rules.

• Layer groups organise basemaps, operational layers, reference data and overlays
• Initial extent and bookmark locations reflect priority user workflows
• Pop-up templates present essential attributes without overwhelming map users
• Layer visibility rules match scale, user role and task relevance
• Filtering expressions isolate current incidents, assets or service areas
• Prototype reviews test task completion with representative map users

Participants can publish and consume standard web mapping services with clear service contracts.

• WMS requests render styled map images from published layers
• WFS services deliver queryable vector features and attribute records
• WMTS tile matrices support fast display at predefined zoom levels
• GetCapabilities documents reviewed for layers, formats and coordinate systems
• Service endpoints tested using parameterised requests and response inspection
• OGC service contracts define naming, metadata, limits and availability

Participants can configure and publish controlled map and feature services using GeoServer.

• GeoServer workspaces separate projects, data stores and publication permissions
• Data stores connected to PostGIS tables and raster source files
• Layer publishing settings define bounds, coordinate systems and advertised services
• Styled Layer Descriptor rules create category, range and scale styling
• Feature type configuration controls queryable attributes and output formats
• Service logs inspected to diagnose failed requests and rendering errors

Participants can use GeoJSON and API request patterns to exchange spatial features with web applications.

• GeoJSON feature collections structured with properties, geometries and identifiers
• REST request patterns use paths, parameters, status codes and pagination
• Bounding-box parameters limit returned features to current map extent
• Attribute filters designed to reduce unnecessary data transfer
• API response validation checks coordinate order, nulls and geometry types
• Versioned endpoints protect client applications during schema changes

Participants can build an interactive browser map using Leaflet layers, controls and event handling.

• Leaflet map initialisation sets centre, zoom range and base layers
• Tile layers added with attribution, opacity and zoom constraints
• GeoJSON layers styled from feature attributes and classification rules
• Click events open pop-ups with formatted feature information
• Layer controls switch thematic overlays and alternative basemaps
• Marker clustering manages dense point datasets at small map scales

Participants can design map interactions that help users find, interpret and act on location information.

• Search fields support place names, asset identifiers and addresses
• Facet filters combine category, status, date and administrative area
• Geocoding results checked for ambiguity, confidence and result ranking
• URL parameters preserve map extent, selected layers and active filters
• Progress indicators explain slow queries, loading tiles and failed requests
• Keyboard interaction and screen-reader labels support accessible map controls

Participants can select and implement suitable spatial analysis methods for online map applications.

• Point-in-polygon queries assign locations to service or risk zones
• Proximity searches identify assets within configured travel or buffer distances
• Server-side analysis protects sensitive datasets and reduces browser workload
• Client-side filtering supports immediate interaction with modest feature volumes
• Precomputed indicators accelerate recurring summaries and thematic displays
• Analysis results presented with method notes, dates and source references

Participants can diagnose web map performance and apply appropriate optimisation methods.

• Network inspection identifies slow requests, oversized responses and failed tiles
• Vector simplification reduces payload size without obscuring operational patterns
• Tile caching pre-generates frequently requested map images and zoom levels
• Spatial index plans examined for slow database query behaviour
• Lazy loading delays nonessential layers until users request them
• Performance thresholds defined for initial load, pan, search and filtering

Participants can define proportionate security and privacy controls for published spatial information.

• Role-based access control separates viewers, editors, publishers and administrators
• Authentication methods compared for internal users, partners and public visitors
• Sensitive locations masked, aggregated or withheld before external publication
• Transport Layer Security protects credentials and service requests in transit
• Cross-origin resource sharing rules configured for approved web clients
• Audit logs record access, edits, service failures and configuration changes

Participants can plan a controlled release of a web GIS application into operational use.

• Development, test and production environments separated for controlled releases
• Release checklists cover services, styles, permissions, links and documentation
• Domain names and HTTPS certificates configured before public launch
• Rollback procedures preserve previous application versions and service settings
• Browser compatibility tests cover desktop, tablet and mobile devices
• Operational handover assigns ownership, support contacts and incident procedures

Participants can establish maintenance routines that keep web GIS data and services dependable.

• Update schedules align source data refreshes with publication windows
• Automated validation checks geometry, mandatory fields and coded values
• Service monitoring tracks availability, response times and error rates
• Usage analytics identify popular layers, searches and abandoned interactions
• Change logs record dataset revisions, styling amendments and service updates
• Support triage separates data defects, application faults and user requests

Participants can define a web GIS delivery plan with measurable quality and acceptance criteria.

• User stories define map tasks, users, constraints and acceptance criteria
• Data inventory identifies authoritative sources, gaps, owners and refresh cycles
• Architecture decision records document alternatives, rationale and consequences
• Risk registers address privacy, availability, data quality and supplier dependencies
• Test cases cover functional, spatial, usability, security and performance requirements
• Acceptance reviews compare delivered functions against agreed service specifications

Participants can build, review and present a complete web GIS application comprising prepared data, published services, an interactive map and an operational release plan.

• Problem statement defines users, decisions, map tasks and success measures
• Prepared datasets documented with metadata, schemas, projections and quality checks
• Published services configured with styles, permissions and tested endpoints
• Interactive Leaflet map implements layers, search, filters and pop-up information
• Peer review applies usability, performance, security and governance criteria
• Final presentation explains architecture, design choices, limitations and release actions