Title: prCENTR 15449 Geographic information Standards, specifications, technical reports and guidelines, re
1prCEN/TR 15449Geographic information
Standards, specifications, technical reports and
guidelines, required to implement Spatial Data
Infrastructures
- Paul C. Smits
- (Altered and elaborated by Morten Borrebæk)
- Convener CEN/TC 287 WG SDI
- Spatial Data Infrastructure Unit
- Institute for Environment and Sustainability
- European Commission Joint Research Centre
- paul.smits_at_jrc.it
2(No Transcript)
3Short about CEN/TC 287 WG5
Original terms of reference
- Check consistency of standards, and identify
existing material required to implement Spatial
Data Infrastructures, by drafting the Technical
Report Standards, specifications, technical
reports and guidelines, required to implement
Spatial Data Infrastructures - Ensure interoperability between national and
European SDI developments by drafting the
Technical Report Profiles and guidelines
related to the use of standards for the
implementation of interoperable spatial data
infrastructures - Identify what requirements are needed for
interoperability conformance testing by drafting
the Technical Report conformance testing for
interoperability of components of Spatial Data
Infrastructures
4CEN/TC 287 WG5
Original terms of reference
The organisations to be asked are e.g. The
National Mapping Agencies e.g. BKG in
Germany Regional mapping agencies e.g. 16
federal states of Germany Local organisations
National Association for Geoinformation Europea
n Commission (INSPIRE)
Survey on the use of standards in SDI-project
5CEN/TC 287 WG5
- What type of spatial data infrastructure projects
your organisation is currently involved with? - Is it on national, regional or local level?
- Which CEN/TC287, ISO/TC211, OGC and/or W3W
standards are used in that SDI project? (Please
tick in the list of standards enclosed) - Do you find a specification particularly useful
for setting up a SDI? - Are there any national standards you employ?
- Do you have specified a profile of standards for
your SDI? - What standards you think you will use in the near
future? - What standards you think are missing and should
be created soon? - What type of spatial data you are going to make
accessible with your SDI. - Any additional comments
6CEN/TC 287 WG5
Survey on the use of standards in SDI-project
7CEN/TC 287 WG5
National Standards in the field of Geographic
information
Eksempel
8Deltakere i utarbeidelse av TRen
Among others
- Alina Kmiecik Polen
- André Bernath Sveits
- Morten Borrebæk Norge
- Paul Smits Convenor (JRC)
- Anders Skog Sverige
- Stefania Crotta Italia
-
9Outline
- Scope
- Structure
- Reference Model for a SDI
- Current status (2006-05-15)
- Conclusions
10Scope
- Spatial Data Infrastructure (SDI)
- metadata, spatial data sets and spatial data
services network services and technologies
agreements on sharing, access and use and
coordination and monitoring mechanisms, processes
and procedures, established, operated or made
available in an interoperable manner. - In this context the term SDI is restricted to a
platform- and implementation-neutral
technological infrastructure for geospatial data
and services, based upon standards and
specifications.
11Scope
- This CEN Technical Report identifies the
standards, technical specifications, technical
reports and guidelines, required to implement a
Spatial Data Infrastructure (SDI) in Europe. - It gives recommendations as to whether any of
these items should become EN, and proposes a
roadmap for future work items. - It further provides recommendations for measures
to be taken in order to support implementation
and maintenance of a SDI. In so doing, the report
addresses a range of topics, including
multi-lingual aspects, consistent identification
of geographical items, conformance testing,
geographic information metadata including
catalogue service profile and guidelines, and WMS
and WFS profiles and guidelines.
12Outline
- Scope
- Structure
- Reference Model for a SDI
- Current status (2006-05-15)
- Conclusions
13Structure
- FOREWORD
- INTRODUCTION
- 1 SCOPE
- 2 CONSIDERED STANDARDISATION INITIATIVES
- 3 TERMS AND DEFINITIONS
- 4 ABBREVIATED TERMS
- 5 SPATIAL DATA INFRASTRUCTURE AS AN
IMPLEMENTATION-NEUTRAL FRAMEWORK - 6 DATA-CENTRIC VIEW ON SDI
- 7 SERVICE-CENTRIC VIEW ON SDI
- 8 REFERENCE MODEL FOR A SDI
- 9 MULTI-LINGUAL AND CULTURAL ADAPTABILITY
- 10 GEO-PORTALS
- 11 IMPLEMENTATION STEERING INSTRUMENTS
- 12 REQUIREMENTS NOT CURRENTLY COVERED BY GI
STANDARDS - ANNEX A DESCRIPTION OF REFERENCED ISO STANDARDS,
EN ISO STANDARDS, ISO PROJECTS AND OGC
SPECIFICATIONS - ANNEX B CROSS-REFERENCE OF CEN/TC 287 AND ISO/TC
211 STANDARDS AND REPORTS TO SDI TOPICS - ANNEX C OPEN GEOSPATIAL CONSORTIUM
- BIBLIOGRAPHY
14Outline
- Scope
- Structure
- Reference Model for a SDI
- Current status (2006-05-15)
- Conclusions
15Reference Model for a SDI
Applications
Geographic application area specific
standardsCEN/TC 287, ISO/TC 211, OGC, ...
Geographic infrastructure standards ISO/TC 211,
OGC
ICT-standards ISO JTC 1, W3C, IETF, OASIS, OMG
etc.
16Reference Model for a SDI
- Based on GIRM
- Geospatial Interoperability Reference Model
- What is GIRM?
- The Geospatial Interoperability Reference Model
(GIRM) references geospatial standards and
specifications within a highly structured model,
to help decision makers choose standards to
facilitate interoperable geoprocessing - Editor John Evans (NASA), Geospatial
Applications and Interoperability WG, FGDC - Internet http//gai.fgdc.gov/girm/
17Geospatial Interoperability Reference Model
Clients
User applications
Access to transformed data, pictures, maps
Service chaining
Metadata search and retrieval
Middleware
Geo-processing Services
Direct data access
Catalogs
Metadata update
Content Repositories
Servers
Features
Coverages
Other data
18Geospatial Interoperability Reference Model
- User applications
- Software seen by users
- Customized analytical or field applications
- General-purpose viewers
- Input from
- data repositories
- intermediate services
User applications
19Geospatial Interoperability Reference Model
- Geoprocessing services
- Computing facilities
- Data transformation
- Maps from raw data
- Advanced analytical functions
- Input from
- data repositories
- other geoprocessing services
- Can be cascaded into service chain
Geo-processing Services
20Geospatial Interoperability Reference Model
- Content repositories
- Geospatial data
- Features, coverages, data objects, tables
- Catalogs
- Allow clients and services to find out what
repositories are available - What services are available
- Machine-understandable
Features
Coverages
Other data
Catalogs
21Geospatial Interoperability Reference Model
- Viewpoints and levels of abstraction
Computation Viewpoint
Information Viewpoint
Service Invocation
Information Transfer
Implementation specification (how)
Interface
Encoding
Abstract models (what)
Content
Behavior
22Outline
- Scope
- Structure
- Reference Model for a SDI
- Current status (2006-05-15)
- Conclusions
23Current status (2006-05-15)
- Process
- WG draft submitted to CEN members (2006-02)
- Comments received on working draft (2006-05)
- Final text due on 2006-06-23
- In principle only editorial changes
- Comments
- DE, GB, SE
- Votes
- Wide acceptance of TR
- One abstained (ANFOR reason lack of expertise)
24Outline
- Scope
- Structure
- Reference Model for a SDI
- Current status (2006-05-15)
- Conclusions
25Conclusions
- Wide acceptance of report
- Useful comments from Member States
- Will be incorporated into a new version
- Final version to be sent to CEN Management Centre
by 2006-06-23 - Negotiation on-going with CEN Management Centre
to release the report as a publicly available
Technical Report
26Anbefalte standarder og dokumenter
- Registries
- For the realisation of SDI in Europe, it is
recommended to establish one or more registration
authorities. - A SDI needs, like any other distributed
information system, a reference frame. A
reference frame is the aggregation of the data
needed by different components of the information
systems. In a SDI context, the reference frame
concerns - the units of measures
- the coordinate reference systems
- the codelist definitions
- the feature data dictionaries (see ISO 19126)
- the feature catalogues (see ISO 19110)
- the portrayal catalogues and related symbology
registers. - Registries shall be established for the
above-listed information elements and
geographical items, and for - Cultural and linguistic adaptability of metadata
elements - European common data models
- National data which are of interest in a cross
border community or in a multilingual community.
27Anbefalinger
- Data
- The model-driven approach is promoted for ESDI.
- Unique identifiers for use in a European SDI
shall be composed of a namespace and a
Universally Unique Identifier (UUID). - ISO 19109 and referred standards are promoted as
ESDI rules for specifying data structures and
semantics. - UML class diagrams used according to ISO/TS 19103
is promoted as an ESDI conceptual schema
language. - ISO 19136 (GML) is promoted as the ESDI encoding
method when transferring geographic data. - ISO 19139 is promoted as the ESDI encoding method
when transferring information related to
geographic data such as metadata, feature
catalogues, data dictionaries,
28Anbefalinger
- Services
-
- This technical report recommends that all
services be categorized according to the ISO
19119 taxonomy. - This technical report recommends applying the
Web Service Architecture (WSA), including WSDL,
SOAP, UDDI and XML when the following issues are
considered to be important - components of information systems run on
different platforms - the system consists of components from different
vendors - the service must be published and available on
the internet - wrapping of existing services where these are
exposed as web services - make existing services available for other
applications on other platforms. - It is inappropriate to apply WSA when dealing
with large datasets.
29Anbefalinger
- Conceptual Schema Languages
- This Technical Report encourages the use of UML.
- If an information community applies a Conceptual
Schema Language other than UML, it is the
responsibility of that information community to
map the ISO general feature model to the
meta-model of the Conceptual Schema Language of
choice, and to maintain the mapping rules,
following the ISO/TS 191032005 conformance
statement - Non-UML schemas shall be considered conformant if
there is a well-defined mapping from a model in
the source language into an equivalent model in
UML and that this model in UML is conformant. - In order to provide a GML application schema, an
application schema shall be made by applying a
conceptual schema language, and the GML
application schema shall be derived from that
conceptual model, applying the rules for mapping
from UML as described in ISO 19136 in Annex E.
30Anbefalinger
- Conformance testing
- It is recommended to establish a conformance
authority charged with the conformance testing of
implementations of SDI elements in Europe. - Roadmap for new work
- It is recommended that CEN/TC 287, in
collaboration with ISO/TC 211 and OGC, start new
work on the following items - catalogue server
- XML encoding of portrayal
- quality aspects of services
- standards for registries for geographical items,
depending on the progress on ISO 19126 - Digital Rights Management
- the use of Web Services for dealing with large
datasets.