agrc / backseat-driver Goto Github PK

Utah SGID Change Log & Data Stewardship

• User CLI could be replaced with GUI
• Combine functionality with the current AppMaker update log utility

Make oauth credentials file name unique to application

Blob fields could either be excluded or be read and added to the hash.

UtahTransitSystems.json needs an updated feature_classes array. See agrc/gis.utah.gov#774

Add:
SGID10.ECONOMY.TaxAreas2017
SGID10.ECONOMY.TaxEntities2017
To:
CurrentTaxingUnits.json

The Drive code currently assumes all files are stored in a standard user Google Drive.

Using Team Drive would be make managing file ownership easier, but would eliminate shared folder links on the website.

A way is needed to guard against nonexistent feature being run. This seems to be a common occurrence.

The process currently will create a feature spec json and fail silently. It would be better not to create specs for features that don't really exist in the workspace.

• better error reporting
• email notifications

Add install procedure to readme

• Backseat now fits more naturally within the ship phase of forklift v9
• Run reports are already implemented in Forklift

last update to google drive download was 3/20/2018

• All installs of the tool would see the same info
• Drive storage location of download files would be available to other applications

Feature name changes require renaming some things to preserve the drive id and download link:

• feature spec json
  • sgid_name field
  • name field
• rename feature folder on drive
• Rename gdb and shp zip files in feature folder
• delete hash folder for feature
  • recreating the hash folder will require user credentials in zip_loader.py

Package name changes require renaming to preserve the folder links:

• package spec json
  • name field
• remove old package name from features
• rename package folder on drive
• Rename gdb and shp package folders

remove deprecated oauth2client and replace with: google-auth-httplib2 and google-auth-oauthlib.

• Backseat already generates this data, but doesn't store it
• Animated maps of all spatial changes over time would look really cool
• Changes could be used in future validation pipelines