In order to successfully get from source data to outputs, this repository has at least 2 dependencies (GDAL/PostGIS, Anaconda) that are installed at a lower level than a base python installation. Thus far we have been using shell scripts to keep track of these dependencies, for example:
On Windows however, we do not have a straightforward way of debugging these environmental/operating system requirements and configuration. We have discussed keeping track of dependencies in a simple text file.
How would this help us for debugging problems at the OS/environment level? For example, if a windows user needs to completely reinstall Anaconda, what do they need to do to re-configure gdal for Anaconda?
For everything but PostGIS/GDAL processing we will attempt to use Windows as detailed in the analytics Wiki link above. When we run into issues with that, we will use Vagrant/Shell as linked to above to debug.
In order to successfully get from source data to outputs, this repository has at least 2 dependencies (GDAL/PostGIS, Anaconda) that are installed at a lower level than a base python installation. Thus far we have been using shell scripts to keep track of these dependencies, for example:
https://github.com/MetropolitanTransportationCommission/bayarea_urbansim_setup/tree/vagrant-ubuntu14
On Windows however, we do not have a straightforward way of debugging these environmental/operating system requirements and configuration. We have discussed keeping track of dependencies in a simple text file.
How would this help us for debugging problems at the OS/environment level? For example, if a windows user needs to completely reinstall Anaconda, what do they need to do to re-configure gdal for Anaconda?