### Data Type and Required Field Validation
**Objective:**
- Validate the types of the fields in the JSON data and ensure required fields are present and properly formatted.
**Process:**
1. **Initial Setup:**
- A JSON object containing bus stop data is provided. Each entry has fields like `bus_id`, `stop_id`, `stop_name`, `next_stop`, `stop_type`, and `a_time`.
2. **Validation:**
- Create a dictionary that tracks errors for each field.
- Iterate over each entry in the data:
- Check if `bus_id` and `stop_id` are integers.
- Verify `stop_name` is a non-empty string.
- Ensure `next_stop` is an integer.
- Confirm `stop_type` is either 'S' (start), 'O' (on demand), 'F' (finish), or empty.
- Check `a_time` is a non-empty string.
3. **Output:**
- The code counts and reports the number of errors for each field type and the total errors across all fields.
### Syntax and Format Validation
**Objective:**
- Ensure that specific fields in the data conform to expected formats using regular expressions.
**Process:**
1. **Stop Name Validation:**
- Ensure stop names follow a pattern, like ending with "Street", "Avenue", "Boulevard", or "Road", and start with an uppercase letter.
2. **Stop Type Validation:**
- Ensure stop types are either 'S', 'O', 'F', or empty.
3. **Arrival Time Validation:**
- Verify that the time follows the format `HH:MM`.
4. **Output:**
- Report the number of format errors found in each field (stop names, stop types, and arrival times).
### Count Stops Per Bus Line
**Objective:**
- Count and report the number of stops for each bus line.
**Process:**
1. **Group Stops by Bus Line:**
- Organize the data by `bus_id`, collecting all stops under each bus line.
2. **Count Stops:**
- For each bus line, count the number of stops and print the results.
### Check for Start and End Stops
**Objective:**
- Verify that each bus line has both a start (`S`) and an end (`F`) stop, and list all start, transfer, and finish stops.
**Process:**
1. **Identify Stops:**
- For each bus line, check if it has at least one start and one finish stop.
- Collect and categorize all stops into start, transfer, and finish stops.
2. **Output:**
- Print the total number and names of start, transfer, and finish stops.
- If any bus line lacks a start or finish stop, report an error.
### Validate Arrival Times
**Objective:**
- Ensure that the arrival times for each stop are in ascending order along the bus route.
**Process:**
1. **Track Arrival Times:**
- For each bus line, order the stops according to their sequence.
- Compare the arrival time of each stop with the next one to ensure it is earlier.
2. **Output:**
- If any stop has a time that is not in the correct sequence, report an error.
### On-Demand Stop Validation
**Objective:**
- Ensure on-demand stops are not the same as start, finish, or transfer stops, which would be incorrect.
**Process:**
1. **Identify Stop Types:**
- Separate stops into start, finish, transfer, and on-demand categories.
- Identify and report any on-demand stops that are also classified as start, finish, or transfer stops.
2. **Output:**
- Report any incorrectly classified on-demand stops, or confirm that the classification is correct.
**Summary:**
Each stage of the process focuses on a different aspect of validating and analyzing bus stop data. The code is designed to ensure data correctness by checking types, formats, sequencing, and logical consistency across different fields and bus lines. By sequentially validating and analyzing the data, errors are detected and reported, ensuring that the bus data is accurate and reliable.
