OGC Web Services Phase 8

Slide: 1 2 3 4 5 6 7 8 9 10 11

Bulk Geodata Transfer (BGT) & Geosynchronization (GeoSync)

Thread Architects:
Michael Maynard, Jennifer Harne
Lockheed Martin

Past OGC initiatives devised the Geosynchronization specification, which is approaching final standards status. Testing in a variety of situations has identified the need to prototype synchronization mechanisms involving subsets of the full data set as a critical use case. Transfers under conditions of little or no network connectivity are an important requirement.

These are the main task areas:

Bulk Geodata Transfer: The ability to distribute individual data sets and/or collections of data sets in a consistent manner offline and over networks.
Geosynchronization: Web services and client components to support synchronization and updates of geospatial data across a hierarchical Spatial Data Infrastructure (SDI). OWS-8 enhances the work from OWS-7 to streamline validation scenarios, bootstrap database creation and population, and define query-based subscription mechanisms.

Click right sidebar to continue...

Slide: 1 2 3 4 5 6 7 8 9 10 11

OWS-8 Geosync Team

Slide: 1 2 3 4 5 6 7 8 9 10 11

Geosync Objectives

GeoSync is comprised of 2 subthreads. The GSS/GML/WFS Subthread focuses on data, schema, query and mobile client enhancements. You will get more in depth information about this subthread through demos from CarbonProject, CubeWerx, OpenGeo and GIS.FCU. The FileGeodatabase API subthread focuses on bulk data transfer which Esri and OpenGeo will discuss during their demonstrations.

Sub-threads
- - FileGeodatabase API Sub-thread- The API Approach
  - Showing the transfer of base data from headquarters to the field operations airport. Field Ops will edit and return updated data.
  - Participants: Esri, OpenGeo.
  - Goals: Accurate and consistent round-trip transfer of “bulk data” FileGeodatabase, utilizing the ESRI FileGeoDatabase API.
- - GSS/GML/WFS Sub-thread- The Encoding Approach
  - Showing bulk transfer of base data using the WFS and GML approach, and will provide the data to Mobile/disadvantaged clients. Geosync will be used to publish and review edits and support temporal queries.
  - Participants: The CarbonProject, CubeWerx, OpenGeo, GIS.FCU.
  - Goals: Data & Schema initialization, GSS Enhancements, Mobile Clients, Tempo-spatial queries of GSS, efficient "Geodata Bulk Transfer" (GBT) mechanism.

Slide: 1 2 3 4 5 6 7 8 9 10 11

Geosync Reports and Components

This is a list of the deliverables for the GeoSync thread. These Engineering Reports (ER) and Change Requests (CR) are publicly available, see the Deliverables Page on this website. Most component deliverables are prototypes and may not be available for commercial use. These will all be maintained for at least a few months after the testbed. Contact the relevant participant organization or OGC staff if questions.

Geodata Bulk Data Transfer
- - Documents:
  - ER 11-085: Geodata Bulk Transfer format (CubeWerx).
  - ER 11-114: FileGDB Engineering Report (Esri / OpenGeo).
  - ER 11-087: WFS 2.0 Change Proposal from OWS-8 Add CreateSchema and DropFeature Type operations. (CarbonProject).
- - Components:
  - Bulk Data Transfer Export Component (Esri / OpenGeo/ CubeWerx).
  - Bulk Data Transfer Import Component (CarbonProject / CubeWerx).
  - Prototype Sample Bulk Geodata set.
Geosynchronization
- - Documents:
  - ER 11-125: Best Practices for use of Geosynchronization (CubeWerx).
- - Components:
  - WFS 2.0 Service (CubeWerx).
  - Export & Import Utility + a client app to demonstrate both elements of the GBT flow (CubeWerx).
  - Geosynchronization Server (GSS) for Time Sliced & Time Stamped Data (GIS.FCU/OpenGeo)
  - Geosynchronization Client (CarbonProject).
  - Mobile handheld editing client (CarbonProject).

Slide: 1 2 3 4 5 6 7 8 9 10 11

Ideas for Next Steps

Here are some ideas for next steps, for any questions details or additional information please see the GeoSync Thread participants.

FileGeodatabase API Sub-thread
- - FGDB improvements in the API:
  1. * Compressed FGDB files *
    The API doesn't currently allow accessing files that use FGDB's own compression schemes.
  2. * Precision Enforcement should be Optional *
    If FGDB is going to be a workable interchange format between multiple systems it needs to be able to turn off the precision enforcement.
- - Investigate the use of ISO and NMF metadata, checksum, and topology rules in FGDB.
- - Some features in the OGR model that are not implemented in the driver (DeleteField, DeleteFeature, ReorderFields, SetFeature, for example).
- - Full support will allow open source desktop tools like QGIS to more fully use FGDB data files.
GSS/GML/WFS Sub-thread
- - Deploy and demonstrate a GBT network using different servers at different operational levels.
- - A lot of OGC/NGA data is very schema intensive, thought required on mobile GML versions.
- - Test GBT with non-feature data types that GML can handle; for example, coverage dynamic features, observations & measurements.

Slide: 1 2 3 4 5 6 7 8 9 10 11

OWS-8 Geosync Demonstrations

GIS.FCU: oil spill response
- Jo-Yu Liu (Katt)
Esri, OpenGeo: API Approach for bulk data transfer
- FileGeodatabase API Sub-thread
  - Dave Danko , Lance Shipman (Esri)
  - Paul Ramsey, Chris Holmes (OpenGeo)
CubeWerx, Carbon Project, OpenGeo: GML/WFS encoding approach for bulk transfer, with Geosynchronization illustrating schema & data initialization
- GSS/GML/WFS Sub-thread
  - Jeff Harrison (CarbonProject)
  - Peter Vretanos (CubeWerx)
  - Gabriel Roldan (OpenGeo)

Slide: 1 2 3 4 5 6 7 8 9 10 11

Oil Spill Response Scenario

Slide: 1 2 3 4 5 6 7 8 9 10 11

Bulk GeoData Transfer – API Approach

This is a high level overview of the Bulk data transfer process. It shows the steps and flow on how the FGDB API can be accessed by anyone to open, read, and write data. The next three demos illustrate this process in a round-trip example.