session - EC GI & GIS Portal

More documents

Recommendations

Info

SESSION SDI TECHNOLOGY API developed are Javascript libraries, allowing to add WMS-generated maps into third-party developed portals. API can be easily configured and integrated into the organisation SDI: they just require maps to be served by WMS services, and client browsers interpreting Javascript in accordance to ECMAScript specifications11. API offer interface methods to serve maps (with/without overview) and navigation tools (ToC, toolbar, …). Like Google Maps (and others), caching techniques are extensively used to better perform map interactions, and to increase usability. AJAX technique12 is also used to perform feature/objects selections through Web Service / EJB server-side components; AJAX also allows to provide many challenges in adhering to WAI accessibility guidelines, as also remarked into the recent CEN/TC287 prTR 15449 “Standard, specifications, technical reports and guidelines, required to implement Spatial Data Infrastructure”13 (chapter 10 – GeoPortals). Information requested (GetFeatureInfo) are provided in XML format, and through XSL transformation HTML page is generated and integrated into a DIV 14 element. Conclusions Efforts have been focused on the possibility to implement Google-like API solutions within the SDI framework, so that to interface API to data managed by the organisation providing WMS services. In this way organisations developing SDIs are able to made their own data through WMS services, using XML format for the GetFeatureInfo response; geodata can be then accessed via simple API available to GIunskilled programmers, and completely configurable within complex geoportals and/or simple web pages. 9 Regione Emilia-Romagna and Regione Autonoma della Sardegna 10 Content Management System – see at http://en.wikipedia.org/wiki/Content_management_system 11 European Computer Manufacturers Association (ECMA) - ECMA-62 specification (http://en.wikipedia.org/wiki/ECMAScript) 12 Asynchronous JavaScript And XML (AJAX) – see at http://en.wikipedia.org/wiki/Ajax_%28programming%29 13 CEN prTR15449 (ballot for vote document), pag. 54 - http://www2.nen.nl/cmsprod/groups/public/documents/bestand/218397.ppt 14 http://www.html-reference.com/DIV.htm 44
SESSION SDI TECHNOLOGY CSCAT: Catalogue of Coordinate Reference System Definition and Translation Web Service M.A. Manso, M.A. Bernabé Department of Topography and Cartographic Engineering Universidad Politécncia de Madrid (UPM) Campus Sur, Carretera de Valencia, km 7. 28031- Madrid (Spain) m.manso@upm.es, ma.bernabe@upm.es This paper presents a Web Service (WS) prototype implementation of CSCAT acting as Coordinate Reference System (CRS) catalogue and code space translation system for CRS, datum, ellipsoid and projection definitions. The main task of this catalogue is to interpret and dynamically parsing (translating) the private code space types used by the software manufacturers (Esri, Intergraph, MapInfo, Autodesk, Oracle, IBM, Erdas, et) to standardized code space (i.e. EPSG), Well Known Text (WKT) format definitions, ISO 19115 XML schemas or GML CRS XML schema. This WS prototype implements and expands the WS design proposal presented in GISPLANET 2005 Conference by the same author. The problem is presented first and an original solution proposed. Finally the current solution model and functional prototype is described and shown. Presentation of the Problem A previous analysis of the geographic information storage formats was carried out and the conclusion reached was the need of CRS homogenization. Two problems were detected in this research: � different ways of conveying that information: WKT format text, alphanumeric mnemonics or integer numbers. � every data format innately uses a different form to express that information: After careful examination of data format, two pseudo-standardized forms were located to represent that information. The first one is in text form, Well Known Text Format and the second one is in EPSG numerical encoding form. Text code space encoding, either WKT or mnemonics, are legible and understandable by human users, allowing to infer that two definitions are equal, equivalent or different. Next examples of these types of encoding are shown � WKT: DATUM ["Israel", SPHEROID["GRS 1980", 6378137, 298.257222101] Mnemonics: GCS_European_1950. � Numerical encoding makes human interpretation difficult, though it facilitates its automated use based on programmes. Next some examples by the same CRS are shown: � Erdas’s encoding: Projection: 1 Datum: European 1950 Ellipsoid: 5 � Intergraph’s encoding: Projection: 7 Datum: 4 Ellipsoid: 5 The interoperability of data and services in the context of SDI intend to be capable of being automatically used with the least human intervention. Next a few significant samples are presented showing the interoperability problems in the interpretation of CRS from different sources. CRS representations in WKT format: DB2 & Esri ECW MapInfo & Oracle PostG iS GCS_European_1950 European_datum_1950 Longitude /latitude (ED50) GCS_North_American_1 927 North_American_1927 Longitude /latitude (NAD27) 45 ED50 NAD 27
Page 1 and 2: The mission of the JRC is to provid
Page 3 and 4: Table of Contents MISSION STATEMENT
Page 5 and 6: SESSION NATIONAL SDI II Table of Co
Page 7 and 8: SESSION SDI INSPIRE from the Nation
Page 9 and 10: SESSION SDI The Spirit of INSPIRE l
Page 11 and 12: SESSION SDI Will INSPIRE come up to
Page 13 and 14: SESSION SDI Framing the evolution o
Page 15 and 16: SESSION PEER GROUP The Importance o
Page 17 and 18: SESSION PEER GROUP Setting up a GI
Page 19 and 20: SESSION PEER GROUP Landscape Charac
Page 21 and 22: SESSION PEER GROUP Contaminated Env
Page 23 and 24: SESSION NATIONAL SDI development of
Page 25 and 26: - Political level - Conceptional le
Page 27 and 28: SESSION NATIONAL SDI The Spanish SD
Page 29 and 30: SESSION NATIONAL SDI Strengths and
Page 31 and 32: SESSION METADATA AND CATALOGUES Nea
Page 33 and 34: SESSION METADATA AND CATALOGUES Sta
Page 35 and 36: SESSION METADATA AND CATALOGUES STY
Page 37 and 38: SESSION METADATA AND CATALOGUES be
Page 39 and 40: SESSION: NATIONAL SDI II of Turku m
Page 41 and 42: SESSION: NATIONAL SDI II public sec
Page 43 and 44: SESSION: NATIONAL SDI II in August
Page 45 and 46: SESSION: NATIONAL SDI II available,
Page 47 and 48: SESSION: NATIONAL SDI II forest emp
Page 49: SESSION SDI TECHNOLOGY “Where wou
Page 53 and 54: SESSION SDI TECHNOLOGY The role of
Page 55 and 56: SESSION SDI TECHNOLOGY Therefore in
Page 57 and 58: SESSION SDI TECHNOLOGY Figure 2. Ge
Page 59 and 60: SESSION NATIONAL / REGIONAL SDI OUT
Page 61 and 62: SESSION NATIONAL / REGIONAL SDI DEV
Page 63 and 64: SESSION NATIONAL / REGIONAL SDI REA
Page 65 and 66: SESSION NATIONAL / REGIONAL SDI EU-
Page 67 and 68: SESSION NATIONAL / REGIONAL SDI Geo
Page 69 and 70: SESSION: DATA HARMONISATION is to d
Page 71 and 72: SESSION: DATA HARMONISATION A New P
Page 73 and 74: SESSION: DATA HARMONISATION Figure
Page 75 and 76: SESSION: DATA HARMONISATION The GML
Page 77 and 78: SESSION: DATA HARMONISATION (CSML)
Page 79 and 80: SESSION: DATA HARMONISATION Data ce
Page 81 and 82: SESSION: DATA HARMONISATION Figure
Page 83 and 84: SESSION: DATA HARMONISATION Step by
Page 85 and 86: SESSION: NATIONAL / REGIONAL SDI II
Page 93 and 94: SESSION SDI IMPACTS A Roaming-enabl
Page 95 and 96: SESSION SDI IMPACTS Transparency of
Page 97 and 98: SESSION SDI IMPACTS Pricing models
Page 99 and 100: SESSION SDI IMPACTS CC has develope
Page 101 and 102:
SESSION SDI IMPACTS improve the tra
Page 103 and 104:
SESSION SDI IMPACTS MOTIIVE Experie
Page 105 and 106:
SESSION SDI IMPACTS identify the fu
Page 107 and 108:
The adopted Standards. SESSION REGI
Page 109 and 110:
SESSION REGIONAL SDI How Municipali
Page 111 and 112:
SESSION REGIONAL SDI Metadata about
Page 113 and 114:
SESSION: DATA SHARING Eliminating O
Page 115 and 116:
SESSION: DATA SHARING the maker of
Page 117 and 118:
SESSION: DATA SHARING Tools of the
Page 119 and 120:
SESSION: DATA SHARING Availability
Page 121:
European Commission EUR 22318 DG Jo
show all

session - EC GI & GIS Portal

Create successful ePaper yourself

Delete template?

Save as template?