Open GoogleCodeExporter opened 8 years ago
It is my understanding that using the CF terms also forces use of whatever
units are
defined withing those terms. That is what the standard-name-table seems to
show,
also (for example, air_pressure units are Pa- no flexibility there). IMO, this
is a
big negative for CF, since it will require multiple terms for every unit to be
supported. If I am missing something, please correct me.
Thanks,
T
Original comment by TheRest...@gmail.com
on 20 May 2009 at 4:26
From Tony's email - Fri, May 1, 2009 at 12:03 PM
Encoding example:
<swe:uom> does not directly include a codespace attribute, but there does
appear to
be a couple of ways to point to the definition. Not sure exactly the best way
or how
it will work, but here is the structure:
<swe:uom code="cm" xlink:href="might_could_use_this"">
<gml:UnitDefinition gml:id="databaseHandleIfAvailable">
<gml:name codeSpace=""></gml:name>
<gml:quantityType></gml:quantityType>
<gml:catalogSymbol codeSpace=""/>
</gml:UnitDefinition>
</swe:uom>
Original comment by ber...@gmail.com
on 26 May 2009 at 7:47
A working group is being created by MMI to work on this issue
Original comment by ber...@gmail.com
on 27 May 2009 at 6:25
Original issue reported on code.google.com by
eric.bri...@gmail.com
on 9 Apr 2009 at 6:04