-
Notifications
You must be signed in to change notification settings - Fork 8
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
HERE new data pulling plan #892
Comments
|
The new columns only applied for path data... and not probe_mix. The selection for those columns does not show up for probe_mix requests. |
The oldest date we can backfill is 2018-01-01, the oldest data we have currently in the database is 2017 Sept. So if we were to backfill we will only loss a few months of data. |
We are gonna get some new columns from here, set up a plan on how to implement pulling new columns.
New Columns:
harmonic_mean
: Harmonic Meansvdt
: Vehicle Distance Travelledprobe_count
: Probe CountWe should keep pulling all the other columns we are pulling for now, even if they are similar to these new columns:
e.g.
mean
, arithmetic mean I guesssample_size
, depending on if you are pulling path only, or probe mix, the count differsWe can re-evaluate whether we want to keep pulling them after getting the actual data.
Step 1:
Pull a sample of new data and observe the order of columns.
Step 2:
Add new columns to
here.ta
andhere.ta_path
Step 3:
Edit here.ta_view and here.ta_path_view to include new columns
Step 4:
Edit insert trigger to include new columns in the correct order.
Step 5:
Edit here pulling api, to request for these extra columns.
The text was updated successfully, but these errors were encountered: