v0.9.8

improve raw noise vectors mapping in xsar datatree see #143

v0.9.7

add noise Look of Tables mapped in datatree as they are stored in the xml annotations files.
see #141

v0.9.6

fix for attributes of the datatree

v0.9.5

fix FRAME of orbit missing, and change type of definition attr in geolocation_annotation dataset

v0.9.4

fix missing variable lineSpacing and sampleSpacing

v0.9.3

fix issue with method Sentinel1Dataset.get_ll_from_SLC_geoloc() see #131

v0.9.2

• add capability to get geolocation fields at specific image coordinates without loading full HR variable
• add lazy_loading option to turn "on" of "off" the map_block_coords() mechanism that currently suffer memory leak
• add load_luts option to turn "on" of "off" the decoding and rasterization of LUTs.
• prevent the usage of resolution when reading a IW or EW SLC product (this feature is out of scope for xsar)

v0.9.1

• add land mask suitable for SLC products (compute burst by burst)
• fix re-projection issue with rasterio==1.3.3

v0.9 xsar with datatree

What's Changed

This new 2022 release will provide the users a nice overview of the mapped SAR Sentinel-1 product into xarray-datatree to support groups/nodes of variables.
The original xarray.Dataset containing the high resolution variables is still available for users but extra xarray.Dataset from .xml annotations are now provided to the users. These annotations are :

• Doppler estimates,
• bursts information,
• image information,
• low resolution geo-location,
• FM rate information,
• ...etc...

Rationales

The main motivations for this release are:

• making xsar outputs more self discoverable
• starting to separate as much as possible the decoding of the SAR product and the "interpretation layer" (i.e. interpolation, calibration denoising). In particular this release will enable expert SAR users to perform their own operations on the data using directly the annotations.
• keeping the traceability of each variable in xsar using:
  • the attributes origin (xpath),
  • the .xsd files to have official ESA definition of variables
  • keeping the exact same names for the variables

Disclaimer

For now the datatree v0.0.9 is not supporting the double mutability, it means that only the changes in the datatree will affect the datasets but opposite way is not yet supported (see: xarray-contrib/datatree#80 ).
It means that modifications done on thedatasets should be assign explicitely with such syntaxe:
datatree['measurement'] = datatree['measurement'].assign(dataset)

Contributors

@agrouaze , thanks to @keewis for his hints and to @lanougue for his feedbacks

v0.8.3

What's Changed

• use s1meta.pixel_axtrack_m for Sentinel1Dataset.pixel_axtrack_m by @oarcher in #102

Full Changelog: v0.8.2...v0.8.3