Symbology for dynamic Layers in streamtemp Project Type

[uryckid]

Specification

Project Type: streamtemp
Layer(s):
Layer Name (reference line in business logic if possible - e.g. :
https://github.com/Riverscapes/RiverscapesXML/blob/master/RaveBusinessLogic/V2/streamtemp.xml#L12

Type(s) - Vector

Description and/or Explanation of Need

Repeaters were cleverly introduced as a way to capture varied layer names among different projects of the same type (streamtemp). Separately, I assigned labels to each of the layers indicating season only (e.g., "Spring"), assuming that the project hierarchy would help the user orient. However, QGIS will simply not visualize a new layer with the same label as an existing layer already displayed.

To resolve this issue, I was hoping to use dynamic labeling that would add the name of the variable (e.g., "air temp") AND a temporal marker (e.g., "2020s"), from the output from the Repeater. However, I was not able to accomplish this even with the help of Gemini. After trying several different solutions, Gemini concluded that this particular xml parser cannot evaluate functions in the label field and finally suggested post-processing the label names in QGIS.

I'm hoping we can come up with a solution for dynamic labelling. Let me know if it's helpful to include the conversation and solutions I attempted with Gemini.

Example(s) of Inspiration

Optional: Drag and paste in here any examples or screen shots of what you want this to look like

---

To-Do

Instructions for tasks:

1. delete those tasks not needed;
2. check off tasks as you complete them;
3. do not close issue until all tasks completed
4. reference this issue in all commits (e.g. with #33 notation where 33 is issue number)

• Start new branch with descriptive name for these changes (e.g. curation_Veg_RCAT)
• Make necessary edits to business logic and commit to new branch
• Author *.qml for QRAVE of layer(s) and test in QRAVE and commit
• Produce screen shot of each qml layer to provide in commit or later pull request for reviewer (include legend). Also, provide warehouse link to riverscape project you did testing on (use same project(s) for testing ArcRAVE and WebRAVE)
• Make pull request for just QRAVE changes. Choose appropriate reviewer(s)
• Author *.lyr for ArcRAVE of layer(s) and test in ArcRAVE and commit
• Make pull request for just ArcRAVE changes. Choose appropriate reviewer(s)
• Produce screen shot of each lyr file to provide in commit or later pull request for reviewer (include legend)
• Author symbology files for WebRAVE and provide link in commit to webRAVE of project it can be tested on
• Make pull request for just WebRAVE changes. Choose appropriate reviewer(s)
• Author or Update any project type documentation
• Update or Add Project Views to Reflect Changes (if necc.)
• After pull request(s) merged, test in updated qRAVE
• After pull request(s) merged, test in updated ArcRAVE
• After pull request(s) merged, test in updated WebRAVE
• Delete local branch(es) you used for your pull request(s)