This message came from the CF Trac system. Do not reply. Instead, enter your comments in the CF Trac system at https://cf-pcmdi.llnl.gov/trac/.
#104: Clarify the interpretation of scalar coordinate variables -----------------------------+---------------------------------------------- Reporter: jonathan | Owner: [email protected] Type: enhancement | Status: new Priority: medium | Milestone: Component: cf-conventions | Version: Resolution: | Keywords: -----------------------------+---------------------------------------------- Comment (by caron): Hi David: Replying to [comment:41 davidhassell]: > Replying to [comment:40 caron]: > > Hello John, > > Thanks for this. It's definitely clarified things for me. I still bravely maintain that DSG is not affected ''logically'' by #104. I sympathize with your last example ("I don't like it because it makes it looks like a profile"), but surely the resemblance is passing, since the `featureType` attribute will be `"point"`, rather than `"profile"`, and extra dimensions are not prohibited. Is that right? no, its not really fatal, just an idiom that i like. but it does make me wonder if height is really an "independent" variable. if so, it would be nice to know more precisely what that means. Also, note that I am not reffering to the implications of DSG representation, just the way that one would do point data pre-DSG. > > > suppose that you are sampling at the same point. Its intuitive to indicate this using scalar coordinates: > > > {{{ > dimensions: > sample = 39238923; > variables: > float data(sample); > data:coordinates = "lat lon time"; > float lat; > float lon; > float time(sample); > }}} > > > > so here you are really doing a shorthand for lat(sample), lon(sample) indicating that these are constants. which is really useful to know. > > I like this example, but I don't understand how the scalar `lat` is shorthand for `lat(sample)` when `sample` = 39238923. Am I missing something? I just mean to say that by making it a scalar, you indicate that all the values of lat(39238923) would be identical if you made it into a dimensioned variable. So by looking at the "structural metadata" of the file, you know something thats very useful. Regards, John -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/104#comment:43> CF Metadata <http://cf-pcmdi.llnl.gov/> CF Metadata This message came from the CF Trac system. To unsubscribe, without unsubscribing to the regular cf-metadata list, send a message to "[email protected]" with "unsubscribe cf-metadata" in the body of your message.
