We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At the moment we can access latitudes/longitudes on a GribField as follows (ds is a FieldList in the examples below):
ds
This call returns a dict: {"lat": array, "lon": array}
{"lat": array, "lon": array}
ds[0].to_latlon()
This call returns a tuple (lat-array, lon-array):
(lat-array, lon-array)
ds[0].data(["lat", "lon"])
This call returns only the latitudes (as an array):
ds[0].data("lat")
We can even use metadata to get the latitudes, though this type of usage should be discouraged:
metadata
ds[0].metadata("latitudes")
On a FieldList we can only call metadata out of these methods, which would return a list of arrays (one per GribField):
ds.metadata("latitudes")
The following questions arise:
latitudes
longitudes
to_latlon
data
The text was updated successfully, but these errors were encountered:
No branches or pull requests
At the moment we can access latitudes/longitudes on a GribField as follows (
ds
is a FieldList in the examples below):This call returns a dict:
{"lat": array, "lon": array}
This call returns a tuple
(lat-array, lon-array)
:This call returns only the latitudes (as an array):
We can even use
metadata
to get the latitudes, though this type of usage should be discouraged:On a FieldList we can only call
metadata
out of these methods, which would return a list of arrays (one per GribField):The following questions arise:
latitudes
andlongitudes
to GribField?to_latlon
to FieldList?data
to FieldList?latitudes
andlongitudes
(if we implement them on GribField) to FieldList?The text was updated successfully, but these errors were encountered: