Custom Query (125 matches)


Show under each result:

Results (85 - 87 of 125)

Ticket Resolution Summary Owner Reporter
#106 invalid aneed additional area_types cf-conventions@… rhorne@…

The GOES-R system generates fire, aerosol, rainfall rate/quantity, and volcanic ash products. These products include summary (aggregate) statistics (min, max, mean, and std deviation) whose formal CDL/NcML specifications make use of the CF "cell_methods" attribute. These statistics are associated with areas where the following environment conditions apply:

(!) fire (2) smoke (3) dust (4) volcanic_ash (5) raining

The cell_methods attribute associated with these statistics could benefit by using the existing "where" clause that reference of the five environment conditions listed above.

As a result, we would like fire, smoke, dust, volcanic_ash, and raining to the area_type table.

very respectfully,


#109 fixed resolve inconsistency of positive and standard_name attributes davidhassell jonathan

John Graybeal raised the question of what happens if the positive and standard_name attributes of a vertical coordinate variable are inconsistent according to the definition of the latter e.g. if positive="up" and standard_name="depth", which is defined as vertical distance below the surface, implying that positive is down. Steve Hankin and I discussed this on the CF email list and further by email and phone. We would like to propose the following clarification, which should answer the question without materially changing the convention or invalidating existing data.

Append the following to the last paragraph (beginning "Optionally") of introductory part of Section 4.3 (before Section 4.3.1):

If both positive and standard_name are provided, it is recommended that they should be consistent. For instance, if a depth of 1000 metres is represented by -1000 and positive is up, it would be inconsistent to give the standard_name as depth, whose definition (vertical distance below the surface) implies positive down. If an application detects such an inconsistency, the user should be warned, and the positive attribute should be used to determine the sign convention.

Insert the following into Section 4.3 of the conformance document:


The positive attribute should be consistent with the sign convention implied by the definition of the standard_name, if both are provided.

There is no general way to check consistency at present.


#110 invalid test new installation cf-conventions@… painter1

This is a test of the new Trac installation - sorry to bother you!

Note: See TracQuery for help on using queries.