Post on 15-Sep-2019
CONFIGURATION
CLIMATE DATABASE IN CROATIA Helena Lebo Andreis
Meteorological and Hydrological Service of Croatia (MHSC)
Once the data have been verified, users can view tables, charts, maps, etc. They are accessed through a web browser.
Programs generate reports on users’ demand.
Some of the products are shown below.
Monthly precipitation and maximum snow depth at station Zagreb Maksimir for year 2014
Daily maximum and minimum air temperature at station Zadar for December 2014
Main meteorological stations in Croatia on interactive map Climatological stations in Croatia on interactive map
Sea temperature at stations Krk and Rab for June 2014, at 14:00 h
Sea temperature at station Rab for June 2014, measured at 07:00, 14:00 and 21:00 h
DATA STORAGE
Responsibility Database administration, creating queries, monitoring, backing up is a responsibility of IT Department of MHSC. Tools For designing tables, creating users, privileges, etc. we use graphical tools pgAdmin and phpPgAdmin. Those features are also available in command line.
USER INTERFACE
Monthly report for air temperature at station Zagreb Maksimir for January 2014
Input form for climatological station, accessed through a web browser. Data are controlled on screen before being stored in the database.
Graphical interface of pgAdmin tool (locally installed) Graphical interface of phpPgAdmin tool (web-oriented tool )
PostgreSQL:
• free
• cross-platform
• open source
MAINTENANCE
Developers • IT Department of MHSC • programming languages and
tools: PHP, JavaScript, HTML, CSS, SQL, Google maps, ...
Users • employees of MHSC • data input, providing quality
controls, corrections, running reports, exchanging data etc.
User interface • web-oriented, in a browser • user-friendly • easy user-developer
communication
Input control • Control of users’ privileges • On-screen control of data
(“sanity check”)
Data storage
After input, data are automatically stored in two copies.
• One copy is kept unchanged (see dataset 1),
• Other copy is controlled and corrected if necessary (see dataset 2). This set of data is used for reports, etc.
Verification
Verification indicators are stored in a separate table, for later use.
DATASET 2 DATASET 1
DATA INPUT
2 copies
• KEEPING ORIGINAL DATA
• NO CORRECTIONS ALLOWED *
• USED FOR COMPARISON WITH CORRECTED DATA **
• QUALITY CONTROL
• CORRECTIONS
• VERIFICATION
• REPORTS ***
About climate database
At MHSC we have been using relational database since 2007. The climate database has been developed in IT Department of MHSC.
Technical data • Database:PostgreSQL 8.4.20 • Platform: Linux CentOS 6.4 • HTTP Server: Apache 2
10th EUMETNET Data Management Workshop - "High quality climate data - the foundation of Climate Services”, St. Gallen, Switzerland, 28th – 30th October 2015
REPORTS
* except for typing mistakes ** see poster “The influence of
subjective corrections on climate data”
*** see section “Reports”
Backup Entire database is regularly backed up on the remote location. Example of PostgreSQL command line: login