How can I validate conformance to the shapefile standard?

[Anonymous User]

For any given shapefile, how can I validate conformance to the shapefile standard?

Given the ubiquity of shapefile writing software this is an important task when ingesting data from a variety of sources.

Ideally, I'd like to know which parts of the specification aren't implemented or were implemented incorrectly.

[DanPatterson]

Check Geometry (Data Management)—ArcGIS Pro | Documentation

provides esri and OGC checks, 

cracks exist regardless, but well written software should write good geometry in most cases

[Anonymous User]

Thank you both for the replies. I'm more concerned about conformance (strict or otherwise) to the specification in George's link.

For example, GEOS does not support m value geometry. Therefore if it's a dependency, (most open source Python in the geo world) then you can't technically meet the full specification.

This is a problem working between libraries. Here you can see osmdroid's ValidationPreferences, and an implementation for a PointZ shp. If a given writer isn't writing the correct header length in this case, then more steps are required to reformat the file.

This can lead to difficult and obscure debugging situations. So I'm looking for some sort conformance check beyond just geometry.

If I know where a given shapefile is not conforming I can run it through the proper correction.

[George_Thompson]

Here is an old white paper I found: https://www.esri.com/content/dam/esrisites/sitecore-archive/Files/Pdfs/library/whitepapers/pdfs/shap...

It is a little old