Changes between Version 119 and Version 120 of Procedures/NEODCDelivery


Ignore:
Timestamp:
Feb 6, 2019, 10:32:24 AM (5 years ago)
Author:
wja
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NEODCDelivery

    v119 v120  
    77}}}
    88The 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.
     9
     10Note that if you are creating JSONs for a LiDAR delivery that used the old azgcor processing, the projection will need to be input manually using the --projection flag. Look in the ReadMe for the projection used.
    911
    1012If you are running without a GUI you might get a problem due to the matplotlib backend. You can overcome this by changing the backend using an environmental variable: