@mfbenitezp is hitting more proj issues. This is the only problematic external dependency we have, and it'd be so great to remove it. Where do we use it?
We use data/raw_data/nationaldata/MSOAS_shp/msoas.dbf just to get the polygon per MSOA. It comes somewhere from ONS, but I've definitely found this in nicer formats (GeoJSON or TopoJSON) and already in WGS84. We could just swap the inputs out. @HSalat, this shapefile has a population count unrelated to the rest of SPC, and we plumb it through in the output. Is it important at all?
The other use is converting the coordinates of venues from QUANT. We could just rewrite this file once to use WGS84. AFAICT, the QUANT data file we use is not completely based on anything open source (https://github.com/maptube/QUANT_RAMP is not enough to reproduce the tar.gz file we got), so making further modifications to this data is fair game. Do either of you know where the QUANT data file we use came from?
@mfbenitezp is hitting more proj issues. This is the only problematic external dependency we have, and it'd be so great to remove it. Where do we use it?
We use
data/raw_data/nationaldata/MSOAS_shp/msoas.dbf
just to get the polygon per MSOA. It comes somewhere from ONS, but I've definitely found this in nicer formats (GeoJSON or TopoJSON) and already in WGS84. We could just swap the inputs out. @HSalat, this shapefile has a population count unrelated to the rest of SPC, and we plumb it through in the output. Is it important at all?The other use is converting the coordinates of venues from QUANT. We could just rewrite this file once to use WGS84. AFAICT, the QUANT data file we use is not completely based on anything open source (https://github.com/maptube/QUANT_RAMP is not enough to reproduce the tar.gz file we got), so making further modifications to this data is fair game. Do either of you know where the QUANT data file we use came from?