Update some docs pre-RVR

Author: billyc

docs/guide-dashboards.md

@@ -24,15 +24,17 @@ A dashboard config requires a top-level `header` containing _tab_ and _title_ an
 header:
   tab: 'Summary'
   title: 'Top-Level Summary Statistics'
-  description: 'At-a-glance figures we usually look at' #optional
-  triggerPattern: "*.drt.csv" #optional
+  description: 'At-a-glance figures we usually look at' # optional
+  fullscreen: true # optional
+  triggerPattern: "*.drt.csv" # optional
 ```
 
 |**Field**|**Description**|**Default**|
 |---------|---------------|-----------|
 |title|Header title displayed at top of dashboard|--|
 |tab|Name shown on the tab|Same as title|
 |description|Longer text shown below dashboard title|--|
+|fullscreen|Fill the height of the window instead of assigning specific heights to each row|false|
 |triggerPattern|If specified, the dashboard defined in this YAML will only be generated when a filename matching the given triggerPattern exists in the current folder. For example, if it is set to `triggerPattern: "*.drt.csv"` and the file `output_mode.drt.csv` exists in the current folder, then this dashboard will be created. If no file matches the given pattern, then this dashboard will be skipped. If triggerPattern is not specified, then the dashboard will always be generated.|--|
 
 ## Dashboard Layout

docs/matsim-transit-supply.md

@@ -12,7 +12,20 @@ This viz shows transit route details.
 
 No YAML is required. If the run folder contains a `*output_transitSchedule.xml.gz` file, then this view will be available and the transit route supply can be explored.
 
-If the run folder also contains `*pt_stop2stop_departures.csv.gz` then the transit ridership (demand) will also be loaded. This may take a few seconds.
+**Stop-to-stop ridership:** If the run folder also contains `*pt_stop2stop_departures.csv.gz` then the transit ridership (demand) will also be loaded. This may take a few seconds.
+
+## Dashboard
+
+The following configuration options are available when embedding the transit viewer in a dashboard.  Use `type: transit` for this plugin.
+```yaml
+layout:
+  row1:
+    - type: transit
+      title: Transit Explorer
+      network: "*output_network.xml.gz"
+      transitSchedule: "*output_transitSchedule.xml.gz"
+      projection: EPSG:25832 # Use your EPSG coordinate system here
+```
 
 ### Exploring transit
 

docs/ref-xy-hexagons.md

@@ -17,15 +17,35 @@ In addition, the presence of the MATSim regular output file `output-trips.xml.gz
 
 ## Dashboards
 
-XY Hexagon plots can be embedded in dashboards using `type: hexagons` and specifying the config details in the props as follows:
+XY Hexagon plots can be embedded in dashboards using `type: hexagons` and specifying the config details in the YAML as follows:
 
 ```yaml
-row:
-  - title: My Hexagon Plot
-    type: hexagons
-    # ...
+layout:
+  row1:
+    - title: My Hexagon Plot
+      type: hexagons
+      # ...etc
 ```
 
+To load the standard MATSim `output_trips` origins/destinations plot, the following code should do the trick:
+
+```yaml
+layout:
+  row1:
+    - type: hexagons
+      file: "*output_trips.csv.gz"
+      title: Output Trips
+      projection: EPSG:25832  # Set your coordinate projection here
+      aggregations:
+        Trips:
+          - title: Origins
+            x: start_x
+            y: start_y
+          - title: Destinations
+            x: end_x
+            y: end_y
+
+```
 
 ## YAML fields explained