Accept .geojson/.json, .shp or .zip, at most 10 MiB. Read GeoJSON as UTF-8 JSON; files are processed locally.

Require a supported geometry, Feature or FeatureCollection. Features must contain geometry. Legacy crs declarations reject the file.

Validate SHP headers and record boundaries.

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.

Require supported coordinate structures and finite positions. Lines require at least two positions; collections have a 64-level nesting limit.

Each ring requires at least four positions; the first and last x/y positions must match. Input is never automatically closed.

Only consistently two-dimensional coordinates reach GEOS. Z/M coordinates are skipped; mixed dimensions fail parsing. No reprojection or spherical interpretation occurs.

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.

Check record payloads, parts, coordinates and shell/hole structure. Malformed or ambiguous records fail parsing without repair.

Support all seven GeoJSON geometry types and 2D SHP Point, MultiPoint, PolyLine and Polygon. SHP Z/M and MultiPatch records are outside scope.

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.

Find different records occupying the same space, regardless of vertex order or attributes. No tolerance or repair is applied.

Points · Lines · Polygons · Excludes collections

Duplicate geometry rules are off.

Check required fields, types and allowed values with your own field rules. Select to configure or import rules.

GeoJSON properties · Shapefile ZIP with DBF

• AR-001 · Required attributes: Check configured fields and null or empty-value policies.
• AR-002 · Attribute types: Check strict string, int, double, boolean or date values without coercion.
• AR-003 · Attribute constraints: Check configured numeric bounds, enums, string lengths and regular expressions.
• AR-004 · Attribute sources: Read Feature properties or matching DBF attributes; unavailable or damaged sources have no field validity result.
• AR-005 · Attribute configuration: Validate a versioned attribute rule file before starting inspection.
• 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.