-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace missing RWD source files #65
Comments
We discussed creating a data verification script which will scan each directory to check that the files we expect to be there actually exist. The README.txt file on the GDrive has documentation which describes which files should exist in each directory. Once we obtain a list of missing files using this script, we can determine if these files are present in the zip files on the GDrive. One challenge I found is that it's not a straightforward process to identify which file contains which subwatershed. The sort order used to group these files does not use a natural numeric sort order. So a zip file may contain subwatersheds |
I was able to locate which zip file that a specific subwatershed belongs to by doing the following.
Take the line number yielded from |
The missing catchment zip has been upload to the GDrive. Some additional notes:
|
I'm going to start pushing this to staging now. |
This volume contains missing shapefiles from MSsub47.zip. Connects WikiWatershed/rapid-watershed-delineation#65
For future reference, I have uploaded RWDProductionVolumeContents20170220.txt.tar.gz to the GDrive. This file contains the full list of RWD files that exist on staging/production as of today. Here's a sample:
|
At least catchment
26965
&27260
are missing inRWD_DATA
(Subwatershed_ALL/Subwatershed26965/subwatershed_26965dist.tif
) on staging and on the dev data stick that has been distributed. This is responsible for errors being reported as in #26.gwmaster.shp
Source: https://drive.google.com/drive/u/1/folders/0B7V8il12WGQJM1JFWkN6bXpOX1k
Those are questions to pursue, but ultimately we need to restore any missing catchment tifs and cut an updated volume drive.
For testing, these two points are in the known missing catchments.
The text was updated successfully, but these errors were encountered: