Open djhocking opened 9 years ago
We now have a not_on_network flag in the locations table, which I added a week or two ago. I also added it to the location creation and location edit forms on the web app, but those haven't been rolled out to the main production app yet (which most users are using).
The bigger challenge is with the high resolution flow lines. Chris added them to the GIS data server, but they were incredibly slow. So they haven't been added to the maps yet. I'm going to try loading them into PostGIS and the PostgreSQL database, which I think will make them faster, but haven't gotten there yet.
In any case, this capability will be available soon. The tougher matter will be getting all the users to review all of the locations and assign the flag.
What do we do when someone has data from a small stream that is not on one of our flowlines? Is there a box for the user to check indicating that the data comes from a stream that is not on our map? It would be helpful so that I can either filter that out of the modeling and/or assign it the local but not upstream covariate values.
I'm not sure if this has actually come up with real stream temperature data since we have the hi res flow lines, but it could definitely happen. Right now I have no way of knowing when there are multiple
location_id
within the samefeatureid
whether they are both real, just on different sections of the stream, or if one is on our stream and one is on a small tributary that doesn't even map to our flowlines.