22

I have a small script that I'm using to generate GeoJSON data from a data format not currently supported by GIS software.

I would like to validate the output, but when I use ogr2ogr to read it, it doesn't give me any helpful information about what aspects, lines, or characters contained invalid data.

Is there a decent GeoJSON validator somewhere, or a good method of validating GeoJSON data with OGR?

EDIT: I am not looking for JSON validators or the GeoJSON spec. I've seen and used both to get to this point, but OGR still returns an error.

Taras
  • 32,823
  • 4
  • 66
  • 137
BenjaminGolder
  • 1,793
  • 4
  • 20
  • 31

5 Answers5

29

5 months late, but I made this thing that should help http://geojsonlint.com/.

Jason
  • 698
  • 2
  • 8
  • 12
4

If you prefer JavaScript there are now two options

null_radix
  • 653
  • 2
  • 6
  • 11
2

I have explained it before in this post.

The differences between JSON and GeoJSON are all about spelling. You can add more definition if you want. I don't think it is very important if you do not take part in the JSON spec for GeoJSON... there is no limit for a JSON object; the only important thing is that your JSON must be valid for correct usage.

You can check whether or not your GeoJSON file is valid with JSONLint which is a JSON Validator...

and you can check against the GeoJSON spec here.

I hope this helps you.

urcm
  • 22,533
  • 4
  • 57
  • 109
2

This GeoJSON validator is extremely useful in parsing different types, but also helpfully points out exactly where the errors lie.

saze
  • 21
  • 1
2

I don't have enough reputation to reply to comments, but apparently enough to add an answer. Go figure. For the links that @null_radix provided, here are the corresponding npm links that should still be valid:

The geojsonhint has been deprecated, but, as of the time of this comment, was still getting around 54K downloads per week, while geojson-validation was getting 15K.