Changes between Version 109 and Version 110 of Procedures/NEODCDelivery


Ignore:
Timestamp:
Jan 26, 2018 12:33:19 PM (20 months ago)
Author:
asm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NEODCDelivery

    v109 v110  
    66create_ceda_json.py -p .
    77}}}
    8 The script will identify the different deliveries under delivery directory and files will be placed in under''' processing/json_files/'''''''. The type of delivery will be taken from the delivery name if it has the keywords: owl, hyperspectral, lidar or camera. Once the files have been created, have a look to the overview image and compare to the mosaic in the delivery to make sure everything is correct. Also open one JSON file in a text editor to check quicky all fields are correct. '''Specially check the''' '''ceda_path''' looks OK. If the project has been already archived, you will be able to get the link by opening  http://data.ceda.ac.uk/ followed by the ceda_path. If the project has not been archived, check that the path looks similar to others in the same period of time.
     8The script will identify the different deliveries under delivery directory and files will be placed in under''' processing/json_files/'''''''. The type of delivery will be taken from the delivery name if it has the keywords: owl, hyperspectral, lidar or camera. Once the files have been created, have a look to the overview image and compare to the mosaic in the delivery to make sure everything is correct. Also open one JSON file in a text editor to check quickly all fields are correct. '''Specially check the''' '''ceda_path''' looks OK. If the project has been already archived, you will be able to get the link by opening  http://data.ceda.ac.uk/ followed by the ceda_path. If the project has not been archived, check that the path looks similar to others in the same period of time.
    99
    1010You can also specify the delivery directory by using {{{-d}}} and even run two different '-d' statements as well as you can choose a different output folder using {{{-o}}}. If you want to create a JSON file for each photograph file, then use {{{--camera_per_frame}}}. If at any time the overview image is not displaying correctly (not centred and because of that not displaying all data or labels) re-run the script with option {{{-i}}}. That will create an interactive plot that will allow you to check and show all data in the plot before exiting the script.
    1111
     12
     13=== Committing the JSON to the PostGIS database ===
     14If all JSON files look OK under processing/json_files we need that data in our database. If this is a new project you can upload all JSON files for the different deliveries by running:
     15{{{
     16json_into_postgis.py -p .
     17}}}
     18
     19If  you want to only commit a specific type of JSON (camera, owl, lidar or hyperspectral) because other deliveries were already committed; you can do so by using the {{{--json_dir}}} argument insetad of {{{--project}}}. For example, if you want to add only the camera_json files just run:
     20{{{
     21json_into_postgis.py -j ./processing/camera_jsons/
     22}}}
     23
     24In the case that the project has been reprocessed and new JSON files have been created, we do not want duplicates in the database. Running the script with the flag {{{--reprocessed}}} will delete the data in the sensor table (if data for that sensor were already present) and commit the new data. For example, if the camera has been redelivered and new JSON files have been created you can run:
     25{{{
     26json_into_postgis.py -j ./processing/camera_jsons/  --reprocessed}
     27}}}
    1228
    1329