a iDfb@sddlmZddlZddlZddlmZddlmZdZ hdZ ddddd d d Z d Z d Z d dZddZddZddZddZddZddZdS)) annotationsN)coding)Variablez_.@+- !"#$%&\()*,:;<=>?[]^`{|}~> int64byteuint64floatdoublerealZushortcharshortboolstringintZuintint32int16Zint8)rrZuint32Zuint16Zuint8r utf-8adcould not safely cast array from {dtype} to {new_dtype}. While it is not always the case, a common reason for this is that xarray has deemed it safest to encode np.datetime64[ns] or np.timedelta64[ns] values with int64 values representing units of 'nanoseconds'. This is either due to the fact that the times are known to require nanosecond precision for an accurate round trip, or that the times are unknown prior to writing due to being contained in a chunked array. Ways to work around this are either to use a backend that supports writing int64 values, or to manually specify the encoding['units'] and encoding['dtype'] (e.g. 'seconds since 1970-01-01' and np.dtype('int32')) on the time variable(s) such that the times can be serialized in a netCDF3 file (note that depending on the situation, however, this latter option may result in an inaccurate round trip).cCsJt|j}|tvrFt|}||}||ksBttj||d|}|S)aCoerce an array to a data type that can be stored in a netCDF-3 file This function performs the dtype conversions as specified by the ``_nc3_dtype_coercions`` mapping: int64 -> int32 uint64 -> int32 uint32 -> int32 uint16 -> int16 uint8 -> int8 bool -> int8 Data is checked for equality, or equivalence (non-NaN values) using the ``(cast_array == original_array).all()``. )dtype new_dtype)strr_nc3_dtype_coercionsZastypeall ValueErrorCOERCION_VALUE_ERRORformat)ZarrrrZcast_arrrd/nfs/NAS7/SABIOD/METHODE/ermites/ermites_venv/lib/python3.9/site-packages/xarray/backends/netcdf3.pycoerce_nc3_dtype>s    rcCsFt|tr n6t|tr"|t}n tt|}|jdkrBt d|S)Nz'netCDF attributes must be 1-dimensional) isinstancebytesrencodeSTRING_ENCODINGrnpZ atleast_1dndimr)valuerrrencode_nc3_attr_valueZs    r&cCsdd|DS)NcSsi|]\}}|t|qSr)r&).0kvrrr gz$encode_nc3_attrs..)items)attrsrrrencode_nc3_attrsfsr.cCsl|j}|jjdvrh|jdd}|durhtj|rh|t tj j k}| rht ||jdtj|}|S)NiuunitsZ _FillValue)datarkindr-getr variablesZ _is_time_liker#Ziinforminanywherenan)varr1r0maskrrr_maybe_prepare_timesjs  r;cCsTtjjddtjfD]}||}qt|}t|}t|j}t |j |||j S)NF)Zallows_unicode) rstringsZEncodedStringCoderZCharacterArrayCoderr!r;rr.r-rdimsencoding)r9Zcoderr1r-rrrencode_nc3_variablezs   r?cCs|pt|ddkS)zrReturn True if the given UTF-8 encoded character is alphanumeric or multibyte. Input is not checked! rr)isalnumlenr!)crrr _isalnumMUTF8srCcCszt|tsdSt|d}td||kox|tvox|dkoxd|vox|ddkoxt|dsh|ddkoxtd d |DS) arTest whether an object can be validly converted to a netCDF-3 dimension, variable or attribute name Earlier versions of the netCDF C-library reference implementation enforced a more restricted set of characters in creating new names, but permitted reading names containing arbitrary bytes. This specification extends the permitted characters in names to include multi-byte UTF-8 encoded Unicode and additional printing characters from the US-ASCII alphabet. The first character of a name must be alphanumeric, a multi-byte UTF-8 character, or '_' (reserved for special names with meaning to implementations, such as the "_FillValue" attribute). Subsequent characters may also include printing special characters, except for '/' which is not allowed in names. Names that have trailing space characters are also not permitted. FrNFCr/ _css|]}t|p|tvVqdS)N)rC _specialchars)r'rBrrr r+z$is_valid_nc3_name..) rrrAr! unicodedata normalize_reserved_namesrCr)s num_bytesrrris_valid_nc3_names   rP) __future__rrKnumpyr#ZxarrayrZxarray.core.variablerrIrMrr"rrr&r.r;r?rCrPrrrrs.