App category
Data and scientific formats
Validate specialist data before it enters a pipeline, exchange, catalog, or research workflow. These apps cover health, transit, procurement, geospatial, scientific, genealogy, workflow, catalog, and linked-data formats with checks suited to each standard.
Choose an app when
- Use FHIR Conformance Check for one R4 resource and FHIR Server Check for a server's CapabilityStatement and SMART discovery.
- Use GTFS Feed Check or NeTEx Dataset Check for transit data; use Data Catalog Check, Geospatial Catalog Check, Data Package Check, or OCDS Package Check for the named catalog or package.
- Use netCDF CF Check, VOTable Check, or Structure File Check for scientific formats, and Croissant Dataset Check for ML dataset metadata.
- Use E-Invoice Check, GEDCOM File Check, CWL Workflow Check, or Thing Description Check for their named business, genealogy, workflow, or device standard.
CWL Workflow Check
2 tools
Validate a hosted Common Workflow Language document with the reference cwltool --validate engine: real SALAD reference resolution and cross-step type wiring, not a YAML syntax parse
Data Catalog Check
2 tools
Check a hosted DCAT-AP open-data catalog against the official SHACL shapes, with exact shape-and-focus-node evidence
Data Package Check
2 tools
Validate a hosted Data Package descriptor AND its referenced remote data rows: types, constraints, primary keys, and cross-resource foreign keys the sandbox can't fetch
E-Invoice Check
2 tools
Validate a hosted or pasted EU e-invoice against EN 16931 and the KoSIT Schematron business rules: hundreds of rules beyond the XSD, with exact rule-ID and element evidence
FHIR Conformance Check
2 tools
Check a hosted or pasted public FHIR resource against its declared profile with the official HL7 validator, with exact StructureDefinition and invariant evidence and an explicit list of the profile rules offline validation never checked
FHIR Server Check
1 tool
Read what a public FHIR server declares about itself (its /metadata CapabilityStatement and SMART discovery document) and check it with the official HL7 validator, with US Core resource-type coverage and errors grouped into distinct findings
GEDCOM File Check
2 tools
Validate a hosted GEDCOM 7 genealogy file against the GEDCOM-registries corpus with the reference GedValidate engine, with exact rule-class evidence: real corpus validation, not a line-grammar parse
Geospatial Catalog Check
2 tools
Traverse and validate a hosted STAC catalog's linked metadata tree as far as the traversal caps reach, before you publish it
GTFS Feed Check
2 tools
Check a GTFS transit feed against the spec, with exact notice-code evidence, before you republish
Croissant Dataset Check
2 tools
Validate a hosted Croissant ML-dataset metadata doc with the real mlcroissant structure-graph engine, plus a bounded distribution-reachability probe
netCDF CF Check
2 tools
Check a hosted netCDF file against the CF Metadata Conventions from a public URL, with per-check rule evidence and no upload
NeTEx Dataset Check
2 tools
Check a hosted NeTEx transit dataset against the CEN schema and the Entur Nordic profile rules, with exact rule-and-element evidence
OCDS Package Check
2 tools
Check a hosted OCDS release or record package against the standard, its declared extensions, and the lib-cove additional checks, with exact check-and-location evidence
Structure File Check
2 tools
Validate a hosted PDBx/mmCIF structure against the wwPDB DDL2 dictionary with gemmi, with exact category-and-item evidence: real dictionary validation, not a syntax parse
Thing Description Check
2 tools
Validate a hosted or pasted W3C WoT Thing Description against both the JSON Schema and the beyond-schema assertions ajv alone cannot check, in chat
VOTable Check
2 tools
Validate a hosted astronomy VOTable against astropy's ~80-code IVOA conformance corpus with exact line-and-code evidence: real conformance validation, not an XSD or well-formedness parse