Web-GIS portal for multi-source geographic data of Nordic Sea

1. Web-GIS portal for multi-source geographic data of Nordic Sea Name :Phalguni Pal Supervisor: Dhayalan. Velauthapillai Nansen Environmental and Remote Sensing Center

2. Outline of the talk • Introduction • Problem definition • Objectives • Software and tools • Database (ODB) • Initial work • Challanges • Discussion • Conclusion

3. Introduction • Nansen Ceneter(NERSC) : an independent non-profit research institute affiliated with the University of Bergen. • Basically work on applied environmental research.

4. Introduction 2 • This master thesis is combination of two projects running at Nansen Center called DISPRO and INTAS. • DISPRO: • European research project. • Currently running on Nansen Center. • Web-base GIS system. • Monitoring oil spills and harmful algal blooms using satellite images.

5. Indroduction3 • INTAS: • EU project running at NERSC. • Oceanographic data (OD) collected from Nordic sea. • Huge number of unorganized data. • Make a well managed ODB.

6. Problem definition • Prepare oceanographic data for a suitable & well organized way • Display the informations in the browser with user friendly manner • To avoid use of expansive GIS tools e.g. ArcExlporer,

7. Problem definition • Prepare oceanographic data for a suitable & well organized way • Display the informations in the browser with user friendly manner • To avoid use of expansive GIS tools e.g. ArcExlporer, Idealware, ArcMap etc.

8. ODB of INTAS : • Huge numbers of data collected during the period 1882-2007 from North Atlantic with the NS sub area. • Three different databases and data processing: • Initial data with chance of duplicity. • Observed and interpolated data. • Objective analyzed monthly fields data with errors estimates.

9. Data Processing:Initial data with chance of duplicity: Error estimation process: 1.Download data (more than 20 converters) from initial sources to separate databases.2.Quality control for all initial databases (9 procedures).3.Standard deviation flags.4.Interpolation at the standard levels.5.Objective analysis of the monthly fields (with kriging errors estimates). Quality-duplicate controlled, merged initial database

10. Observed and interpolated data. Objectively analyzed databases for requested grid net • Objective analyzed monthly fields data with errors estimates. Mean and anomalies fields at standard levels, in layers and on density surfaces

11. NS database content: reference period for anomalies computing

12. NS database content: countries

13. NS database content: station sources

14. Initial data for this project • Working on the selected data of 2006. • Two different source of data, PF (Profiling floats) and RV (Research Vessels). • PF is approx 2980 data and RV is approx 2404 data.

15. Station position 1.01-31.12.2006 ODB-> Profiling floats (st: 2908)

16. 1.01-31.12.2006 ODB-> Research Vessels (st: 2404) Station position

17. Objectives • An oceanographic Database (ODB). • Develop a web-based application (Web-GIS) to display all different parameters in the ODB system in a browser as a station graph, section graph or section map without using any software/tools. • The system will also display satellite images and forecasts from numerical models on the same map as ODB data.

18. What is GIS? • Geographical Information System. • GIS is a computer system for capturing, storing, checking, integrating, manipulating, analyzing and displaying data related to positions on the Earth's surface. • GIS is used for handling maps.

19. Projection of Nordic sea:

20. Selection of development methodand why? • Agile development methods • XP- eXtreme Programming

21. Selection of technoligies and why? • Database: MySQL • Other possibilities: Oracle, DB2, SQL Server, PostgreSQL • UMN Mapserver 5.x (GDAL, OGR ). • Apache Tomcat, Java. • HTML, XML. • Python. • Full package : MS4W for Windows.

22. Pictorial view of the project: Request for data(.ovf) Request Client/ Browser DB MySQL MapServer Map file Response Response data Application Server

23. DISPRO database • Tables: • STATION • P_SALINITY • P_TEMPERETURE • STATION_INFO

24. Details of table’s columns: • STATION • ABSNUM • STLAT • STLON • STDATE • STTIME • STSOURCE • STVERSION • STCOUNTRYNAME • STVESSELNAME • STDEPTHSOURCE • STLEVEL • STDEPTHGRID • STDEPTHGRIDMIN • STDEPTHGRIDMAX

25. P_SALINITY Columns: • ABSNUM • LEVEL • VALUE • FLAG

26. P_TEMPERATURE Columns: • ABSNUM • LEVEL • VALUE • FLAG

27. STATION_INFO Columns: • ABSNUM • COUNTRYCODE • VESSELCODE • STNUMINCRUISE • PROJECTCODE • INSTITUTECODE • INSTRUMENT • SOURCEUNIQUEID • SOURCEDATAORIGIN • VESSELCRUISEID

28. Relationship: ∞ P_SALINITY • LEVEL • ABSNUM • VALUE • FLAG STATION 1 • ABSNUM • STLAT • STLON • STDATE • STTIME • STSOURCE • STVERSION • STCOUNTRYNAME • STVESSELNAME • STDEPTHSOURCE • STLEVEL • STDEPTHGRID • STDEPTHGRIDMIN • STDEPTHGRIDMAX 1 1 STATION_INFO P_TEMPERATURE • ABSNUM • COUNTRYCODE • VESSELCODE • STNUMINCRUISE • PROJECTCODE • INSTITUTECODE • INSTRUMENT • SOURCEUNIQUEID • SOURCEDATAORIGIN • VESSELCRUISEID • LEVEL • ABSNUM • VALUE • FLAG ∞ ∞ 1

29. HTML request form MAPFILE REQUEST SERVICE VERSION LAYERS STYLES SRS BBOX WIDTH HEIGHT FORMAT

30. Result: position located on the map

31. Expected display on browser (Section Map):Time series length (years) for latitude-longitude grid net for salinity.

32. Challenges : • New types of work. • Work with maps. • Initial problems with software versions and tool drivers • Time consuming during upgrading softwares in server • Changing of database many times. • Changing of Platform(Linux -> Windows) • Shortage of literature and web help in this field

33. Discussion • XP method realy fits with the project • All new types of tools • Selection of database was crucial • Spatially enabled MySQL • Problems in GUI & took lots of time to fix it • Version problems & working with existing software • Started late and working just 6 months

34. Conclusion • Still have some future work. • Will have opportunity to future enhancement of the system.

35. Welcome Questions?