experiences with wfs-t in the duero information system editing geometries and tracking changes...

EXPERIENCES WITH WFS-T IN THE DUERO INFORMATION SYSTEM

Editing geometries and tracking changes

Javier Fernández Pereira

WISE TG Meeting - Madrid, June 7th 2010

MÍRAME-IDEDuero / WFS-T Editing

CONTENTS INTRODUCTIONINTRODUCTION

PROPOSED ARCHITECTURE. ALTERNATIVES• Server software

• Client software

SOME RESULTS• Editing

• User Authentication

• Change History

CONCLUSIONS

FURTHER DEVELOPMENTS


MIRAME-IDEDuero

http://www.mirame.chduero.es

INTRODUCTION


Capabilities already available within the Duero Information System:

• Map service (WMS) :

http://www.mirame.chduero.es/DMADuero_09_Viewer

• Feature service (WFS):

http://www.mirame.chduero.es/duerowfd

• Get capabilities service:

http://www.mirame.chduero.es/geonetwork/srv/es/csw?service=CSW&request=GetCapabilities&version=2.0.2

• Catalog service (CSW) :

http://www.mirame.chduero .es/geonetwork/srv/es/csw

• Nomenclator service (WFS-G):

http://www.mirame.chduero.es/dueroGazetteer

BACKGROUND:

INTRODUCTION


CURRENT SITUATION

INTRODUCTION

ALFANUMERIC DATA

Registered users

Edition capabilities

Change approval workflow

Change history

GEOGRAPHIC DATA

Free access

Online edition not available

Manual Workaround:

BUT CHANGES NOT REGISTERED


GOALS

ENHANCE MIRAME IDE-DUERO SO THAT USERS CAN EDIT GEOGRAPHIC INFORMATION AS NEEDED

GUARANTEE DATA INTEGRITY

• User authentication

• Change approval workflow

• Change history

And OpenSource…

INTRODUCTION


CONTENTS

INTRODUCTION

PROPOSED ARCHITECTURE. ALTERNATIVES• Server software

• Client software

SOME RESULTS• Editing


• Change History

CONCLUSIONS



ARCHITECTURE

Web Browser

Oracle(+Spatial)

MIRAMEWeb App

Web Viewer MapServer

DesktopClient

WFS-T server

WFS-T

WMS

HTTP

SQL

ARCHITECTURE

Others


ARCHITECTURE

DesktopClient

WFS-T server

WFS-T

ARCHITECTURE

CLIENT

• gvSIG

• uDIG

• ArcGIS Server

SERVER

• Degree

• GeoServer


SERVERS - Degree

Bonn University, Geography Department

OpenSource: GNU LPGL

J2EE technology

Good OGC support although not 100% conformity: WMS, WFS(-T), WCS, CSW, WPS, SOS…

WFS 1.1.0 well supported and tested

Unfriendly installation and configuration

ARCHITECTURE


SERVERS - GeoServer

TOPP – The Open Planning Project – GeoTools

OpenSource: GNU LGPL

J2EE technology

GeoServer 1.3

• WFS-T 1.0.0 compliant – 100% Compliant !

• Proposal for versioning (not standard)

Easy configuration (web console)

Supports many storage repositories (Oracle, PostGIS…)

WFS-T atomic transactions

ARCHITECTURE


SERVER COMPARISON SUMMARYGeoServer deegree

Current Release 2.0.1 2.3

Technology Java Java

WMS support WMS 1.1.1 WMS 1.1.1

WFS support WFS 1.1 .0 WFS 1.1.0

WFS-T support WFS-T 1.0.0 WFS-T 1.0.0

OGC compliance GeoServer 1.3:WFS(T) 1.0.0 (compliant)

WFS 1.0.0 (compliant)GeoServer 1.5.

WCS 1.0 (compliant)

deegree WMS 1.1.2 WMS 1.1.1 (compliant)

deegree WMS 2.1.0:WMS 1.1.1 (compliant)WMS 1.3.0 (compliant)

WFS-T compliance

100% compliantWFS(T) 1.0.0

Partially compliant

Versioning Own versioning system Not available

Authentication ACEGI IGeoSecurity

ARCHITECTURE


CLIENT – gvSIG

Generalitat Valenciana

OpenSource – GPL

Large user base

WFS-T support

• Experimental

• Unable to make it work

• tested with latest stable release, 1.9 Build 1253

• Author of WFS-T plugin declared it non-functional

• Only read capabiliy implemented

ARCHITECTURE


CLIENT – uDig

Eclipse Based desktop GIS tool

OpenSource: LPGL

Less commonly used than gvSIG

WFS-T support

• Compliant

• It works! (uDig 1.2 RC 3)

ARCHITECTURE


CLIENT – ArcGis Server 9.3

ESRI license needed

“Static” management of WFS service request

WFS-T support

• Direct read or with conversion from GML to geodatabase

• ArcMap does not have a mechanism for transactional WFS- editing.

• Versioning: reconcile and post

ARCHITECTURE


CLIENT COMPARISON SUMMARY

gvSIG uDig ArcGis

Tested Release

1.9 build 1253 1.2 RC3 9.3

Technology Java Java + Eclipse Api Flex

WFS-T support

Read only Full Read only

Editing capabilit

ies

Good Basic Good

ARCHITECTURE


CONTENTS

INTRODUCTION

PROPOSED ARCHITECTURE. ALTERNATIVES

• Server software

• Client software

SOME RESULTS

• Editing


• Change History

CONCLUSIONS



FEATURES - EDITING

Workflow

• 1. In uDig user connects to WFS-T server (GeoServer)

• 2. uDIG requests features from server using WFS-T

• 3. User edits features locally using basic editing capabilities of uDig

• 4. User clicks on ‘Send Changes’ button

• 5. User types user and password

• 6. uDig sends WFS-T requests to GeoServer

• 7. GeoServer writes modified data in DB

RESULTS


Prototype


FEATURES – USER AUTHENTICATION

GeoServer uses its own authentication scheme

• File-based: user.properties and service.properties

MIRAME IDE-Duero has a proprietary authentication scheme

• Web admin console to manage users and roles

• New roles defined in DB for geometry editing

Agent that synchronizes MIRAME IDE-Duero users with geoserver authentication files

• Passwords stored using MD5 encription

RESULTS


FEATURES – CHANGE HISTORY


CHANGE APPROVAL PROCESS

RESULTS

EDITION FINISHED

QC/QA PROCESS

NEW LAYER

DISCARD

OLD LAYERHISTORIC LAYER

PUBLIC LAYER

INTERMEDIATE TABLE

OKNO OK


CHANGE HISTORY

Supports feature changes

• Points

• Lines

• Polygons

Follows GIS Guide Recommendations

• Predecesor reference

Limitations

• Doesn’t support complex operations (split, merge)

RESULTS

OLD LAYERHISTORIC LAYER


GIS GUIDE RECOMMENDATIONS Appendix 9 – Management of

Identifiers Cases specified

• New object (ID11);

• Object deleted (ID5);

• Split (ID4 into ID8 and ID9);

• Merge (ID3 and ID2 to ID7);

• Geometry change; possible cases:

• ID remains the same; small change (change of geometry only) (ID1);

• Large geometry change – new (ID6 to ID10).

RESULTS


GIS GUIDE RECOMMENDATIONS Appendix 9 – Management of

Identifiers

Cases covered by MIRAME IDE-Duero implementation:

• New object (ID11);

• Object deleted (ID5);

• Split (ID4 into ID8 and ID9);

• Merge (ID3 and ID2 to ID7);

• Geometry change; possible cases:

• ID remains the same; small change (change of geometry only) (ID1);

• Large geometry change – new (ID6 to ID10).

?

?

RESULTS


CONTENTS

INTRODUCTION


• Server software

• Client software

SOME RESULTS

• Editing


• Change History

CONCLUSIONS



CONCLUSIONS Server Component

• GeoServer – good choice

Client Component• gvSIG

• currently not feasible (no WFS-T support)

• uDIG• basic editing capabilities

• WFS-T supported

Integration• User Authentication - EASY

• Change History - CHALLENGING

CONCLUSIONS


CONTENTS

INTRODUCTION


• Server software

• Client software

SOME RESULTS

• Editing


• Change History

CONCLUSIONS




Implement the rest of cases for management of identifiers

Visualization of differences between original and edited version.


THANKS FOR YOUR ATTENTION

experiences with wfs-t in the duero information system editing geometries and tracking changes...

Documents

wfst supportwfst

wfst requests

wfst server geoserver

transactional wfs editing

compliant wfst compliance

wfs supportwfs

author of wfs

sos wfs