I would like to spend a few moments to clarify our data organization structure. I have set up the 'sync' application on my local computer. Should I first load in of my files and then link to your corresponding sync repository?
Also, you had indicated that we will differentiate our use of version control applications for GIS data management across two platforms:
Currently, all our relevant data (vector and raster) is hosted in a common folder (presumably uploaded in your GeoGig repo) called source material. Should we create a parallel file directory structure within both version control application (identical names and folder levels in both GeoGig and Sync)?
I would like to spend a few moments to clarify our data organization structure. I have set up the 'sync' application on my local computer. Should I first load in of my files and then link to your corresponding
sync
repository?Also, you had indicated that we will differentiate our use of version control applications for GIS data management across two platforms:
Currently, all our relevant data (vector and raster) is hosted in a common folder (presumably uploaded in your GeoGig repo) called
source material
. Should we create a parallel file directory structure within both version control application (identical names and folder levels in both GeoGig and Sync)?