Friday, March 13, 2015

Exercise 7 - ArcPad Data Collection II

Introduction

The exercise this week was the third and final part of the microclimate exercise. This consisted of the entire class collecting ground points across the UWEC campus. The whole class was to use the same geodatabase that was provided by one of the students. After all the groups had collected the points in each of their areas we were then going to put them all together into one feature class so that we would have all of the points collected on the same map. We could then create maps of the data collected.

Study Area

The area that we were to map out included the UWEC campus (see figure 1) with the class being split into seven group and each group taking a section shown in the yellow polygons. My group had the western portion of the lower campus.

The study area including each group's section shown in yellow. (fig. 1)

Methods

We started out with the same geodatabase as a class and split into groups of two. One of us had the Trimble GPS device and the other had the Kestral. We went to our section to collect the data and started in the western portion and worked out way in a circle until we had the entire section covered with points. One of us would be measuring the different climate fields from the geodatabase which was described in exercise 5 and the other would input the information into the Trimble. We took turns collecting the data and inputting the data. We weren't able to collect wind direction however because we didn't have a compass to collect it.

The data we collected included wind speed, surface temperature, temperature at two meters high, dew point, humidity and ground cover.

One we had collected as many points as we had time for we came back to the classroom and combined everyone's feature class into a single geodatabase. One we got it into one feature clad with everyone's points included we were then able to map the data in coherent ways.

Discussion

The data provided us with many different possibilities for map making. Below are some of the different maps I was able to create with the data we collected. I was able to create just straight data plots of the different fields as well as interpolation of the data across the study area.

Some problems I ran into while collecting points, besides not being able to collect wind speed, included sometimes not being able to collect points due to buildings being in the way or otherwise inaccessible locations.

Map of the dew point across campus (fig. 2)

Map of prevent humidity across campus (fig. 3)

Map of the surface temperature across campus (fig. 4)

Map of the wind speed across campus (fig. 5)

Conclusion

The exercise was a great way learn how to collect field data and how to use Kestral devices. We also were able to create some informational maps that showed interesting trends in the microclimate of UWEC. Collecting data in the field is a long and detailed process and practicing this skill can help get more efficient in using GPS devices and data collection devices such as the Kestral.

Thursday, March 5, 2015

Exercise 6 - ArcPad Data Collection I

Introduction

In this exercise we set up the ArcPad devices for the next week when we will go out and collect point data for micro climates across the UWEC campus. Last week we set up a geodatabase with domains for collecting micro climate data. We set up the fields that we wanted to collect and tried out a test run for next week when we do it for real.

Study Area

Our area of interest is the UWEC campus as seen below (fig. 1). We will mostly stick to the open mall area in the middle. In the picture it is shown as a dirt field however now it is covered in snow. We will be collecting 20 points in the final data collection next week. This week we just took a few points to test the ArcPad application out.

Study Area of the UWEC campus (fig. 1)
Methods

ArcPad is a mobile version of ArcGIS that can be accessed out in the field using a Trimble device as seen below (fig. 2). The device application is a watered-down version of ArcGIS with many of the same features as the desktop version. We are able to access ArcGIS .mxd files the same way as on the desktop but we have to transfer them over to the device first.

Trimble ArcPad device (fig. 2)
First we need to take the geodatabase that we created last week and alter it to be able to be put on the ArcPad device. To do this I first pull up the file in ArcGIS on our desktop. I then access the extension ArcPad Data Manager. I then click Get Data for ArcMap and work through the ArcPad wizard in order to create a folder containing the .mxd file with both the feature class we created last week with all of the fields ready, as well as a basemap of the study area. Once we have the ArcPad folder ready we have to first make a copy of this folder just in case.

We then connected the ArcPad to the computer and pull up the Trimble folder within Windows Explorer. Next we find the folder within the Trimble that we wish to put our .mxd file in and simply copy and paste it in.

Now that we can access the .mxd file from our Trimble we are able to edit the feature class that we made in it last week. The feature class was a micro-climate point feature class with fields that included temperature, wind speed, wind direction, dew point, humidity, ground cover, wind chill and others. Once we were out in the field we started to collect points. To do this we first need to turn on the satellite receiver in order to get a GPS signal. Once we get a strong signal from surrounding satellites we can edit the point feature class. Once in the editing mode on the ArcPad we can just click the point feature class and collect a point. The window then comes up with the values that we wish to put in which include the fields that we set up in the geodatabase last week. To measure the micro-climate data we need a Kestrel meter as shown below (fig. 3). The Kestrel meter measures all kinds of climate data including temperature, wind speed, dew point and humidity.
Kestrel Meter for measuring micro-climate information (fig. 3)
I measured out the temperature at surface, the temperature at 2 meter height, humidity, wind speed and dew point with the Kestrel meter. The wind direction will be measured by a compass which we lacked this week but will have next week. The ground cover then was to be selected by a drop down menu that I created in domains last week. Once we collected enough points we went inside.

Now we can take the data off of the Trimble. To do this we simply copy and paste the folder from the Trimble back into the folder we took it out of. Next we go into ArcGIS and click Get Data from ArcPad in the ArcPad Data Manager Toolbar from before. The wizard then displays the points which we can then save as a feature class in a geodatabase on the computer.

Discussion

I had no problems with my Trimble however my partner need help getting his background basemap to show up on his Trimble. To fix that we simply took a lidar image and set the extent at the area of interest and that allowed us to put a background image on the Trimble so that we could see where we were when collecting out points.

The test run went very smoothly and next week we should be able to start collecting data without any problems or delays.

Conclusion


This test run was very important in ironing out any kinks or problems we could encounter when first go out into the field to collect data. Now however we have all of the data ready to go and should have no problems with the collection, feature class or geodatabase going in the exercise next week.

Sources
ArcPad photo and information from ESRI Online: Link
Kestrel Meter photo and information from KestrelMeters.com Link

Thursday, February 26, 2015

Exercise 5 - Creating A Geodatabase with Domains

Introduction

Geodatabases are a key part in using GIS technology and analyzing geospatial data. When creating one to be used in the field you must create domains beforehand to make collecting data in the field easier. A domain is a key for the data to follow when you are collecting it in the field in order to reduced the occurrence of data mishaps. An example would be setting a temperature field to between 0 and 100 so that if you accidentally input 200 degrees instead of 20 the feature class doesn't allow you to do that.

An important part of creating a geodatabase is planning your field methods ahead of time in order to get as much information collected out in the field as possible. In this exercise we used the example of collecting micro-climate data at different points on campus which we will do in the following exercise. We first need to plan out what we will be looking at and then any domain we will need to create for those fields. The table below shows the field of the factors we will look at in the field as well as any domains needed for the data collection.

Field
Domain
Temperature (surface)
Floating integer (-30-60°F)
Temperature (head level)
(same as above)
Dew Point
(same as above)
Wind Chill
(same as above)
Wind Speed
Floating integer (0-50 mph)
Wind Direction
Floating integer (0-360°)
Ground Cover
Text with coded values:
GRA - grass
SNW - snow
CON - concrete
BLK - blacktop
SAN - sand
GRV - gravel
OTH – other (specify in notes field)
Notes
Text (extra information not included in the fields above)

The following video goes through the process of creating the geodatabase, domains, feature class and fields. Once this is finished we can clip a basemap using the Extact by Mask spatial analysis tool and we'll be ready for next week's exercise out in the field.


Exercise 4 - Unmanned Aerial Systems (UAS) Mission Planning

Introduction

Unmanned Aerial Systems or UAS is a very important tool in the geospatial sciences. It allows us perform field analysis that couldn't be possible on foot. We can collect aerial imagery and analyze spatial patterns from the air quickly and cheaply. In this exercise we were required to log a couple of hours in the flight simulator program RealFlight and try out different types of UAS aircraft. After we have become familiar with the different kinds of UAS aircraft we then will look at two scenarios where UAS would be useful and decide which type of aircraft would be best suited for each specified scenarios.

Flight Simulator

We needed powerful computers to use the RealFlight 7.5 UAS flight simulator software due to the intense processing power needed to render the graphics. We were to chose two fixed-winged aircraft and two multi-rotor aircraft. I chose the Slinger and F-86 Sabre for the fixed-winged aircraft and the Quad-copter and Explorer 580 for the multi-rotor aircraft I was to try out. I picked different locations for the flight sessions for each different aircraft. I was pretty good at this simulator due heavy practice in my youth through Xbox video games. Below I go through each aircraft flight and what I think they are most useful for.
RealFlight 7.5 software package with controller
Fixed-Wing

Slinger

The Slinger was the first fixed-winged aircraft I tried out. It is battery-powered and propelled by a motor propeller in the rear. It was fairly easy to fly and fun to fly around obstacles and was very fast. However, when flying it from a ground viewpoint it was hard to keep in the air when it got far away. This was very fun to fly and entertaining to try and fly it through buildings and other openings.

Slinger aircraft from RealFlight 7.5

Flight 1
Flight 2
Flight 3
Time

8 minutes
12 minutes
7 minutes
View

From ground
Third person behind aircraft
First person
Wind

15 mph
5 mph
0 mph
Airfield

Junkyard
Junkyard
Junkyard
Reason for crash

Lost view of aircraft and hit the ground
Ran out of battery
Hit bird (kind of on purpose)

F-86 Sabre (Ducted Fan)

This aircraft was a small replica of a real-life aircraft and handled similarly to the Slinger except with more maneuverability and more speed. I tried some trials where I flew through rings and its maneuverability made that pretty easy. The high speeds did make it harder to control but if I kept it higher it wasn't an issue.

F-86 Sabre aircraft from RealFlight 7.5

Flight 1
Flight 2
Flight 3
Flight 4
Time

5 minutes
7 minutes
8 minutes
6 minutes
View

First person
First person
From ground
From gound
Wind

5 mph
5 mph
5 mph
20 mph
Airfield

Buena Vista
Buena Vista
Buena Vista
Buena Vista
Reason for crash

Hit ground
Hit tree
Hit log cabin trying to go through it
Hit ground


The fixed-wing UAS aircraft had some strengths and some weaknesses. Their strengths are that they can cover large distances quickly, they can fly very high and they are very easy to fly in first person. Their weaknesses are that they aren't maneuverable enough to go through small spaces, they crash easily when out of view or near ground and they aren't easy to fly from the ground. They would be best for collecting data over large distances and collecting data that could be collected high above.

Multi-rotor

Quad-copter

The multi-rotor aircraft were much more difficult to fly than the fixed-winged, but they were also harder to crash. They also were way more maneuverable and stable than the fixed-wing aircraft because you were able to hover and move slowly. However, falling hard will break the rotors and it won't be able to take off again. It is a very fragile aircraft but very stable. I was able to easily maneuver around the castle building and landing was a breeze.

Quad-copter aircraft from RealFlight 7.5

Flight 1
Flight 2
Flight 3
Flight 4
Time

6 minutes
8 minutes
7 minutes
7 minutes
View

From ground
From ground
First person
From ground
Wind

25 mph
0 mph
0 mph
10 mph
Airfield

Castle
Castle
Castle
Castle
Reason for crash

Flipped over and broke
Hit the ground in the courtyard of the castle and broke most of the rotors
Hit eagle statue
Hit lamp post

Explorer 580

I didn't notice much different between the quad-copter and this one, it was just a different model of the same design. I did notice that flying from the ground was hard to control because it was hard to figure how the aircraft was moving in relation to my perspective. As the aircraft turned it was hard to tell which was the front and changing direction proved difficult in that view. In first person however it was very natural and understandable.

Explorer 580 aircraft from RealFlight 7.5

Flight 1
Flight 2
Flight 3
Time

5 minutes
18 minutes
6 minutes
View

First person
Third person
From ground
Wind

0 mph
0 mph
15 mph
Airfield

Sierra Nevada Cliff
Sierra Nevada Cliff
Sierra Nevada Cliff
Reason for crash

Ran into a window that wasn't open
Hit tree
Ran into ledge I was standing on overlooking valley

The multi-rotor UAS aircraft had some strengths and some weaknesses as well. The strengths are that they are very maneuverable allowing for flying into buildings, they have longer battery life than fixed-wing, they can move slowly allowing for low flights and they are easy to fly in first person view. The weaknesses are that they can't cover large distances quickly, they can go super high and they are harder to fly from the ground until they are mastered. They would be most useful in data collection that required slow, low fly aircraft. They are most

Scenarios

We were provided a variety of scenarios to chose from that had dilemmas that could be cured by using UAS. Using the information we found in the flight simulator we were to figure out which type of UAS would best serve each scenario.

Scenario 1 - Power Lines

"A power line company spends lots of money on a helicopter company monitoring and fixing problems on their line. One of the biggest costs is the helicopter having to fly up to these things just to see if there is a problem with the tower. Another issue is the cost of just figuring how to get to the things from the closest airport."

In this situation there is a need to not only get a high view but also a stable view so that a diagnostic can be performed on the power line tower. For this situation I would recommend using a GoPro on a multi-rotor UAS aircraft. This would provide the operator to cheaply examine the tower without having to fly an expensive helicopter from the airport. The GoPro would allow them to see everything at the top of the tower which would provide easy analysis of the tower. They would be able to just bring the quad-copter with them and fly it up to any tower they needed to see if further work was needed on any given tower. No matter how many times they would need to analysis a tower or how many towers needed to be looked at, the savings would be immense.

Scenario 2 - Pineapple Plantation

"A pineapple plantation has about 8000 acres, and they want you to give them an idea of where they have vegetation that is not healthy, as well as help them out with when might be a good time to harvest."

This situation covers a large area and needs a moderate level of detail in the data collection. I would recommend a fixed-winged UAS aircraft with a infrared camera under the payload for this situation. The fixed-wing would provide the user with the ability to cover the large plantation. The height of the fixed-wing and the speed at which it would fly would determine the amount of detail that would be achieved. The infrared camera would be used to collection lidar data that could then be processed using normalized difference vegetation index or NDVI analysis which would let the farmer know which parts of their plantation was healthy and which were not. This process could be repeated as frequently as the farmer wanted providing a extremely cheap and up-to-date solution.

Conclusion

Both types of UAS provided different needs in data collection and it is very important to know which to use in different situations. Fixed-winged aircraft are best for data collection that require large distances to be covered and don't require close detail. Multi-rotor aircraft are best for data collection that require slow moving and close, detailed analysis. Some projects could even use both so that you can achieve detail in places while covering large distances.

It is most important to plan ahead and know what kind of data you're collecting (either a need for detail or large area) in order to know which type to use. If you plan ahead, UAS can solve any spatial data collection need with ease.

Sources
Scenarios provided by Dr. Joe Hupy.
RealFlight 7.5 Simulator

Photos:
RealFlight w/ controller: Link
Slinger: Link
Quad-copter: Link
F-86 Sabre (Ducted Fan): Link
Explorer 580: Link