Inputting JSON datasets

News
1

Previously EDT would only input JSON if its top level was an array or an object containing a single array. We’ve now relaxed that so that it will try to make sense of any valid JSON. You can try this here:

Windows:
https://www.easydatatransform.com/downloads/EasyDataTransform_1_13_2_snapshot_3.exe

Mac:
https://www.easydatatransform.com/downloads/EasyDataTransform_1_13_2_snapshot_3.dmg

We notice that some ‘JSON’ files (such as some GeoJSON datasets) seem to contain multiple top level objects without comma separators, like this:

{<object1>}
{<object2>}

This is not valid JSON. It should either be:

{
  {<object1>},
  {<object2>}
}

or

[
  {<object1>},
  {<object2>}
]

Is this invalid JSON commonly used?

2

It looks like these files with multiple top level objects are following the https://jsonlines.org/ spec. We should be able to support that.

3

Very interesting. I’m not sure I have experienced a json data set as described above.
Now I’m going to be up all night looking for one to experiment with.

4

@DanFeliciano
There seems to be lots of GeoJSON data in the object per line format at:
https://batch.openaddresses.io/data

v1.13.2 Snapshot 3 can’t handle this format, but the next release will.