You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SimaPro CSV format does not quote empty string when exporting a dataset, as in the following ProcessBlock:
Process
PlatformId
Category type
waste scenario
Process identifier
Dev99229000009369600014
Status
Infrastructure
No
Date
11/18/2021
End
In this block, properties such as platformId or Status has an empty line. So in order to be consequent with that, during the writing process of null or "" values, an empty line should be placed in the output file.
Actual Behavior
However, the current API produces files as the following:
Process
PlatformId
""
Category type
waste scenario
Process identifier
Dev99229000009369600014
Status
""
Infrastructure
No
Date
11/18/2021
End
In this output file, empty strings are quoted which is not consistent with SimaPro behavior.
Importing olca-simapro-csv produced files to SimaPro
Despite of this, output files from the API can be imported to SimaPro without any issue or wrong data imported, as far as we have tested. So this seems to be harmless for olca-simapro-csv users.
The text was updated successfully, but these errors were encountered:
Expected Behavior
SimaPro CSV format does not quote empty string when exporting a dataset, as in the following
ProcessBlock
:In this block, properties such as
platformId
orStatus
has an empty line. So in order to be consequent with that, during the writing process ofnull
or""
values, an empty line should be placed in the output file.Actual Behavior
However, the current API produces files as the following:
In this output file, empty strings are quoted which is not consistent with SimaPro behavior.
CSVPrinter
issueolca-simapro-csv
uses Apache commons csv library and this behavior is produced by a known issue of the library:https://issues.apache.org/jira/browse/CSV-63
Importing
olca-simapro-csv
produced files to SimaProDespite of this, output files from the API can be imported to SimaPro without any issue or wrong data imported, as far as we have tested. So this seems to be harmless for
olca-simapro-csv
users.The text was updated successfully, but these errors were encountered: