This concerns exports of datasets directly from the Dataset Manager (as opposed
to from an EMF case).
When using certain types of row filters, I am finding that the resulting
exported dataset sometimes contains records from older versions of the same
dataset that have since been edited or deleted.
Example: dataset nonroad_ff10_california_2011neidraft_augmented_VOC, version 7.
When exporting using this row filter:
scc like '226%' or scc like '228%'
then records from older versions of the dataset appear in the results. For
example, we get duplicated PM records:
"US","06115",,,,"2282010005","X","EXH__PM10",1.43814,...
"US","06115",,,,"2282010005","X","EXH__PM2_5",1.37229,...
"US","06115",,,,"2282010005","X","EXH__PM10-PRI",1.43814,...
"US","06115",,,,"2282010005","X","EXH__PM25-PRI",1.37229,...
PM10/PM2_5 were renamed PM10-PRI/PM25-PRI in Version 2 of this dataset, and so
Version 7 only has PM10-PRI and PM25-PRI, not PM10 or PM2_5. This is a double
count.
When exporting the same dataset/version without that row filter (or with a less
complicated row filter), we only get the PM10-PRI and PM25-PRI records and not
the PM10/PM2_5 records.
Two other notes about the Dataset Manager exporter:
- The "overwrite files if they exist" option does not work. If selected, and
the file exists, the resulting status message is "FILE EXISTS" and the file is
not overwritten.
- The "Export" button becomes disabled after clicking it once, so if one wishes
to re-export with a different row filter or to a different directory, one has
to close the window and re-enter everything again. We would prefer the "Export"
button remain active after clicking it once.