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.

Sign up for GitHub

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

Jump to bottom

rename "environs" in DB #96

Closed
rtburg opened this issue Jul 19, 2012 · 1 comment
Closed

rename "environs" in DB #96

rtburg opened this issue Jul 19, 2012 · 1 comment
Milestone
Week of 7/23

Comments

@rtburg
Copy link

rtburg commented Jul 19, 2012

We should remove "environs" from all such city names in the database. For true cities, add "town limits". And for similarly named "communities" change "environs" to "area"

So
"Whiteville" becomes "Whiteville town limits"
"Whiteville environs" becomes "Whiteville area"
"Bogue environs" becomes "Bogue"
@ghost ghost assigned sarahdooley and ghost Jul 19, 2012
ghost pushed a commit that referenced this issue Jul 19, 2012
refs #96 - Change city naming scheme on import
1badec3
@ghost
Copy link

ghost commented Jul 19, 2012

I changed the import code accordingly, and it brings up a new database with the desired changes. According to @copelco, the easiest thing to do to update current data will be to reload the Columbus County data with the new rules. Once that is complete we can close this issue.

ghost pushed a commit that referenced this issue Jul 20, 2012
refs #96 - Code comments
39ce413
@ghost ghost closed this as completed Jul 20, 2012
@ghost ghost mentioned this issue Jul 20, 2012
Open
@rtburg rtburg unassigned ghost Sep 23, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Week of 7/23
Development

No branches or pull requests
2 participants
@rtburg @sarahdooley