@erget Thanks!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/issues/253#issuecomment-625843902
This list forwards relevant notifications from Github. It is distinct from
Would someone be willing to moderate this issue? Three weeks without objections
have passed but we are missing a moderator. Thanks in advance.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@JimBiardCics Thanks for the feedback. Actually, its urban atmospheric model
data with resolved buildings. The grid is often aligned to the building
structure. Therefore, the grid orientation considerably depends on the city or
district in focus. But, I just help formatting/processing the data
> How are the wind components oriented along non-physical axes?
Depends on the definition of a physical axis ... . The physical meaning depends
on the values of `x(i,j)` and `y(i,j)`.
* The wind flows along the grid points defined by `x(i,j)` and `y(i,j)`. `x`
and `y` span up an arbitrary
@JimBiardCics No: no physical representation. I just added them because the two
wind components are oriented along these axes. The `axis` attribute should be
attached to them as I learned above.
```
int i(i) ;
i:axis = "X" ;
...
int j(j) ;
j:axis = "Y" ;
...
```
--
You are
Hi Bert,
sorry, I miss-read your post and the one of Martin. Thanks for the
clarification.
Daniel
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
In a current project, we have a similiar use case as @hrajagers : our projected
x/y coordinates depend on two dimensions. Our wind `x_wind` and `y_wind` blows
along the coordinate axes (the 1d-ones).
```
int i(i) ;
...
int j(j) ;
...
double x(j, i) ;
x:standard_name =
See issue #253 for discussion of these changes in [Appendix F: Grid
Mappings](http://cfconventions.org/Data/cf-conventions/cf-conventions-1.8/cf-conventions.html#appendix-grid-mappings)
of the CF Conventions:
* Replace `PROJ.4` by `PROJ`.
* Replace `http://proj4.org/projections/` by
# Title
PROJ.4 has advanced to PROJ v7: update Appendix F accordingly
# Moderator
@user
# Requirement Summary
The current name of the `PROJ` package should be used which is not `PROJ.4`
anymore (although `PROJ.4` was better to search for than `PROJ` ... .). URLs to
external sites should work.
@taylor13 : Thanks for the feedback. If it is clearer on the first view, I
could adapt the original figure to be like the first figure in my last comment
-- printing `(lon_bnds_n, lat_bnds_n)`-tuples at the vertices and writing
`lon_bnds_n = lon_bnds(i, j, n), ...` at the top.
--
You are
@taylor13
Maybe this figures shows clearer what I mean?
![coordinates_lonlat2](https://user-images.githubusercontent.com/29165465/76023046-af252880-5f28-11ea-9905-18db086b7cda.png)
lon1, lon2, ... actually mean lon_bnd1, lon_bnds2, ... .
For my example I assume that we have some grid, which
Unfortunately, we did not assign a moderator here so that this issue was
forgotten. Are there any caveats including these figures into the CF
conventions?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@erget : Sorry for the delay. I forget to upload the files in the end of last
week.
Attached a netCDF (als zip archive) and a CDL file (with `txt` ending).
[example_file_cf_issue_212.zip](https://github.com/cf-convention/cf-conventions/files/4128680/example_file_cf_issue_212.zip)
Excuse me that I did not provide a file. I will add a file until end of this
week.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/issues/212#issuecomment-576712516
This list
> I'm starting the 3 weeks timer, after which I will merge provided that a
> sample file has been provided (@neumannd can you please do this?) and [...].
@erget: Do you mean a sample netCDF file that is uses this new feature (some
projection information with `false_easting = 0` and
@erget: Thanks for the info. I updated the text accordingly.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/pull/225#issuecomment-572075650
This list forwards relevant
@marqh I will create a pull request the next days and submit it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/issues/212#issuecomment-571222577
This list forwards relevant
One minor comment on whether to run Trac and GitHub tickets in parallel or not:
Most of us are registered at various web services and need to remember/save the
login details for these services. Using Trac and GitHub in parallel for a long
time period means for us to have two logins detail sets
I just realized that netCDF also has its own DOI as mentioned here:
https://www.unidata.ucar.edu/software/netcdf/docs/faq.html#How-should-I-cite-use-of-netCDF-software
It is written (if the URL does not work at some point in the future):
```
The registered Digital Object Identifier for all
19 matches
Mail list logo