Closed RussellSenior closed 2 years ago
There are a number of instances where the variable name latitude_qc appears where lat_qc was perhaps intended:
$ git grep latitude_qc erddap/templates/private/dataset.deployment.xml: <destinationName>latitude_qc</destinationName> erddap/templates/public/dataset.agg.xml: <sourceName>latitude_qc</sourceName> erddap/templates/public/dataset.agg.xml: <destinationName>latitude_qc</destinationName> erddap/templates/public/dataset.deployment.xml: <sourceName>latitude_qc</sourceName> erddap/templates/public/dataset.deployment.xml: <destinationName>latitude_qc</destinationName>
Also on the wiki:
$ git grep latitude_qc NGDAC-NetCDF-File-Format-Version-2.md: byte latitude_qc(time) ;
Similarly for longitude_qc:
$ git grep longitude_qc erddap/templates/private/dataset.deployment.xml: <destinationName>longitude_qc</destinationName> erddap/templates/public/dataset.agg.xml: <sourceName>longitude_qc</sourceName> erddap/templates/public/dataset.agg.xml: <destinationName>longitude_qc</destinationName> erddap/templates/public/dataset.deployment.xml: <sourceName>longitude_qc</sourceName> erddap/templates/public/dataset.deployment.xml: <destinationName>longitude_qc</destinationName>
@RussellSenior is this still an issue?
Glider QARTOD QC checks are now implemented and stored in standard variable names.
There are a number of instances where the variable name latitude_qc appears where lat_qc was perhaps intended:
Also on the wiki:
Similarly for longitude_qc: