Skip to content

add draft .qml#913

Closed
uryckid wants to merge 5 commits intoRiverscapes:masterfrom
uryckid:uryckid-streamtemp-symbology
Closed

add draft .qml#913
uryckid wants to merge 5 commits intoRiverscapes:masterfrom
uryckid:uryckid-streamtemp-symbology

Conversation

@uryckid
Copy link
Copy Markdown

@uryckid uryckid commented Sep 18, 2025

I could use some feedback on this .qml. I'm uncertain how to name and organize the symbology files. I have a geopackage with 34 layers and views. Layers of interest correspond to different epochs and line or polygon representations, with 4 variables of interest over 4 seasons each (e.g., sp_stream_temp, su_stream_temp, fa_stream_temp, wi_stream_temp).

This particular .qml was built to symbolize seasonal "stream_temp" by NHDv2 comid flowlines for the layer called "vw_stream_temperature_anomalies_1990s_lines."

The other variables of interest are antec_air_temp, SwS, log_flow, which are reported in the layer(s) "vw_temporal_covariate_anomalies_[epoch]_[lines/polygons]."

So far I have 8 .qml files: one for each of four variables (stream_temp, antec_air_temp, SWS, log_flow) as lines or polygons.

Please let me know if I'm on the right track and, if so, how to name these files.

Thanks!

@MattReimer MattReimer force-pushed the master branch 2 times, most recently from 930f69c to 7ba48e1 Compare October 28, 2025 22:08
@philipbaileynar
Copy link
Copy Markdown
Contributor

@uryckid I'm going to close this now and NOT accept it, given that I pushed a different approach.

We can revisit this if there are things in this request that you still want to include.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants