Updated CCF recipe for dropbox in examples.

Author: Eli

dms_datastore/config_data/structures_registry.csv

@@ -2,7 +2,7 @@
 tpsb,Tom Paine Slough Barrier,37.790311,-121.418505,639249.8742,4183727.837
 oldrb,Old River Barrier,37.810146,-121.542836,628267.6895,4185750.765
 glcb,Grant Line Canal Barrier,37.819771,-121.448316,636570.6401,4186952.71
-ccfbg,Clifton Court Forebay Radial Gates,37.829885,-121.556913,626994.7,4187921.712
+ccfb,Clifton Court Forebay Radial Gates,37.829885,-121.556913,626994.7,4187921.712
 midrb,Middle River Barrier,37.885483,-121.482265,633463.8794,4194194.92
 smscg,Suisun Marsh Salinity Control Structure,38.0932,-121.886341,597653.8558,4216741.398
 dcc,Delta Cross Channel Radial Gates,38.246588,-121.509607,630416.5954,4234225.234

examples/dropbox/dropbox_spec_ccf.yaml

@@ -9,7 +9,7 @@ data:
   - name: ccfb
     skip: False
     collect:
-      file_pattern: "CC_Gate_Positions_*.csv"
+      file_pattern: "CC_Gate_Positions_2026*.csv"
       wildcard: time_overlap    # time_sharded | time_overlap | data | none. 
             # If time_sharded, indicates non-overlapping timestamps that uses year chunking. 
             # If time_overlap, indicates wildcards are ordered by date 20250531(lexicographic must = chronological)
@@ -52,8 +52,8 @@ data:
       subloc: radial
       time_zone: ${target_tz}
       time_zone_label: ${target_tz_label}  
-      latitude: 37.8299         # projected will be inferred. User changes should be made to projected, not latitude/longitude. 
-      longitude: -121.55694     # what happens when this and registry entry have conflicting metadata for something like latitude.
+      latitude: registry_lookup        # projected will be inferred. User changes should be made to projected, not latitude/longitude. 
+      longitude: registry_lookup       # what happens when this and registry entry have conflicting metadata for something like latitude.
                                 # seems like this prevails, but we should prevent conflicts.
 
     output: