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

Los Carneros History #598

Closed
3 tasks
elistockwell opened this issue Jan 29, 2021 · 4 comments · Fixed by #709
Closed
3 tasks

Los Carneros History #598

elistockwell opened this issue Jan 29, 2021 · 4 comments · Fixed by #709

Comments

@elistockwell
Copy link
Contributor

This AVA has the following revisions:

  • [T.D. ATF-142, 48 FR 37368, Aug. 18, 1983]
  • [T.D. ATF-249, 52 FR 5956, Feb. 27, 1987]
  • [T.D. TTB-55, 71 FR 66455, Nov. 15, 2006]

Each revision should be represented by a polygon inside the .geojson file for this AVA. See the Adding Historical Boundaries document for more information on how to add historical boundaries.

@elistockwell
Copy link
Contributor Author

One technical amendment that adds references to maps in boundary description for clarity (no actual boundary change) and one name change amendment (Carneros -> Los Carneros). Worth adding history? If so, both amendments or just name change?

@MicheleTobias
Copy link
Contributor

We decided that minor corrections to a boundary description that don't change the actual boundary don't need a new polygon, BUT if the name changes, we do need a new polygon even if none of the other attributes change.

@elistockwell
Copy link
Contributor Author

I was wrong, it is actually not a name change. The name was always Los Carneros, but the recent amendment adds a part in the introductory text that says "Carneros" can also be used. I guess that would only affect the sameas field, so not worth a revision.

@MicheleTobias
Copy link
Contributor

If it affects the attributes, we need a revision. It might be the same boundary but we need that information. It would go in the "aka" (also known as) field.

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

Successfully merging a pull request may close this issue.

2 participants