Broadened the wildcard.

Author: Eli

examples/dropbox/dropbox_spec_ccf.yaml

@@ -9,7 +9,7 @@ data:
   - name: ccfb
     skip: False
     collect:
-      file_pattern: "CC_Gate_Positions_2026*.csv"
+      file_pattern: "CC_Gate_Positions_*.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,9 +52,8 @@ data:
       subloc: radial
       time_zone: ${target_tz}
       time_zone_label: ${target_tz_label}  
-      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.
+      latitude: registry_lookup        # coordinates are provided by the registry and cannot be supplied here in a way that might contradict 
+      longitude: registry_lookup       # 'registry_lookup' is just a marker for clarity on this point
 
     output:
       repo_name: structures_formatted    # This is a pointer to an entry in dbase_config.yaml