Processing chains with OGC Web Processing Services to process satellite data in a geoportal
Download as PPT, PDF1 like1,902 views
The document outlines a project focused on utilizing OGC Web Processing Services (WPS) for processing MODIS satellite data in a geoportal, detailing objectives, workflows, and a web-based interface for creating and managing data. It emphasizes modularity and efficiency in data management alongside the use of a CMS for monitoring and user authentication. Key features include the implementation of various MODIS product generation processes and a discussion on the challenges and potential of web-based processing workflows.
Processing chains with OGC Web Processing Services to process satellite data in a geoportal
- 1. Processing chains with OGC Web Processing Services to process satellite data in a geoportal Jonas Eberle (University of Jena) Supervisors: Dr. Christian Strobl (DLR), Prof. Dr. Christiane Schmullius (Uni Jena) FOSS4G 2011 Denver
- 3. Thematical purpose Processing workflow Download data Extract fire points L0 to L1B Create quicklooks Publish data MODIS Level-0 Near-Realtime Data archive Operational Service Webpage Geodatabase
- 4. Technical purpose OGC Web Processing Service Download data MOD14 L0 to L1B GeoTiff-Export Quicklook-Generation Publish data WPS Orchestration Engine Fireproduct Landsurface-temperature MODIS-Visualisation WebGIS Client Data search WPS client Workflow creation Visualisation
- 5. 2. Concept & Software
- 7. pyWPS for OGC Web Processing Service 2 Instances: Public processes Administration processes (secured) Data Management: Handling large data Exchange of data between processes Local processing directory (optional)
- 8. Software for process chaining 52 North Orchestration Engine Apache ODE with BPEL DIMS-WPS Orchestration Taverna Workbench Summary: no standardised way for chaining BPEL is complex simple XML-Workflow only for DIMS-WPS
- 10. Overview of developed processes & workflows Common processes m odis_download m odis_l1b m odis_l1b_crefl m odis_l1b_crefl_geotiff Individual processes m odis_mod14 m odis_lst Additional processes i nfo_points_grass c onvert_gml_to_shp Dissemination storeMODIS storeFires publishData Administration cleanUpData Workflows Fireservice Fireproduct Landsurfacetemperature Corrected reflectance
- 11. 4. Client application / WebGIS
- 13. WPS client
- 15. 5. Summary & Discussion
- 16. Summary Modular WPS based processes to derive MODIS products Automatic services as well as interactive application flow Direct interface to DIMS metadata system and data archive WebGIS based on a CMS to start and monitor processes, v isualize processed output data, add aditional content and maps, a nd assign individual user rights Web-based workflow editor based on WPS
- 17. Discussion Web-based processing High potential of web-based processing with workflows S tandards for “ simple ” process chaining are missing Efficient data management with list of available data WebGIS Using a CMS as background framework User-Authentification with security proxies
- 18. Thank you for your attention! Questions? Contact information: Jonas Eberle Friedrich-Schiller-University Institute for Geography Department Earth Observation Loebdergraben 32 07743 Jena, Germany phone: +49 3641 94 88 89 email: jonas.eberle@uni-jena.de
- 19. Visualize processed output data with GeoServer GeoServer REST API Openlayers Map Drupal CMS
- 20. Overview: MODIS software Level 0 L0.pds Level 1 L1A.hdf GEO.hdf L1B_1KM.hdf L1B_HKM.hdf L1B_QKM.hdf Level 2 MOD14.hdf MOD11.hdf MOD14.tif MOD11.tif CREFL_HKM.hdf CREFL_1KM.hdf SeaDAS-Software Science Processing Algorithm
- 21. WPS client
- 22. Creating workflows Using Drupal CMS as WPS proxy for DIMS-WPS Orchestration P roviding getCapabilities and DescribeProcess functions C hain = node I ndividual user rights
- 23. Drupal CMS Managing contents: Monitoring of started processes with HTTP Authorisation
- 24. OGC Web Processing Service Methods: getCapabilities DescribeProcess Execute Possible input and output data types: Literal Complex BoundingBox Execution synchron and asynchron Data can be transfered directly or as reference
- 25. Overview of developed processes 1. Initialization 2. Data acquisition modis_download 4. Productderivation modis_mod14 modis_lst modis_l1b_crefl init_get_defaults init_get_processdir 3. Pre-processing modis_l1b 5. Post-processing modis_l1b_crefl_geotiff modis_l1b_crefl_quicklooks convert_gml_to_shp convert_gml_to_kml info_points_grass 6. Dissemination storeModis storeFires publishData 7. Administration cleanupData dimsWPSAdmin
- 26. About me Freelance Web developer since 2000 Bachelor of Science 2004-2007 Course of studies: Applied Informatics / GIS Master of Science 2008-2011 at University of Jena Course of studies: Geoinformatics Masterthesis at German Aerospace Center, Remote Sensing Data Center, Dept. Crisisinformation and Georisks Current: Ph.D student University of Jena, Dept. Earth Observation Project: Siberian Earth System Science Cluster
Editor's Notes
- #9: 52 North OE: Exchange of process outputs to process input only with XML-internal data Not always standard-compliant Workflow-creation only with Google WebToolkit or Java sourcecode Apache ODE: Wide range of workflow possibilities (if, while, ...) Complex XML files describing workflow Yet no usable WPS framework to provide workflows as WPS DIMS: DLR-internal software Easy XML description of workflow Only Execute-Service, no getCapabilities and DescribeProcess Pause and restart workflows