aresys-io 1.0.0__tar.gz

aresys_io-1.0.0/.gitignore

@@ -0,0 +1,197 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm-project.org/#use-with-ide
+.pdm.toml
+.pdm-python
+.pdm-build/
+pdm.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Distribution / packaging
+build/
+_build/
+dist/
+*.egg-info/
+.ipynb_checkpoints/
+.nox
+
+# Pyenv
+.python-version
+
+# VS Code project settings
+.vscode
+
+# PyCharm project settings
+.idea
+
+# Spyder project settings
+.spyproject
+
+# Environments
+venv*
+
+# Docker
+docker-compose.yml
+Dockerfile
+.devcontainer
+
+# Other
+*.bak
+.coverage
+htmlcov
+*.svg

aresys_io-1.0.0/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (C) Aresys S.r.l. <info@aresys.it>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

aresys_io-1.0.0/PKG-INFO

@@ -0,0 +1,121 @@
+Metadata-Version: 2.5
+Name: aresys_io
+Version: 1.0.0
+Summary: Python library for reading and writing Aresys EO/SAR product formats.
+Project-URL: Homepage, https://github.com/aresys-srl/aresys_io
+Project-URL: Repository, https://github.com/aresys-srl/aresys_io
+Project-URL: Documentation, https://opensource.aresys.it/aresys_io
+Author-email: "Aresys S.R.L." <info@aresys.it>
+License: MIT License
+        
+        Copyright (C) Aresys S.r.l. <info@aresys.it>
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+License-File: LICENSE.txt
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Education
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Natural Language :: English
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Utilities
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: lxml
+Requires-Dist: numpy>2
+Requires-Dist: numpydantic
+Requires-Dist: perseo-core
+Requires-Dist: pydantic
+Requires-Dist: scipy
+Requires-Dist: xsdata>=26.2
+Provides-Extra: dev
+Requires-Dist: ruff>=0.16.7; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: mkdocstrings-python; extra == 'docs'
+Requires-Dist: zensical; extra == 'docs'
+Provides-Extra: test
+Requires-Dist: pytest; extra == 'test'
+Requires-Dist: pytest-cov; extra == 'test'
+Provides-Extra: typecheck
+Requires-Dist: pyrefly==1.1.0; extra == 'typecheck'
+Requires-Dist: scipy-stubs; extra == 'typecheck'
+Description-Content-Type: text/markdown
+
+# Aresys Formats Input/Output (aresys_io)
+
+![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11%20%7C%203.12%20%7C%203.13%20%7C%203.14-blue)](https://python.org)
+[![PyPI - Version](https://img.shields.io/pypi/v/aresys_io)](https://pypi.org/project/aresys_io/)
+[![aresys-io CI](https://github.com/aresys-srl/aresys_io/actions/workflows/aresys_io.yml/badge.svg)](https://github.com/aresys-srl/aresys_io/actions/workflows/aresys_io.yml)
+
+**Aresys I/O (`aresys_io`)** is the official Aresys Python library for reading, writing, and manipulating Aresys Earth Observation (EO) and Synthetic Aperture Radar (SAR) product formats.
+
+Designed to be modular, independent, and extensible, `aresys_io` provides unified data access and metadata management across the entire SAR processing and simulation pipeline. It is built to integrate with [**PERSEO**](https://github.com/aresys-srl/perseo) ([docs](https://opensource.aresys.it/perseo)), the Aresys modular framework for Earth Observation and SAR data handling.
+
+## Supported Formats & Core Features
+
+`aresys_io` provides complete support for the core internal Aresys formats:
+
+- **Product Folder (PF)**: The official Aresys SAR product format for organizing and storing data and auxiliary information. Supports **Level 0 (RAW)**, **Level 1 (SLC / GRD)**, and **Interferometric** products across multi-swath and multi-polarization channels with dedicated XML annotations, binary/TIFF raster data, manifests, and preview overlays.
+- **Point Target Binary**: Dedicated format for discrete radar reflectors (such as corner reflectors, active radar calibrators, or synthetic point scatterers) used in SAR simulation, calibration, and IRF analysis. Stores 3D Cartesian coordinates ($X, Y, Z$) and full polarimetric radar cross sections ($HH, HV, VH, VV$) with support for memory-mapped zero-copy access and high-level `NominalPointTarget` representations.
+- **SAR System**: Serialization and handling of SAR system and simulation parameters, including trajectory state vectors, timeline tables, swath parameter tables, and satellite definitions.
+- **Metadata & Raster Engine**: Robust XML serialization/deserialization for Aresys metadata schemas, orbit and attitude modeling, polynomial conversions, and flexible 2D raster I/O.
+
+## Installation
+
+This package is available on [PyPI](https://pypi.org/project/aresys_io/) and can be installed with `pip`:
+
+```bash
+pip install aresys-io
+```
+
+> [!NOTE]
+> `aresys_io` requires **Python 3.11** or higher.
+
+## Documentation
+
+- **Aresys I/O documentation**: [https://opensource.aresys.it/aresys_io](https://opensource.aresys.it/aresys_io)
+- **PERSEO documentation**: [https://opensource.aresys.it/perseo](https://opensource.aresys.it/perseo)
+
+## Related Repositories
+
+| Repository | Description | Documentation |
+| :--- | :--- | :--- |
+| [aresys-srl/perseo](https://github.com/aresys-srl/perseo) | Python Ecosystem for Remote Sensing & Earth Observation | [docs](https://opensource.aresys.it/perseo/) |
+| [aresys-srl/sct](https://github.com/aresys-srl/sct) | SAR Calibration Toolbox | [docs](https://opensource.aresys.it/sct/) |
+| [aresys-srl/sct_plugins](https://github.com/aresys-srl/sct_plugins) | SCT input product format plugins | [docs](https://opensource.aresys.it/sct_plugins/) |
+
+## Contributing
+
+Contributions are welcome! If you encounter a bug, have a feature request, or want to contribute code:
+
+- **Report bugs & request features**: open an issue on [GitHub](https://github.com/aresys-srl/aresys_io/issues). Include a clear description, steps to reproduce, and environment details.
+- **Submit changes**: fork the repository, create a feature branch, and open a pull request. Ensure your code passes all linting (`ruff`), typing (`pyrefly`), and test suites (`pytest`).
+- **Questions**: use GitHub Discussions for general questions and discussions.
+
+## License
+
+This project is licensed under the MIT License.
+
+Copyright &copy; 2026-present Aresys S.r.l. <info@aresys.it>

aresys_io-1.0.0/README.md

@@ -0,0 +1,57 @@
+# Aresys Formats Input/Output (aresys_io)
+
+![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11%20%7C%203.12%20%7C%203.13%20%7C%203.14-blue)](https://python.org)
+[![PyPI - Version](https://img.shields.io/pypi/v/aresys_io)](https://pypi.org/project/aresys_io/)
+[![aresys-io CI](https://github.com/aresys-srl/aresys_io/actions/workflows/aresys_io.yml/badge.svg)](https://github.com/aresys-srl/aresys_io/actions/workflows/aresys_io.yml)
+
+**Aresys I/O (`aresys_io`)** is the official Aresys Python library for reading, writing, and manipulating Aresys Earth Observation (EO) and Synthetic Aperture Radar (SAR) product formats.
+
+Designed to be modular, independent, and extensible, `aresys_io` provides unified data access and metadata management across the entire SAR processing and simulation pipeline. It is built to integrate with [**PERSEO**](https://github.com/aresys-srl/perseo) ([docs](https://opensource.aresys.it/perseo)), the Aresys modular framework for Earth Observation and SAR data handling.
+
+## Supported Formats & Core Features
+
+`aresys_io` provides complete support for the core internal Aresys formats:
+
+- **Product Folder (PF)**: The official Aresys SAR product format for organizing and storing data and auxiliary information. Supports **Level 0 (RAW)**, **Level 1 (SLC / GRD)**, and **Interferometric** products across multi-swath and multi-polarization channels with dedicated XML annotations, binary/TIFF raster data, manifests, and preview overlays.
+- **Point Target Binary**: Dedicated format for discrete radar reflectors (such as corner reflectors, active radar calibrators, or synthetic point scatterers) used in SAR simulation, calibration, and IRF analysis. Stores 3D Cartesian coordinates ($X, Y, Z$) and full polarimetric radar cross sections ($HH, HV, VH, VV$) with support for memory-mapped zero-copy access and high-level `NominalPointTarget` representations.
+- **SAR System**: Serialization and handling of SAR system and simulation parameters, including trajectory state vectors, timeline tables, swath parameter tables, and satellite definitions.
+- **Metadata & Raster Engine**: Robust XML serialization/deserialization for Aresys metadata schemas, orbit and attitude modeling, polynomial conversions, and flexible 2D raster I/O.
+
+## Installation
+
+This package is available on [PyPI](https://pypi.org/project/aresys_io/) and can be installed with `pip`:
+
+```bash
+pip install aresys-io
+```
+
+> [!NOTE]
+> `aresys_io` requires **Python 3.11** or higher.
+
+## Documentation
+
+- **Aresys I/O documentation**: [https://opensource.aresys.it/aresys_io](https://opensource.aresys.it/aresys_io)
+- **PERSEO documentation**: [https://opensource.aresys.it/perseo](https://opensource.aresys.it/perseo)
+
+## Related Repositories
+
+| Repository | Description | Documentation |
+| :--- | :--- | :--- |
+| [aresys-srl/perseo](https://github.com/aresys-srl/perseo) | Python Ecosystem for Remote Sensing & Earth Observation | [docs](https://opensource.aresys.it/perseo/) |
+| [aresys-srl/sct](https://github.com/aresys-srl/sct) | SAR Calibration Toolbox | [docs](https://opensource.aresys.it/sct/) |
+| [aresys-srl/sct_plugins](https://github.com/aresys-srl/sct_plugins) | SCT input product format plugins | [docs](https://opensource.aresys.it/sct_plugins/) |
+
+## Contributing
+
+Contributions are welcome! If you encounter a bug, have a feature request, or want to contribute code:
+
+- **Report bugs & request features**: open an issue on [GitHub](https://github.com/aresys-srl/aresys_io/issues). Include a clear description, steps to reproduce, and environment details.
+- **Submit changes**: fork the repository, create a feature branch, and open a pull request. Ensure your code passes all linting (`ruff`), typing (`pyrefly`), and test suites (`pytest`).
+- **Questions**: use GitHub Discussions for general questions and discussions.
+
+## License
+
+This project is licensed under the MIT License.
+
+Copyright &copy; 2026-present Aresys S.r.l. <info@aresys.it>

aresys_io-1.0.0/docs/.gitignore

@@ -0,0 +1 @@
+build.md

aresys_io-1.0.0/docs/about/build.template.md

@@ -0,0 +1,13 @@
+---
+icon: lucide/badge-info
+---
+
+# Build
+
+Documentation build info and versioning information.
+
+Version: ==__TAG__==
+
+Commit: ==__SHA__==
+
+Build date: ==__DATE__==

aresys_io-1.0.0/docs/changelog.md

@@ -0,0 +1,26 @@
+---
+icon: lucide/history
+title: "Changelog"
+tags:
+    - changelog
+    - release notes
+---
+
+# Changelog
+
+## v1.1.1
+
+**Other changes**
+
+- Improving `MetaDataChannel` and `MetaData` classes with ``__contains__`` methods.
+- Vectorized Polynomials evaluation in range and separating input azimuth and range values.
+
+## v1.1.0
+
+First public release.
+
+The interface has been reviewed and updated.
+
+## v1.0.0
+
+First beta release.

aresys_io-1.0.0/docs/documentation/point_target/api.md

@@ -0,0 +1,18 @@
+---
+icon: fontawesome/brands/python
+title: "API"
+tags:
+    - point targets
+    - simulation
+    - e2e
+    - API
+    - python
+---
+
+## Point Target Binary
+
+::: aresys_io.product.point_target.point_target_binary
+
+## Nominal Point Targets
+
+::: aresys_io.product.point_target.nominal_point_targets

aresys_io-1.0.0/docs/documentation/point_target/index.md

@@ -0,0 +1,111 @@
+---
+icon: lucide/crosshair
+title: "Point Target Binary"
+tags:
+    - point target
+    - simulation
+    - e2e
+    - calibration
+    - python
+---
+
+# Point Target Binary { #targets data-toc-label="Point Target" }
+
+The **Point Target Binary** format is the official Aresys format for storing and organizing artificial or real
+point targets used throughout SAR simulation and calibration processing chains.
+
+Each target is defined by its 3D spatial coordinates and its full polarimetric radar cross section (RCS). The format
+stores discrete radar reflectors (such as corner reflectors, active radar calibrators, or synthetic point scatterers) and
+it's mainly used in SAR end-to-end (E2E) simulators, performance assessment, and impulse response function (IRF) analysis.
+
+Managing and working with this format is handled directly via `aresys_io.product` or in the dedicated module `aresys_io.product.point_target`.
+Common operations include:
+
+- creating and writing Point Target Binary products
+- reading point target coordinates and polarimetric RCS values
+- chunked and windowed reading for large simulation datasets
+- memory-mapped access for zero-copy, efficient streaming of large scatterer fields
+- converting arrays to structured nominal point target objects
+
+## Product Structure
+
+A Point Target Binary product is physically organized as a **folder** containing a fixed set of binary raster files
+accompanied by corresponding XML metadata files.
+
+A complete point target product consists of **7 binary raster files** and **7 matching XML annotation files**:
+
+- **3 Coordinates rasters & metadata**: one for each spatial dimension ($X$, $Y$, and $Z$) in Cartesian coordinates (typically ECEF).
+- **4 Radar Cross Section (RCS) rasters & metadata**: one for each linear polarization channel ($HH$, $HV$, $VH$, and $VV$) representing the complex scattering matrix.
+
+Each binary file represents a 1D column raster containing the respective value for every point target in the dataset.
+
+## Point Target Binary at a Glance
+
+From a structural point of view, a Point Target Binary product folder is organized as follows:
+
+```text
+Point Target Folder/
+├── PointTargetPosX          # X coordinate binary raster
+├── PointTargetPosX.xml      # X coordinate metadata
+├── PointTargetPosY          # Y coordinate binary raster
+├── PointTargetPosY.xml      # Y coordinate metadata
+├── PointTargetPosZ          # Z coordinate binary raster
+├── PointTargetPosZ.xml      # Z coordinate metadata
+├── PointTargetRCSHH         # HH polarization complex RCS binary raster
+├── PointTargetRCSHH.xml     # HH polarization metadata
+├── PointTargetRCSHV         # HV polarization complex RCS binary raster
+├── PointTargetRCSHV.xml     # HV polarization metadata
+├── PointTargetRCSVH         # VH polarization complex RCS binary raster
+├── PointTargetRCSVH.xml     # VH polarization metadata
+├── PointTargetRCSVV         # VV polarization complex RCS binary raster
+└── PointTargetRCSVV.xml     # VV polarization metadata
+```
+
+All 7 raster files share the exact same number of lines ($N$, corresponding to the total number of point targets) and have
+a single sample per line (`samples = 1`).
+
+## Product Components
+
+### Coordinates Rasters and Metadata
+
+The **coordinates rasters** store the 3D position vector for each point target:
+
+- `PointTargetPosX`: $X$ coordinate in meters.
+- `PointTargetPosY`: $Y$ coordinate in meters.
+- `PointTargetPosZ`: $Z$ coordinate in meters.
+
+Positions are stored as floating-point values, using either single precision (`FLOAT32`) or double precision (`FLOAT64`).
+Each raster has an associated XML annotation file containing a `RasterInfo` element describing the data layout, cell type,
+number of lines ($N$), and byte order.
+
+### RCS Rasters and Metadata
+
+The **RCS rasters** store the complex scattering coefficients representing the full polarimetric scattering matrix for
+each point target:
+
+- `PointTargetRCSHH`: Horizontal transmit, Horizontal receive ($S_{HH}$).
+- `PointTargetRCSHV`: Vertical transmit, Horizontal receive ($S_{HV}$).
+- `PointTargetRCSVH`: Horizontal transmit, Vertical receive ($S_{VH}$).
+- `PointTargetRCSVV`: Vertical transmit, Vertical receive ($S_{VV}$).
+
+Scattering values are stored as complex numbers, using either single-precision complex (`FLOAT_COMPLEX`) or double-precision
+complex (`DOUBLE_COMPLEX`). The corresponding XML files provide standard Aresys metadata for each polarization channel.
+
+### Consistency Requirements
+
+When opening a Point Target Binary product in read mode:
+
+1. The folder must exist and be a valid directory.
+2. All 7 binary raster files and all 7 XML metadata files must be present.
+3. Every metadata file must specify `samples = 1`.
+4. The number of lines (`lines`) must be consistent across all 7 metadata files, defining the total number of targets.
+
+## High-Level Representation: Nominal Point Targets
+
+While the binary product stores tabular data in separate rasters for performance and fast column access, `aresys_io`
+also provides a high-level Python representation:
+
+- `NominalPointTarget`: A dataclass encapsulating an individual target's 3D position vector ($X, Y, Z$), complex polarimetric
+  scattering coefficients ($S_{HH}, S_{HV}, S_{VH}, S_{VV}$), and an optional delay.
+- `convert_array_to_point_target_structure()`: A conversion utility to transform raw coordinate and RCS arrays into a
+  keyed dictionary of `NominalPointTarget` instances.