Question 1

How do I use geojsonhint to validate a GeoJSON file from the command line?

Accepted Answer

Install it globally with `npm install -g @mapbox/geojsonhint`, then run `geojsonhint file.geojson` to get error messages with line numbers, as shown in the CLI utility section.

Question 2

Is geojsonhint still maintained or should I use something else?

Accepted Answer

No, geojsonhint is archived and development is paused. The README recommends using @placemarkio/check-geojson as an alternative for ongoing support and updates.

Question 3

geojsonhint vs GeoJSON-Validation: which is better for Node.js?

Accepted Answer

geojsonhint strictly follows RFC 7946 and provides line-numbered errors, while GeoJSON-Validation might have different features. Since geojsonhint is unmaintained, consider active alternatives like check-geojson for long-term projects.

Question 4

How can I suppress precision warnings in geojsonhint?

Accepted Answer

Set the `precisionWarning` option to false when calling `hint()`. For example, `geojsonhint.hint(geojson, { precisionWarning: false })` will ignore warnings about coordinates with over six decimal places.

Question 5

Does geojsonhint support validating GeoJSON with custom properties?

Accepted Answer

It only validates structural compliance with RFC 7946, so custom properties are allowed if they don't violate the standard, but no additional validation is provided for them.

Question 6

Why does geojsonhint have two input types and which should I use?

Accepted Answer

Use string input for detailed line-numbered errors when debugging, or object input for faster validation in performance-critical applications, as explained in the Line Numbers section with the up to 10x speed difference.

geojsonhint

What is geojsonhint?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions