GIS Data Standards and Interoperability Training Course

Participants can select, document and transform coordinate reference systems for interoperable spatial datasets.

• Coordinate reference system components: datum, ellipsoid, projection and coordinate axes
• EPSG codes used to identify coordinate reference systems consistently
• Geographic, projected and vertical coordinate reference systems compared
• Datum transformations selected using area, accuracy and source-data criteria
• Axis order and unit mismatches diagnosed in web service exchanges
• Documenting positional accuracy, epochs and transformation assumptions within metadata

Participants can explain how conceptual feature models support consistent spatial data interpretation.

• Feature types, attributes, associations and constraints defined through UML
• Object-based, field-based and network data models compared for interoperability
• Geometry types and topology rules matched to feature behaviour
• Generalisation rules preserve meaning across scales and publication products
• Feature catalogues define shared definitions, permissible values and relationships
• Separating conceptual, logical and physical models during system design

Participants can design reusable feature schemas with controlled values and persistent identifiers.

• Attribute domains restrict valid values, ranges and null conditions
• Code lists distinguish controlled, extensible and externally managed values
• Persistent identifiers support record tracking across systems and versions
• Naming conventions address feature classes, attributes, aliases and abbreviations
• UML multiplicities express mandatory relationships and cardinality constraints
• Schema versioning records additions, deprecations and backward compatibility decisions

Participants can define and assess spatial data quality using measurable criteria and thresholds.

• ISO 19157 quality elements: completeness, consistency, accuracy and temporal quality
• Positional accuracy assessed through checkpoints, error statistics and stated tolerances
• Attribute accuracy tested against domains, reference sources and verification samples
• Logical consistency checks identify topology, format and conceptual rule violations
• Completeness measures quantify missing features, attributes and required coverage
• Acceptance sampling plans set inspection rates and supplier remediation thresholds

Participants can create metadata records that support discovery, evaluation and responsible reuse.

• ISO 19115 metadata elements describe identification, extent, lineage and constraints
• Metadata profiles tailor mandatory elements to organisational sharing requirements
• Lineage statements record sources, processing steps, assumptions and limitations
• Spatial and temporal extents enable relevant catalogue search results
• Use constraints document licences, restrictions, security classifications and attribution
• Maintenance fields identify custodians, update cycles and metadata review dates

Participants can organise spatial data discovery through catalogues, registries and clear ownership records.

• Catalogue services index datasets, services, applications and supporting documentation
• Keyword vocabularies improve retrieval through preferred terms and synonyms
• Gazetteers provide authoritative geographic names, identifiers and spatial footprints
• Registers distinguish approved datasets, schemas, code lists and service endpoints
• Custodianship matrices assign ownership, stewardship and publication responsibilities
• Discovery workflows assess fitness using metadata, previews and quality statements

Participants can select exchange formats and specify controlled conversion processes for spatial data.

• GeoPackage, GeoJSON, GML and shapefile capabilities compared for exchange
• GeoTIFF, Cloud Optimized GeoTIFF and NetCDF compared for raster distribution
• Encoding constraints affect geometry, field names, domains and null values
• Conversion specifications map source fields, target fields and transformation logic
• Character encoding and decimal conventions checked before international data transfers
• Round-trip testing identifies information loss during import and export

Participants can specify and assess OGC web services for interoperable spatial data delivery.

• WMS requests deliver rendered map images using named layers
• WFS requests expose queryable vector features and attribute properties
• WMTS tile matrices support predictable cached map display performance
• WCS coverage services provide gridded data values for analysis
• Capabilities documents advertise operations, coordinate systems, formats and constraints
• Service endpoints tested with GetCapabilities, GetMap and GetFeature requests

Participants can evaluate modern API patterns for publishing discoverable and machine-readable spatial data.

• OGC API Features exposes collections, items and query parameters
• REST resource design uses stable paths, representations and HTTP methods
• JSON and JSON-FG structures support web-oriented feature exchange
• Pagination, filtering and sorting control large feature collection responses
• Content negotiation selects GeoJSON, HTML or alternate response formats
• Persistent URIs link features, code lists and external reference resources

Participants can plan interoperable spatial database structures and enterprise system connections.

• PostGIS geometry types, spatial indexes and coordinate reference constraints
• Primary keys and foreign keys preserve relationships across enterprise datasets
• Database views publish controlled subsets without duplicating source records
• ETL interfaces synchronise GIS assets with asset management systems
• Transaction models manage concurrent editing, approvals and audit trails
• Data ownership boundaries prevent conflicting updates across connected applications

Participants can document repeatable extract, transform and load processes for spatial data exchange.

• Source-to-target mapping tables document fields, rules and default values
• Extract profiles define selections, temporal cutoffs and required feature classes
• Transformation rules handle unit conversion, geometry repair and value recoding
• Load procedures establish ordering, duplicate handling and rejection records
• Exception reports classify invalid records for correction and resubmission
• Automated workflows retain logs, parameters and reproducible processing histories

Participants can create conformance tests that verify datasets and services against stated requirements.

• Conformance classes group requirements for datasets, encodings and services
• Test cases define inputs, expected results and pass-fail criteria
• Schema validation checks XML, JSON and GML against declared structures
• Topology validation detects overlaps, gaps, self-intersections and disconnected networks
• Service tests verify responses, status codes, parameters and advertised operations
• Defect registers record severity, evidence, ownership and closure decisions

Participants can integrate remote-sensing products with GIS standards, metadata and analysis-ready delivery requirements.

• Sensor metadata records platform, acquisition time, bands and processing level
• Analysis-ready data specifications define projection, tiling and radiometric requirements
• STAC catalogues describe spatiotemporal assets through searchable JSON metadata
• Raster pyramids, overviews and tile schemes support efficient image access
• NoData values, masks and quality bands communicate valid observations
• Vector-raster alignment checks pixel grids, extents and coordinate transformations

Participants can establish governance controls that sustain GIS standards beyond an initial implementation.

• Data governance roles distinguish owner, steward, custodian and consumer
• Standards registers control approved schemas, profiles and technical specifications
• Change control evaluates impact before modifying shared data structures
• Data lifecycle policies address creation, maintenance, archival and disposal
• Issue escalation paths resolve semantic disputes and recurring quality failures
• Performance indicators track completeness, timeliness, reuse and conformance rates

Participants can document access, licensing and security requirements for shared spatial data services.

• Data classification distinguishes public, restricted, confidential and sensitive spatial information
• Role-based access control assigns permissions by operational responsibility
• API keys, tokens and OAuth flows protect service access
• Open licences define reuse permissions, attribution duties and redistribution conditions
• Personal data risks assessed for location traces, addresses and movement records
• Release procedures remove sensitive attributes and apply disclosure controls

Participants can translate interoperability requirements into target architectures and supplier specifications.

• Architecture diagrams show producers, consumers, services, stores and transformation components
• Interface control documents define endpoints, payloads, authentication and error handling
• Non-functional requirements address availability, latency, throughput and retention
• Procurement specifications require deliverable schemas, metadata and acceptance testing
• Supplier handover packs include source data, transformation logs and documentation
• Decision matrices compare build, buy and platform configuration options

Participants can plan a controlled migration from inconsistent legacy data to approved standards.

• Data profiling identifies duplicate values, null patterns and structural anomalies
• Gap analysis compares legacy fields against target feature schema requirements
• Crosswalk tables map obsolete codes to approved controlled vocabularies
• Migration waves prioritise high-value datasets, dependencies and operational risk
• Parallel running verifies outputs before retiring legacy datasets and services
• Adoption plans combine training, support, governance checkpoints and communications

Participants can conduct structured reviews of operational GIS data exchanges and improvement priorities.

• Readiness assessments score standards maturity, data quality and service capability
• Architecture reviews trace requirements from business need to technical interface
• Metadata audits identify missing, outdated and inconsistent documentation elements
• Service monitoring tracks uptime, response times, errors and usage patterns
• Root-cause analysis separates source data, transformation and consumer application failures
• Improvement backlogs prioritise corrective actions by risk, value and effort

Participants can build, review and present a complete standards-based GIS data exchange implementation package.

• Define a priority exchange scenario, stakeholders and measurable business requirements
• Model feature classes, attributes, identifiers, code lists and relationships
• Prepare ISO 19115 metadata and a dataset quality statement
• Specify coordinate systems, exchange formats, transformation rules and service interfaces
• Create conformance tests, acceptance thresholds and defect management procedures
• Present governance roles, implementation milestones, risks and supplier requirements