UWEC Track and Field Area By Peter Curry and Mike Kadow
1
Explanation of Our Project We mapped the following items located in the upper campus region: -The perimeter of the whole field -The outside perimeter of the track -The inside perimeter of the track -The football field inside the track -The field goal posts -The backstop in the northeast corner of the field -The scoreboard All of the GPS mapping went smoothly, except for a few minor mishaps. First of all, it got dark around 7:30 p.m. Fortunately, the GPS unit's display screen lit up in a neon green color. However, it got fairly difficult to see the keys on the GPS unit. The second problem a bit more major. While were mapping the outside perimeter of the track, the memory of the GPS unit filled up. We deleted the biggest and oldest files in order to create more room on the unit for our project. However, we accidently continued recorded our data as "area" instead of "lines" (as we had been doing previously). This situation created problems for us later when editing our data. Instead of a smooth line around outside perimeter of the track, the GPS unit connected stray lines in unnecessary places. Therefore, we had to take time to delete those lines and create new ones to make the map look appropriate and presentable. As one can see on the map in the upper left- hand corner of our poster, our PDOP's ranged from 1.8 to 6.0. The PDOP's were lower when we were walking along the edge of the field by McPhee (the athletic building on the UWEC campus). Otherwise, the PDOP's were fairly high when mapping the whole field, ranging mostly from 3.6 to 6.0. Our readings remained fairly consistent when mapping the track and the football field, for they maintained a concise of 2.6 to 3.5. One major conflict we encountered with the PDOP's occured as we were traveling under trees on the edge of the field. Tree branches obstructed satellite signals, and so the GPS unit failed to record anything in those few short moments. Overall, working on this final project was a very rewarding experience. It allowed both of us the opportunity to put our skills with GPS , Adobe Illustrator, and ArcView into practical application. Football Field UWEC Track and Field Area 1/4 Mile Track Our Raw Data Field Goals Backstop Scoreboard The "Soul Train" Max_PDOP 1. 8 2.0 2. 1 2. 5 2. 6 3. 0 3.1 3.5 3. 6 4. 0 4. 1 4. 5 4. 6 5. 0 5. 1 5. PDOP's 5 5. 6 6. 0 Overview of Mapped Area By Peter Curry and Mike Kadow Fall 2001 UWEC Track and Field Area Geography 199
Transcript of UWEC Track and Field Area By Peter Curry and Mike Kadow
Explanation of Our Project We mapped the following items located in the upper campus region: -The perimeter of the whole field -The outside perimeter of the track -The inside perimeter of the track -The football field inside the track -The field goal posts -The backstop in the northeast corner of the field -The scoreboard All of the GPS mapping went smoothly, except for a few minor mishaps. First of all, it got dark around 7:30 p.m. Fortunately, the GPS unit's display screen lit up in a neon green color. However, it got fairly difficult to see the keys on the GPS unit. The second problem a bit more major. While were mapping the outside perimeter of the track, the memory of the GPS unit filled up. We deleted the biggest and oldest files in order to create more room on the unit for our project. However, we accidently continued recorded our data as "area" instead of "lines" (as we had been doing previously). This situation created problems for us later when editing our data. Instead of a smooth line around outside perimeter of the track, the GPS unit connected stray lines in unnecessary places. Therefore, we had to take time to delete those lines and create new ones to make the map look appropriate and presentable. As one can see on the map in the upper left-hand corner of our poster, our PDOP's ranged from 1.8 to 6.0. The PDOP's were lower when we were walking along the edge of the field by McPhee (the athletic building on the UWEC campus). Otherwise, the PDOP's were fairly high when mapping the whole field, ranging mostly from 3.6 to 6.0. Our readings remained fairly consistent when mapping the track and the football field, for they maintained a concise of 2.6 to 3.5. One major conflict we encountered with the PDOP's occured as we were traveling under trees on the edge of the field. Tree branches obstructed satellite signals, and so the GPS unit failed to record anything in those few short moments. Overall, working on this final project was a very rewarding experience. It allowed both of us the opportunity to put our skills with GPS , Adobe Illustrator, and ArcView into practical application.
p
Football Field
UWEC Track and Field Area
1/4 Mile Track
Our Raw Data
Field Goals
BackstopScoreboard
The "Soul Train"
Max_PDOP
1. 8 2. 0
2. 1 2. 5
2. 6 3. 0
3. 1 3. 5
3. 6 4. 0
4. 1 4. 5
4. 6 5. 0
5. 1 5.
PDOP's
5
5. 6 6. 0
Overview of Mapped Area
By Peter Curry and Mike KadowFall 2001 UWEC Track and Field AreaGeography 199
