# Presentation: 597885

## Managing Multiple Track Segments with DNR Garmin

## Objectives

_**Using DNR Garmin:**_
**Download tracks **
**Save track segments to shapefiles****  **

## Summary of Topics

**Multiple Track Features Scenario**
**Download Tracks**
**Save Polygon Feature as Shapefile**
**Save Line Features as Shapefiles**

## Data Collection Scenario

**Collected one polygon feature**
**Saved Track (needed fire acres)**
**Collected two line features**

**3 Separate Track segments in the Active Track Log**

**Hand Line**

**Dozer Line**

**Fire Perimeter**

**Notes:**
Here is a typical scenario.  Three different features out there.  I collected perimeter first so I could calc acres.  I decided to save perimeter separately.  Then I collected the dozer line and the burned over hand line.  All three segments are in one active log.  There is one saved track, the first segment which was a polygon of the fire perimeter.

## Data Summary

**Data Summary**

_**Have (GPS)**_
**3 track segments**
**	****polygon**
**	****line**
**	****line**
**1 saved track**
**	****polygon**

_**Need (GIS)**_
**1 fire perimeter polygon**
**1 dozer line**
**1 hand line**

**Notes:**
I need to get these data out for use in GIS.  How can I separate the data to make it easier to understand?  

## Goal:  Save All Track Points to Single Shapefile

## Select Track Download

**Select Track Download**

**verify Coordinate System**

**Notes:**
Verify coordinate system:

Unless you are sure no one else touched your computer since the last time you downloaded
Unless you are sure you didn’t switch since the last time (maybe trying out something different)

## View Track Data Table

**View Track Data Table**

**resize window**

**watch download**

**scrollbar**

**scrollbar**

**show/hide data table**

**Notes:**
See in the bottom bar how many track points were downloaded.
When you select Track | Download, ALL tracks come into the DNRGarmin table – both tracks in the Active Track log (on receiver as Track Log %) and saves tracks.  They display differently in the table.

## Select All Active Log Track Points

**Notes:**
Select all records that say “Active Log” in the ident.  Select multiple records by clicking on the number and holding the shift key.

## ...Save...

## ...As Text File First!

**...As Text File First!**

**A **_**Text File**_** should always be saved First as a back up file to the **_**ESRI (ArcView) Shapefile**_

**Name should indicate all track points**
**20080319_rxwui_alltrackpts**

**Notes:**
Text first!

## Status Window

**Status Window**

**Name:  20080319_rxwui_alltrackpts.txt**

## ...Save Again...

**Notes:**
Save to 

## ...As ArcView Shapefile...

**...As ArcView Shapefile...**

**Note points files already there**

_**Projected**_** shapefile uses projected coordinates.  **
_**Unprojected**_** shapefile uses WGS84 coordinates.**

**Notes:**
In this case the projected coordinates were UTM NAD83 Zone 16N

Note:  once we selected shapefile format, it lets us see any other shapefiles already there.  However, we can’t see the associated files since they use a different file extension.  

## ...As a Point

**...As a Point**

**Notes:**
Why are we saving to point??????  Can you save to a line or polygon?  NO.  We have three features coming across here.  If you save to Line they will all try to connect as one big line.  If you save to polygon the track points will all try to connect to one big polygon.  If you save track points to shapefile points, the data is in a raw form that show the GIS specialist exactly what your positions were and he or she can create lines and polygons from your points.  

## Status Window

**Status Window**

**Name same as text file, extension different**
**20080319_rxwui_alltrackpts.shp**

## Locate Shapefile

**Locate Shapefile**

**Note additional files**

**Note file path**

**Notes:**
We talk of creating a shapefile, however, in reality we are always creating more than one file, we are creating at least 3 files and in this case 5 files.  In other words, ArcMap requires 5 files in order to display the collected points on a map.  

## Goal:  Save Multiple Shapefiles

## Select First Track Segment

**Select the first Active Log track segment**

**light blue-start of **_**new**_** track segment **

**First segment is fire perimeter**
**Second segment is dozer line**
**Third segment is **
**	****hand line**

**Notes:**
To create 3 separate feature shapefiles you can select each track segment separately in the table.  In this data collection scenario, I collected the perimeter first, the dozer line second and the hand line last.  I will select the perimeter by clicking on the first Active Log row in the table, holding my shift key and selecting the last row before the light blue row.  Remember the light blue indicates the beginning of the new track segment (dozer line).

## ...Save...

## ...As Text File First!

**...As Text File First!**

**A **_**Text File**_** should always be saved First **
**as a back up file to the **_**ESRI (ArcView) Shapefile**_

**Name should indicate feature type**
**20080319_rxwui_perim.txt**

**Notes:**
Text first!

## ...Save Again...

**Notes:**
Save to 

## ...As ArcView Shapefile...

**...As ArcView Shapefile...**

**Note all track points file already there**

**Name should indicate feature and shape type  20080319_rxwui_perim_pts.shp**

**Notes:**
In this case the projected coordinates were UTM NAD83 Zone 16N

Note:  once we selected shapefile format, it lets us see any other shapefiles already there.  However, we can’t see the associated files since they use a different file extension.  

## ...As a Point

**...As a Point**

**- Save to a Point Shape to ensure integrity**
**- Save to a Polygon ONLY if you are sure your ****	****data is perfect**

**Notes:**
Why are we saving to point??????  Can you save to a line or polygon?  NO.  We have three features coming across here.  If you save to Line they will all try to connect as one big line.  If you save to polygon the track points will all try to connect to one big polygon.  If you save track points to shapefile points, the data is in a raw form that show the GIS specialist exactly what your positions were and he or she can create lines and polygons from your points.  

## ...Save Again to ArcView Shapefile...

**...Save Again to ArcView Shapefile...**

**Note all track points file and perimeter points listed**

**Name should indicate feature and shape type  20080319_rxwui_perim_poly.shp**

**Notes:**
In this case the projected coordinates were UTM NAD83 Zone 16N

Note:  once we selected shapefile format, it lets us see any other shapefiles already there.  However, we can’t see the associated files since they use a different file extension.  

## Save to Polygon

**Save to Polygon**

## Check Saved Files

**Check Saved Files**

**Text file of all Active Log track points**

**Text file of fire perimeter track points**

**Point shapefile of all Active Log track points**

**Point shapefile of fire perimeter track points**

_**Polygon**_** shapefile of fire perimeter**

## Let’s Peek at your Work!

**Point Shapefile: 20080319_rxwui_perim_pts.shp**

**Polygon Shapefile:  20080319_rxwui_perim_poly.shp**

**Great!**

**Give **_**both**_** shapefiles to GIS Specialist**

## Select Second Track Segment

**Select Second Track Segment**

**light blue - start of **_**new**_** track segment **

**First segment is fire perimeter**
**Second segment is dozer line**
**Third segment is**
**	**** ****hand line**

**Notes:**
To create 3 separate feature shapefiles you can select each track segment separately in the table.  In this data collection scenario, I collected the perimeter first, the dozer line second and the hand line last.  I will select the perimeter by clicking on the first Active Log row in the table, holding my shift key and selecting the last row before the light blue row.  Remember the light blue indicates the beginning of the new track segment (dozer line).

## ...Save...

## ...As Text File First!

**...As Text File First!**

**A **_**Text File**_** should always be saved First **
**as a back up file to the **_**ESRI (ArcView) Shapefile**_

**Name should indicate feature type**
**20080319_rxwui_dzline**

**Notes:**
Text first!

## ...Save Again...

**Notes:**
Save to 

## ...As ArcView Shapefile...

**...As ArcView Shapefile...**

**Note other shapefiles**

**Name should indicate feature type  20080319_rxwui_dzline.shp**

**Notes:**
In this case the projected coordinates were UTM NAD83 Zone 16N

Note:  once we selected shapefile format, it lets us see any other shapefiles already there.  However, we can’t see the associated files since they use a different file extension.  

## ...As a Point or a Line???

**...As a Point or a Line???**

**Point Shape ensures integrity**

**You can save to a Line ONLY if you are sure your data is perfect**

**Notes:**
Why are we saving to point??????  Can you save to a line or polygon?  NO.  We have three features coming across here.  If you save to Line they will all try to connect as one big line.  If you save to polygon the track points will all try to connect to one big polygon.  If you save track points to shapefile points, the data is in a raw form that show the GIS specialist exactly what your positions were and he or she can create lines and polygons from your points.  

## Check Saved Files

**Check Saved Files**

**Shapefile of Dozer Line**

**Text file of Dozer Line**

## Select Third Track Segment

**Select Third Track Segment**

**last segment in table **

**First segment is fire perimeter**
**Second segment is dozer line**
**Third segment is**
**	****hand line**

**Notes:**
To create 3 separate feature shapefiles you can select each track segment separately in the table.  In this data collection scenario, I collected the perimeter first, the dozer line second and the hand line last.  I will select the perimeter by clicking on the first Active Log row in the table, holding my shift key and selecting the last row before the light blue row.  Remember the light blue indicates the beginning of the new track segment (dozer line).

## ...Save...

## ...As Text File First!

**...As Text File First!**

**A **_**Text File**_** should always be saved First **
**as a back up file to the **_**ESRI (ArcView) Shapefile**_

**Name should indicate feature type**
**20080319_rxwui_handline**

**Notes:**
Text first!

## ...Save Again...

**Notes:**
Save to 

## ...As ArcView Shapefile...

**...As ArcView Shapefile...**

**Note other saved shapefiles**

**Name should indicate feature type  20080319_rxwui_handline.shp**

**Notes:**
In this case the projected coordinates were UTM NAD83 Zone 16N

Note:  once we selected shapefile format, it lets us see any other shapefiles already there.  However, we can’t see the associated files since they use a different file extension.  

## ...As a Point or a Line???

**...As a Point or a Line???**

**- Point Shape ensures integrity**
**- Save to a Line ONLY if you are sure ****	****your data ****	****is perfect**

**Notes:**
Why are we saving to point??????  Can you save to a line or polygon?  NO.  We have three features coming across here.  If you save to Line they will all try to connect as one big line.  If you save to polygon the track points will all try to connect to one big polygon.  If you save track points to shapefile points, the data is in a raw form that show the GIS specialist exactly what your positions were and he or she can create lines and polygons from your points.  

## Check Saved Files

**Check Saved Files**

**Shapefile of Hand Line**

**Text file of Hand Line**

## Review of Topics

**Multiple Track Features Scenario**
**Download Tracks**
**Save Polygon Feature as Shapefile**
**Save Line Features as Shapefile**

## Final Data Review & Question

**Final Data Review & Question**

_**GPS**_
**3 track segments**
**	****polygon**
**	****line**
**	****line**
**1 saved track**
**	****polygon**

_**GIS**_
**1 fire perimeter polygon**
**1 dozer line**
**1 hand line**

**All GIS shapefiles came from Active Track**

**Why didn’t we use Saved Perimeter Track?**

**Notes:**
I need to get these data out for use in GIS.  How can I separate the data to make it easier to understand?  

## Compare Geometry

**Active Track Log**

**Saved Track**

**Which would be a better representation on a map?**

## Compare Area Calculations

**Compare Area Calculations**

**Saved Track – **
**Good estimated Acres!**

**Active Track Acres Calculated in ArcGIS**

**Saved Track Acres Calculated in GPS**

## Review of Topics

**Multiple Track Features Scenario**
**Download Tracks**
**Save Polygon Feature as Shapefile**
**Save Line Features as Shapefiles**

## Conclusions

**Active Track Log **
**Actual GPS positions**
**Good depiction of features**
**Saved Track**
**Saves “critical” GPS positions only**
**Creates linear shapes for curved features**
**Good approximate acre calculation**

## Slide 49