rompy-xbeach
Rompy Xbeach Config package.
Features
Grid
CRS aware grid object
Ability to specify origin in different coordinate systems from the grid (e.g., lat/lon)
Plotting supporting projections and high resolution coastlines
Option to display the grid mesh
Option to display the offshore boundary and origin
Method to expand the grid boundaries
Property methods to hold the cartopy stereographic projection and the transform
shape property method
Method to return Multipolygon geometry of all grid cells
Method to save the grid to file
Method to load the grid from file
Data
CRS aware
Interpolator interface
Modified source objects to support crs (rioxarray based)
New custom Geotiff specific source
New custom XYZ source supporting interpolation
Seaward extension framework
Lateral extension capability
Xarray Accessor
Class method to create a xbeach dataset from model files
Method to plot the bathymetry grid, profiles and slopes together
Questions
Support interpolate_na in the data objects? before or after interpolating the data?
Metadata
Release files for rompy-xbeach 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rompy_xbeach-0.2.0.tar.gz | 1.2 MB | With provenance | Details for rompy_xbeach-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rompy_xbeach-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for rompy_xbeach-0.2.0-py3-none-any.whl |
Total release size: 1.3 MB
Release files / rompy_xbeach-0.2.0.tar.gz
| Download URL | rompy_xbeach-0.2.0.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f592b45758e2c7d92ce42c00d6f3addd2e5207a3d330ac05dfd0ccd857da54b4
|
|
BLAKE2b-256 checksum How to use checksums |
d66212d0c76d1846a83de69496fa503a5178feafaadea7838ae1092a60f4ca92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2025.
Transparency logRelease files / rompy_xbeach-0.2.0-py3-none-any.whl
| Download URL | rompy_xbeach-0.2.0-py3-none-any.whl |
|---|---|
| Size | 35.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
003e873626ca99fb3af246d8a783751aeb4aa9f23cb90faab959b762037a7bfd
|
|
BLAKE2b-256 checksum How to use checksums |
24aecd0de0c7abffdd8505cba2f07110feb35f277908faee12e966e2506d7ce8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2025.
Transparency logSecurity for rompy-xbeach 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for rompy_xbeach-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 22, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.