@JonathanGregory thanks for these improvements! > Since you too find the terms not obvious, maybe it would help the reader to > acknowledge this, for instance by appending a sentence after "so that order > of operations is essential in achieving accurate results", such as "(The two > axes are conventionally called the sweep-angle and fixed-angle axes; we > adhere to this terminology, although many find these terms rather > confusing.)" Then at least the reader won't be surprised to be confused.
I've phrased this as follows in cfb37b1: > The two axes are conventionally called the sweep-angle and fixed-angle axes; > we adhere to this terminology, although some find these terms confusing, for > the sake of interoperability with existing implementations. > The diagram in the PROJ document is helpful and it's fine to leave it there. > I didn't look at it the first time because it sounded as though it was just > about the software. Could you rephrase this sentence as "Explanatory diagrams > for the projection may be found on the PROJ website, as well as notes on > using the PROJ software for computing the mapping"? Done in 0f1f8f39. > The `sweep_angle_axis` and `fixed_angle_axis` attributes should be added to > Table F.1; `perspective_point_height` is already there. In the table, you can > state their two possible values and that each is optional if the other is > present. Done in dd75623. > In general CF attributes with a prescribed list of possible values are > regarded as case-insensitive, for ease of use of the convention, since > insisting on either upper or lower case will probably mean some people will > write incorrect files. I think we may have a general statement about that > somewhere. If your x and y are case-insensitive, it would be helpful to say > so. Done in 9511395. Best regards, Daniel -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/258#issuecomment-626570955 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
