Made some comments and readme fixes.

Author: V

jobs/gtfs-schedule-validator/Dockerfile

@@ -28,7 +28,7 @@ COPY ./gtfs-validator-4.1.0-cli.jar ${V4_1_VALIDATOR_JAR}
 ENV V4_2_VALIDATOR_JAR=/gtfs-validator-4.2.0-cli.jar
 COPY ./gtfs-validator-4.2.0-cli.jar ${V4_2_VALIDATOR_JAR}
 
-# v5.0.0 from https://github.com/MobilityData/gtfs-validator/releases/download/v5.0.0/gtfs-validator-5.0.0-cli.jar
+# v5 from https://github.com/MobilityData/gtfs-validator/releases/download/v5.0.0/gtfs-validator-5.0.0-cli.jar
 ENV V5_VALIDATOR_JAR=/gtfs-validator-5.0.0-cli.jar
 COPY ./gtfs-validator-5.0.0-cli.jar ${V5_VALIDATOR_JAR}
 

jobs/gtfs-schedule-validator/README.md

@@ -27,9 +27,31 @@ since data creation.
 If you run into trouble when adding the new validator jar, it's because the default set for check-added-large-files in our pre-commit config which is a relatively low 500Kb. It's more meant as an alarm for local development than as an enforcement mechanism.
 You can make one commit that adds the jar and temporarily adds a higher file size threshold to the pre-commit config [like this one](https://github.com/cal-itp/data-infra/pull/2893/commits/7d40c81f2f5a2622123d4ac5dbbb064eb35565c6) and then a second commit that removes the threshold modification [like this one](https://github.com/cal-itp/data-infra/pull/2893/commits/1ec4e4a1f30ac95b9c0edffcf1f2b12e53e40733). That'll get the file through.
 
-Remember you need to rebuild and push the latest docker file to dhcr before changes will be reflected in airflow runs.
-
-You will need to parse the rules.json from the mobility validator.  [Here is a gist to help](https://gist.github.com/vevetron/7d4bbebd2f1d524728d5349293906e3a).
-
-Here is a command to test
-docker-compose run airflow tasks test unzip_and_validate_gtfs_schedule_hourly validate_gtfs_schedule 2024-03-22T18:00:00
+Remember you need to rebuild and push the latest docker file to `dhcr.io` before changes will be reflected in airflow runs.
+
+You will need to parse the `rules.json` from the mobility validator.  Here is a code example for the upgrade to v5:
+```
+# https://github.com/MobilityData/gtfs-validator/releases/tag/v5.0.0
+import json
+import pandas as pd
+
+# Replace with your JSON data 
+with open('rules.json') as f:
+    data = json.load(f)
+result = []
+for key in data.keys():
+    # print(key)
+    result.append({
+        'code': data[key]['code'],
+        'human_readable_description': data[key]['shortSummary'],
+        'version': 'v5.0.0',
+        'severity': data[key]['severityLevel']
+    })
+# Create CSV
+df = pd.DataFrame(result)
+df.to_csv('gtfs_schedule_validator_rule_details_v5_0_0.csv', index=False)
+```
+
+Here is a command to test once you have appropriate gtfs zip files in the test bucket:
+
+`docker-compose run airflow tasks test unzip_and_validate_gtfs_schedule_hourly validate_gtfs_schedule YYYY-MM-DDTHH:MM:SS`