Skip to content

Commit 96372fe

Browse files
Cashe93philipbaileynar
authored andcommitted
Updated QRAVE Symbology Documentation
I'm not sure how to test these changes. Before I continue with editing documents, I want to make sure this is on the right track.
1 parent dda5432 commit 96372fe

1 file changed

Lines changed: 55 additions & 4 deletions

File tree

docs/Technical_Reference/Symbology/qrave_symbology.md

Lines changed: 55 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,63 @@ weight: 2
55

66

77

8+
# QRAVE Symbology files
89

9-
## Symbology Files
10+
Here are step by step instructions for curating symbology in QGIS
1011

11-
### QRAVE
12+
### QRAVE How-to Create a Q Layer File (`*.qml`)
1213

13-
#### QRAVE How-to Create a Q Layer File (`*.qml`)
14+
Note: Be sure you are working within a <a class="button small" href="https://thenewstack.io/dont-mess-with-the-master-working-with-branches-in-git-and-github/">branch</a> of a given repository. Instructions on how to create a branch can be found <a class="button small" href="https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository">here</a>.
1415

15-
#### QRAVE How-to Convert from a `*.lyr` to a `*.qml`
16+
1. Symbolize the layer to your liking.
1617

18+
2. Once the layer has been symbolized, right click the layer within the layers panel.
19+
20+
3. Scroll down to *Export* and select *Save as QGIS Layer Style* (Since QGIS doesn't recognize *.lyr files, we will need to export our symbology as *.qml files).
21+
22+
4. Save your *.qml within *RiverscapesXML > Symbology > qgis* with appropriate naming.
23+
24+
- Naming should reflect what's being referenced in the Business Logic.
25+
26+
- If the layer is used for multiple tools (BRAT, RSContext, VBET, etc. ) then be sure to save it within the *Shared* folder.
27+
- If the layer is unique to a particular tool, save it in the folder for that specific tool.
28+
29+
5. Commit your changes to the branch and create a pull request.
30+
31+
32+
33+
<div class="responsive-embed widescreen">
34+
<iframe width="560" height="315" src="https://youtu.be/cbAsvdh7_Ws" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
35+
</div>
36+
37+
38+
39+
### QRAVE How-to Convert from a `*.lyr` to a `*.qml`
40+
41+
Often times, we may already have symbology that exists as an ESRI *.lyr file that we want to convert into a QGIS *.qml file. Here are a couple of ways in which we can do that.
42+
43+
#### SLYR TOOL
44+
45+
The quickest and easiest way to convert *.lyr to *.qml is by using the <a class="button small" href="https://north-road.com/slyr/">SLYR Tool</a> .
46+
47+
Note: You will need the ET-AL SLYR account details in order to run the licensed version
48+
49+
1. Downloading and installing the SLYR plugin for QGIS
50+
51+
Important: Before installing the licensed version of SLYR, you must first uninstall the community version (if installed) and restart QGIS
52+
53+
1. Download the installer from [https://usuwatershed:JloiY%24%29o%7Bskp@north-road.com/qgis_plugins/2872eb8e-bc44-46ac-9f11-f124c0ce4915/slyr_install.zip](https://usuwatershed:JloiY%24)o{skp@north-road.com/qgis_plugins/2872eb8e-bc44-46ac-9f11-f124c0ce4915/slyr_install.zip)
54+
2. Unzip the downloaded file, and then drag the extracted "install_slyr_qgis.py" over a running QGIS install. The script will add a connection to the private plugins repository, and install the SLYR plugin for you.
55+
3. After the plugin is installed, the SLYR options dialog will open. You must enter your unique license key at this screen, exactly as it appears at the end of this email.
56+
57+
2. To use the plugin
58+
59+
1. Navigate to the tool within the QGIS Processing Toolbox.
60+
2. Select the LYR datasets dropdown and open up the Convert LYR to QML tool.
61+
3. Simply drag and drop the *.lyr file that you want converted into a *.qml and save it within *RiverscapesXML > Symbology > qgis* with appropriate naming.
62+
4. Once the *.qml has been created, double check that the symbology was properly converted and commit your changes.
63+
- Although this tool has been shown to work correctly more times than not, it is important that you always check the *.qml output and make sure the symbology was accurately converted.
64+
65+
<div class="responsive-embed widescreen">
66+
<iframe width="560" height="315" src="https://youtu.be/lxYP79fkAQY" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
67+
</div>

0 commit comments

Comments
 (0)