rashid
rashid checks whether a Portolan catalog follows the specification.
Give it a catalog directory or its root catalog.json. rashid checks the metadata, structure, and asset bytes. It reports each problem with a stable rule ID.
The name comes from the Arabic root ر ش د. Its participles رَاشِدٌ and رَشِيدٌ mean "taking, or following, a right way or course or direction".
Install
uv tool install rashid
rashid requires Python 3.10 or later.
Check a Catalog
rashid check path/to/catalog
Exit code 0 means the catalog breaks no MUST requirement. Exit code 1 means it breaks at least one.
By default, rashid checks:
- Portolan metadata requirements.
- STAC 1.1.0 core structure with schemas included in the package.
- Local and remote asset bytes against their metadata and format rules.
Use --no-data when you only need a metadata and structure result. Use --data-scope local to keep byte checks inside the catalog directory.
rashid check path/to/catalog --data-scope local
Use --live to check HTTP range support and CORS on published assets. Relative asset links also require the catalog's public base URL. With the base URL, rashid also confirms that every linked document exists on the publish host.
rashid check path/to/catalog \
--live \
--live-base-url https://data.example.org/my-catalog/
Use --json for a machine-readable report.
Read the Report
Each finding contains a rule ID, severity, message, and file path. MUST requirements produce errors, and SHOULD requirements produce warnings.
A catalog can produce thousands of similar findings. After 50 findings, rashid groups results by rule and shows representative examples.
Use --all to list every finding. Use --summary to group any report by rule. JSON output always contains the complete findings array and a summary.by_rule object.
Choose Additional Checks
rashid provides six separate validation passes:
- Metadata checks Portolan requirements in catalog JSON.
- Structural checks STAC 1.1.0 core structure offline.
- Extension checks each object against the schemas of the STAC extensions it declares, offline.
- Schema checks each object against the packaged Portolan profile schema.
- Data reads asset bytes and verifies checksums, sizes, formats, and extents.
- Live hosting checks HTTP range support and CORS on remote servers.
Metadata, structural, extension, and data checks run by default. Use --schema as a cross-check against the published profile schema. Use --live for checks that require a published catalog and network access.
The extension pass uses the versions that the profile's extension registry pins. rashid packages those schemas, so a catalog at the pinned versions needs no network. A catalog that declares an older version of a registered extension is checked against that version's schema, which rashid fetches over https. rashid reports an extension outside the registry as an info finding rather than validating it. Use --schema-allow-network to fetch and check such a schema.
If a pass cannot run, rashid reports a warning. It does not treat the skipped pass as successful.
For transfer details and every rule ID, see the rule reference.
Use rashid from Python
from rashid import validate
report = validate("path/to/catalog")
for finding in report.errors:
print(finding.message)
validate() uses the same default passes as the command-line interface. Set schema=True or live=True to add those passes. Set extensions=False to skip the extension pass.
Use RulesConfig to disable rules or change their severity.
from rashid import RulesConfig, Severity, validate
config = RulesConfig(
disabled=frozenset({"PTL-VIZ-004"}),
severity_overrides={"PTL-TTL-002": Severity.ERROR},
)
report = validate("path/to/catalog", config=config)
The public rashid.api module also provides helpers for tools that repair catalogs. Names from this module remain available across 0.x releases. Other internal modules can change in a patch release.
Documentation
- Rule reference describes every validation pass, rule group, and degraded-pass code.
- Contributing guide covers development setup, tests, and repository checks.
- Portolan specification defines the requirements that rashid implements.
License
rashid is available under the Apache License 2.0.
Metadata
Release files for rashid 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 | |
|---|---|---|---|
| rashid-0.2.0.tar.gz | 555.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rashid-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 733.9 kB
Release files / rashid-0.2.0.tar.gz
| Download URL | rashid-0.2.0.tar.gz |
|---|---|
| Size | 555.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46eaf27a4fb664dc533470c0ec5bf694c6bf87aa1f1e8bbf23bba31099510153
|
|
BLAKE2b-256 checksum How to use checksums |
987e404225c3e5771e7fc342c18e5e7f66b61b4381d87889dda7d226bfde6990
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 12, 2026.
Transparency logRelease files / rashid-0.2.0-py3-none-any.whl
| Download URL | rashid-0.2.0-py3-none-any.whl |
|---|---|
| Size | 178.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cdbe36ac8fc6b6ecf8e74c3f8c5ee450418d2b2d4ec3497e258a79896524e414
|
|
BLAKE2b-256 checksum How to use checksums |
14207e86d35170da48819e6d3336664d9e44be8a7f7d6959f0e103340161c18b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 12, 2026.
Transparency log