1 / 13

Geodata to Geoservices Design Issues for GI Infrastructures

Geodata to Geoservices Design Issues for GI Infrastructures. Josef Strobl Universität Salzburg Austrian Umbrella Organisation for Geographic Information - AGEO. Data etc. Data etc. Look at the complete picture …. GI infrastructures are not ‚just‘ a technical or organisational or

jin
Download Presentation

Geodata to Geoservices Design Issues for GI Infrastructures

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Geodata to GeoservicesDesign Issues for GI Infrastructures Josef Strobl Universität Salzburg Austrian Umbrella Organisation for Geographic Information - AGEO

  2. Data etc Data etc Look at the complete picture … GI infrastructures are not ‚just‘ a • technical or • organisational or • business or • conceptual or • people … problem, but all of these and then some! • 10 Building Blocks for SDI‘s!

  3. Standards • … of course, that‘s why we there are many of them  • OGC • ISO • CEN • national and industry standards 1

  4. Interoperability • Based on (technical) connectivity • Implemented as (web) services • Concepts, Architectures, Standards • Languages like GML • ORGANISATIONAL and PEOPLE interop.!! 2

  5. Business Model • Web Services require a distributed, ‚incremental‘ business model based on • Value Added per service • Differential pricing schemes result, depending on different value added • From Value Chain to Value Web! 3

  6. Service Level • Different levels of • Quality / Completeness / Scale • Currentness • Availability • Performance / Throughput • Emergency Services Access 4

  7. Workflow / process models • GII‘s cannot well be defined as collections, but rather as requirements from workflow analysis • „Same“ item in different workflows can have very different requirements – more than one model (or view) of an aspect of reality! • Organisationally and socially integrated! 5

  8. Metadata • Describing suitability, fitness-for-use • Search domain for catalog services • Profiles are still a research topic! • Further, ongoing development needed … 6 File Format File Format Data

  9. ‚Active Catalog‘ Services • From centralized to distributed cataloging • Catalog interoperability – independence from entry point into search space • Search engines with ‚centrifugal‘ sorting 7

  10. geo - Integration • Instead of separate geodata, we want to enable ‚geo-views‘ onto „all“ data • no ‚geodata‘, but ‚geospatially enabled data sets‘ or ‚…services‘ • Geo-IT as an integral part of IT! 8

  11. Integrated LBS • LBS components as part of many devices (clients) and services, automatically generating position-focused responses • geoCommunication – generating ad-hoc communities 9

  12. ‚real world‘ Geoinformation • … as opposed to stored representations, data models. • position encoding in facility infrastructure elements like stations, switches … • ‚Live GIS‘ – operating directly on critical infrastructure! 10

  13. „Thinking Spatially“ • Awareness • Education • Practice

More Related