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

Update processing for pourpoint attributes #79

Open
lbross opened this issue Feb 24, 2020 · 2 comments
Open

Update processing for pourpoint attributes #79

lbross opened this issue Feb 24, 2020 · 2 comments

Comments

@lbross
Copy link
Contributor

lbross commented Feb 24, 2020

Starting with BAGIS 1E we have used the awdb_id as the AOI ID. We will continue to use this ID if the AOI is created using the FGDB layer. The awdb web services have both awdb_id and stationTriplet available. Note that the attribute name for awdb_id data in the usgs awdb web service is usgs_id. NWCC's current preference is to use the stationTriplet to identify the AOI; the stationTriplet will be printed in the AOI Map Package cover page when that is released for ArcGIS Pro.

BAGIS V3 will be updated to record the stationTriplet in the stationTriplet field and the usgs_id in the awdb_id field if the pourpoint layer is a web service. We will warn if the stationTriplet is missing, but will still create the AOI. If the pourpoint layer is an FGDB layer, nothing will change.

@jdduh
Copy link

jdduh commented Feb 24, 2020

Good design with the modification. Can we also capture and store the station name in the attribute table? The station name was used as the default name of the AOI, but BAGIS modifies the name and allows users to change the AOI name. It might be useful to have both AOI name and state name on the Map Package's cover page.

@lbross
Copy link
Contributor Author

lbross commented Feb 24, 2020

Sure. It looks like the BAGIS settings store the field from which the name is derived, so we will use that field to capture the name. I will store the name value in a field called 'stationName' unless you have a different suggestion.

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

No branches or pull requests

2 participants