99 - name : ccfb
1010 skip : False
1111 collect :
12- file_pattern : " CC_Gate_Positions *.csv"
12+ file_pattern : " CC_Gate_Positions_ *.csv"
1313 wildcard : time_overlap # time_sharded | time_overlap | data | none.
1414 # If time_sharded, indicates non-overlapping timestamps that uses year chunking.
1515 # If time_overlap, indicates wildcards are ordered by date 20250531(lexicographic must = chronological)
@@ -50,22 +50,27 @@ data:
5050 unit : ft
5151 subloc : radial
5252 time_zone : ${target_tz}
53- time_zone_label : ${target_tz_label}
53+ time_zone_label : ${target_tz_label}
5454 latitude : 37.8299 # projected will be inferred. User changes should be made to projected, not latitude/longitude.
55- longitude : -121.55694
55+ longitude : -121.55694 # what happens when this and registry entry have conflicting metadata for something like latitude.
56+ # seems like this prevails, but we should prevent conflicts.
5657
5758 output :
58- repo_name : structures
59- staging :
59+ repo_name : structures_formatted # This is a pointer to an entry in dbase_config.yaml
60+ staging : # This is where the read and transformed time series will be staged.
61+ # It will be used to update the repo, but that uses update_repo and may not mean a full replacement
6062 dir : ./drop_staging
6163 write_args :
6264 float_format : " %0.3f"
6365 chunk_years : False
6466 reconcile :
65- repo_data_dir : ./fake_repo/formatted
66- prefer : staged
67+ # repo_data_dir: ./fake_repo/formatted # This is a practice directory so you don't go overwriting a real repo while developing the recipe
68+ # When omitted the target location is the repo_root as configured in dbase_config.yaml
69+ prefer : staged # This is an argument to the update process:
70+ # - staged means "prefer the new stuff we staged"
71+ # - repo means "prefer the stuff in the repo, just top off with any new time stamps"
6772 allow_new_series : true
68- inspection :
69- recent_years : 3
70- p3 : 0.15
71- p10 : 0.05
73+ inspection : # update parameters. These should be included but seldom change
74+ recent_years : 3 # Up to 3 year old data will be checked whenever update is performed
75+ p3 : 0.15 # probability of a spot check for 3-10 ago, differences will trigger full replacment of all years
76+ p10 : 0.05 # pprobability of a spot check for data 10+ years old, differences will trigger full replacment of all years
0 commit comments