-
Notifications
You must be signed in to change notification settings - Fork 25
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
Inconsistent use of neighborhood name vs. region name #3293
Comments
They do refer to the same thing, nice eye! |
Would you propose |
I think that "neighborhood" is probably more meaningful to people than "region", so I've been moving our user-facing stuff over to using "neighborhood" for awhile. So I say "neighborhood"! |
Sweet. Let's do it. You might ask: what's prompting all of these API questions recently? Well, it's emails like Frank's today asking about how to get the data and how to do some basic analysis. :) |
Perfect. Sounds good!
|
closing via #3323 |
In the
attributes
API, we haveNeighborhood Name
:But in the
neighborhoods
API, we haveregion_name
(andregion_id
):Do they refer to the same thing? If so, we should use the same name across all our API endpoints.
The text was updated successfully, but these errors were encountered: