CZO Central WOF codes vs viz.criticalzone.org codes

[emiliom]

Here is one example of a CZOCentral WaterOneFlow data stream, as represented in viz.criticalzone.org and CZOCentral WOF:

I picked a Christina River site b/c @aufdenkampe can weigh in with direct expertise.

• CZOCentral WOF GetSiteInfo: http://water.sdsc.edu/czo_udel/REST/waterml_1_1.svc/siteinfo?location=czo_udel:MCCORKLES2
• Corresponding viz url to open that site pop-up: http://viz.criticalzone.org/Christina?action=oiw:fixed_platform:CRB2CZO_MCCORKLES2

Note that there's effectively a mapping between the WOF site code czo_udel:MCCORKLES2 and the viz site code CRB2CZO_MCCORKLES2, and you can see that the string token MCCORKLES2 is identical. This pattern applies in almost all cases (say, >95%), except when the WOF site code included undesirable characters that we needed to sanitize.

I can provide a table mapping of WOF site codes and viz site codes. We could host it on github, so SDSC can harvest it easily, I can update it easily as needed, and it's accessible to others who may find use for it.

The mappings at the level of variables is trickier, are not 1:1, and will evolve over the next couple of months. Right now on viz we have url parameters such as the sw_temperatur_119 token at the end of this url: http://viz.criticalzone.org/Christina?action=oiw:fixed_platform:CRB2CZO_MCCORKLES2:observations:sw_temperatur_119

sw_temperatur_119 is a token I'm constructing using some heuristics, where sw is a shorthand for the sample medium (in this case, sw = surface water), temperatur is a substring of the WOF/WaterML variable code, and 119 is an integer counter (I forget its exact derivation at this moment).

Pinging @SRGDamia1, @tom2275, @valentinedwv, @izaslavsky and @dlubinski