The GIS Behind iMapInvasives: The “Open Source Sandwich”

  • Georgianna Strode
Part of the Lecture Notes in Geoinformation and Cartography book series (LNGC)


Invasive species can be considered an ecological “time bomb” that contributes to a number of human and environmental problems, including reduced crop and livestock production and biodiversity loss. It is estimated that 5,000 acres of western lands become infested each day (North American Weed Management Association 2002). Westbrooks assesses the financial costs to Americans at $138 billion per year. Of the current methods for treating invasive species, Early Detection and Rapid Response (ED/RR) is highly ranked because it is cost-effective and environmentally sound and it increases the possibility of successful eradication (ibid).

For ED/RR to be effective, land managers must have access to comprehensive and accurate data. Tracking invasive species is challenging because multiple agencies and organizations collect data, often resulting in isolated datasets. In addition, each agency uses its own collection format. Sensitive and unverified data add further complications. Land managers need to see the “big picture,” which often crosses political boundaries and results in differing ideas concerning collection and dissemination techniques.

To facilitate collaboration, was created as a versatile mapping tool to serve the needs of land managers, conservation planners, and agency decision makers. Internet Geographical Information Systems (IGIS) provide collaboration and networking capabilities that were previously unavailable with desktop GIS. Data are collected from multiple agencies and Users can access data from all sources, regardless of the original data format. There are other useful features such as customizable Early Detection notifications and restriction of sensitive data from users with less system authorization.

iMapInvasives uses an “open source sandwich” approach to IGIS. The “sandwich” uses mostly open source technologies, but the middle layer, or map, may contain images produced from commercial products. Together, these complementary components provide the robustness required for tracking invasive species with ample flexibility for customization.

While the challenges facing iMapInvasives are specific to invasive species management, the conceptual and technological issues presented here apply to any area of data collection and dissemination. This chapter gives an overview of the internal workings of the system and details some of the features that are unique to invasive species tracking.


Geographic Information System Invasive Species User Level Structure Query Language Spatial Query 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.



Thanks to Meg Wilkinson of the New York Natural Heritage Program (NYNHP) for her vision of this project and her skill in managing its direction. Thanks also to the members of the iMapInvasives Executive Committee for their guidance and insights. Thanks to Stephen Hodge and Erik Hazzard of the Florida Resources and Environmental Analysis Center (FREAC) of the Florida State University (FSU) for their keen eye for details, technical support, and GIS/programming skills.


  1. Bouchal LC (2010) Water chestnuts found in Lake Hopatcong, New Jersey H. New Jersey Herald. Scholar
  2. Crooks JA, Soule ME (1999) Lag times in population explosions of invasive species: causes and implications. In: Sandlund OT, Schei PJ, Viken A (eds) Invasive species and biodiversity management. Kluwer, DordrechtGoogle Scholar
  3. Fee J (2010) Give Me a Map Sandwich,
  4. Frye C (2010) The ‘Map Sandwich,’ Mapping Center. Environmental Science Research Institute(ESRI).,610f1695
  5. Hazzard E (2011) OpenLayers 2.10 beginner’s guide. Packt, Publishing LTD, BirminghamGoogle Scholar
  6. Lass LW, Prather TS, Glenn NF, Weber KT, Mundt JT, Pettingill J (2005) A review of remote sensing of invasive weeds and example of the early detection of spotted knapweed (Centaurea maculosa) and babysbreath (Gypsophila paniculata) with a hyperspectral sensor. Weed Sci 53:242–251CrossRefGoogle Scholar
  7. North American Weed Management Association (2002) North American invasive plant mapping standards. Federal interagency committee for the management of noxious and exotic weedsGoogle Scholar
  8. Owen SJ (1998) Department of conservation strategic plan for managing invasive weeds. Department of Conservation, WellingtonGoogle Scholar
  9. Randall J (2010) E-mail Interview, 10 Sep 2010Google Scholar
  10. Tiemann M (2010) Open source software. In: Bates MJ, Maack MN (eds) Encyclopedia of library and information sciences, vol 1, 3rd edn. Taylor & Francis, London, pp 4031–4036Google Scholar
  11. Tufte E (2010) Presenting data and information, Arlington. Lecture, 14 Apr 2010Google Scholar
  12. Viger R, David O, O’Hara CG (2004) GEOLEM: a knowledge-handling infrastructure for integrating GIS and environmental modelingGoogle Scholar
  13. Westbrooks RG (2004) New approaches for early detection and rapid response to invasive plants in the United States. Weed Technol 18:1468–1471CrossRefGoogle Scholar


  1. Apache (2010) The Apache Software Foundation.
  2. Django (2010) Django Software Foundation.
  3. iMapInvasives (2010) The Nature Conservancy.
  4. MooTools (2010) mad4milk.
  5. OpenLayers (2010) OpenLayers: free maps for the web, open source geospatial foundation.
  6. PostgreSQL (2010) PostgreSQL Global Development Group.
  7. Python (2010) Python Publishing Foundation.
  8. REST (2010) ArcGIS Server REST API, Environmental Science Research Institute (ESRI).
  9. What’s Invasive! (2010) Community data collection.
  10. WIMS (2010) Weed information management system, The Nature Conservancy.

Copyright information

© Springer-Velag Berlin Heidelberg 2012

Authors and Affiliations

  1. 1.Florida Resources and Environmental Analysis Center (FREAC)Florida State University (FSU)TallahasseeUSA

Personalised recommendations