CSV Export Format

Currently the CSV format is different than CSV of nshmp-ws-static.

There should be a more standardized CSV format for all NSHMP web services and web applications.

The erp-rtgm-calculator uses the Dynamic hazard tool export CSV as the HTTP POST body. The RTGM web service would need updated to handle the new format.

Formats

Dynamic Hazard Tool Export

Peak Ground Acceleration
Ground Motion (g), 0.0023, 0.0035, ...
Annual Frequency of Exceedance, 2.7430e-2, 1.8166e-2, ...

...

Static Hazard Tool Export

Site class - AB
Peak Ground Acceleration
Ground Motion (g), 0.0023, 0.0035, ...
Annual Frequency of Exceedence, 7.0161e-1, 5.4007e-1, ...

...

nshmp-ws-static

Static Hazard Curves for Colorado Using the 2018 NSHM

Longitude,-104.99,Latitude,39.34,SiteClass,AB,Imt,PGA
Ground Motion (g),0.00233,0.0035,0.00524,0.00786,0.0118,0.0177,...
Annual Frequency of Exceedence,0.035814,0.02564,0.017864,0.012019,...

Related:

• nshmp-ws-static#58
• ghsc/erp/erp-rtgm-calculator#36

cc @pmpowers

assigned to @bclayton

mentioned in issue ghsc/erp/erp-rtgm-calculator#36

changed milestone to %CSV Format

changed the description

I like seeing metadata in header lines. Here are a few suggestions:

• start all header lines with "#" would make it a lot easier to process with external tools, to maintain CSV parsing, the first two characters could be "#,"
• be consistent when specify metadata values, stick with a "PARAMETER,VALUE" format, e.g. "IMT,Peak Ground Acceleration (g)" or "Site Class,AB"

@nluco @amakdisi @pmpowers @jaltekruse

Do we have any thoughts on a standardized CSV format?

changed the description

mentioned in issue #107 (closed)