earthkit.data.core.fieldlist¶
Classes¶
Base class for a FieldList. |
Functions¶
|
Create a fieldlist object from the given fields. |
Module Contents¶
- class earthkit.data.core.fieldlist.FieldList(**kwargs)¶
Bases:
earthkit.data.sources.Source,earthkit.data.core.EncodableBase class for a FieldList.
A FieldList is a collection of Fields. It is an immutable object that provides methods to access the field values and metadata and allows iteration over the fields. It also provides methods to select a subset of fields based on their metadata.
Implementations¶
FieldList is an abstract class. All the concrete implementations are derived from
IndexFieldListBase. This class is formed by multiple inheritance with theIndexclass that implements indexing capabilities without specifying the actual indexed objects. It is still an abstract class but provides concrete implementations for many of the FieldList methods. It also implements fieldlist arithmetic.Some of the concrete implementations are:
EmptyFieldListis a FieldList implementation that contains no fields. It can be used when building fieldlists by concatenation. of a FieldList with no fields. It can be used when building fieldlists by concatenation.SimpleFieldList: a FieldList containing a list fields. Can be created from a list of fields byfrom_fieldsor the top level earthkit-datacreate_fieldlistfactory function.GribFieldListInFile: a FieldList containing fields from a GRIB file.XArrayFieldList: a FieldList containing fields from an xarray Dataset.
Creating a FieldList¶
A FieldList can be created by calling the
to_fieldlist()method of a high level data object, see Data objects for more details.A
SimpleFieldListcan also be created directly from a list of fields by calling thefrom_fields()method, or alternatively by calling the top level earthkit-datacreate_fieldlist()factory function.- abstractmethod batched(n)¶
Iterate through the fieldlist in batches of
nfields.- Parameters:
n (
int) – Batch size.- Returns:
Returns an iterator yielding batches of
nfields. Each batch is a new fieldlist containing a view to the data in the original object, so no data is copied. The last batch may contain fewer thannfields.- Return type:
object
- abstractmethod data(keys=('lat', 'lon', 'value'), flatten=False, dtype=None, index=None)¶
Return the values and/or the geographical coordinates.
Only works when all the fields have the same grid geometry.
- Parameters:
keys (
str,listortuple) – Specifies the type of data to be returned. Any combination of “lat”, “lon” and “value” is allowed here.flatten (
bool) – When it is True the “lat”, “lon” arrays and the “value” arrays per field will all be flattened. Otherwise they will preserve the field’sshape.dtype (
str,array.dtypeorNone) – Typecode or data-type of the arrays. When it isNonethe default type used by the underlying data accessor is used. For GRIB it isfloat64.index (
array indexing object, optional) – The index of the values to be extracted from each field. When it is None all the values are extracted.
- Returns:
The elements of the array (in the order of the
keys) are as follows:the latitudes array from the first field when “lat” is in
keysthe longitudes array from the first field when “lon” is in
keysa values array per field when “values” is in
keys
- Return type:
array-like- Raises:
ValueError – When not all the fields have the same grid geometry.
Examples
How-to examples:
GRIB: getting latitudes, longitudes and values (regular LL grid)
GRIB: getting latitudes, longitudes and values (reduced Gaussian grid)
More examples:
>>> import earthkit.data as ekd >>> fl = ekd.from_source("sample", "test6.grib").to_fieldlist() >>> len(fl) 6 >>> d = fl.data() >>> d.shape (8, 7, 12) >>> d[0, 0, 0] # first latitude 90.0 >>> d[1, 0, 0] # first longitude 0.0 >>> d[2:, 0, 0] # first value per field array([272.56417847, -6.28688049, 7.83348083, 272.53916931, -4.89837646, 8.66096497]) >>> d = fl.data(keys="lon") >>> d.shape (1, 7, 12) >>> d[0, 0, 0] # first longitude 0.0
- abstractmethod describe(*args, **kwargs)¶
Generate a summary of the fieldlist.
- static from_fields(fields=None)¶
Create a fieldlist from the given fields.
- Parameters:
fields (
iterable,Field,None) – Iterable ofFieldobjects. When it is None or empty, an empty fieldlist is returned.- Returns:
A fieldlist object containing the given fields. When
fieldsis None or empty, anEmptyFieldListis returned. Otherwise aSimpleFieldListis returned.- Return type:
- abstract property geography¶
Return the geography of the FieldList.
- Returns:
If the fields in the FieldList have the same grid geometry, the returned geography is the one of the first field. Otherwise an error is raised.
- Return type:
GeographyBase- Raises:
ValueError – When not all the fields have the same grid geometry or the FieldList is empty.
- abstractmethod get(keys, default=None, astype=None, raise_on_missing=False, output='auto', group_by_key=False, flatten_dict=False, remapping=None, patch=None)¶
Return values for the specified keys from all the fields.
- Parameters:
keys (
str,list,tuple) – Specify the field metadata keys to extract. Can be a single key (str) or multiple keys as a list/tuple of str. Keys are assumed to be of the form “component.key”. For example, “time.valid_datetime” or “parameter.name”. Keys from the raw field metadata (if any) can be accessed using the “metadata.key” syntax. For example, when aFieldwas created from a GRIB message, the ecCodes GRIB keys can be accessed as “metadata.shortName” or “metadata.level”.default (
Any,None) – Specify the default value(s) forkeys. Returned when the given key is not found andraise_on_missingis False. Whendefaultis a single value, it is used for all the keys. Otherwise it must be a list/tuple of the same length askeys.astype (
type as str,intorfloat) – Return type forkeys. Whenastypeis a single type, it is used for all the keys. Otherwise it must be a list/tuple of the same length askeys.raise_on_missing (
bool) – When True, raises KeyError if any ofkeysis not found.output (
type,str) –Specify the output structure type in conjunction with
group_by_key. Whengroup_byis False (default) the output is a list with one item per field andoutputhas the following effect on the items:- ”auto” (default):
when
keysis a str returns a single value per fieldwhen
keysis a list/tuple returns a list/tuple of values per field
list or “list”: returns a list of values per field.
tuple or “tuple”: returns a tuple of values per field.
dict or “dict”: returns a dictionary with keys and their values per field.
When
group_by_keyis True the output is grouped by key and return an object with one item per key. The item per key contains the list of values for that key from all the fields. Whenoutputis “dict” a dict is returned, otherwise a list.group_by_key (
bool) – When True the output is grouped by key as described inoutput.flatten_dict (
bool) – When True andoutputis dict, for each field if any of the values in the returned dict is itself a dict, it is flattened to depth 1 by concatenating the keys with a dot. For example, if the returned dict is{"a": {"x": 1, "y": 2}, "b": 3}, it becomes{"a.x": 1, " a.y": 2, "b": 3}. This option is ignored whenoutputis not dict.remapping (
dict, optional) –Create new metadata keys from existing ones. E.g. to define a new key “param_level” as the concatenated value of the “parameter.variable” and “vertical.level” keys use:
remapping={"param_level": "{parameter.variable}{vertical.level}"}
patch (
dict, optional) – A dictionary of patch to be applied to the returned values.
- Returns:
The returned value depends on the
outputandgroup_by_keyparameters. See above.- Return type:
list,dict- Raises:
KeyError – If
raise_on_missingis True and any ofkeysis not found.
Examples
>>> import earthkit.data as ekd >>> fl = ekd.from_source("sample", "test.grib").to_fieldlist() >>> fl.get("parameter.variable") ['2t', 'msl'] >>> fl.get(["parameter.variable", "parameter.units"]) [('2t', 'K'), ('msl', 'Pa')] >>> fl.get(("parameter.variable", "parameter.units")) [['2t', 'K'], ['msl', 'Pa']]
- graph(depth=0)¶
- abstractmethod group_by(*keys, sort=True)¶
Iterate through the fieldlist in groups defined by metadata keys.
- Parameters:
*keys (
tuple) – Positional arguments specifying the metadata keys to group by. Keys can be a single or multiple str, or a list or tuple of str.sort (
bool, optional) – IfTrue(default), the fieldlist is sorted by the metadatakeysbefore grouping.
- Returns:
Returns an iterator yielding batches of fields grouped by the metadata
keys. Each batch is a new fieldlist containing a view to the data in the original object, so no data is copied. It generates a new group every time the value of thekeyschange.- Return type:
object
- abstractmethod head(n=5, **kwargs)¶
Generate a list like summary of the first
nfields.Same as calling
lswithn.- Parameters:
n (
int,None) – The number of fields (n> 0) to be printed from the front.**kwargs (
dict, optional) – Other keyword arguments passed tols.
- Returns:
See
ls.- Return type:
Pandas DataFrame
Notes
The following calls are equivalent:
fl.head() fl.head(5) fl.head(n=5) fl.ls(5) fl.ls(n=5)
- ignore()¶
Indicates to ignore this source in concatenation/merging.
- Return type:
bool
- abstractmethod ls(n=None, keys='default', extra_keys=None, collections=None)¶
Generate a list like summary using a set of metadata keys.
- Parameters:
n (
int,None) – The number of fields to be listed. None means all the fields,n > 0means fields from the front, whilen < 0means fields from the back of the fieldlist.keys (
listofstr,dict,None) – The metadata keys to extract. Ifkeys="default", a built-in default set of keys is used. To specify a column title for each key in the output use a dict as a mapping from the keys to the column titles.extra_keys (
listofstr,dict,None) – List of additional keys on top ofkeys. To specify a column title for each key in the output use a dict as a mapping from the keys to the column titles.collections (
str,listofstr,None) – The collections to extract. Can be a single collection (str) or multiple collections as a list of str. A collection is a component of the field (e.g. “time”, “parameter”, “geography”, etc.) as a dictionary. It can also be a collection within the raw “metadata” component. For example, when aFieldwas created from a GRIB message, the ecCodes GRIB “namespaces” can be accessed as collections, e.g. “metadata.mars” means the ecCodes GRIB “mars” namespace.
- Returns:
DataFrame with one row per
Field.- Return type:
Pandas DataFrame
- abstractmethod metadata(*args, **kwargs)¶
Return the raw metadata values for each field.
- Parameters:
*args (
tuple) – Positional arguments defining the metadata keys. Passed toField.metadata()**kwargs (
dict, optional) – Keyword arguments passed toField.metadata()
- Returns:
List with one item per
Field- Return type:
list
Examples
>>> import earthkit.data as ekd >>> fl = ekd.from_source("sample", "test.grib").to_fieldlist() >>> fl.metadata("param") ['2t', 'msl'] >>> fl.metadata("param", "units") [('2t', 'K'), ('msl', 'Pa')] >>> fl.metadata(["param", "units"]) [['2t', 'K'], ['msl', 'Pa']]
- mutate()¶
- mutate_source()¶
- name = None¶
- abstractmethod order_by(*args, remapping=None, patch=None, **kwargs)¶
Change the order of the fields in a fieldlist.
- Parameters:
*args (
tuple) – Positional arguments specifying the metadata keys to perform the ordering on. Each argument can be a single key (str) or multiple keys as a list/tuple of str or a dictionary. Any metadata keys thatearthkit.data.core.field.Field.get()accepts can be used here. The order of the keys defines the priority of the ordering. When a dictionary is used it must specify the ordering direction or the order of the values for each key. The ordering direction can be either “ascending” or “descending” (the default is “ascending”). The order of values for a key is defined by a list of values for that key, which must include all the available values for that key in the fieldlist. See the examples below for more details.remapping (
dict) –Define new metadata keys from existing ones to use in
*argsand**kwargs. E.g. to define a new key “param_level” as the concatenated value of the “parameter.variable” and “vertical.level” keys use:remapping={"param_level": "{parameter.variable}{vertical.level}"}
See below for a more elaborate example.
**kwargs (
dict, optional) – Other keyword arguments specifying the metadata keys to perform the ordering on. Used in the same way as a dictionary in*args.
- Returns:
Returns a MaskFieldList with the reordered fields. It provides a view to the data in the original object, so no data is copied. When called without any arguments it returns the original fieldlist.
- Return type:
MaskFieldList,FieldList
Examples
How-to examples:
Ordering by a single metadata key (“parameter.variable”). The default ordering direction is
ascending:>>> import earthkit.data as ekd >>> fl = ekd.from_source("sample", "test6.grib").to_fieldlist() >>> for f in fl.order_by("parameter.variable"): ... print(f) ... Field(t,850,20180801,1200,0,0) Field(t,1000,20180801,1200,0,0) Field(u,850,20180801,1200,0,0) Field(u,1000,20180801,1200,0,0) Field(v,850,20180801,1200,0,0) Field(v,1000,20180801,1200,0,0)
Ordering by multiple keys (first by “vertical.level” then by “parameter.variable”). The default ordering direction is
ascendingfor both keys:>>> for f in fl.order_by(["vertical.level", "parameter.variable"]): ... print(f) ... Field(t,850,20180801,1200,0,0) Field(u,850,20180801,1200,0,0) Field(v,850,20180801,1200,0,0) Field(t,1000,20180801,1200,0,0) Field(u,1000,20180801,1200,0,0) Field(v,1000,20180801,1200,0,0)
Specifying the ordering direction:
>>> for f in fl.order_by( ... {"parameter.variable": "ascending", "vertical.level": "descending"} ... ): ... print(f) Field(t,1000,20180801,1200,0,0) Field(t,850,20180801,1200,0,0) Field(u,1000,20180801,1200,0,0) Field(u,850,20180801,1200,0,0) Field(v,1000,20180801,1200,0,0) Field(v,850,20180801,1200,0,0)
Using the list of all the values of a key (“parameter.variable”) to define the order:
>>> for f in fl.order_by({"parameter.variable": ["u", "t", "v"]}): ... print(f) Field(u,1000,20180801,1200,0,0) Field(u,850,20180801,1200,0,0) Field(t,1000,20180801,1200,0,0) Field(t,850,20180801,1200,0,0) Field(v,1000,20180801,1200,0,0) Field(v,850,20180801,1200,0,0)
Using
remappingto specify the order by a key created from two other keys (we created key “param_level” from “parameter.variable” and “vertical.level”):>>> ordering = ["t850", "t1000", "u1000", "v850", "v1000", "u850"] >>> remapping = {"param_level": "{parameter.variable}{vertical.level}"} >>> for f in fl.order_by({"param_level": ordering}, remapping=remapping): ... print(f) Field(t,850,20180801,1200,0,0) Field(t,1000,20180801,1200,0,0) Field(u,1000,20180801,1200,0,0) Field(v,850,20180801,1200,0,0) Field(v,1000,20180801,1200,0,0) Field(u,850,20180801,1200,0,0)
- property parent¶
The parent source, if any.
- abstractmethod sel(*args, remapping=None, **kwargs)¶
Select the fields matching the given metadata conditions.
- Parameters:
*args (
tuple) –Positional arguments specifying the filter conditions as a dict. Both single or multiple keys are allowed to use. When multiple filter conditions are specified, they are combined with a logical AND operator. Each metadata key in the filter conditions can specify the following type of filter values:
single value:
fl.sel({parameter.variable: "t"})
list of values:
fl.sel({parameter.variable: ["u", "v"]})
slice of values (defines a closed interval, so treated as inclusive of both the start
and stop values, unlike normal Python indexing). The following example filters the fields with “vertical.level” between 300 and 500 inclusively:
fl.sel({vertical.level: slice(300, 500)})
Date and time related keys from the “time” field component are automatically normalised for comparison. This is also applied to the following keys from the raw metadata: “metadata.base_datetime”, “metadata.valid_datetime” and “metadata.step_timedelta”.
For example, when filtering by “time.valid_datetime” the following calls are equivalent:
>>> fl.sel({ "time.valid_datetime": "2018-08-01T12:00:00"}) >>> fl.sel({ "time.valid_datetime": datetime(2018, 8, 1, 12, 0) })
Similarly, when filtering by “time.step” the following calls are equivalent (values are assumed to be in hours when the unit is not specified):
>>> fl.sel({ "time.step": "6h"}) >>> fl.sel({ "time.step": 6}) >>> fl.sel({ "time.step": "360m"}) >>> fl.sel({ "time.step": timedelta(hours=6)})
remapping (
dict) –Define new metadata keys from existing ones to use in
*argsand**kwargs. E.g. to define a new key “param_level” as the concatenated value of the “parameter.variable” and “vertical.level” keys use:>>> remapping={"param_level": "{parameter.variable}{vertical.level}"}
See below for a more elaborate example.
**kwargs (
dict, optional) – Other keyword arguments specifying the filter conditions.
- Returns:
Returns a MaskFieldList with the reordered fields. It provides a view to the data in the original object, so no data is copied. When called without any arguments it returns the original fieldlist.
- Return type:
MaskFieldlist,FieldList
Examples
How-to examples:
More examples:
>>> import earthkit.data as ekd >>> fl = ekd.from_source("sample", "tuv_pl.grib").to_fieldlist() >>> len(fl) 18
Selecting by a single key (“parameter.variable”) with a single value:
>>> fl1 = fl.sel({parameter.variable: "t"}) >>> for f in fl1: ... print(f) ... Field(t,1000,20180801,1200,0,0) Field(t,850,20180801,1200,0,0) Field(t,700,20180801,1200,0,0) Field(t,500,20180801,1200,0,0) Field(t,400,20180801,1200,0,0) Field(t,300,20180801,1200,0,0)
Selecting by multiple keys (“parameter.variable”, “vertical.level”) with a list and slice of values:
>>> fl1 = fl.sel( ... {parameter.variable: ["u", "v"], vertical.level: slice(400, 700)} ... ) >>> for f in fl1: ... print(f) ... Field(u,700,20180801,1200,0,0) Field(v,700,20180801,1200,0,0) Field(u,500,20180801,1200,0,0) Field(v,500,20180801,1200,0,0) Field(u,400,20180801,1200,0,0) Field(v,400,20180801, 1200,0,0)
Using
remappingto specify the selection by a key created from two other keys (we created key “param_level” from “parameter.variable” and “vertical.level”):>>> fl1 = fl.sel( ... param_level=["t850", "u1000"], ... remapping={"param_level": "{parameter.variable}{vertical.level}"}, ... ) >>> for f in fl1: ... print(f) ... Field(u,1000,20180801,1200,0,0) Field(t,850,20180801,1200,0,0)
- set(*args, **kwargs)¶
Set the metadata values for each field.
All the arguments are passed to
earthkit.data.core.field.Field.set()for each field in the fieldlist.- Parameters:
*args (
tuple) – Positional arguments defining the metadata keys and values.**kwargs (
dict, optional) – Keyword arguments defining the metadata keys and values.
- Returns:
New FieldList with the updated metadata values.
- Return type:
See also
- source_filename = None¶
- abstractmethod tail(n=5, **kwargs)¶
Generate a list like summary of the last
nfields.Same as calling
lswith-n.- Parameters:
n (
int,None) – The number of fields (n> 0) to be printed from the back.**kwargs (
dict, optional) – Other keyword arguments passed tols.
- Returns:
See
ls.- Return type:
Pandas DataFrame
Notes
The following calls are equivalent:
fl.tail() fl.tail(5) fl.tail(n=5) fl.ls(-5) fl.ls(n=-5)
- abstractmethod to_array(**kwargs)¶
Return the values of all the fields as an array.
It is formed as the array of the
earthkit.data.core.field.Field.to_arrayvalues per field.- Parameters:
flatten (
bool) – When it is True the values are flattened per field. Otherwise an array with the field’sshapeis returned per field.dtype (
str,array.dtypeorNone) – Typecode or data-type of the array. When it isNonethe default type used by the underlying data accessor is used. For GRIB it isfloat64.copy (
bool) – When it is True a copy of the data values per field is returned. Otherwise a view is returned where possible.array_namespace (
str,array_namespaceorNone) – The array namespace to be used. When it isNonethe underlying array format of the field is used. For GRIB it is “numpy”.device (
strorNone) – The device where the array will be allocated. When it isNonethe default device is used.index (
array indexing object, optional) – The index of the values to be extracted per field. When it is None all the values are extracted. is None all the values are extracted.
- Returns:
Array containing the field values. It is formed as the array of values extracted by
earthkit.data.core.field.Field.to_arrayper field.- Return type:
array-like
Examples
How-to examples:
- abstractmethod to_cube(*args, **kwargs)¶
Convert to a cube-like structure.
This method is intended to support fieldlist usage in the
anemoi-datasetspackage. Planned to be removed in the future and useto_tensorinstead.
- abstractmethod to_fieldlist(array_namespace=None, device=None, flatten=False, dtype=None)¶
Change how the values stored in each field in a fieldlist.
This method converts the data values in each field to an array with a given
array_namespaceand/ordevice. The resulting fieldlist is then composed of the converted fields. The field values are extracted using theearthkit.data.core.field.Field.to_array()method of each field.When a field already stores its values as an array with a matching
array_namespaceanddevice, a copy of that array is made and stored in the resulting field. This means that even if called without any arguments, the resulting fieldlist will have its own copy of the data values.The primary use of this method is to convert the values in GRIB fields loaded from disk to in-memory arrays. By default, the values in GRIB fields loaded from disk are not stored as arrays in memory, but rather as references to the on-disk data. This allows for efficient access to the data without loading it all into memory at once. However, in some cases it may be desirable to convert these values to in-memory arrays for faster access or for compatibility with other libraries. This method provides a way to do that while preserving the metadata of the fields.
- Parameters:
array_namespace (
str,array_namespaceorNone) – The array namespace to be used for the field values in the resulting fieldlist. When it is None, the default array namespace used by the underlying data accessor of the field is used. For GRIB it is “numpy”.device (
strorNone) – The device where the array will be allocated. When it isNonethe default device is used.flatten (
bool) – When it is True the values are flattened per field. Otherwise the array will have the field’sshapeper field.dtype (
str,array.dtypeorNone) – Typecode or data-type of the array. When it isNonethe default type used by the underlying data accessor per field is used. For GRIB it isfloat64.
- Returns:
New fieldlist formed from the converted fields.
- Return type:
SimpleFieldList
Examples
How-to examples:
The following example will convert a fieldlist read from a GRIB file into a
SimpleFieldListstoring data values as single precision arrays in each field.>>> import numpy as np >>> import earthkit.data as ekd >>> fl = ekd.from_source("sample", "tuv_pl.grib").to_fieldlist() >>> r = fl.to_fieldlist(array_namespace="numpy", dtype=np.float32) >>> r.to_numpy().dtype dtype('float32')
- abstractmethod to_numpy(flatten=False, dtype=None, copy=True, index=None)¶
Return the values of all the fields as a Numpy array.
- Parameters:
flatten (
bool) – When it is True the values are flattened per field. Otherwise an ndarray with the field’sshapeis returned per field.dtype (
str,numpy.dtypeorNone) – Typecode or data-type of the array. When it isNonethe default type used by the underlying data accessor of the field is used. For GRIB it isfloat64.copy (
bool) – When it is True a copy of the data values per field is returned. Otherwise a view is returned where possible.index (
ndarray indexing object, optional) – The index of the values to be extracted per field. When it is None all the values are extracted.
- Returns:
Array containing the field values. It is formed as the array of values extracted by
earthkit.data.core.field.Field.to_numpyper field.- Return type:
ndarray
Examples
How-to examples:
- abstractmethod to_target(target, *args, **kwargs)¶
- abstractmethod to_tensor(*args, **kwargs)¶
Convert to a tensor-like structure.
This method is intended to use internally to support the Xarray engine, which converts fieldlist to a tensor-like structure before converting it to an Xarray Dataset or DataArray.
- abstractmethod unique(*args, sort=False, drop_none=True, squeeze=False, unwrap_single=False, remapping=None, patch=None, cache=True, progress_bar=False)¶
Return the unique values for a given set of metadata keys.
- Parameters:
*args (
tuple) – Positional arguments specifying the metadata keys to collect unique values for.sort (
bool, optional) – Whether to sort the collected unique values. Default is False.drop_none (
bool, optional) – Whether to drop None values from the collected unique values. Default is True.squeeze (
bool, optional) – When True only returns the metadata keys that have more than one values. Default is False.unwrap_single (
bool, optional) – When True and only one metadata key is specified, the unique values are returned as a tuple instead of a dict. Default is False.remapping (
dict, optional) – A dictionary for remapping keys or values during collection. Default is None.patch (
dict, optional) – A dictionary for patching key values during collection. Default is None.cache (
bool, optional) – Whether to use an a cache attached to the fieldlist for previously collected unique values. Default is True.progress_bar (
bool, optional) – Whether to display a progress bar during collection. Default is False.
- Returns:
A dictionary containing the unique values for the specified metadata keys.
- Return type:
dict
- abstract property values¶
Return the values of all the fields as a 2D array.
- Returns:
Array containing the values of all the fields. The return array is formed as the array of the flattened values extracted from each field by
Field.values.- Return type:
array-like
Examples
>>> import earthkit.data as ekd >>> fl = ekd.from_source("sample", "test.grib").to_fieldlist() >>> for f in fl: ... print(f.values.shape) ... (209,) (209,) >>> v = fl.values >>> v.shape (2, 209) >>> v[0][:3] array([262.78027344, 267.44726562, 268.61230469])
- earthkit.data.core.fieldlist.create_fieldlist(fields=None)¶
Create a fieldlist object from the given fields.
- Parameters:
fields (
iterable,Field,None) – Iterable ofFieldobjects. When it is None or empty, an empty fieldlist is returned.- Returns:
A fieldlist object containing the given fields. When
fieldsis None or empty, anEmptyFieldListis returned. Otherwise aSimpleFieldListis returned.- Return type: