Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Note
iconfalse

Project BwN DM 1.1, Deliverable 2009

Tip

Printing: If you want to print this document select tools -> export to pdf from the top right corner

NOTE: This protocol currently applies only to the OpenEarth administrators at Deltares. In the near future outsiders can also put netCDF data files on the OpenEarth opendap server.

How to put netCDF files on the OPeNDAP server of OpenEarth.

  • Verifieer of de data open is, en op internet mag. (Bewaar email of hard-copy van brief oid, liever geen gezeur achterafVerify whether the data are open, whether you are allowed to publish it on internet. (Keep a copy of the email or a hard-copy of the letter, avoid nasty discussions afterward).
  • Put the raw data in the OpenEarthRawData repository.
    • Make direcory per institute (Lower a new directory per originator/copyright owner (lower case).
    • Add an INSPIRE *.xml file.
    • Add a *.url internet shortcut file to the intetnet source (if any).
    • Make subdirectories /raw, /cache and /scripts.
      • Store the raw data in /raw
      • /cache is for data that could in principle be downloaded, so there is no need for version control. However, some sources, notably www.waterbase.nl, are down for along a long time, so caching is useful.
      • Make a script to transform the data into netCDF files. Store the script in /scripts. Make sure the script only needs tools from /script and OpenEarth tools.
  • Zet de netCDF files altijd eerst op Always put new netCDF first in your local synchronized local copy of the data in the OPeNDAP server. Make this local copy available to your entire company by making it accessible through your local network. This network copy is for optional fast access within your institute. Within Deltares this is P:\mcdata\opendap\ . (Schrijfrechten aanvragen bij (ask for write access Gerben de Boer). This is for optional fast access withing the Deltares network.For users outside Deltares we are working on ftp access to the filer server under OPeNDAP, which enable you to make synchronized local copy (with rsync).
  • Make a new directory per originator/copyright owner that owns the copyright of the data. In principle the following sources need exactly the same directory structure:
    • the OpenEarthRawData repository
    • the OPeNDAP servers,
    • your synchronized local copy of the data in the OPeNDAP servers (within Deltares:
    Maak een directory aan voor het instituut dat de data-eigenaar is. In principe moeten
    • P:\mcdata\opendap,
    • de OPeNDAP servers,
    • de OpenEarthRawData repository
    • )
    • the *.de kml direcory (zie beneden) exact dezelfde directory structuur hebben.
  • Vanaf een windows PC, en alleen vanuit het Deltares netwerk, kun je de netCDF files met het programma From a windows PC - and currently only from within the Deltares network - you can add netCDF files from local copy to the OPeNDAP servers with the free program WinSCP (http://winscp.net/Image Removed) op deze servers zetten.). You can also use fabric fabric.
  • Currently OpenEarth has employed two OPeNDAP serversEr zijn twee OPeNDAP servers van OpenEarth:
    1) productie production server: http://opendap.deltares.nlImage Removed
    2) test/acceptation/backup fall-back server: http://dtvirt5.deltares.nlImage Removed
    Probeer altijd eerst je data uit op de dtvirt5, en daarna pas op de echte productie server. Als de data goed is bevonden, is, gelieve deze op allebei de servers neer te zetten.
  • Log in met je Deltares username. Je wachtwoord is je bekend voor de dtvirt5, en is je reguliere Deltares wachtwoord voor de productieserver (verandert niet mee als je je Deltares wachtwoord verandert). Je kutn je password veranderen met linux commando passwd.
  • :8080
    Always try the data first on the dtvirt5 (test function), and only on the real production server afterwards. If the data assessed as OK, do put the data on both servers, also on the dtvirt5 (fall-back function). If you are going to make changes to the OPeNDAP server isself, please test this first successfully on the dtvirt5, before installing/employing this on the production OPeNDAP server (acceptation function).
  • Log in with your Deltares username. Your password is known to you for the dtvirt5, and is your regular Deltares password for the productionserver. You can change your je passwords on the linux machines with command passwd.
  • Copy the netCDF files to the Kopier de netCDF dan naar de data directory:
    @opendap.deltares.nl: /drbd/
    opendap (samba-data/share)
    @dtvirt5.deltares.nl: /data
  • The dtvirt5.deltares.nl has a limited storage capacity. If your data works fine, put it on the opendap.deltares.nl and remove it from the dtvirt5. You can check teh size of datasets on both machine with the linux command du -h --max-depth=1.
  • If you made Als je een Google Earth *.kml/*.kmz file hebt gemaakt, kun je die ook op de dtvirt5 neerzetten. hier wordt naartoe gelinked vanaf files too, you can put them on the dtvirt5 too. The www.OpenEarth.nl wiki links to the kml directory: @dtvirt5.deltares.nl: /data/kml
    Hanteer wederom dezelfde directory structuur Please use the same directory structure again (organised per originator/copyright owner.
  • If you added a nice dataset, do post a news item on Als het een mooie dataset betreft, post dan ook even een news bericht op www.OpenEarth.nl.