Open ChristinaLast opened 5 months ago
1 locationId float8 YES NULL NULL NULL
2 location text YES NULL NULL NULL
3 parameter text YES NULL NULL NULL
4 value float8 YES NULL NULL NULL
5 date text YES NULL NULL NULL
6 unit text YES NULL NULL NULL
7 coordinates text YES NULL NULL NULL
8 country text YES NULL NULL NULL
9 city text YES NULL NULL NULL
10 isMobile bool YES NULL NULL NULL
11 isAnalysis text YES NULL NULL NULL
12 entity text YES NULL NULL NULL
13 sensorType text YES NULL NULL NULL
Ensuring that the locationId
for Amgalan and US Diplomatic Post are the same as in the cohorts_MN
table.
cohort_builder
, this will generate the windows (e.g. cohort
columns), and extract the date utc and x y from coordinates. cohorts_all_MN
table and generate a uniqueId
which is a combination of the locationId
, timestamp_utc
and cohort
column. The text description of how to translate Rob's columns to the API columns: Key differences:
date
columns should retain the utc and local {"utc": "2024-01-07T18:00:00+00:00", "local": "2024-01-08T02:00:00+08:00"}
unit
column should be µg/m³
rather than µg/m³
location
column should contain the location
in Ulaanbaatar Particulate Matter Sensor Data
mobile
should be FALSE
if false
(which is currently a type str when it should be processed to boolean in postgresisAnalysis
column should be null
sensorType
should be "reference grade"
entity
columns should be assigned from sourcetype
Steps to build first model version