AQD IPR pilot study programme on e-reporting

Transcription

1 AQD IPR pilot study programme on e-reporting A quick start guide working with the e-reporting schemata Tony Bush 4 th pilot meeting Copenhagen March 2012

2 Introduction What to worry about first if you re worried about everything Data management fundamentals Tools to support extract transform and load (ETL) Simplifying the schemata Æ Identifiers Æ INSPIRE attributes and data elements Æ Naming conventions Æ Xlinks and xlinks to information that does not exist (yet) Q&A

3 Data management fundamentals Get organised! Or get you contractors organised! Store you data efficiently ü Spreadsheets ü Databases ü Link your GI data to you database information Understand roles and responsibility Ä Who s got what, where and in what format Think about your data holdings and metadata now Use the data model (and Guidance) to help structure you data holdings

4 Using the data model to help AQ zones

5 Using the data model to help measurements 1

6 Using the data model to help measurements 2

7 Transformation tools Many on offer All come with their own baggage Human (developer) There is no one size fits all solution Choice will be personal ETL Tools Dependent on database configuration Commercial Open source Some really good starting info at

8 Transformation tools essentials Should be schema aware Must work with GML on by GML version agnostic Configurable with any native database model Based on OGC and INSPIRE standards Dependent on database configuration Some really good starting info at

9 Transformation tool implementations Snowflake Software, GO Publisher suite Safe Software, FME suite Python Others.?

10 INSPIRE and GML identifiers The attribute gml:id supports a handle for the GML object Mandatory for all GML objects Must be unique in the GML document within which it occurs The attribute ef:inspireid external unique object identifier published by the responsible body, which may be used by external applications to reference the spatial object. A local identifier, assigned by the data provider. The local identifier is unique within the namespace, i.e. no other spatial object carries the same unique identifier. Namespace uniquely identifying the data source of the spatial object. e.g.

11 Feature types and spatial objects Gml:id applies to feature types data objects that have an identity and may be reasonably need to be cited or referred to Not all data objects are feature types, therefore gml:id is not universally applied to all data elements Data elements describing attributes of a feature types are known as data types Not all feature types are spatially resolved Inspire identifiers apply to spatial objects only, real world objects or conceptual objects (parcels of air) that have a position in space and time

12 Naming conventions proposals Interim file naming conventions for the pilot These are formative and open for comment Data flow deliveries should be prepared for with a 3-part notation dataflowsuffix_countrycode_generictimereference.xml Using this convention E2a_GB_ xml - relates to UTD dataflow for the 24-hour period specified B_GB_2012.xml - relates to AQ zones for the year specified

13 Naming conventions proposals XML should be human readable it helps Gml:id is important cross-schema referencing system Common nomenclature would be beneficial Across the 9 AQD feature types requiring a gml:id we propose the following interim naming system

14 Naming conventions proposals AQD feature type Has a gml:id of the construct AQD_Zone <<AQD_z>>FID of the zone AQD_Network <<AQD_n>>DEM network code AQD_Station <<AQD_s>>EOIcode AQD_SamplingPoint <<AQD_sp>>unique numeric value AQD_Process <<AQD_p>>unique numeric value AQD_featureOfInterest <<AQD_sp>>unique numeric value_foi AQD_RepresentativeArea <<AQD_sp>>unique numeric value_ra AQD_AssessmentRegime <<AQD_ar>>unique numeric value AQD_Attainment <<AQD_at>>unique numeric value

15 Interim xlink conventions Xlink components are used in GML to implement associations between data objects by reference. xlink:href in an GML document indicates find this property at this location A reference to an object element in the same GML document may be encoded as: <ef:procedure xlink:href="process_1"/> A reference to an object element in a remote XML document using the gml:id value of that object may be encoded as: <ef:procedure xlink:href= <ef:procedure xlink:href=

16 Interim xlink conventions In the pilot testing programme there will be a need for interim xlink conventions Metadata cited by xlink conventions in one data flow may not exist elsewhere (yet) e.g. within UTD data flow </om:parameter><om:observedproperty xlink:href="#pm10"/><om:featureofinterest xlink:href="samplefeature_gb0729a_sp2"/> Doesn t exist yet! So in this case you will need to refer to the gml:id and location where you expect it to be when you have finished the job

17 Technical information Good technical information at a these locations Transformation tools General INSPIRE rules and data types GML encoding standard

18 Any Questions?