Clojurians Log v2

No, geojson is the ticket. The problem is that sometimes you'll find geojson files that are shaped differently, so you end up having to specify a few extra things in how the json is being interpetted

Like, sometimes the assumptions about the shapes being loaded in matches up perfectly, as in the examples on the vega-lite examples page.

Do you have any suggestions as to why the following draws a blue circle in Oz or in the vega-lite editor. This is the closest GeoJSON to my data set districts (its quite big so hammers the browser a bit)

{
  "$schema": "<https://vega.github.io/schema/vega-lite/v4.json>",

  "data": {
    "url": "<https://opendata.arcgis.com/datasets/6638c31a8e9842f98a037748f72258ed_0.geojson>",
    "format": {
      "type": "json",
      "property": "features"
    }
  },
 
  "mark": "geoshape"

}

I remember having to do this in a project in the past, but am not sure where now; basically though if you compare the shape of your json file (with jq or something similar) to the geojson file used in one of the vega-lite/vega example visualizations, you may see that it has some obviously different shape. Like, the actual geojson part of the data might be nested under some parent entity in a different way. So just as with data where the attributes you want to specify are nested, you have a to modify your field specifications to match.

Thanks, that makes sense. I will calve out some time to experiment.