Add HEAT estimates to model flows about pct-scripts HOT 10 CLOSED

@Robinlovelace Any reason to comment L96 in load.Rmd ?

# regions <- readOGR(file.path(pct_bigdata, "regions.geojson"), layer = "OGRGeoJSON

I've traced it back to this(386ff5f). Previously it was a more cautious if-else.

I was about to test some HEAT nos. and bumped into it.

from pct-scripts.

Asking not out curiosity: it prevents it from running! :0

from pct-scripts.

@audev that line loads the old 'CUA' regional boundaries: https://github.com/npct/pct-bigdata/blob/master/regions.geojson

Now we use the new regional boundaries which I defined, of which there are 45. This is loaded here: 477b57a#diff-f728b105860d99bed1d5f0718c4ec40bR88

Update - it's loaded here (correct link): https://github.com/npct/pct-load/blame/master/load.Rmd#L87

from pct-scripts.

Problem is this: Before it read the json file only when geo_level == "cua", otherwise the json:

if(geo_level == "cua"){
  regions <- readOGR(dsn = file.path(pct_bigdata, "cuas-mf.geojson"), layer = "OGRGeoJSON")
  regions$Region <- regions$CTYUA12NM
}

 regions <- readOGR(file.path(pct_bigdata, "regions.geojson"), layer = "OGRGeoJSON")

Now it doesn't read it, as by default geo_level ='regions' . Am I missing sth? Or is it that pct-bigdata repository needs re-pulling?

from pct-scripts.

I've rerun and it's reading region_shape. No problem , thanks

from pct-scripts.

No there was an issue with this: fixing it now, my bad.

from pct-scripts.

Apologies - these are the correct regions and the new script loads them by default. I was playing around with geo_level = 'custom' and accidentally removed that part. Fixed here: 24c0852

from pct-scripts.

No worries, just wanted it for having real figures.

from pct-scripts.

Done by @AnnaGoodman1 but still needs to be done...

from pct-scripts.

npct/pct-shiny#229

from pct-scripts.