Presentation on theme: "EXPERIENCES WITH WFS-T IN THE DUERO INFORMATION SYSTEM Editing geometries and tracking changes Javier Fernández Pereira WISE TG Meeting - Madrid,"— Presentation transcript:
1 EXPERIENCES WITH WFS-T IN THE DUERO INFORMATION SYSTEM Editing geometries and tracking changes Javier Fernández Pereira WISE TG Meeting - Madrid, June 7th 2010Good morning
2 CONTENTS INTRODUCTION PROPOSED ARCHITECTURE. ALTERNATIVES SOME RESULTS Server softwareClient softwareSOME RESULTSEditingUser AuthenticationChange HistoryCONCLUSIONSFURTHER DEVELOPMENTS
3 MIRAME-IDEDuero http://www.mirame.chduero.es INTRODUCTION He puesto una secuencia de 6 pantallazos que aparecen cada segundoThe Duero Information system aims to support the development of the new RBMP. Besides, it intends to be basis for the technical work in the River Basin Authority.It is available through the linkMÍRAME-IDEDuero is a geonode within the Spatial Data Infrastructure, providing the tematic information the CHD is responsible for.It is also a tool being used for the public participation processes.
4 INTRODUCTIONBACKGROUND:Capabilities already available within the Duero Information System:Map service (WMS) :Feature service (WFS):Get capabilities service:Catalog service (CSW) :.es/geonetwork/srv/es/cswNomenclator service (WFS-G):So far the Available services are:Visualization servicesdownload servicesCalagog services andNomenclator servicesBUT… TO THE DATE, there are no editing capabilities.4
5 BUT CHANGES NOT REGISTERED INTRODUCTIONCURRENT SITUATIONALFANUMERIC DATARegistered usersEdition capabilitiesChange approval workflowChange historyGEOGRAPHIC DATAFree accessOnline edition not availableManual Workaround:BUT CHANGES NOT REGISTEREDWorkaround:Export layer, edit in desktop, insert in DBInformation System: Alphanumeric + GeographicAllows alphanumeric editingRegistered usersChange approval workflowChange historyRegarding geographic informationCan’t edit layers in DBExport layer, edit in desktop, Import layer
6 INTRODUCTIONGOALSENHANCE MIRAME IDE-DUERO SO THAT USERS CAN EDIT GEOGRAPHIC INFORMATION AS NEEDEDGUARANTEE DATA INTEGRITYUser authenticationChange approval workflowChange historyAnd OpenSource…SO,Due to the requirements to accomplish the current directives: WFD, INSPIRE and coming into force of New Directives: floods, marine strategy, priority substances) there is a need of continuos uploading of data.With this on view and in agreement with the developmento of WISE as a distributed system.The objectives for this proyect is, basically /enjéis/1. Enhance MIRAME IDE-Duero so that users can edit geographic information as needed, in the same way they edit alphanumeric data.By taking into account that it must be a service that guarantees data integrity including topological relationships between geographic features.To assure this, only authentified editors can implement changes and every change must be subject to QA/QC, when passing through the validation process.As an addional requirement for Duero, it is required the service must be implemented with OpenSource Tools, since the tool will be offered to the other River Basin Authorities.6
7 CONTENTS INTRODUCTION PROPOSED ARCHITECTURE. ALTERNATIVES SOME RESULTS Server softwareClient softwareSOME RESULTSEditingUser AuthenticationChange HistoryCONCLUSIONSFURTHER DEVELOPMENTS7
8 ARCHITECTURE Desktop WFS-T Client server ARCHITECTURE WFS-T WMS Web ViewerWMSMapServerWeb BrowserMIRAMEWeb AppSQLHTTPOracle(+Spatial)Besides the existing services...The proposed architecture includes a new service that provides the WFS-T capabilities and a client to edit the dataOthers
9 ARCHITECTURE CLIENT SERVER Desktop WFS-T Client server gvSIG Degree uDIGArcGIS ServerSERVERDegreeGeoServerWe have evaluated several alternatives both in the Client and server sides.The ones tested are:We didn´t make the test with ArcGis but compared functionalities….9
10 SERVERS - Degree Bonn University, Geography Department ARCHITECTURESERVERS - DegreeBonn University, Geography DepartmentOpenSource: GNU LPGLJ2EE technologyGood OGC support although not 100% conformity: WMS, WFS(-T), WCS, CSW, WPS, SOS…WFS well supported and testedUnfriendly installation and configurationDeveloped by…With license…Based on…Not all tehe WFS-T requests are supported.WPS: Web processing servicesSOS: Sensor observation services (monitoring networks).
11 SERVERS - GeoServer TOPP – The Open Planning Project – GeoTools ARCHITECTURESERVERS - GeoServerTOPP – The Open Planning Project – GeoToolsOpenSource: GNU LGPLJ2EE technologyGeoServer 1.3WFS-T compliant – 100% Compliant !Proposal for versioning (not standard)Easy configuration (web console)Supports many storage repositories (Oracle, PostGIS…)WFS-T atomic transactionsIncluded in theAnd it allows atomic transactions:An atomic transaction avoids any change in the database in case a transaction is interrupted. It impoves security.
12 SERVER COMPARISON SUMMARY ARCHITECTURESERVER COMPARISON SUMMARYGeoServerdeegreeCurrent Release220.127.116.11TechnologyJavaWMS supportWMS 1.1.1WFS supportWFSWFS 1.1.0WFS-T supportWFS-T 1.0.0OGC complianceGeoServer 1.3:WFS(T) (compliant)WFS (compliant)GeoServer 1.5.WCS 1.0 (compliant)deegree WMS 1.1.2WMS (compliant)deegree WMS 2.1.0:WMS (compliant)WFS-T compliance100% compliantWFS(T) 1.0.0Partially compliantVersioningOwn versioning systemNot availableAuthenticationACEGIIGeoSecurityComparing the different alternatives…The main reason for the selection of GeoServer was the availabitity of the ATOMIC TRANSACTIONS AND THE VERSIONING SYSTEM.
13 CLIENT – gvSIG Generalitat Valenciana OpenSource – GPL Large user base ARCHITECTURECLIENT – gvSIGGeneralitat ValencianaOpenSource – GPLLarge user baseWFS-T supportExperimentalUnable to make it worktested with latest stable release, 1.9 Build 1253Author of WFS-T plugin declared it non-functionalOnly read capabiliy implemented
14 CLIENT – uDig Eclipse Based desktop GIS tool OpenSource: LPGL ARCHITECTURECLIENT – uDigEclipse Based desktop GIS toolOpenSource: LPGLLess commonly used than gvSIGWFS-T supportCompliantIt works! (uDig 1.2 RC 3)
15 CLIENT – ArcGis Server 9.3 ESRI license needed ARCHITECTURECLIENT – ArcGis Server 9.3ESRI license needed“Static” management of WFS service requestWFS-T supportDirect read or with conversion from GML to geodatabaseArcMap does not have a mechanism for transactional WFS- editing.Versioning: reconcile and postArcMap does not have a mechanism for transactional WFS editing, meaning you must use a third-party client to edit features using WFS“static” management of WFS service request. WFS are automatically loaded with no choiceWFS-T is not supported at ArcGIS (even with data interoperability extension)
16 CLIENT COMPARISON SUMMARY ARCHITECTURECLIENT COMPARISON SUMMARYgvSIGuDigArcGisTested Release1.9 build 12531.2 RC39.3TechnologyJavaJava + EclipseApi FlexWFS-T supportRead onlyFullEditing capabilitiesGoodBasicEven if gvSig appears as the most promising open gis for edition of WFS it has not been possible yet to save the editions and send them to the server, only save editions developed locally, and consequently its use had to be disregarded.Regarding ArcGis, besides the license issues, it does not present edition capabilities.Finally, uDig seems to date the only open source client able to develop transactional operations and consequently it was the client implemented.
18 FEATURES - EDITING Workflow RESULTSFEATURES - EDITINGWorkflow1. In uDig user connects to WFS-T server (GeoServer)2. uDIG requests features from server using WFS-T3. User edits features locally using basic editing capabilities of uDig4. User clicks on ‘Send Changes’ button5. User types user and password6. uDig sends WFS-T requests to GeoServer7. GeoServer writes modified data in DBIn uDig the user connects to WFS-T server (GeoServer) and logs in. This user has been previously authentified in the server and has edition permissions. Currently this authentification in Geo server is perfectly integrated and synchronized with users in the MIRAME-IDEDUERO systemConnecting via the WFS to the server, the available features for edition are listed.
28 In that moment the user is required to insert a username and password
29 FEATURES – USER AUTHENTICATION RESULTSFEATURES – USER AUTHENTICATIONGeoServer uses its own authentication schemeFile-based: user.properties and service.propertiesMIRAME IDE-Duero has a proprietary authentication schemeWeb admin console to manage users and rolesNew roles defined in DB for geometry editingAgent that synchronizes MIRAME IDE-Duero users with geoserver authentication filesPasswords stored using MD5 encriptionThe file user.properties defines the usersThe file service.properties defines the role and service accessed: i.e wfs.Transaction= ROL_EDITOR_GEOSERVERAnytime the user is connected to GeoServer, the user. Properties file is automatically loaded.
30 FEATURES – CHANGE HISTORY Changes are visible till validation only through the MIRAME-IDEDuero system. Authorized user can validate changes in the system.30
31 CHANGE APPROVAL PROCESS RESULTSCHANGE APPROVAL PROCESSEDITIONFINISHEDINTERMEDIATETABLENEW LAYERPUBLIC LAYERDISCARDQC/QAPROCESSNO OKOKUser changes are not immediately applied to public layerStored in an intermediate tableValidator user needs to review and approve changesThen current version is moved to change historyNew version is written into public layerVersioning en Udig: default version (root version created by software editors) and WFS-T version created by wfs editors. Edits made to each version apply only to that version.Changes are not visible from the beginning. Once changes are sent the original layer is displayed and changes are saved in the historic of geometries.OLD LAYERHISTORIC LAYER31
33 GIS GUIDE RECOMMENDATIONS RESULTSGIS GUIDE RECOMMENDATIONSAppendix 9 – Management of IdentifiersCases specifiedNew 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).
34 GIS GUIDE RECOMMENDATIONS RESULTSGIS GUIDE RECOMMENDATIONSAppendix 9 – Management of IdentifiersCases 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).??The uncertainty is in what a SMALL/LARGE change means.En en caso de puntos sí está definido (más de 125 metros es large).In red are signed cases currently covered by MIRAME-IDEDuero implementation.Further developments will include the visualization of differences between the original version and modifications stored in the historic of geometries