1)ID numbers were assigned in excel and are shown in the Band_ID files and Encounter_ID files under column A. Band_ID and Encounter_ID are found in m\projects\bird_band\working. All data has been cut and pasted from these files.
Because Arc View does not allow for spaces when displaying the data properly The following changes were made.
Edits: Replaced Band Code = Replace_BC How Obtained = How_Obt Who Reported = Who_Reprt Present Condition = Pres_cond Why Reported = Why_Reprt Region of Recovery = Reg_Recov 10 min of Recovery = 10_min_recv Banders Permit# = BP# Region of Banding = Reg_Band 10min of banding = 10min_B Date Banded = Date_B Band Type = B_Type Cycle Processed = Cy_Proc Hunting Season Survived = Hunt_S_S
2) ID numbers were copied and pasted with the lat/long coordinates into a new excel book. The book was then saved as "Formatted Text (space delimited)". The file was then reopened as fixed width with the columns set to separate id #'s, lat degrees, lat minutes, long degrees, and long minutes into separate columns.
3) Lat/long was then converted to decimal degrees. Y coordinates were calculated by dividing the 3rd digit (of the 7 digit code) by 6 and adding the remainder to the first 2 digits. Dividing the last digit of the code by 6 and adding the remainder to the 4th, 5th, and 6th digits created X coordinates. Ex. From "3351153", x would = 115 + 3/6 and y would = 33 + 5/6. Coordinates are represented to the 12th decimal place. Lat comes before long in the 7-digit code, however longitude represents x coordinates and thus needs to be placed before latitude (y coordinates). It is also important to convert X coordinates to negative numbers. This is easily done as an excel function. Ex. If X coordinates are in column G, insert a new column and type "=0-G1". Select the rest of the new column and "fill down" from the edit menu. 4) For point coverages, comma columns were inserted between the ID & X and X & Y columns. The file was then saved again as "Formatted text" reopened again in word. "end" was typed after the final entry and the file was then used as the input file for the generate command in Arc. For the line coverage's, commas columns were inserted between the X & Y columns and "Z" columns were inserted after the ID column and both y columns. An "end" column was placed after the final "Z" column. "Find and Replace" was used in Word to replace all spaces with nothing and all "Z"s with line breaks. Simply go to "Find & Replace" (under edit menu) hit the space bar once in the Find box and then go to "Replace all". Afterwards, type z in the Find box, and insert "manual line break" from the "Special" menu into the Replace box.
bands: banding data from Bands_ID recovery: bird recovery data from "10 Minute Block of Recovery" column in Encounter_ID encounter: bird encounter data from "10 minute block of Encounter" column in Enounter_ID en_rec: both encounter and recovery data taken from their respective columns in Encounter_ID. Recovery coordinates come before encounter coordinates.
Each of the above files shows both an excel and text icon. The excel version is the data in fixed width and can be used for manipulation. The text version is the text file used for input when generating the coverages.
5) All of the above files were used to generate new coverages. Each one is projected in both decimal degrees and UTM. Those projected in UTM have the same name with the suffix "pro". bird_recov: bird recovery point data bird_enctr: bird encounter point data bird_band: bird banding point data bird_enrec: bird encounter and recovery line data (important note: recovery points are from node and encounter points are the to node)
Encountered and recovered files combined and frequency column calculated.
Coverage clipped to Southern California.