Closed frankinspace closed 7 months ago
Data was able to load in UAT account after removing the 'inf' values
2024-04-15T02:29:02.462-07:00INFO:podaac.sworddb.setup_sword:Indexing tables
2024-04-15T02:39:19.935-07:00INFO:podaac.sworddb.setup_sword:Performing row count
2024-04-15T02:39:20.653-07:00INFO:podaac.sworddb.setup_sword:Reach row count: (241852,)
2024-04-15T02:39:47.746-07:00INFO:podaac.sworddb.setup_sword:Node row count: (10865963,)
Summary
An error occurred when trying to load the SWORD v16 data. The error log is appended to the end of this file. The error indicated a problem trying to persist ‘inf’ values into the MySQL database because ‘inf’ values are not a supported data type. Upon inspection, there was only one attribute (sinuosity) in about 20 of the node files that contained ‘inf’ values. After checking with applied science team, it was determined that replacing these ‘inf’ values with ’NaN’ would not be a misrepresentation of the meaning behind the data. Since MySQL supports ‘NaN’ values, a script was written to convert the ‘inf’ values in SWORD v16 to ’NaN’ values. The resulting data was then loaded into the FTS database.
Bucket Contents
Description of the objects present in the s3://sword-v16-shp bucket (services UAT)
SWORD_v16_shp.zip
The original SWORD file downloaded from gaia.geosci.unc.edu/SWORD/SWORD_v16_shp.zip.
shp/
This is the unzipped SWORD_v16_shp.zip with the ‘inf’ -> ’NaN’ conversion already applied.
sword_convert_inf.py
This is the script used to convert ‘inf’ values to ‘NaN’ values.
Error Log
Error log from original load attempt has been copied from cloud watch below: