?period_name=hod / dow / moy returns 500 for v3 /measurements

[majesticio]

@caparker not sure if the problem is here that the query in measurements.py doesn't have a way to use 'hod', 'dow', or 'moy' in the query, and is not failing gracefully if period_name=hod is used. Will try to put '1hod' into the SQL query similarly to '1 month'. example:
https://api.openaq.org/v3/locations/2178/measurements?date_from=2023-06-12T12:00:00&date_to=2023-06-13T13:00:00&period_name=hod

[caparker]

Those are from the /v2/averages method and likely do not have a place in the measurements endpoint because they do not return a valid timestamp. The same method would work in the trends endpoint though. I would recommend that split it out into two different query models, PeriodNameQuery which could be used in /v2/averages and /v3/trends and then maybe PeriodQuery which would be used in the /v3/measurements endpoint.

openaq-api-v2/openaq_fastapi/openaq_fastapi/routers/averages.py

Line 137 in 66fb112

factor = "to_char(datetime - '1sec'::interval, 'HH24') as hod"

[majesticio]

Thanks for clarifying, that was an assumption on my part that those were supposed to be included