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

Organize data directory #159

Open
jotok opened this issue May 9, 2015 · 1 comment
Open

Organize data directory #159

jotok opened this issue May 9, 2015 · 1 comment
Labels

Comments

@jotok
Copy link
Contributor

jotok commented May 9, 2015

I think we should create subdirectories for scripts, input files, output files, and configuration files (maybe). Input files could be split into data files (which need to be processed to feed into the app) and geo files. What do you think, @cmgiven ?

I'm thinking something like:

data/
  - scripts/
  - geodata/
  - inputs/
  - outputs/
@jotok jotok added the Data label May 9, 2015
jotok pushed a commit that referenced this issue May 9, 2015
@cmgiven
Copy link
Member

cmgiven commented May 9, 2015

Agreed, this would be a great step. Per our conversation, here are the files the front-end reads:

  • charters.json
  • dcps.json
  • hospitals.json
  • libraries.json
  • neighborhoods.csv
  • neighborhoods44.json
  • source.csv

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

No branches or pull requests

2 participants