Add mart_gtfs.fct_vehicle_locations_dwell table

[tiffanychu90]

Description

Describe your changes and why you're making them. Please include the context, motivation, and relevant dependencies.

Part of #3645

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

How has this been tested?

Include commands/logs/screenshots as relevant.

For making a new table:

jovyan@jupyter-tiffanychu90 ~/data-infra/warehouse (vp-dwell) $ poetry run dbt run -s fct_vehicle_locations_dwell
18:20:03  Running with dbt=1.5.1
18:20:09  [WARNING]: Configuration paths exist in your dbt_project.yml file which do not apply to any resources.
There are 1 unused configuration paths:
- models.calitp_warehouse.mart.ad_hoc
18:20:09  Found 477 models, 1018 tests, 0 snapshots, 0 analyses, 852 macros, 0 operations, 12 seed files, 178 sources, 4 exposures, 0 metrics, 0 groups
18:20:09  
18:20:12  Concurrency: 8 threads (target='dev')
18:20:12  
18:20:12  1 of 1 START sql table model tiffany_mart_gtfs.fct_vehicle_locations_dwell ..... [RUN]
18:20:21  1 of 1 OK created sql table model tiffany_mart_gtfs.fct_vehicle_locations_dwell  [CREATE TABLE (392.0k rows, 2.1 GiB processed) in 8.31s]
18:20:21  
18:20:21  Finished running 1 table model in 0 hours 0 minutes and 11.33 seconds (11.33s).
18:20:21  

For adding docs:

jovyan@jupyter-tiffanychu90 ~/data-infra/warehouse (vp-dwell) $ poetry run dbt docs generate
18:25:18  Running with dbt=1.5.1
18:25:21  [WARNING]: Configuration paths exist in your dbt_project.yml file which do not apply to any resources.
There are 1 unused configuration paths:
- models.calitp_warehouse.mart.ad_hoc
18:25:22  Found 477 models, 1018 tests, 0 snapshots, 0 analyses, 852 macros, 0 operations, 12 seed files, 178 sources, 4 exposures, 0 metrics, 0 groups
18:25:22  
18:25:31  Concurrency: 8 threads (target='dev')
18:25:31  
18:26:16  Building catalog
18:26:40  Catalog written to /home/jovyan/data-infra/warehouse/target/catalog.json

Post-merge follow-ups

Document any actions that must be taken post-merge to deploy or otherwise implement the changes in this PR (for example, running a full refresh of some incremental model in dbt). If these actions will take more than a few hours after the merge or if they will be completed by someone other than the PR author, please create a dedicated follow-up issue and link it here to track resolution.

• No action required
• Actions required (specified below)

[tiffanychu90]

@vevetron I only tested the sql on one operator, one day to see if I'm getting results I want. Can you give me comments related to how to better structure the SQL?

[vevetron]

#3651 - this should help with the python dbt checks. Something might need to be updated...

[tiffanychu90]

@vevetron I only tested the sql on one operator, one day to see if I'm getting results I want. Can you give me comments related to how to better structure the SQL?

Feedback:

• rename tables for CTE to be more readable as is...merged, get_next should get renamed
• add vp_primary_direction...a single column in mart_gtfs is not that consequential!
• run dbt test with -s +fct_vehicle_locations_dwell+ to make sure it's good
• formatter for dbt sql