The client needs to be able to run analyses using non-US places. To run a successful analysis for a non-US place, a custom population file and jobs file will need to be provided to the analysis script. An OSM extract may be needed as well if the file cannot be found at the geofabrik URL, which we derive the country's alpha3 code. This PR parameterizes the analysis script to fulfill those needs, then extends those parameters to the UI through the "Run Analysis" button in the Analysis Jobs admin page.
Demo
Notes
We had to increase the allowable geographic width of a shapefile in detect_utm_zone.
Testing Instructions
make sure you have a few hours in which you can let this run
nearly half a work day later, you should see Updating job status: COMPLETE Finished analysis and some scores
for good measure, navigate to http://localhost:9301/admin#/places//// and click on your neighborhood, then verify that the scores came through (i.e. it's not all 0s)
Overview
The client needs to be able to run analyses using non-US places. To run a successful analysis for a non-US place, a custom population file and jobs file will need to be provided to the analysis script. An OSM extract may be needed as well if the file cannot be found at the geofabrik URL, which we derive the country's alpha3 code. This PR parameterizes the analysis script to fulfill those needs, then extends those parameters to the UI through the "Run Analysis" button in the Analysis Jobs admin page.
Demo
Notes
We had to increase the allowable geographic width of a shapefile in detect_utm_zone.
Testing Instructions
scripts/setup
,vagrant ssh
,scripts/server
Updating job status: COMPLETE Finished analysis
and some scoresChecklist
Resolves #614, #889, #890, #891