check-geojson
4 | 5 |check-geojson development is supported by 🌎 placemark.io
6 |geojsonhint for 2021.
7 |I started working on geojsonhint in 2014. It's a pretty useful project. 8 | But it has been stagnant for a long time now, and has some annoying long-term 9 | issues.
10 |check-geojson is intended to be a full successor for geojsonhint. Like geojsonhint, 11 | it is tailored to a particular usecase: writing GeoJSON by hand, or quickly sussing 12 | out issues in GeoJSON that you've received.
13 | 14 | 15 |📕 API Documentation
16 | 17 | 18 | 19 |Main differences from geojsonhint
20 | 21 |-
22 |
- Actively maintained 23 |
- Written in TypeScript and includes types 24 |
- Uses momoa to parse JSON instead of a homemade 25 | parser. This is probably the biggest one. jsonlint-lines was a hack, which I created 26 | because I could not find a single parser that actually parsed JSON and gave line numbers 27 | for values. momoa is much better than that hack, and using it makes line-level errors 28 | much cleaner. 29 |
Unlike geojsonhint, this checker only produces errors, not warnings. So things 31 | that geojsonhint would warn about, like:
32 |-
33 |
- excessive coordinate precision 34 |
- right-hand rule compliance 35 |
This does not check for. Additionally, the crs member is ignored by this tool: as of
37 | the latest GeoJSON specification, this is not used.
We're using the same test fixtures as geojsonhint as a starter.
39 | 40 | 41 |Usage
42 | 43 |Not finalized yet
44 |import { check } from "check-geojson"
try {
const parseValue = check('… geojson string …')
} catch (e) {
/// e.issues
}
45 | 47 |
Optional override for formatting stack traces
3 |https://v8.dev/docs/stack-trace-api#customizing-stack-traces
4 |