Problem accessing geojson properties when generated inline

Perhaps I am missing something, but there appears to be a problem in accessing inline geoJson objects.

The following spec, which loads a geoJson file works as expected:

{
  "$schema": "https://vega.github.io/schema/vega-lite/v2.json",
  "width": 200, "height": 200,
  "data": {
    "url": "https://gist.githubusercontent.com/jwoLondon/6caab27b0d131c74c194efd943389201/raw/e9ea15b56001dfac9c3795dff4f2a0f67dbfc710/geojsontest.json",
    "format": { "type": "json", "property":  "features" }
  },
  "projection": { "type":  "orthographic" },
  "encoding": {
    "color": {
      "field": "properties.myRegionName",
      "type": "nominal"
    }
  },
  "mark": "geoshape"
}

But if I generate the same content inline, I do not seem to be able to access the myRegionName property:

{
  "$schema": "https://vega.github.io/schema/vega-lite/v2.json",
  "width": 200, "height": 200,
  "data": {
    "values": [
    {
      "type": "FeatureCollection",
      "features": [
        {
          "type": "Feature",
          "geometry": {
            "type": "Polygon",
            "coordinates": [ [ [-3,52], [4,52], [4,45], [-3,45], [-3,52] ] ]
          },
          "properties": { "myRegionName": "Southern region" }
        },{
            "type": "Feature",
            "geometry": {
              "type": "Polygon",
              "coordinates": [ [ [-3,59], [4,59], [4,52], [-3,52], [-3,59] ] ]
            },
            "properties": { "myRegionName": "Northern region" }
          }
        ]
      }
    ],
    "format": { "type": "json", "property": "features" }
  },
  "projection": { "type": "orthographic" },
  "encoding": {
    "color": {
      "field": "properties.myRegionName",
      "type": "nominal"
    }
  },
  "mark": "geoshape"
}

This spec generates the error : TypeError: undefined is not an object (evaluating 'e.hasOwnProperty’)

Is this perhaps related to one of the issues in #3369, or is there some other way of accessing nested inline fields?

[jwoLondon]

Thanks @iliatimofeev, that’s helpful and clarifies where the problem lies, and so as far as I can see once the documentation is updated this issue can be closed.

[ratnanil]

Ok, so you have something planned? Would suggestions for some minimal examples be helpful?