Med-Hycos - the Software Tools
MED-HYCOS - USER MANUAL
The products included in this programme are designed to manage hydrological data stored in a local database, to visualise and import data from the remote Oracle server of the Med-Hycos site and also to retrieve data measured from the network of Data Collecting Platforms (DCP) of the Med-Hycos project.
The main purpose is to give to the users several products of simple use, which cover the works of hydrologists from national services included in the Med-Hycos project related to the DCP station data, the management of the hydrological database and the connection to the Med-Hycos site.
So this product is not created to replace highly developed products with a more limited field of use, but to satisfy the general needs of computer programs for a specified user. With this product you don't have the power of graphic oriented products for graphics or the power of pure data management tools. But you do have a collection of functions that include graphic representation, a spreadsheet, database management of the interface between the two databases ACCESS and Oracle, and the connection to the Med-Hycos project web site in Montpellier as well as the Eumetsat satellite collecting site in Darmstadt (which collects data from Med-Hycos DCPs)
As the product is PC oriented, all the needs can be used with a PC with more than 8MB of RAM, at least 100MB of free space on the hard disc, a printer, screen with more than 600*400 pixels resolution and an Internet connection.
This product uses the Windows’95 environment and can be installed under all latest versions, Windows NT included.
As the database is given with the program, it is not required to have ACCESS (which is a part of Microsoft Office). However if the user wants to see the database directly he will need an ACCESS’97 installation.
As an exclusive feature for remote Oracle users, this product includes ne Oracle product: SQL*Net version 2.3.4. It maintains the interface between the TCP/IP network (Intra Net and Internet) and Oracle access modules.
It is not necessary to install ODBC drivers for Oracle or ACCESS before using Data Manager & Retriever, but ODBC is needed for the use of ACCESS database from the cartographic application – MedMap.
The installation package contains 15 files: the program setup.exe ; the list of installed files: setup.lst; 13 compressed CAB files and a compressed file which contains the products needed for the connection with the remote Oracle database: oo4o805.exe.
The program installation has to be made with à common set-up program, started by the setup.exe.
In the case where the set-up program asks for a new Windows start-up or the change of existing files, you should continue the installation and if possible to keep the newest files.
It is not advised to change
the working directory while the set-up is executing. In the general case
the program use the same database folder as the MedMap program. This folder
has to be in ‘Program Files’ folder and uses the name ‘Med-hycos’.
If you need to access hydrological data from the remote Oracle server of Med-Hycos pilot regional centre, you will need an Internet connection by line or a modem. In this case you have to install SQL*Net.
First you have to extract on the hard disc the contents of the compressed file oo4o805.exe which is given to provide the connection with the remote Oracle database only to registered users without redistribution rights
From the directory where
this file is unzipped choose the directory win32/install and run the Setup.exe
program. From the option list install SQL*Net 2.3.4.
1.1. In the first window choose: " Add database alias ". In the blank field enter " world ".
1.2. For the protocol choose " TCP/IP ".
1.3. For the host name enter the name of the web server of Med-Hycos project "medhycos.mpl.ird.fr" or the substituted name from the file "hosts" given with the installation of Data Manager & Retriever.
1.4. In the field "data base instance" enter "HMD". Save the configuration and exit the menu.
After the new start-up of Windows you can test the connection with the remote database.
2. What tests to make?
2.1. The first test checks the TCP/IP connection: from à DOS screen run the command line "pingmedhycos.mpl.ird.fr". If the remote computer answers, you have the TCP/IP connection. If not, check if the "hosts" file (Windows directory) contains the corresponding line for the Med-Hycos server. If not, add it from the "hosts" file from Data Manager Installation (directory " Program Files\MedDat ".
2.2. The second test checks
the connection with the database: from the DOS prompt enter " tnsping world
". If the remote computer answers, you have a working SQL*Net layer. If
not, check the similarity between host name in "hosts" file and the host
name in " SQL*Net easy configuration ". If necessary, install again SQL*Net.
After the installation of the program " Med-Hycos Data Manager " a shortcut will appear in the main Start menu of Windows. So you can start the program from this entry.
General rules for reading: Entries from the menu are in bold characters in parenthesis; Frames and panels are in underlined italics in parenthesis; Buttons are in italics in parenthesis.
The program shows a main window with one line of menus:
The optional parameters can be changed after the installation. They include:
Names for the ACCESS database, working directory and a directory that will contain the archive of DCP messages.
The name used for "Database Alias" in SQL*Net installation, the user name for Oracle database and the password for Oracle remote database. The field named DSN is not more used.
The web address of the Eumetsat site from which is entered the operator’s user name and password, the web address of the site Eumetsat where the DCP messages are stored, user name of the operator and his password.
Here you have different options related to the program's automatic jobs: the operating mode, the periods of querying the Eumetsat web server and the update of Oracle database (only available to the operating service of PRC Med-Hycos in Montpellier).
It is important to mention that the "Automatic" mode doesn’t exclude manually executing the different procedures. However, try to avoid doing this while an automatic procedure is running (like Internet transfer or transfer between ACCESS and Oracle). You need to know that any automatic procedure needs about 10 minutes to run, so normally it must be finished in the 15 minutes after the hour of forced start. In this manner, if the Eumetsat retrieval hour is fixed at 10:00, the procedure will be achieved by 10:15; at 11:15 the updating of ACCESS multivariable table will be done. The update of univariable tables (only for DCP stations) in ACCESS has to be done manually.
With this entry you can load the built-in browser which will give you the Internet access to the Eumetsat web site. With this connection you can see the data related to the DCP stations without use of automated program retrieval procedures.
This entry opens a window with the list of files retrieved from Eumetsat web site files and the corresponding error or success messages.
Opens a window with the list of processed files (assimilated) by the program. Data found in messages without errors are already integrated in the ACCESS database’s multivariable table.
Shows the errors derived from the processing of DCP data files. The data from these messages are not integrated in the database but are still usable. In the case where the description of the error contains the text " FOUND in DATABASE ", the message has been corrected and the related data are found in the database. However, even if this text doesn’t appear it is still possible that the data are already in the database but the analysing software can’t find it. This is the case when the error is in the message header (e.g. in the station number, date or time fields)
The last three windows are connected with synonymous files found in the working directory. You can edit them in the program or with any text editor, change their content or add comments. The program adds new lines while the retrieval or processing procedures are working.
Starts the procedure of DCP's message retrieval from the Eumetsat web server. In automatic mode this procedure is started at the hour chosen in " Options " - " Options " - " Miscellaneous " and doesn’t need the operator’s intervention. In manual mode you need first to use the button "Operator Login", to connect to the Eumetsat web site and to enter your user name and password. Then you can either choose from one of two lists on the right side of the window, or to click the button " Retrieve Stations ". The choice from the middle list will retrieve all messages for that station (normally for the last five days). The choice from the right list will retrieve only the new messages from the chosen station (in other words, those which have not been retrieved yet).
The button " Retrieve Stations " starts a cyclical procedure to retrieve all the files (from the last five days) for all the stations for which the pair [number of station-eumetsat number] is shown in the middle of the window. After this, you must unpack the retrieved files using the button " UnTar New Files ". This procedure will read the retrieved files in binary mode (because of their UNIX content), change the non-ASCII characters to question marks after which they can be read by the program and Window editors in ASCII mode. Then the program will suggest that you move TAR files (UNIX format) from the working directory to the archive directory. You have to know that the TAR files coming from the Eumetsat server are stored with a name, which includes the Eumetsat station number, the date and time of the retrieval. In other words, there is not a real possibility to overwrite files and lose information. Also, the information is repeated inside the files for a period of days equal to 5 – the given in " Options " - " Options " - " Miscellaneous ". This side effect gives more reliability to the system without overloading the database where only one record per message is stored. The increasing number of TAR files can to be stored to a back-up drive or be erased. The retrieval procedure started with " Get Messages " is strongly related to the scripts running on the Eumetsat web server. Having said this, if the structure or the operation of the web page is changed by the service it is possible that the procedure will stop working. In such a case it will be necessary to synchronise the procedure with the changes in the operation. Otherwise the retrieval of Tar’s should be done with à browser. The files have to be unpacked with unzip (or with the program) and then can be processed further in the same manner with the program. Just remember to put either Tar’s or DCP’s in the working directory.
This entry processes the messages which are stored in ASCII format (files with the extension DCP) in the working directory. In case of an automated job this processing is done in the hour after the time of the retrieval from the Eumetsat server. In the case of manual start you can use the entry " DCP " - " New Assimilation ". The processing includes: reading all the files with DCP extension from the working directory (following a previous retrieval); detecting the messages with the corresponding data, that is, station number, date and hour, and various hydrological data; data checking; and, integrating the data into the multivariable table of the ACCESS database. After this processing, these files receive a new name (for example Cr685) formed by the letters Cr (code CREX) and a number between 100 and 999. These files are then stored in the sub-directory ‘’Archiv’’ of the working directory, from where they can be extracted for further use with the program operation. The files, which are intended to be processed again, are copied from the sub-directory ‘’Archiv’’ in the sub-directory ‘’Cs’’.
After the processing you can see on the list in the upper right hand field, the names of processed files followed by the erroneous lines and the error messages derived from the syntactic and logical analysis. In the upper left corner you have all the files from the "Archiv" directory. To correct an error in a specific message, first you have to select the name of the corresponding Crxx file on the right side list. The text of this message will appear in the bottom frame. Then when you select an erroneous line from the right frame the program will position the pointer on the corresponding line of the open file for editing. After the corrections, save the file and go on with the next line or close the window. The corrected files will be processed during the next sequence reception - processing.
Shows a quick survey of the received messages, whose data is already integrated, in the multivariable table of the ACCESS database. The window includes the date, the time, the names and numbers of stations of the last reception.
Gives the user the possibility to correct data, which are already integrated in the ACCESS database. The fields are visualised starting from the most recent hour. In this way fields whose names finish with ‘’_1’’ correspond to the hour shown on top of the window (HH), the fields with ‘’_2’’ to the hour HH-1 and the fields with ‘’_3’’ to the hour HH-2. The corrections are taken into account after changing the field (or with the button "Update") and they are not recoverable. Moving to other date or hour is done with the tool on the bottom of the window. In principle you can add a non-existing record or delete one but don’t forget that the changes in this window are not recoverable
By Station "
This tool includes two important functions. The first one is to transfer automatic stations data from the Med-Hycos network recorded in the multivariable ACCESS table to one-variable tables, also in ACCESS database. The second one is to calculate the synthetic values of resulting variables (ex. hourly rainfall, daily rainfall, monthly rainfall, mean daily temperature) from values measured at the stations in hourly time steps. (The primary value of rainfall is the "total" cumulative rainfall with hourly time steps, that is from the station set-up). You have, at the left of the window, the list of DCP stations. On the right you have to choose between two panels, which handle the mentioned functions.
The first panel " Populate hourly tables" serves to update one-variable tables of [tbsXX] type in ACCESS database. You have to choose the station, to click on the corresponding variable check boxes, to set-up an update period with the boxes from the bottom (the " SET " button allow the user to see already existing periods in the one-variable tables) and to click on button " Add ", " Update " or " Add & Update ". The confirmation or the rejection of the update can be made with "Commit" and " Discard " buttons. In principle, until you have "confirmed" your choices, the changes to the database can be rejected, but it is advised to make a confirmation or a rejection after each update operation (before the next and before the change of the station).
The second panel " Populate Resulting Tables " serves to calculate the synthetic values of resulting variables (up to the moment hourly rainfall, daily rainfall and monthly rainfall).
As with the first panel, you have to choose a station, to click the boxes corresponding to the time step, to define a period of update using the fields on the bottom of the "SELECT Period of Data Update " frame (the "SET " button allows the user to see already existing periods in the resultant tables) and then click one of the buttons "Add", "Update" or " Add & Update ". The confirmation or the rejection of the update can be made with "Commit" and " Discard " buttons. Remember that the hourly rainfall of type "total cumulative" is first stored in the [tbs99] table. Then after a comparative estimation, real hourly rainfall values are calculated and stored in the [tbs21] table. In automatic mode this window is activated at the Oracle update hour, but only for Oracle users in PRC. In this condition, the ACCESS tables and Oracle database are updated for whole stations and whole hourly variables coming from DCPs (synthetic rainfall only with hourly time step). Otherwise this operation must be done manually.
Shows the table, which contains information about DCP stations. From this table are formed station lists for the previous windows related to entries " Get Messages " and " Update Access Tables ". This table defines station numbers from which data messages will be searched for in the Eumetsat web server database. By adding a new number here you will be able to retrieve data from the new DCP station. But first you must add the corresponding record in the ACCESS database inventory (table [HMSCD10_L] accessible from the entry " ACCESS Inventory " and also from " Import Data In ACCESS tables " for adding new records).
These four entries permit you to change the layout of simultaneous opened windows in main program screen.
" Oracle Data View "
Gives the users of the remote Oracle database access to data stored in the Med-Hycos Oracle server. This window includes a complex system for visualising, editing and transferring data. From the menu you have first to choose the time step of the data and then the variable needed.
Even after opening the visualising window you can still change the variables with those in database that have the same time step to show them simultaneously in one graphic. The choice of the time period for data loading in memory is normally done before the window opens, but can also be made after the window opens from inside the window before viewing data from another station.
To download data from the Oracle server you need a fast Internet connection, especially if you need a huge amount of hourly data or data for several years. In other words, try to reduce the data time period if your connection is slower. The station name for which data is shown in the left grid is displayed at the top left of the window. On its right is the field that shows the country name. If the station has a WMO number, it is shown in the right corner of the same frame. The actual variable is shown (and can be changed from with respect of the time step) in a frame on the left with the name "Variable to show". A frame entitled "Graph Options " on the top of the windows gives access to several types of graphs: lines, columns (bars) or 3D, with lines representing the mean value, the tendency (trend), lines corresponding to margins of standard deviation, graphic correlation between two series and so on.
On the right side of the command frame, a vertical band contains several buttons for the representation of graphic objects. You have several choices: visualisation of distinct value points (" M ") but not the lines which connect them (" S "); a logarithmic (" Lg ") or percent based presentation (" %b); the legend (" L "), the title (" T "); you can increase or decrease the thickness of lines (" +L ", " -L ") and dots (" ++ ", " -+ "). The " C " button changes the behavior of the frame named " Avg or Cum ". These buttons can only toggle between "On-Off" positions, but some have only in one function, such as (" +L ", " -L ") and (" ++ ", " -+ "), for the opposite function, use the buttons with the minus sign.
On the right side are the main available commands of the window. From top to the bottom they are: commands related to changes made in database table (in the case of remote user of the Oracle database, the changes are not allowed and only the button " Transfer to ACCESS " works). Next, are commands related to the visualisation: " Add Graph " (adds a new data series for the actual variable in the graphic chart); " Clear " (clears the graphics frame); " Add to Value " (adds values of the actual series to the already drawn series and shows the resulting chart as a new series); and commands related to additional information such the general information about the station (" Gen Info ") and some statistical information (" Stat Info ") about the current data series. Lastly, are the commands for copying data or the graph to the Windows clipboard (" To Clip "), the printer (" Print ") or to a text file (" To text "). The frame named " Avg or Cum " lets you calculate and show the synthetic cumulative or averaged values using a larger time step than was originally used in the database. (depending on button " C " and the choice made in the frame itself).
The frame with three choices (" U ", " A ", " & "), situated in the top right corner, serves to fine tune the transfer of Oracle data to the local ACCESS database: the first option permits only the update of existing records in both databases; the second only adds records to ACCESS which are in Oracle but not in ACCESS; the third option copies all Oracle data to ACCESS whether it already exists or not. In the last case, equal values for the same given time period are not changed, however if you have values for dates in ACCESS which are not present in Oracle, they will not be erased or updated. The frame " Period begin " gives you the possibility to change the period of the data you want to load in memory; you can choose the beginning and ending year. The frame "More" allows the user to change the density of labels or ticks on the chart, and also the period for the chart representation (the period to be represented is always smaller than or equal to the period of data loaded in memory).
It is important to know that for data export in ASCII format it is advisable to use year representation with four digits when the data series include years before 1.1.1930 (ex. dd-mm-yyyy).
This window is identical to the previous one except for commands related to data update. Since the data represented in this window is the user data you can edit edit, delete, update or add records to the grid as you see fit. The buttons "Commit" and " Discard " are to confirm or reject the previous series of changes made to the database. The button " Transfer to Oracle " works only for the Oracle user in PRC Med-Hycos.
This window shows the inventory of the Oracle database of Med-Hycos pilot regional centres. The grid shows the records of the inventory [station-variable-time step], which are open to the external user. Records are shown by the order of station number. The move from one station to another is made with the buttons " Next " and " Previous ". Oracle station number is shown at the top of the window. For the remote users the buttons "Update", "Commit" and " Delete " do not work. Nevertheless, you can copy all the corresponding lines for the actual station to your local ACCESS database inventory by clicking the button " Copy Inventory to ACCESS " on the top of the window. The button " Analyse This Station " starts a procedure that will make a simple statistical analysis. It extracts and shows the following calculated values: the number of records; the starting date and the ending date of the data series in the database; the real percentage of the time period covered from the data in database; the mean value for the whole series; the standard deviation for the series; the variance of series; the first date corresponding to the maximum of the series; the value of the maximum; the first date corresponding to the minimum of the series; value of the minimum. In the case where you analyse several entries (stations) the results will be added at the end of the resulting grid on the bottom of the window. With the button " Print " you can print the content of the resulting table.
This window gives access to functions similar to " Oracle Inventory ". The differences are in the gathering of entries. Here all the entries [station-variable- time step] are shown in one grid at the top of the window. Like this, the analysis will be made for all the triples [station-variable-time step] from the ACCESS inventory table. With the " Print " button you can print the resulting analysis made for whole ACCESS database.
You can make two analyses
of report type: the first takes account of the whole time periods of data
present in the ACCESS database; the second is made over the last two months.
These two reports contain less data then the analyses, but are more clear
and can be exported to a file, printed to the printer or sent by mail.
This window gives access to data describing station’s parameters, as: name, latitude, longitude, country, basin, river, equipment etc. The user can see, add or modify the station description in the table [STATDESC] in ACCESS or Oracle databases. These data are used to situate stations on the map and they are show also in the window " General Information about the Station ".
" Convert Levels <> Discharges " :
This window permits the conversion between water levels and streamflow discharges in the both directions. The user can specify the direction of the conversion, the begin and the end of the period of data to convert and also the aggregation level of data (the corresponding entries in inventory must be present). To be able to covert data, one or more rating curves have to exist for the chosen station. The user has to choose the corresponding curve by clicking on her ending date in the left upper list named: " Existing End Dates ". The conversion is started after the user presses the button " Go ". After the conversion finished the label ‘STATE’ is changed to label ‘Q-READY’ or ‘H-READY’. After this moment the user can save the result by clicking on the button " Store ". This operation can be committed or discarded with buttons " Commit " or " Discard ".
This window serves to visualise and manage the rating curves. The curve to manage is chosen by the station name and the ending date of validity. The couples level-discharge are shown in the left-side grid. The user can modify, add or delete couples but has always to keep the ascending downward direction of levels. The couples are added and deleted by the buttons " Add Level " and " Del Level ". An entire curve can be deleted using the button " Del Curve ". The first two operations have to be competed by a " Store " command that will write changes to the database. The " Store " command itself can be committed or discarded using the buttons " Commit " or " Discard ". The button " Refresh " serve to visualise modified by the user data after the " Store " command. Notice that you can not see the marker in the grid but after you click on a cell the marker is positioned at the end of the number and you can use BACKSPACE key to delete to the left or ‘0’ to ‘9’ keys to write numbers. If the ‘Add new’ check box is on, the new chosen curve will be added to the end of the already shown. The user can copy the data and the graph to the Windows clipboard, to export the curve to an ASC file and to print the graphic.
The tool " Query Builder " serves to extract from the database (Oracle or ACCESS) a synthetic and targeted information on one or more kind of data having the same or different aggregation levels. The user has to begin with the higher level of the query adding as much fields as needed but with respect to the rule of the descending levels. The fields can be ‘country’, ‘basin’, ‘river’, ‘station name’, and also variables. The variables can be simple or modified by a math function between: maximum, minimum, average, sum, number of records, maximum-minimum, maximum-average. The variables have the same level but all of them have on level less than fields: ‘country’ etc. The variables are also influenced by the chosen aggregation level (within the box named ‘Agr. Level’). The user can limit the number of returned records by setting a condition on high level fields or on variables, by instance of type ‘Country=France’ or ‘Date BETWEEN 01/01/80 AND 01/01/90’. After have been chosen with ‘Select’ and ‘Function’-boxes, the fields are added to the query using the button " Add to select list ". The conditions on variables are chosen with ‘Where’-box and added with the " Add to where list " button. The conditions on high level fields are chosen with the ‘Having’-boxes and added with the button " Add to having list ". The period from which data is analysed is selected within the frame " Select Period ". To execute the query the user should first visualise it by pressing the " Show query " button. This option is chosen to leave the user the possibility to write a query directly in the white window without having to select fields by the program. After having visualise the query the user can execute it by the " Execute " button. The " Reset " button clears the selections and empties the query window. The buttons " Show Graph " and " Show Map " give respectively a graphic and mapping presentation of the result of the query. The user can copy the graph and the corresponding data to the clipboard using the " Copy to Clip " button.
With this window you can access several functions :
From here you can add lines (records) to the ACCESS database inventory. If there is already at least one record for the station that you want to add new records to, you have two possibilities:
In the frame " What to import", choose the station name, the variable and the time step. If the label ‘’Inventory Entry not Created’’ appears you can create the entry by using the button " Add new entry in inventory ".
However if the variable has not been already created in the database for any station, then you can use the frame " More new things " to choose (and introduce) the combination [station-variable-time step] you need.
On the other hand, if the station has not yet been defined (the location co-ordinates, the altitude, the owner of the station and data), you have to input several complementary fields. In the last two cases use the button " Add new Station in Inventory " to add the corresponding record to the inventory of the ACCESS database. In the case of a new variable, pay attention to how the acronym is formed. It should be compounded from the first letters of the variable name and the time step name. In any case, the acronym must not be already used (for example, Water Turbidity Daily gives WTD, while we have already WTD for Temperature of Water Daily). In such cases just get the next letter (by ex. WUD). Always in case you add a new variable you need to mention the new table name that will be used to store the its data. The table names begin with the letters " tbs (from " tablespaces " used in the Oracle database) and finish with a 2 digit number. It is necessary to choose a non-occupied number for the new combination [variable-time step]. It would be a good idea to define beforehand the numbers corresponding to pairs [variable-time step] cf. table p. 31.
Importation of data stored in an ASCII file. After you have made the choice of the triplet [station-variable-time step] from the top frame (the label ‘’Has an entry in inventory’’ must appear), you have to choose the disc, the repertory and the file that contains the data to insert in the corresponding table. In the frame from the middle of the window, you have to choose the date format, field delimiter and the header option. It is important to know that for the import of ASCII data that includes years before 1930, the format of the year in text file must represent the year in four digits. Otherwise these data will be imported as data from the XXI century. The regional parameter "decimal symbol" could be the source of some problems with data import and export. It is strongly advised to use in imported files the system defined decimal symbol (you can see it in Windows regional parameters). By default French version of regional parameters considers the comma as the decimal symbol. That opposes the using of the comma as field separator. The import procedure is started with the button " Go " and needs sometimes a long time to finish.
The import of rating curves starts with the choice of the station name. After that user has to set the en date of validity of the curve and the file name that contains data itself. The format of the file has to be according to these rules: 1 line contains the number of the station as it appears at the right side of the name, 2-nd line with the ending date of validity in format ‘DD/MM/YYYY’, following lines contains the couples level-discharge separated with the delimiter specified within ‘Delimiter’ box. The file must contain couples H-Q in increasing evolution of the water level data. In the case of missing entry in the inventory about the station, use the button " Add New Entry in Inventory " to create the entry. The import of the new rating curve begins with pressing the " Go " button. The user has to confirm or reject the importation with " Commit " or " Discard " buttons.
This window permits you:
to perform a station query by country or basin from the Mediterranean map;
to visualise the general data about the station itself, to see simple statistics
about data series or to show the graphic representation of the chosen data
series (see the entries " ACCESS Data View " and " Oracle Data View
"). To choose the station, click on it’s image on the map. Its name will
appear in the frame on the bottom of the window. By clicking on the name
you can view the general information about the station (if this option
is chosen within the frame on the right side). By clicking on the time
step of a variable you will see either the simple statistical information
about data series or the chart for the same series from the ACCESS or Oracle
database (depending on your choice within the right side frame).
This tool gives access to data used to build the mapping representation: names of countries, basins, rivers and also vectorial objects to show them on the map. The user can add new objects, but it has to be beforehand vectored and transformed in the own format of MedMap application. After that the user can import the object’s compressed string from an ASC file.
This entry permits to control the displaying parameters of the map. The first field contains the map name. The followings contain the limits of the map in degree (minimum and maximum latitudes and longitudes). The last one contains the name of the bitmap used for the map background. Notice that the program adds the suffix " GIF ". In the common case the last mentioned file has to be in database directory.
This tool permits to update graphic objects in ACCESS database from Oracle database. In case when one or more objects are added or modified in Oracle the user has to update his own database with new changes.
These menu entries allow the user to maintain the ACCESS database.
You can create an empty ACCESS database, identical to the needs of programs MedMap and MedDat and ready to be filled with data own to particular needs. Notify that with database name other than " operat.mdb " you will not have the advantage of Oracle connection. This is made because of the idea of particular database that has not to share data with Oracle.
Allows compacting of the ACCESS database. Eventually the ACCESS database file becomes fragmented and its size greater than the data storage required. In such cases the defragmentation can reduce the MDB file size by 20% to 50%, and the speed of your application will increase. If at start moment of the program you receive the message ‘‘Database corrupted’’ or ‘‘Database needs repair’’, from this function you can try to repair the ACCESS database. This function may be needed after a power cut or computer failure or when Windows stops responding while the database is open.
Makes a replica of the database. After this operation, the replica and the original database will contain additional information in a complementary field for each record. This field will contain a time stamp for comparisons between original and the replica that will be actualised after executing the " Synchronise " function. The general idea of this is to increase the reliability of the ACCESS database. This will increase considerably the needed storage for both the replica and original databases (about 6 times), and will also decrease the speed of accessing data within the ACCESS database. This function will work if your database is coverted to ACCESS 2000.
This window shows only the program version and system information.
This entry permits to see the User Manual using Word editor.
This entry permits to read
"readme" file using Notepad.
The structure of the ACCESS database is inspired from the structure of the Oracle database of Pilot Regional Centre of the project MED-HYCOS. It includes tables analogous to ‘’tablespaces’’ used by Oracle database management system.
The data inventory is stored
in the table [HMSCD10_L] (L for local). It includes one record for each
triple, station – variable – time step. That is to say the primary key
is defined by fields corresponding to the three variables mentioned above.
For every variable - time step pair, there is a corresponding name in the
same table of a mono-variable table (for a given time step).
In this way, every record in the inventory table gives access to the data of the station (first member of the triple) corresponding to a variable (second member of the triple) with the needed time step (third member) in the corresponding table (defined by the two last members of the triple). The inventory table also contains different information related to the station and to the specific data series (name of the river, of basin, co-ordinates of the station, unit of measure and so on). The tables corresponding to variable - time step pairs include records with three fields: the number of the station, the date of measure and the measured value. Their unique index includes the first two fields, which assure the uniqueness of records. The missing data are not included in the database. An additional table contains the multi-variable data from automatic stations (DCPs), before their processing and distributing between mono-variable tables of type [tbsXX]. This is the table [PCD_TABLE1]. It contains one record by message. In this way storage space for not yet validated data is minimised. This table is related to the [STATIONS] table, which contains one record per DCP station. The table [STATDESC] contains information describing general characteristics for stations. Tables [Rivers], [Countries] and [Basins] contain vectorial data of graphics objects used by cartographic tool MedMap. The table [InfoMap] contains co-ordinates of the map corners, map name and map background bitmap. Most of the queries used by the program are auto-generated, that is, they will be remade if the program doesn’t find them in the database. It will not be the case if they were manually altered (for example, through ACCESS). Then an unexpected error can happen and the result is not predictable. The queries [Last30days] and [StartEnd], that are used for the general report and for the monthly report (see the entry " ACCESS Inventory ") are also generated by the program, but they will use only data from tables mentioned above. In other words, if a new variable is added to the ACCESS database it will not appear in the reports until these queries are modified. These modifications being rather complicated, it is advisable to ask for a patch, which will include the new variable (table) in the reports.