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

Raw JSON boundaries for starting cities #16

Closed
afrasier opened this issue Mar 12, 2015 · 3 comments
Closed

Raw JSON boundaries for starting cities #16

afrasier opened this issue Mar 12, 2015 · 3 comments
Assignees
Labels
Milestone

Comments

@afrasier
Copy link
Contributor

Import GeoJSON for the starter cities at the block group resolution:

  • New York City
  • Chicago
  • Fargo
  • San Francisco
  • Los Angeles
  • Austin
@afrasier afrasier added the dev-2 label Mar 12, 2015
@afrasier afrasier self-assigned this Mar 12, 2015
@afrasier afrasier modified the milestone: Sprint #1 Mar 12, 2015
@afrasier
Copy link
Contributor Author

Waiting on fixed D.C. block file and files for other cities.

@afrasier afrasier assigned jmeisel and unassigned afrasier Mar 27, 2015
@afrasier afrasier modified the milestones: Sprint #1, Sprint #2 Mar 27, 2015
@afrasier afrasier modified the milestones: Sprint #2, Sprint #3 Apr 13, 2015
@afrasier
Copy link
Contributor Author

Re-assigning to myself as the Geo team will be giving us the geoJSON for our initial cities, which I will implement into the geoRequest function.

@afrasier
Copy link
Contributor Author

Resolved by 0ccafb8

@afrasier afrasier removed the test label Apr 23, 2015
neka-io pushed a commit to neka-io/citysdk that referenced this issue Aug 18, 2016
loganpowell added a commit that referenced this issue Dec 17, 2018
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