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

Census Tract as Aggregation Field #35

Open
cmc333333 opened this issue Jun 2, 2014 · 4 comments
Open

Census Tract as Aggregation Field #35

cmc333333 opened this issue Jun 2, 2014 · 4 comments
Milestone

Comments

@cmc333333
Copy link

Right now, the UI (and maybe Qu?) doesn't allow aggregations over census tract (because it's a number maybe?). Combined with state and county, the census tract id because uniquely identifiable across the US.

Not sure if this is as simple as using a string to represent the census tract?

@dezzie
Copy link
Contributor

dezzie commented Jun 2, 2014

Hey CM, can you upload a screenshot of which UI you're referring to?

I'll be adding this to a milestone.

@dezzie dezzie added this to the Next version milestone Jun 2, 2014
@marcesher
Copy link
Contributor

@cmc333333 If you can provide the URL to the query, that's helpful as well

@cmc333333
Copy link
Author

screen shot 2014-06-02 at 11 43 16 am

I'd like to aggregate by state, county, and census tract (as a single query). Does that make sense?

@marcesher
Copy link
Contributor

@cmc333333 Ah. We removed the ability to aggregate on census tract some time ago as it caused significant problems when run unconstrained (i.e. aggregating across all states / msas without a filter). When we upgrade mongo, we can revisit it, as we'll be moving to the aggregation framework and away from map reduce. You can help us test it.

dezzie added a commit to dezzie/docs-template that referenced this issue Jun 5, 2014
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

3 participants