Rules
Required rules are always enabled and execute when applicable and prerequisites are satisfied. Extended geometry rules are selected individually; attribute rules are enabled as one group.
GR-001 · File reading, format, and size
Accept .geojson/.json, .shp or .zip, at most 10 MiB. Read GeoJSON as UTF-8 JSON; files are processed locally.
Required · Always enabled
GR-002 · GeoJSON document and feature containers
Require a supported geometry, Feature or FeatureCollection. Features must contain geometry. Legacy crs declarations reject the file.
Required · Always enabled
GR-003 · Shapefile framing
Validate SHP headers and record boundaries.
Required · Always enabled
GR-004 · ZIP integrity and single layer
Require one .shp layer. Limit expanded content to 10 MiB and 1,024 entries. Validate framing and CRC; reject encryption, split archives, ZIP64, unsupported compression and duplicate filenames.
Required · Always enabled
BR-001 · Geometry structure and coordinates
Require supported coordinate structures and finite positions. Lines require at least two positions; collections have a 64-level nesting limit.
Required · Always enabled
BR-002 · Polygon ring structure
Each ring requires at least four positions; the first and last x/y positions must match. Input is never automatically closed.
Required · Always enabled
BR-003 · Two-dimensional scope
Only consistently two-dimensional coordinates reach GEOS. Z/M coordinates are skipped; mixed dimensions fail parsing. No reprojection or spherical interpretation occurs.
Required · Always enabled
BR-004 · Empty geometry policy
Null geometry, empty top-level coordinates and empty collections are skipped. A collection with an empty member is skipped as a whole after structural validation.
Required · Always enabled
BR-005 · Shapefile record geometry
Check record payloads, parts, coordinates and shell/hole structure. Malformed or ambiguous records fail parsing without repair.
Required · Always enabled
BR-006 · Supported geometry types
Support all seven GeoJSON geometry types and 2D SHP Point, MultiPoint, PolyLine and Polygon. SHP Z/M and MultiPatch records are outside scope.
Required · Always enabled
BR-007 · GEOS planar validity
GEOS 3.13.0 uses GEOSisValidDetail with flags 0 on each supported nonempty 2D geometry. Return the first reason and optional location. Simplicity and spherical interpretation are outside scope.
Required · Always enabled
SR-001 · Duplicate geometries
Detect topologically equal eligible records using GEOS, with no tolerance or snapping.
Optional · Individually selected
AR-001 · Required attributes
Check configured fields and null or empty-value policies.
Optional · Attribute group
AR-002 · Attribute types
Check strict string, int, double, boolean or date values without coercion.
Optional · Attribute group
AR-003 · Attribute constraints
Check configured numeric bounds, enums, string lengths and regular expressions.
Optional · Attribute group
AR-004 · Attribute sources
Read Feature properties or matching DBF attributes; unavailable or damaged sources have no field validity result.
Optional · Attribute group
AR-005 · Attribute configuration
Validate a versioned attribute rule file before starting inspection.
Optional · Attribute group
AR-006 · Feature identification
Preserve string or numeric IDs. Invalid IDs fall back to the source index and produce an identity issue only when attribute rules are enabled.
Optional · Attribute group