1 / 22

NEMO reformatting tool v1

NEMO reformatting tool v1. M. Fichaut. Overview. Objectives, main features and principles of NEMO Technical characteristics Running NEMO : description of the different steps Link with MIKADO NEMO status and planned development. Objectives. NEMO is a reformatting software used to

lallen
Download Presentation

NEMO reformatting tool v1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 3rd SeaDataNet training course – Ostende – 16-19 June 2008 NEMO reformatting tool v1 M. Fichaut

  2. Overview • Objectives, main features and principles of NEMO • Technical characteristics • Running NEMO : description of the different steps • Link with MIKADO • NEMO status and planned development

  3. Objectives • NEMOis a reformatting software used to generate ASCII files at MEDATLAS or ODV formats which are defined as SeaDataNet formats for data exchange between SeaDataNet partners • It was created in IFREMER for internal purposes, and adapted to take into account the SeaDataNet formats and vocabularies

  4. NEMO main features • Reformat any ASCII file of vertical profiles, time-series or trajectories to a SeaDataNet ASCII format (ODV, MEDATLAS). • The input ASCII files can be : • one file per station for vertical profiles or time series • one file for one cruise for vertical profiles, time series or trajectories • Interact with Mikado, to be able to generate ISO-19115 XML descriptions of the data.

  5. NEMO principles • NEMO is able to read “any” ASCII format to translate it to MEDATLAS, ODV • Users of NEMO describe the entry files format so that NEMO is able to find the information which is necessary in the SeaDataNet formats • One pre-requirement is that in the entry files the information about the stations must • be located at the same position : same line in the file, same position on the line or same column if CSV format • be in the same format • For example : for all the stations the latitude is • on line 3 on the station header, • from character 21 to character 27, or 3rd column in CSV • the format is +DD.ddd

  6. Technical characteristics • Written in Java Language (Version >= 1.6) • Available under multiple environments : • Microsoft : Windows 2000, XP, VISTA , • APPLE (not tested) • Unix - Solaris with the graphical library GTK • Linux with GTK also. • Development tool and Framework : ECLIPSE • Use of the SeaDataNet common vocabularies web services • to update lists of values of the SeaDataNet common vocabularies • need network connections in order to have up to date lists of values. • But NEMO works offline once the list are up-to-date

  7. Running NEMO • 4 or 5 steps to convert the entry files to a SeaDataNet format • Describe the type of file(s) • [Describe the cruise, if the files are related to 1 cruise] • NEMO is able to read XML CSR generated with MIKADO • Describe the station information • Describe the measured parameters • Convert the file • One more step to • Save the description of the format (Model)

  8. NEMO - description of entry files • Where are the files? • Is it a cruise? • Is it one file per cruise or one file per station ? • Is it a collection of files ? • grouped by cruises or not? • Is it vertical profile, time series or trajectory data? • Are the files with separators? • Tabulations? Semicolon? Comma?

  9. The file is opened in the left part of the window How many line in the file header? How many lines in the station header? How many lines in the station tail? What indicates that the station is finished?

  10. cruise description • can be imported from a MIKADOXML CSR file or can be input manually (or can be uploaded from the database, IFREMER only)

  11. station description

  12. station description

  13. 1 - Latitude position selected on the left of the screen • station description

  14. 1 - Latitude position selected on the left of the screen • 2 - Input of the latitude format • station description

  15. 1 - Latitude position selected on the left of the screen • 2 - Input of the latitude format • 3 – Set button will automatically input the position of latitude • station description

  16. data description

  17. NEMO – File conversion for files collection • If CDI summary is requested NEMO generates an EXCEL file containing the mandatory fields for data descriptions (CDI)

  18. ODV files Collection of ASCII files XML CDI files SeaDataNet CDI CDI summary CSV file MIKADO NEMO to MIKADO to SeaDataNet CDI

  19. NEMO STATUS • Actual version 1.11 received on May 7th 2008, • Tests completed • New release scheduled end of June with correction of bugs • Why NEMO will not be taught during this training session? • Because some important SDN developments are missing : • Last definition of SeaDataNet formats • Use of Web Services for parameter MEDATLAS to PUV mapping • Keep the quality flags of the input file (if exist) • One file = One station • Trajectories not taken into account • The user manual is missing

  20. Planned development • All the missing development for SeaDataNet are already started • A new version of NEMO with SDN requirements is scheduled in September 2008 • NEMO could be released to the SDN partners last quarter of 2008.

  21. ANY QUESTIONS?

More Related