FARLIS
One of the major responsibilities of the Service's Federal Aid Division is distributing to the states funds collected under the Federal Aid in Sport Fish Restoration and Wildlife Restoration Programs. To utilize these funds, state fish and wildlife agencies submit proposed projects to the Service's Regional Federal Aid Offices for review and approval. Once approved, states carry out the work and, upon completion, are reimbursed for up to 75% of the project cost.
Throughout the program's 50+ year history, states wihin Region 3 have chosen to use a large portion of their funds for land acquisition projects for wildlife and sport fish habitat and management areas, as well as for boating access areas, fish hatcheries and hunting land.
Within the last five years, an average of 150 tracts have been purchased annually in Region 3, for an average annual cost of $11,000,000. It is estimated that the total tracts purchased from 1939 to the present are in excess of 12,000 individual purchases throughout the eight states of Region 3. Although each state has their own system of tracking these purchases, the Federal Aid Division has a responsibility to maintain their own records to ensure that program integrity is achieved.
Administering this very complex funding resource has resulted in a tremendous amount of information which must be archived, accessed and monitored. In 1985, Federal Aid began transferring land records from their hardcopy state to a computerized database to ease the frustration in handling the overwhelming amount of land information data. However, although the computerized database was an improvement over manual manipulation of the hardcopy records, it was still difficult and often impossible to query, summarize and output the data in the many forms it was needed.
When presented with the problem, Federal Aid's computer whiz, Pete Hitchcock, suggested that a graphic interface may help increase the efficiency and versatility of data handling. Since an inherent characteristic of all the land inventory records was their tie to the Public Land Survey System (PLSS), a GIS solution was chosen.
Each land inventory record's location is designated by county, township, range and section. This provides the foundation for associating the land inventory data with other geographic information which can then be used to spatially query the database.
Adding a GIS interface to the FARLIS database required only minor spatial data creation, relying on existing spatial data layers. The primary spatial data layer in the interface is the PLSS section layer which is linked to each FARLIS record through its PLSS location attributes. Another spatial data layer of great importance is the state owned natural resource ownership layer. This layer is used to further delineate where within the section the Federal Aid funding was applied. Other spatial data layers, such as major roads, rivers and municipal boundaries, are also incorporated to provide additional descriptive information to displays, queries and hardcopy outputs.
Rowekamp Associates, Bloomington, MN, a local GIS consulting firm, was contracted to develop the "GIS facelift" for FARLIS. The "facelift" required use of a graphic interface in a windows environment, connectivity between the FARLIS database and the spatial data layers, and development of a user-friendly application requiring minimal GIS expertise on part of the users. Three application modules were identified -- a query module, data entry module and printed reports module.
Arcview 2.1 with SQL connectivity to Paradox was chosen as the avenue for application development. Using Avenue scripting language, Rowekamp Associates developed customized menus, buttons and tools which smoothly lead the user from development of the data query to output of the printed report.
The query module is the backbone of the application. It provides the ability to initiate the query spatially or by querying the FARLIS records. The spatial query begins with a simple graphic showing the eight states of Region 3 (Figure 1). Once a state is identified for the query, a more detailed map showing counties and townships is displayed (Figure 2). At this point, you can query by county or refine the query to township or section. Different data layers can be turned on and off at this point. For instance, in Figure 3, I have zoomed in to the county level and displayed more detailed information.
The
link between the PLSS data layer and the FARLIS database is dynamic. As an area
is selected on the map display, the associated records in the FARLIS database
are also selected (Figure 4, selected records highlighted in yellow). In addition,
this dynamic link allows new data entries in FARLIS to be instantaneously available
for spatial data queries.
Future enhancements are in the works for FARLIS. To date, only access to the state of Iowa database records has been enhanced with a "GIS facelift". However, Rowekamp Associates and the Region 3 GIS Coordinator are working together to incorporate the necessary spatial data layers into FARLIS so the remaining Region 3 states can be accessed through the GIS interface. Future enhancements to the Arcview application are also planned, including upgrading to Arcview 3.0 and adding a module for hardcopy map outputs.
The "GIS facelift" for FARLIS will greatly enhance the Regional Federal Aid Office's ability to access and use the information stored in its database. As electronic databases within the Service mature, the amount of data within them will also grow in extent and value. And as a result, data handling will become cumbersome as quickly as the need to access the data will become crucial. As illustrated with FARLIS, the use of GIS technology can provide the key to solving the problem of handling these large databases and the means to tap into the valuable information that is stored there.
EPA's
BASINS
"Getting to the Point" on Contaminants Issues
EPA has developed a GIS based package to analyze watershed and water quality based issues called Better Assessment Science Integrating Point and Nonpoint Sources (BASINS). BASINS, developed using Arcview software, brings under one roof the many components required to complete a watershed-based contaminants assessment. Key data and analytical components are brought together, allowing the user to efficiently access national environmental information, apply assessment and planning tools and run a variety of proven, robust nonpoint loading and water quality models.
BASINS consists of three geographically-based environmental assessment tools and three watershed nonpoint source and water quality models:
Environmental Assessment Tools
TARGET assists the user in summarizing and displaying information about water quality and/or point source loadings within a regional context, such as a state or ecoregion. TARGET assesses a large amount of detailed, site-specific data associated with the identified region and summarizes the results on a watershed basis. Using these water quality or point source loading summaries, watersheds are then ranked based on the level of selected evaluation parameters (e.g., DO, BOD, zinc).
ASSESS uses the same data as TARGET but operates on a single watershed or a limited set of watersheds. The proximity of specific water quality stations or discharge facilities to waterbodies is the basis of the analysis. Providing a high level of detail, the user can visually focus on the status of specific stream reaches, assess their changes over time, evaluate data availability and the need for source characterization and analysis of cause-effect relationships.
Data Mining is the third tool, working again with the same datasets as the other two tools but providing the highest level of detail at the station level. Data Mining uses a dynamic link to display a combination of tables and maps, adding significant informational value to the raw data on water quality and loadings.
Watershed Nonpoint Source and Water Quality Models
Non Point Source Model (NPSM) estimates land use nonpoint source loadings for selected pollutants at a watershed scale. Based on EPA's Hydrologic Simulation Program-FORTRAN model, NPSM simulates water quantity and quality for a wide range of organic and inorganic pollutants from mixed land-use watersheds. The model uses continuous simulations to predict water balance and pollutant loadings, transformation and transport.
QUAL2E is a model that analyzes pollutant fate and transport through selected stream systems. It is a one dimensional water quality model that assumes steady-state flow but allows simulation of diurnal variations in temperature, algal photosynthesis and respiration. Data from NPSM can also be incorporated, providing modelling capability for both point and nonpoint source loadings.
TOXIROUTE provides a screening level stream routing model that performs simple dilution/decay calculations under mean and low flow conditions for a stream system within a given watershed. It can also integrate non-point source loadings calculated with NPSM.
Before giving my evaluation of BASINS, I must admit that I am a neophyte (or less) when it comes to contaminants assessment and analysis. Therefore, I tried to limit my evaluation to performance of the software package.
I was able to use all the tools and models in BASINS, getting results with very little trouble. The tools are very easy to use, with different aspects of the results displayed simultaneously on the screen. With my limited knowledge of contaminants assessment, the models were a little harder to use, but with the excellent instructions and well-organized menus, I was able to get their basic functions to work.
The Arcview application itself appears to be glitch-free; no tools or buttons were found to be dysfunctional nor was there any occurrence of segmentation violations or premature program termination.
The application was written to allow a novice Arcview user to negotiate all its features but, surprisingly, did this without losing any Arcview functionality. There is enough flexibility in the application to allow the user to add other basemap layers and even to edit the contaminants databases to add more current information.
EPA appears to be strongly committed to BASINS. This is demonstrated by well-written documentation, responsive staff assigned to answer questions, online tips and information on the Internet and work currently in progress on a new, improved version 2, which promises significant enhancements to the application and associated datasets (addressed in more detail below).
Before completing my evaulation, I felt it would be important to get at least a cursory evaluation of BASINS from someone who knows their contaminants. Stan Smith, Region 3 Contaminants Biologist, was able to set aside a few hours out of his busy schedule for this purpose. Stan reviewed two of the environmental assessment tools and looked briefly at the models.
After reviewing both TARGET and ASSESS, Stan stated that analysis results are reported in contaminant loadings (lbs/yr) rather than permitted discharge limits (ug/l or ppm). This measurement is helpful when employed in a regulatory function, for instance, if a state is assessing a watershed's ability to assimulate certain pollutant loadings and readjusting permitted discharge levels in response.
However, for assessing biological impacts, contaminants loadings (lbs/yr) is limiting. For instance, if you are trying to determine the source of a fish kill or the possible impacts on eagle nesting success in a river reach, BASINS could help you collect baseline information such as permitted discharge facilities, what they are permitted to discharge, reported overages and NPDES permit numbers. This information could provide direction for a search of more detailed information like actual discharge levels permitted from a state regulatory agency.
Stan felt that BASINS did provide access to quite a comprehensive collection of contaminants information for waterborne contaminants. However, for the type of contaminants work required of Fish and Wildlife Service Ecological Services offices, the data provided by BASINS has limited application. He felt the lack of permitted discharge limits and access to real time contaminants data were the largest limiting factors.
An evaluation of BASINS would not be complete without feedback from its creators. A discussion with the folks at EPA confirmed Stan's evaluation...BASINS was designed to help planners at the state and regional levels in fulfilling their regulatory functions with regard to contaminant issues using a watershed-based approach. Future enhancements to BASINS are designed to continue upgrading and improving the application with this use in mind. Many of the enhancements to the next version of BASINS are being designed to support development of Total Maximum Daily Loadings (TMDL). This focus is in response to the requirement under the Section 303(d) of the Clean Water Act to use technology-based controls to develop TMDLs for watersheds that are not meeting applicable water quality standards.
EPA staff did emphasize that BASINS was designed with maximum flexibility to allow the user to modify the datasets for their needs. Therefore, they felt that data related to permitted discharge limits could be added to BASINS to allow evaluation of biological impacts. The reason this information was not included in BASINS was due to differences in EPA and state permitted discharge criteria and the influence of local waterbody use designations on the criteria.
This does not mean BASINS would not prove to be a valuable tool for a Fish and Wildlife Service field station. In fact, the enhancements to Version 2 promise significant enough changes to continue to re-evaluate BASINS as a valuable analytical tool. BASINS should not only prove to be valuable to contaminants biologists but also to refuge biologists characterizing and evaluating surrounding watersheds or ascertainment biologists in the development of comprehensive management plans.
The following enhancements to BASINS are in the works, some of which will be made available in Version 2 to be released spring of 1998:
If you are interested in learning more about BASINS, visit EPA's BASINS web page at http://www.epa.gov/ost/BASINS. Since many of you have just purchased Arcview 3.0 and do not have a copy of Arcview 2.1, you will need to obtain the revised Version 1 of BASINS which includes the Avenue script changes for Arcview 3.0. This updated version of BASINS 1 should be available now.
Regionwide Data Coming Available!
Many field stations in Region 3 are in the planning and development stage of using GIS technology. A big part of setting up a GIS is gathering spatial data that has already been created by others. The good news is there is a lot of it out there; the bad news is it is in some of the most unlikely places and often requires format and projection tweaking before you can use it. In other words, the process is not seamless.
But help is on the way. As part of the FARLIS project, a great collection of base map data is being compiled and converted. The basemap data includes:
Federal Aid is happy to share this spatial data with other Service personnel in Region 3. To help serve this and future spatial data, Refuges and Wildlife Resources has purchased an NT workstation. The station will be set up as an FTP site where data can be accessed from the field and will be used to continue to convert and compile future data sets. Federal Aid has also helped in this effort by purchasing a copy of Arc/Info for NT to maintain regional spatial data sets.
Plans are to have the NT workstation and basemap data sets for the Region available by the end of the calender year. So, if you are on a data finding mission, make sure to contact your Region 3 GIS Coordinator...what you need may already be there for the asking.
HATS OFF TO FEDERAL AID AND REFUGE & WILDLIFE RESOURCES!
NCTC To Provide GIS Training
Given by Natural Resource People
For Natural Resource People
Training in the use of GIS technology is becoming more and more commonplace as GIS moves from the high tech end of things to the business mainstream. Although many of these courses are well-presented by knowledgeable people, they deal with issues like how to map a city neighborhood or route emergency vehicles from point A to B. Unless the flora or fauna affect the city planner's vision or the emergency vehicle's route, they are of minor importance or not even included in the spatial data set.
The National Conservation Technical Center (NCTC), as part of the U. S. Fish and Wildlife Service, is different. They are as strongly focused on natural resource problem solving as we are. And they have designed two GIS courses for 1998 that reflect their thoughtful approach.
Understanding that not all of us are working at the same focal length, they have designed one course, "TEC 7114, GIS Design for Refuge Management" for site-specific GIS applications and another, "TEC 7115, GIS Design for Regional Conservation Planning" for work over a broader geographic area.
While attending the FWS National GIS Workshop in June, I was able to attend ½ day prototype classes for both courses and was very impressed. The course outlines, which are designed to be presented over four days, were crammed full of great natural resource examples and taught by individuals working in the natural resource field.
"GIS Design for Refuge Management" will be taught by people with experience working on National Wildlife Refuge GIS. Working sessions will focus on spatial data management and collection, display and organization of spatial data layers and spatial & tabular analysis. Participants will have hands-on experience working with data sets and analysis that are important to natural resource managers.
"GIS Design for Regional Conservation Planning" will be taught by representatives from The Conservation Fund. They bring a wealth of case histories to the classroom involving multiple partners working over large geographic areas on a variety of natural resource issues. Successful initiatives like the following will be presented, focusing on the GIS strategies employed:
Both courses are being offered at NCTC, a brand new Service training facility in Shepherdstown, WV. The computer and geographic information system classrooms are equipped with state-of-the-art computer equipment, allowing all participants individual access to workstations. The NCTC campus, located on 540 acres along the Potomac River and designed with the conservation professional in mind, provides a premier learning environment. Course fee, lodging and meals are free of charge to Service employees, so for the price of Round Trip Airfare, you can get the GIS experience of a lifetime. Go for it!
For more information, contact Marcia McNiff at NCTC (304/876-7452).
The Scoop on Printers
In response to a lively late summer interest in purchasing printers/plotters, I put together the following synopsis of printers/plotters suitable for GIS applications. This information is a little too late for use in formulating year end purchases. However, it should prove helpful as a starting point for any future printer/plotter acquisitions.
Color Printers with Large Format Paper Size For most field stations, one of the three following desktop printers should offer satisfactory versatility and affordability for basic GIS hardcopy output needs. All three provide a large format paper size and two can print as small as 4" x 6" on card stock.
Desktop printers send the hardcopy output to the workstation RAM which is then fed to the printer's input buffer. If the printer buffer cannot process the information fast enough, the print output is written to the hard disk. Therefore, the size of the printer's input buffer as well as the workstation RAM can affect the quality and speed of your printed output.
| Specifications | Epson Stylus 1520 | Canon BJC 4550 | HP DeskJet 1000C |
| Resolution | 1440 x 720 dpi | 720 x 360 dpi | 600 x 600 dpi |
| Maximum Paper Size | 17" x 22"* *Prints 13.5" X 21.78" |
11" x 17" | 11" x 17" |
| Card Stock | Yes | No | Yes |
| Input Buffer | 64 Kb | 64 Kb | 480 Kb |
| Price | $865 | $495 | $550 |
Plotters Due to the price of plotters, a review of your office's need for large format output is strongly recommended. If your office does not identify a need for large format output on a weekly basis, a plotter is probably more printer than you need. However, you may find your need for large format output, although not frequent, is ongoing. In this case, one possible approach would be for several offices with close geographic proximity or strong project interractions to purchase a plotter as a shared resource.
The following table compares three 36-inch wide plotters. All three plotters print in color using inkjet technology. The use of inkjet technology is new to CalComp, although they have 40 years experience manufacturing plotters, scanners, and digitizing tables. Hewlett Packard and Encad have been designing products using inkjet technology since the mid-80's.
Whether or not the plotter comes standard with Adobe PostScript Level II language is noted below. PostScript is not necessary for processing ArcView or Arc/Info output. I included it for those offices that may also need the plotter for output from graphics packages like Adobe Illustrator.
The plotter specification that will affect ArcView and Arc/Info print jobs is the amount of printer RAM. Unlike, the desktop inkjet printers above, plotters need to download the entire print file before creating the hardcopy output. Large and/or complex print jobs can run over 20 Mb in size, requiring upgrades to existing printer RAM. Therefore, I would recommend the standard plotter RAM be increased to 24 Mb at the time of purchase.
| Specification | HP 750C Plus | CalComp TechJet 5500 | Encad NovaJet 4 |
| Maximum Resolution | 300 dpi | 360 dpi | 300 dpi |
| Printer Memory | 8 Mb upgradeable to 72 Mb | 16 Mb upgradeable to 72 Mb | 4 Mb upgradeable to 68 Mb |
| Languages | HP-GL/2, HP-GL, HP-RTL | HP-GL, HP-GL/2, HP-RTL, CCRF-IL, CalComp 907/PCI, CALS G4 and Adobe PostScript Level 2 | HP-GL, HP-GL/2, ENCAD-RTL |
| Network Card | Optional | Standard Ethernet Interface | Optional |
| Estimated Price | $5275 | $5475 | $5995 |
The price of printers and plotters is very dynamic. Check current prices before ordering. Except for the Encad NovaJet 4, the above prices were obtained from Copy Equipment, Inc., Bloomington, MN (612/884-3581). The Encad estimated price was obtained from American Custom Computers, Eden Prairie, MN (612/975-1989).
At the Crossroads
Which Road Coverage To Choose
An integral piece of basemap data is transportation, particularly roadways. This data type can be obtained from a wide variety of local, state and federal sources. So the question is not so much where can we get road data but which source will best suit our needs.
To take a closer look at this question, I obtained transportation coverages from three different sources:
All three coverages were projected to UTM, Zone 15, NAD83 for comparison purposes.
Figure 5 illustrates how each of these three coverages depicts roadways in the same geographic location. The linework is very similar between the three coverages. However, both the USGS and TIGER coverages provide additional (but different) detail. The USGS roads coverage includes unimproved roads and trails that are not included in either of the other two coverages. The TIGER roads coverage provides more detail at the city street level.
The state developed coverage linework does not include the level of detail that the other two coverages have in the areas mentioned above, however, it was designed with a different use in mind. The coverage is based on the dynamic segmentation route model which allows the user to display and analyze data with route-reference locations.
A very useful feature of the TIGER roads data is that it includes street names, giving you the option to label your roads as I have done for some of the roads in Figure 5. The TIGER data for Region 3 will be made available to all field stations once the GIS NT Workstation is up and running.
This brief example illustrates that old adage "don't judge a book by its cover" or, in GIS lingo, don't judge a coverage by its appearance!
Those Nasty NADS
or
Dealing with Datums
Have you ever received two GIS coverages that you know are in the same projection but don't seem to line up quite right? This problem could be the result of several different factors (i.e., different source map scales, inaccurate digitizing methods, etc.). However, if the difference looks fairly uniform throughout the coverages compared and lines and polygons appear to follow the same contours, it's probably a difference in horizontal datums. Figure 6 illustrates how two coverages in different datums would appear when displayed together.
In
North America, there are two major horizontal datums - North American Datum
of 1927 (NAD27) and North American Datum of 1983 (NAD83).
The two datums differ in their reference spheroid. NAD27 uses the Clarke spheroid of 1866 to represent the shape of the Earth. The origin of this datum is a point on the Earth referred to as Meades Ranch in Kansas. The origin of many of the NAD27 control points were calculated from observations taken in the 1800's. Since these calculations were done manually and in sections over many years, errors varied throughout the datum.
NAD83, on the other hand, took advantage of many of the technological advances in surveying and geodesy. With the more powerful tools at hand, errors in NAD27 control points could be detected and rectified. NAD83 was subsequently established to correct these errors and allow for the development of a single datum to cover North America and surrounding areas consistently. NAD83 is based upon both Earth and satellite observations using the GRS80 spheroid. The origin for this datum is the Earth's center of mass.
There are several ways to rectify differences in datums so that all existing data can be used together regardless of the datum. In the following example, I have applied four methods for changing datums to lines and points. The lines and points were originally created in UTM, Zone 15, NAD27. The four methods applied to change the datum to NAD83 were:
1) ESRI PC Arc/Info Project Command's Datum Transformation Program. This method uses NADCON, the accepted national standard for datum transformation with approximate accuracy of .15 to .5 meters.
2) Wessex Transnad Datum Converter. This method also uses NADCON giving a highly accurate datum shift.
3) ESRI ArcView 3.0 Datum Converter. This method uses the Standard Molodensky Datum Transformation which is less accurate than NADCON.
4) ESRI ArcView 3.0 Projector! Extension Spheroid Change. This method simply changes the reference spheroid from Clark 1866 to GRS80.
Figure
7 contrasts the results of the datum shift from NAD27 lines and points to NAD83
lines and points. The datum shift causes a shift in coverage features both latitudinally
and longitudinally. Longitudinally, methods 1 and 2 shifted features about 214
meters north whereas methods 3 and 4 shifted features about 217 meters north.
The difference in longitudinal shift is fairly insignificant between methods
and would not pose significant problems in map production output and in some
on-screen digitizing applications.
However, when contrasting the latitudinal shift, there is a noticeable difference between the first three methods and method 4. Methods 1, 2 and 3 shifted data about 20 meters west whereas method 4 shifted the data 3 meters to the east. As a result, method 4 resulted in a disparity of 23 meters from the other methods and actually shifted the data in an opposite direction.
Before making a decision on which method to use, take into account the mechanics of using the different methods. The pros and cons of using each is summarized below.
1) ESRI PC Arc/Info Project Command's Datum Transformation Program.
2) Wessex Transnad Datum Converter.
3) ESRI ArcView 3.0 Datum Converter.
4)
ESRI ArcView 3.0 Projector! Extension Spheroid Change.
Which method you use to change datums will depend on the reason for shifting the datum of your coverage. If you need to shift the data for compatibility of basemap data and will not be using the features for on-screen digitizing, a spheroid change will be adequate and the least painful. Figure 8 illustrates the result of a spheroid change and application of NADCON to the Tiger data in Figure 6. As you can see, for display purposes there is very little difference.
However, if the features of the converted coverage will be used for on-screen digitizing purposes, Transnad would be the next method of choice, although this will not work on complex polygon data. In the instance of complex polygon data such as landuse or NWI, the Arc/Info Project command must be used. Contact your Region 3 GIS coordinator for datum changes on complex polygon data.
How to Add More Functionality
to your Arcview Project
Have you been wondering exactly how to tap into all that great ArcView functionality that everyone talks about? You know there is a way to buffer features or clip themes but how do you go about it when there is no button or tool to do so? You make one up! Well, not exactly...ESRI has already done a lot of the work for you. Many standard scripts come with your copy of ArcView 3.0, they just haven't been set up so you can access them. Follow my easy-to-understand (I hope) instructions below...more power to you!
Open ArcView and open a SCRIPT Window.
From the pulldown menu, choose SCRIPT and LOAD TEXT FILE
This will bring up a dialog box...Go to esri\av_gis30\arcview\samples\scripts. A list of files with .AVE extensions will appear. Choose the appropriate AVEnue script. Once the text file is loaded, you will find helpful hints in the script for using the function it loads. For our example, I will choose Buffer.ave.
From the pulldown menu, choose SCRIPT and COMPILE
Close the SCRIPT Window
Rename the script with a more descriptive name. The ESRI naming convention is: "Project Type.Function" (i.e., View.Buffer).
From the pulldown menu, choose PROJECT and CUSTOMIZE
For our example, set the TYPE to "View", CATEGORY to "Button"
Select NEW and fill in the following descriptive information in the dialog box by double clicking on each of the following:
CLICK: Script Name (View.Buffer)
HELP: Short description//Long description (Create buffer//Buffer selected features)
ICON: Choose an icon for the button
At this point you can either close the CUSTOMIZE Window or click on the MAKE DEFAULT button. If you just close the window, the button will be available in the current project only. If this is a function you want regular access to, click on MAKE DEFAULT and it will be added to your Default project window and will automatically appear whenever you open ArcView. A word of caution: if you choose to save the added function to your default project window, make sure you have not created any views, etc. since opening ArcView. Otherwise, these will also be saved and become a permanent fixture in your ArcView project window.
If you don't have time to do your own customization, I do have a default.apr that includes a number of functions that I consider basic and would be frequently accessed by users. These include buffer, mask, clip, merge, calculate acres and georeference image. Contact your Region 3 GIS Coordinator for a copy.
Closing Note from your Region 3 GIS Coordinator
I hope some of the ideas and information presented in this issue of Region 3 GIS Notes is helpful to you. Many of my excursions into the GIS Twilight Zone are prompted by questions from the growing GIS contingent in Region 3. Keep those email messages and phone calls coming...I always look forward to hearing from you.
Mary S. Mitchell
Region 3 GIS Coordinator
612/725-3737, x243
Last Modified April 05, 2000 07:54 AM