FOSS4GAcademy · ivettemagallanez · Apr 28, 2015 · Apr 29, 2015 · Apr 29, 2015 · Apr 30, 2015
diff --git a/Module 2 Lab/QGIS 2.8/Lab 2 Data.md b/Module 2 Lab/QGIS 2.8/Lab 2 Data.md
@@ -0,0 +1,11 @@
+## Lab 2 Data Location
+
+The data for Lab 2 is too large to host on GitHub, therefore, 
+the data has been placed online for download as a zip file.
+
+[Download the Lab 2 Data zip file](https://onedrive.live.com/redir?resid=644D24A88CD9CEC!19997&authkey=!ADPV5EAkkcRtpMg&ithint=file%2czip) ~147MB
+
+If you contribute new data, or modify the data, please either:
+
++ Email [email protected] with a link to the new data to host.
++ Host the data yourself in a reliable location for others to link to and update this document.
diff --git a/Module 2 Lab/QGIS 2.8/Module 2 Lab.md b/Module 2 Lab/QGIS 2.8/Module 2 Lab.md
@@ -0,0 +1,192 @@
+# GST 103: Data Acquisition and Management 
+## Lab 2 - Setting Up a Project Database
+### Objective – Learn How to Normalize Data and Import It into a SpatiaLite Database
+
+Document Version: 4/29/2015
+
+**FOSS4G Lab Author:**
+Kurt Menke, GISP  
+Bird's Eye View GIS
+
+**Original Lab Content Author:**
+Richard Smith, Ph.D.  
+Texas A&M University - Corpus Christi
+
+---
+
+
+The development of the original document is funded by the Department of Labor (DOL) Trade Adjustment Assistance Community College and Career Training (TAACCCT) Grant No.  TC-22525-11-60-A-48; The National Information Security, Geospatial Technologies Consortium (NISGTC) is an entity of Collin College of Texas, Bellevue College of Washington, Bunker Hill Community College of Massachusetts, Del Mar College of Texas, Moraine Valley Community College of Illinois, Rio Salado College of Arizona, and Salt Lake Community College of Utah.  This work is licensed under the Creative Commons Attribution 3.0 Unported License.  To view a copy of this license, visit http://creativecommons.org/licenses/by/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.  
+
+This document was originally modified from its original form by Kurt Menke and continues to be modified and improved by generous public contributions.
+
+---
+
+### 1. Introduction
+
+There are two main data models for GIS data: vector and raster. Additionally, GIS data comes in many file formats. When gathering data for a project it is common to acquire data from several sources. Therefore, it is also common for the data to be in several different file formats. In this lab you will create a project geodatabase for the Gifford-Pinchot National Forest in Washington State. First, you will normalize the data. This means that you will put all datasets in the same coordinate reference system (CRS) and clip them to the study area boundary. Lastly, you will put them all into the same file format, a SpatiaLite geodatabase. 
+
+This lab includes the following tasks:
+
+Task 1 Investigate and Normalize Project Data
+
+Task 2 Create a New Database 
+
+Task 2 Populate the New Database
+
+
+**2	Objective: Learn How to Normalize Data and Import It Into a SpatiaLite Database**
+
+The objective of this lab is to explore and understand geospatial data models and file formats. 
+
+
+
+###Task 1		Investigate and Normalize Project Data
+
+In this task, you will familiarize yourself with the lab data and will begin to normalize the data. 
+
+2.	Open QGIS Browser, navigate to the Lab_2\Data folder and select the Data folder so that you see the contents in the Param tab. 
+3.	There are eight vector layers here. There are four shapefiles, two kml files and two coverages (admin_forest and ranger_dist) (in the figure below). Each of these file formats will be treated in different ways. (NOTE: when there are multiple coverages in the same workspace they share the same info folder.)
+
+
+![Data Layers in QGIS Browser](figures/Data_Layers_in_QGIS_Browser.png "Data Layers in QGIS Browser")
+
+4. All the data for this project will need to be in UTM, zone 10, NAD83. Begin by identifying the coordinate reference system of each layer. Investigate the data layers and complete Table 1 below. This will tell you which layers will need to be saved to a new coordinate reference system.
+
+
+LAYER  --  COORDINATE REFERENCE SYSTEM
+
+admin  --  forest
+
+ranger  --  dist
+
+gp  --  veg041008
+
+lakes
+
+NF  --  roads
+
+NF  --  trails
+
+streams
+
+watershed  --  huc4
+
+5. Open QGIS Desktop. Click the Add vector layer button and change the Source type to Directory. Then change the Type to Arc/Info Binary Coverage. Browse to the Data folder  and select the admin_forest folder. Click Select folder (in the figure below). Click Open.
+
+
+![Adding a Coverage to QGIS](figures/Adding_a_Coverage_to_QGIS.png "Adding a Coverage to QGIS")
+
+6. In the Select vector layers to add window choose 3 PAL (Polygon layer). Click OK. 
+
+![Adding_the_Coverage_Polygon_to_QGIS](figures/Adding_the_Coverage_Polygon_to_QGIS.png "Adding_the_Coverage_Polygon_to_QGIS")
+
+7. Save your project as Lab 2.qgs.
+8. This layer is in a custom Albers Equal Area coordinate system. Since they are in a custom CRS there is no EPSG code to use during import into a database. First, you will save this out to a shapefile in the desired CRS. Right click on the layer and choose Save as… Save the resulting dataset to the Data folder and set the CRS to UTM zone 10 NAD 83 (EPSG 26910) you may need to type NAD83 / UTM zone 10 in the filter section to find it. (figure below). Once this is done you can Remove the PAL layer from QGIS Desktop.
+
+
+![Saving the Covererage out to a Shapefile in UTM](figures/Saving_the_Covererage_out_to_a_Shapefile_in_UTM.png "Saving the Covererage out to a Shapefile in UTM")
+
+9. Repeat steps 5-7 for the Ranger District coverage. Once this has been completed, QGIS Desktop should resemble the figure below.
+
+![Shapefile Versions of Both Coverages in UTM](figures/Shapefile_Versions_of_Both_Coverages_in_UTM.png "Shapefile Versions of Both Coverages in UTM")
+
+10.	The only other dataset in Albers Equal Area is the vegetation shapefile. Add the gp_veg041008.shp shapefile to QGIS Desktop and save this as a new shapefile in UTM.
+11.	Add the NF_roads, NF_trails and watershed_huc4 shapefiles to QGIS Desktop. These layers are all shapefiles in the correct CRS. However, they extend beyond the forest boundary. Use the Vector -> Geoprocessing Tools -> Clip tool to clip each to the forest boundary (in the figure below). You can give them the same output name, but end it with clip. For example, NF_roads will become NF_roads_clip.
+
+![Clipping Roads to the Forest Boundary](figures/Clipping_Roads_to_the_Forest_Boundary.png "Clipping Roads to the Forest Boundary")
+
+12.	Remove the original unclipped roads, trails and watershed layers once the three clip operations are complete. Your map should now resemble the figure below. 
+
+![Normalized Layers](figures/Normalized_Layers.png "Normalized Layers")
+
+
+13.	You have taken the initial steps to normalize the data. The rivers and lake layers are KML. KML is always in a geographic CRS with an EPSG code of 4326. These can be repojected when importing into the SpatiaLite database.
+14.	Save your project.
+
+
+###Task 2		Create a New Database
+
+Now that you have taken the initial steps to prepare your data, you will create a new empty SpatiaLite database in which you will import your datasets.
+
+1. Open your Lab2.qgs project in QGIS Desktop if it not already.
+2. Click on the Browser tab at the bottom of the Table of Contents. If your Browser tab is not there go to View -> Panels -> Browser to turn it on. 
+3. Find the SpatiaLite database connection below your hard drives. Right click on it and choose Create database (figure below).
+
+![Create New Database Context Menu](figures/Create_New_Database_Context_Menu.png "Create New Database Context Menu")
+
+4. Navigate to the Data folder and name the new database GiffordPinchot  and click Save (figure below).
+
+
+![Naming Database](figures/Naming_Database.png "Naming Database")
+
+5. The database will now appear under the SpatiaLite database connection. Switch back to the Layers tab.
+6. Save your project.
+
+
+###Task 3		Populate the New Database
+
+Now you will populate the database with the eight layers.
+
+1. Open your Lab2.qgs project in QGIS Desktop if it not already.
+2. Add the stream and lake KML layers to QGIS Desktop.
+3. From the menu bar choose Database -> DB Manager -> DB Manager. Expand the SpatiaLite database connection (figure below). You will see the GiffordPinchot.sqlite database. If you expand the database, you will see many tables but no GIS layers yet.
+
+![DB Manager](figures/DB_Manager.png "DB Manager")
+
+4. First you will load the streams and lakes layers. Since these are KML they are in a geographic CRS with an EPSG code of 4326. This is the case for all KML datasets.
+5. Click the Import layer/file button ![Import layer file button](figures/Import_layer_file_button.png "Import layer file button") .
+
+6. Set up the Input vector layer window as follows (figure below):
+
+ a.	Set the Input as lakes
+
+ b.	Name the table lakes
+
+ c.	Click on Source SRID and enter 4326
+
+ d.	Click the Target SRID and enter 26910
+
+ e.	Click Create spatial index
+
+ f.	Click OK
+
+![Import KML Lakes into SpatiaLite DB](figures/Import_KML_Lakes_into_SpatiaLite_DB.png "Import KML Lakes into SpatiaLite DB")
+
+7. Once the operation has completed successfully click the Refresh button ![Refresh button](figures/Refresh_button.png "Refresh button")   to see the lakes layer in the database.
+8. Repeat steps 5-7 for streams.
+9. Streams and Lakes were the final two layers that required a CRS reprojection. The remaining six UTM layers can now be imported. The only change is that both the input and target SRID’s will be 26910 (UTM zone 10 NAD83).
+10. Click the Import layer/file button ![Import layer file button](figures/Import_layer_file_button.png "Import layer file button") .
+11.	Set up the Input vector layer window as follows (figure below):
+
+ a.	Set the Input as NF\_roads\_clip
+
+ b.	Name the table roads
+
+ c.	Click on Source SRID and enter 26910
+
+ d.	Click the Target SRID and enter 26910
+
+ e.	Click Create spatial index
+
+12.	Click OK
+
+![Import Shapefiles into SpatiaLite DB](figures/Import_Shapefiles_into_SpatiaLite_DB.png "Import Shapefiles into SpatiaLite DB")
+
+13.	Repeat steps 10-12 for trails, watersheds, ranger districts, vegetation and forest boundary layers.
+14.	Now that all eight layers have been imported you can remove the layers you have in QGIS Desktop.
+15.	The layers in the database can be added via the DB Manager or the Add SpatiaLite Layer button. 
+16.	If using the DB Manager, right click on a layer and choose Add to canvas. 
+17.	If using the Add SpatiaLite Layer button ![SpatiaLite layer button](figures/SpatiaLite_layer_button.png "SpatiaLite layer button") , select the database and click the Connect button. Once the layers appear, you can select them and click Add to add them to QGIS (figure below).
+
+![Add SpatiaLite Tables](figures/Add_SpatiaLite_Tables.png "Add SpatiaLite Tables")
+
+**5. Conclusion**
+
+In this lab, you took data in several different file formats and CRS’s and normalized them. They are all now in the same CRS, clipped to the forest boundary and in a geodatabase. This methodology has the benefit of creating a working copy of the data. The raw data still exist. Therefore, if you accidentally delete or corrupt a dataset you still have the original to fall back on. Additionally, the data now all reside in a tidy database. Since they are all in the same CRS you can run any geoprocessing or analysis tools against them knowing they are all in UTM zone 10 NAD83.
+
+
+**6	Discussion Questions**
+
+1. What are the steps involved in setting up a SpatiaLite database?
+2. What are the advantages of normalizing project data?
+
diff --git a/Module 2 Lab/QGIS 2.8/figures/Add_SpatiaLite_Tables.png b/Module 2 Lab/QGIS 2.8/figures/Add_SpatiaLite_Tables.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Adding_a_Coverage_to_QGIS.png b/Module 2 Lab/QGIS 2.8/figures/Adding_a_Coverage_to_QGIS.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Adding_the_Coverage_Polygon_to_QGIS.png b/Module 2 Lab/QGIS 2.8/figures/Adding_the_Coverage_Polygon_to_QGIS.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Browser_Tab_SpatiaLite_Create_New_DB.png b/Module 2 Lab/QGIS 2.8/figures/Browser_Tab_SpatiaLite_Create_New_DB.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Clipping_Roads_to_the_Forest_Boundary.png b/Module 2 Lab/QGIS 2.8/figures/Clipping_Roads_to_the_Forest_Boundary.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Create_New_Database_Context_Menu.png b/Module 2 Lab/QGIS 2.8/figures/Create_New_Database_Context_Menu.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/DB_Manager.png b/Module 2 Lab/QGIS 2.8/figures/DB_Manager.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Data_Layers_in_QGIS_Browser.png b/Module 2 Lab/QGIS 2.8/figures/Data_Layers_in_QGIS_Browser.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Import_KML_Lakes_into_SpatiaLite_DB.png b/Module 2 Lab/QGIS 2.8/figures/Import_KML_Lakes_into_SpatiaLite_DB.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Import_Shapefiles_into_SpatiaLite_DB.png b/Module 2 Lab/QGIS 2.8/figures/Import_Shapefiles_into_SpatiaLite_DB.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Import_layer_file_button.png b/Module 2 Lab/QGIS 2.8/figures/Import_layer_file_button.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Naming_Database.png b/Module 2 Lab/QGIS 2.8/figures/Naming_Database.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Normalized_Layers.png b/Module 2 Lab/QGIS 2.8/figures/Normalized_Layers.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Refresh_button.png b/Module 2 Lab/QGIS 2.8/figures/Refresh_button.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Saving_the_Covererage_out_to_a_Shapefile_in_UTM.png b/Module 2 Lab/QGIS 2.8/figures/Saving_the_Covererage_out_to_a_Shapefile_in_UTM.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Shapefile_Versions_of_Both_Coverages_in_UTM.png b/Module 2 Lab/QGIS 2.8/figures/Shapefile_Versions_of_Both_Coverages_in_UTM.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/SpatiaLite_layer_button.png b/Module 2 Lab/QGIS 2.8/figures/SpatiaLite_layer_button.png
diff --git a/Module 2 Lab/QGIS 2.8/figures/Thumbs.db b/Module 2 Lab/QGIS 2.8/figures/Thumbs.db
diff --git a/Module 2 Lab/QGIS 2.8/figures/qgis-icon.png b/Module 2 Lab/QGIS 2.8/figures/qgis-icon.png
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.dbf b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.dbf
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.prj b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.prj
@@ -0,0 +1 @@
+PROJCS["NAD83_HARN_New_Mexico_Central_ftUS",GEOGCS["GCS_NAD83(HARN)",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137,298.257222101]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",31],PARAMETER["central_meridian",-106.25],PARAMETER["scale_factor",0.9999],PARAMETER["false_easting",1640416.667],PARAMETER["false_northing",0],UNIT["Foot_US",0.30480060960121924]]
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.qpj b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.qpj
@@ -0,0 +1 @@
+PROJCS["NAD83(HARN) / New Mexico Central (ftUS)",GEOGCS["NAD83(HARN)",DATUM["NAD83_High_Accuracy_Reference_Network",SPHEROID["GRS 1980",6378137,298.257222101,AUTHORITY["EPSG","7019"]],TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6152"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4152"]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",31],PARAMETER["central_meridian",-106.25],PARAMETER["scale_factor",0.9999],PARAMETER["false_easting",1640416.667],PARAMETER["false_northing",0],UNIT["US survey foot",0.3048006096012192,AUTHORITY["EPSG","9003"]],AXIS["X",EAST],AXIS["Y",NORTH],AUTHORITY["EPSG","2903"]]
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.sbn b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.sbn
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.sbx b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.sbx
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.shp b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.shp
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.shx b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_routes.shx
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.dbf b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.dbf
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.prj b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.prj
@@ -0,0 +1 @@
+PROJCS["NAD83_HARN_New_Mexico_Central_ftUS",GEOGCS["GCS_NAD83(HARN)",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137,298.257222101]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",31],PARAMETER["central_meridian",-106.25],PARAMETER["scale_factor",0.9999],PARAMETER["false_easting",1640416.667],PARAMETER["false_northing",0],UNIT["Foot_US",0.30480060960121924]]
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.qpj b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.qpj
@@ -0,0 +1 @@
+PROJCS["NAD83(HARN) / New Mexico Central (ftUS)",GEOGCS["NAD83(HARN)",DATUM["NAD83_High_Accuracy_Reference_Network",SPHEROID["GRS 1980",6378137,298.257222101,AUTHORITY["EPSG","7019"]],TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6152"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4152"]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",31],PARAMETER["central_meridian",-106.25],PARAMETER["scale_factor",0.9999],PARAMETER["false_easting",1640416.667],PARAMETER["false_northing",0],UNIT["US survey foot",0.3048006096012192,AUTHORITY["EPSG","9003"]],AXIS["X",EAST],AXIS["Y",NORTH],AUTHORITY["EPSG","2903"]]
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.shp b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.shp
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.shx b/Module 3 Lab/QGIS 2.8/Lab 3 Data/Bus_stops.shx
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.dbf b/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.dbf
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.prj b/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.prj
@@ -0,0 +1 @@
+PROJCS["NAD83_HARN_New_Mexico_Central_ftUS",GEOGCS["GCS_NAD83(HARN)",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137,298.257222101]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",31],PARAMETER["central_meridian",-106.25],PARAMETER["scale_factor",0.9999],PARAMETER["false_easting",1640416.667],PARAMETER["false_northing",0],UNIT["Foot_US",0.30480060960121924]]
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.qpj b/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.qpj
@@ -0,0 +1 @@
+PROJCS["NAD83(HARN) / New Mexico Central (ftUS)",GEOGCS["NAD83(HARN)",DATUM["NAD83_High_Accuracy_Reference_Network",SPHEROID["GRS 1980",6378137,298.257222101,AUTHORITY["EPSG","7019"]],TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6152"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4152"]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",31],PARAMETER["central_meridian",-106.25],PARAMETER["scale_factor",0.9999],PARAMETER["false_easting",1640416.667],PARAMETER["false_northing",0],UNIT["US survey foot",0.3048006096012192,AUTHORITY["EPSG","9003"]],AXIS["X",EAST],AXIS["Y",NORTH],AUTHORITY["EPSG","2903"]]
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.shp b/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.shp
diff --git a/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.shx b/Module 3 Lab/QGIS 2.8/Lab 3 Data/parcels.shx
diff --git a/Module 3 Lab/QGIS 2.8/Module 3 Lab.docx b/Module 3 Lab/QGIS 2.8/Module 3 Lab.docx
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		PROJCS["NAD83_HARN_New_Mexico_Central_ftUS",GEOGCS["GCS_NAD83(HARN)",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137,298.257222101]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",31],PARAMETER["central_meridian",-106.25],PARAMETER["scale_factor",0.9999],PARAMETER["false_easting",1640416.667],PARAMETER["false_northing",0],UNIT["Foot_US",0.30480060960121924]]
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		PROJCS["NAD83(HARN) / New Mexico Central (ftUS)",GEOGCS["NAD83(HARN)",DATUM["NAD83_High_Accuracy_Reference_Network",SPHEROID["GRS 1980",6378137,298.257222101,AUTHORITY["EPSG","7019"]],TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6152"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4152"]],PROJECTION["Transverse_Mercator"],PARAMETER["latitude_of_origin",31],PARAMETER["central_meridian",-106.25],PARAMETER["scale_factor",0.9999],PARAMETER["false_easting",1640416.667],PARAMETER["false_northing",0],UNIT["US survey foot",0.3048006096012192,AUTHORITY["EPSG","9003"]],AXIS["X",EAST],AXIS["Y",NORTH],AUTHORITY["EPSG","2903"]]