Add-site-luguaf
From PTAGISWiki
Contents |
Procedure for adding a new site to the ALRS database
6/28/2006
Using the ALRS webapp for this site entry. Using these data sources:
- Legacy RKM table http://www.psmfc.org/pittag/DB_Codes/Codes-Main.html#TRS
- TMT rendition of RKM ftp://ftp.ptagis.org/Reports/TMT/rkmcodes.txt
Here are the tables and fields I needed to populate:
location
- loc_id: [ 0 makes a new ID ]
- location_name: Lukes Gulch Acclimation Facility, SF Clearwater River
- lat_decimal: 46.032667 (publish 6 points of precision for point sites)
- lon_decimal: -115.976033 (publish 3 points of precision for reaches)
- lat_lon_source: GPS
- lat_estimate: 46.032667
- lon_estimate: -115.976033
- est_lat_lon_source: GPS
- elevations_msl: 0
- y_coord: 165
- x_coord: 344
river_segment
Using pre-existing segment for South Fork Clearwater River
- SegId: 52
location_in_segment
When prompted for Sites of interest and segments of interest: Oxbow (case-sensitive) for both fields
- site_id: LUGUAF
- loc_id: (from location table)
- seg_id: -1 (from river_segment table)
- site_type: acclimation pond
- site_description: Constructed environment
- locality_radius: 500
- general_locality_site:
- km_in_reach: 014
- km_total: 880
- category: leave blank (hybrid, adult, juvenile, tag)
- rkm_fixed_site_y_n: N (A fixed location, such as a dam, bridge or trap, or a temporary release site in a river or stream?)
- fixed_site_y_n: N
- marking_only_y_n: N
- entire_river_y_n: Y
- release_act_suffix_y_n: Y
- archaic_y_n: N
activity_location
- site_code: LUGUAF
- site_id: LUGUAF (key to location-in-segment)
- activity_category: HANDS-ON (hands-on)
- activity_code: TAGGING, RELEASE, RECAPTURE (one record for each activity)
- activity_suffix: blank (con or non continuous flow)
- contact_id: -1
- activity_loc_description: Lukes Gulch Acclimation Facility, SF Clearwater River
- from_km: 0
- to_km: 0
- from_date: 1/1/2006 (from Data > Reports > Interactive > Interrogation sites)
- to_date:
