Calistoga boundary

[kurtishouser]

The recent correction #1003 to the existing Calistoga boundary appears to be for the boundary that was updated when Crystal Springs of Napa Valley was established.

https://www.ecfr.gov/compare/current/to/2024-01-01/title-27/chapter-I/subchapter-A/part-9/subpart-C/section-9.209

It's not uncommon for adjacent boundaries to change when a new AVA is established. It's better to have one person work on something like this rather than two people nearly nine months apart.

• One Federal Register document
• One GitHub issue (Add Crystal Springs of Napa Valley, Update Calistoga)
• One person working on one QGIS project
• One person submitting one PR

Then both intrinsically related changes get merged into the dataset at the same time, as they should.

[MicheleTobias]

Suggestions to our workflow aside, can you explain more about the issue you're seeing with Calistoga? The recent updates to the Calistoga boundary were to address issue #973 where there seems to have been a mistake in which the original digitizer followed the wrong elevation line. Did that cause another problem? Or is there something else I'm not seeing?

[kurtishouser]

The long north-south line (eastern edge of the polygon) that follows the 122° 30′ longitude is the new boundary for Calistoga.

The current workflow contributed to this error.

Also, issue #975 plans to add an "overlaps" column that will be populated via an R script. Had this been implemented at the time and the script run in the nine month gap it would have reported that Calistoga overlaps Crystal Springs of Napa Valley.

Here's the file history Calistoga.
https://github.com/UCDavisLibrary/ava/commits/master/avas/calistoga.geojson

If you want to avoid dealing with git and your local repos you can start here to view/download each version of the file (top 2) for comparison.