Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes a datatype to accommodate bad service alert data #3503

Merged
merged 1 commit into from
Oct 16, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,9 @@ schema_fields:
mode: REPEATED
fields:
- name: start
type: INTEGER
type: STRING
- name: end
type: INTEGER
type: STRING

- name: informedEntity
type: RECORD
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,9 @@ int_gtfs_rt__service_alerts_fully_unnested AS (
cause,
effect,

-- active periods
unnested_active_period.start AS active_period_start,
unnested_active_period.end AS active_period_end,
-- active periods, converting from STRINGS since some agency has bad data that insn't unnestable as INTs
SAFE_CAST(unnested_active_period.start AS INT) AS active_period_start,
SAFE_CAST(unnested_active_period.end AS INT) AS active_period_end,

-- informted entities
unnested_informed_entity.agencyId AS agency_id,
Expand Down
Loading