Skip to content
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

clarification request: directory naming rules for ease of data maintenance? #3

Open
cccs-ip opened this issue Oct 1, 2014 · 0 comments
Assignees

Comments

@cccs-ip
Copy link
Member

cccs-ip commented Oct 1, 2014

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:

  1. vector data: GeoGig
  2. raster: sync

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)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants