3.2.0

• Updated to retrieve latest resources from riverscapes.net instead of riverscapes.xyz
• No longer ships with business logic and symbology. You have to use the update resources feature on the Help menu when you first install the AddIn before you can open any projects. The warning message informs the user of this situation.
• Handles GeoPackages for version 2 project XML.

3.1.0

• Layer Ordering Clean-up (#35)
  • Adding map layers respects the order of business logic
  • Adding group layers respects the order of business logic
• Browse Folder for GeoPackages (#125) fixed. Now opens Explorer at folder that contains the GeoPackage.
• Open two projects with the same name now appends suffix "Copy X" to end of project name (#175)
• Definition Queries implemented (#172)
• View projects in warehouse (#158. Note view layers in source project was already implemented.)
• New close all projects button on RAVE toolbar (#174)
• Closing a single project now removes related project group layer from ArcMap ToC

3.0.3

Hotfix, omitting Basemap xyz map services from ArcRAVE (#169 ) because ArcGIS cannot load them.

3.0.2

• ArcRAVE now shipping with latest business logic and symbology from RiverscapesXML. The ArcRAVE repo no longer stores these files.
• ArcRAVE has new "update resources" feature that pulls the latest files from RiverscapesXML into the users %AppData%\RAVE folder:
  • Business logic XML
  • Symbology layer files
  • BaseMaps.xml
• Completely rewritten project tree loading to more correctly adhere to the official XSD standard. In practice, this means that repeaters and relative xpaths are now working properly.
• ArcRAVE now looks for business logic files by name. Previously it would open every business logic XML file and attempt to match the contents of the ProjectType tag with that of the project XML. Using file names is more like QRAVE.
• If ArcRAVE attempts to use a business logic file and something goes wrong (i.e. bad XML) then the project load aborts and a meaningful error message is provided. Previously when ArcRAVE encountered a bad business logic file it would simply continue to the next search folder without the user knowing that something had gone wrong.

2.1.3

Fixing minor bug in LTPBR symbology.

2.1.2

• LTPBR business logic and symbology

2.1.1

GUT business logic and symbology.

2.1.0

• Viewing Layer Metadata
• Linking to source riverscape projects
• Bankfull symbology and business logic.

2.0.6

VBET business logic and symbology for HAND.

2.0.5

BRAT management layer symbology.
RVD symbology.