chore: more documentation update (#206)

Author: regeter

.github/ISSUE_TEMPLATE.md

@@ -8,7 +8,10 @@
 1.
 1.
 
-## Specifications
+## Photo (good) and/or Video (best) file attached that shows the issue
 
-- Version:
-- Platform:
+url, or attachment
+
+## Zipped file of your cloud logging data that shows the issue.
+
+url, or attachment (search and replace sensitive strings, for instance vehicle ID or trip ID)

README.md

@@ -15,8 +15,9 @@ We also have demo data for:
 
 ### Loading Your Data
 
-1. Export your Fleet Engine logs from Cloud Logging using this filter (customize as needed):
+1. Export your Fleet Engine logs from Cloud Logging using this filter (customize as needed): \
 ```sql
+-- On-demand trips
 resource.type="fleetengine.googleapis.com/Fleet"
 AND (labels.vehicle_id="YOUR_VEHICLE_ID" OR
      labels.trip_id=("TRIP_ID_1" "TRIP_ID_2"))
@@ -30,6 +31,21 @@ AND (
 )
 ```
 
+```sql
+-- Scheduled tasks
+resource.type="fleetengine.googleapis.com/DeliveryFleet"
+AND (labels.delivery_vehicle_id="YOUR_VEHICLE_ID" OR
+     labels.task_id=("TASK_ID_1" "TASK_ID_2"))
+AND timestamp >= "START_TIME" -- ISO 8601 format (YYYY-MM-DDTHH:MM:SS)
+AND timestamp <= "END_TIME" -- ISO 8601 format (YYYY-MM-DDTHH:MM:SS)
+AND (
+    logName:"logs/fleetengine.googleapis.com%2Fcreate_delivery_vehicle" OR
+    logName:"logs/fleetengine.googleapis.com%2Fupdate_delivery_vehicle" OR
+    logName:"logs/fleetengine.googleapis.com%2Fcreate_task" OR
+    logName:"logs/fleetengine.googleapis.com%2Fupdate_task"
+)
+```
+
 2. Download the logs in JSON format and optionally zip them
 3. Import the JSON/ZIP file to Fleet Debugger
 

docs/PlannedPaths.md

@@ -1,5 +1,8 @@
-# LMFS Planned Paths
+# Planned Paths
 
 Displays all planned routes for the vehicle.
+This data comes directly from Navigation SDK, but requires the enablement of restriced use logs.
+
+We are also working on how we can integrate planned paths that are from server side routing. e.g routes from before navigation SDK guidance started.
 
 ![Screenshot](screenshots/planned_paths.png)

docs/Speed.md

@@ -1,5 +1,3 @@
 # Speed
 
-Lorem ...
-
 ![Screenshot](screenshots/speed.png)

docs/reporting-issues.md

@@ -1,36 +1,6 @@
-# Generating Bundle
-To generate a support bundle for reporting issues with either debugger or the full ODRD/LMFS solution run the following commands:
+# Data file
 
-```
-# Generate data files for reporting issues
-dune-buggy.js historical --apikey nokey  --vehicle=my-vehicle-id
-# build sharable, static artifact.  Any webserver should be able to host this.
-npm run build
-tar -czf support-dump.tgz build
-```
-
-The generated support-dump.tgz file can be included in bug reports & communication with support.
-
-# Viewing Bundle
-
-The view-bundle.sh script starts a simple webserver and attempts to open a browser window with the
-correct url (including specifying a valid API key).
-
-```
-tar -xzf support-dump.tgz
-cd build
-./view-bundle.sh
-```
-
-Note that any simple http server can be used to serve the index.html file in the build directior.  The following
-would suffice:
-```
-python3 -m http.server
-```
-
-# Viewing bundle with newer version of the debugger
-
-The data used in the debugger is contained within the data.json file.  This file can be copied
-out of support bundle and placed in the 'public' directory of a fleet-debugger github repo.
-Once copied, 'npm start' in the fleet-debugger repo will let this bundle be viewed with the
-newer UI.
+Since all the data is in the browsers local storage only, sending deep link url's is not really a feature. This would only center the map.
+For this reason, if you experience an issue zip compress your cloud logging json file that reporoduces the issue.
+Search and replace sensitive strings, for instance vehicle ID or trip ID before sending this file in a bug report or similar.
+S