Skip to content

export_measures implicitly converts number-like data, resulting in bad 0-lead labels #393

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

Open
shippy opened this issue Sep 25, 2020 · 0 comments

Comments

@shippy
Copy link
Contributor

shippy commented Sep 25, 2020

This is a problem for youthreport_shq1 and youthreport_shq3, which are coded like so:

code label
1800 6:00p.m.
1830 6:30p.m.
1900 7:00p.m.
1930 7:30p.m.
2000 8:00p.m.
2030 8:30p.m.
2100 9:00p.m.
2130 9:30p.m.
2200 10:00p.m.
2230 10:30p.m.
2300 11:00p.m
2330 11:30p.m.
0000 12:00a.m.
0030 12:30a.m.
0100 1:00a.m.
... ...

Instead of 0000, we export 0. Instead of 0030, we export 30. While this can be worked around, it is contrary to the data dictionary we publish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant