You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CREATETABLEtraffic.tmc_study_legacy_no_xwalk_bikes ASSELECT*FROMtraffic.tmc_study_legacy;
COMMENT ON TABLE traffic.tmc_study_legacy_no_xwalk_bikes IS'A backup of `traffic.tmc_study_legacy` created on 2024-11-06 before bikes in x-walk were added to bicycle volumes.';
ALTERTABLEtraffic.tmc_study_legacy_no_xwalk_bikes OWNER TO traffic_admins;
GRANTSELECTON TABLE traffic.tmc_study_legacy_no_xwalk_bikes TO bdit_humans;
For Turning Movement Counts conducted September 2023 and on, we are updating bicycle counts to include bicycles on road, plus cyclists riding in the crosswalk.
Note: These cyclists are riding their bikes in the crosswalk area, usually before or after riding on the sidewalk. People walking their bikes are counted as pedestrians.
Here’s an example of how that will work for northbound traffic, or the South Approach of an intersection.
What will be updated?
Only Turning Movement Counts conducted September 2023 and on will be updated. Only the bicycle counts will change.
MOVE are adding bikes in crosswalks to the TMC data, but in an opaque way.
traffic.tmc_study_legacy
to something liketraffic.tmc_study_legacy_no_xwalk_bikes
with a comment on the range of data for which it appliesThe text was updated successfully, but these errors were encountered: