Current Distribution of Lynx in Maine

Data format: Shapefile

File or table name: lynxdistribution_sept08

Coordinate system: Universal Transverse Mercator

Theme keywords: Canada Lynx, telemetry, incidental take, track surveys

Abstract: Beginning in 1999, The Maine Department of Inland Fisheries and Wildlife developed formal databases to track observations of lynx in Maine. Biological staff and wardens also provided information of lynx observations prior to 1999 to the best of their abilities (i.e. locations may have been limited to the town and year of observation). These recent verified lynx observations were generated from 4 sources of data (telemetry data, sightings by regional biologists, standardized winter snow-track surveys, and incidental take of lynx) and are described in more detail below.

FGDC and ESRI Metadata:

Metadata elements shown with blue text are defined in the Federal Geographic Data Committee's (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Elements shown with green text are defined in the ESRI Profile of the CSDGM. Elements shown with a green asterisk (*) will be automatically updated by ArcCatalog. ArcCatalog adds hints indicating which FGDC elements are mandatory; these are shown with gray text.

Identification Information:

Citation:
Citation information:
Originators: Maine Department of Inland Fisheries and Wildlife

Title:
Current Distribution of Lynx in Maine
*File or table name: lynxdistribution_sept08

Publication date: September 2008
Publication time: Unknown
*Geospatial data presentation form: vector digital data

Online linkage: \\oit-mhb1fsddpc\ddpc-ifw\wras-users\amy.meehan\lynx\DOTReview\currentdistribution_sept08.shp

Description:
Abstract: fix(original)
Beginning in 1999, The Maine Department of Inland Fisheries and Wildlife developed formal databases to track observations of lynx in Maine.  Biological staff and wardens also provided information of lynx observations prior to 1999 to the best of their abilities (i.e. locations may have been limited to the town and year of observation).  These recent verified lynx observations were generated from 4 sources of data (telemetry data, sightings by regional biologists, standardized winter snow-track surveys, and incidental take of lynx) and are described in more detail below.

Purpose: fix(original)
To provide locations of documented lynx observations for permit review and planning processes.

Supplemental information: fix(original)
Cautionary note: These data are purely a record of documented lynx occurrences.  The shapefile does not reflect numbers of lynx because a single lynx may have generated multiple records of tracks or telemetry fixes.  Further, areas without lynx observations should not be viewed as unoccupied as not all areas were surveyed or were surveyed under different levels of intensity.

*Language of dataset: en

Time period of content:
Time period information:
Single date/time:
Calendar date: September 2008

Currentness reference: fix(original)
publication date

Status:
Progress: Complete
Maintenance and update frequency: Annually

Spatial domain:
Bounding coordinates:
*West bounding coordinate: -71.111525
*East bounding coordinate: -67.487940
*North bounding coordinate: 47.323527
*South bounding coordinate: 44.637704

Local bounding coordinates:
*Left bounding coordinate: 340386.000000
*Right bounding coordinate: 614279.968084
*Top bounding coordinate: 5241117.470398
*Bottom bounding coordinate: 4944675.164050

Keywords:
Theme:
Theme keywords: Canada Lynx, telemetry, incidental take, track surveys
Theme keyword thesaurus: REQUIRED: Reference to a formally registered thesaurus or a similar authoritative source of theme keywords.

Access constraints: Please be sure to use the FGDC or FGDC Classic Stylesheet in ArcCatalog to view complete metadata.
Use constraints: fix(original)
These data are provided by the Maine Department of Inland Fisheries and Wildlife solely for your individual use or the use of your company for the purpose stated in your request for the data.  These data may not be distributed or sold to other users without the written permission of the Commissioner of the Department of Inland Fisheries and Wildlife.

Point of contact:
Contact information:
Contact person primary:
Contact person: Jennifer Vashon
Contact organization: Maine Department of Inland Fisheries and Wildlife
Contact position: Wildlife Biologist/Lynx Study Leader

Contact voice telephone: 207-941-4238
Contact facsimile telephone: 207-941-4450

Contact electronic mail address: jennifer.vashon@maine.gov

Data set credit: fix(original)
Maine Department of Inland Fisheries and Wildlife

*Native dataset format: Shapefile
*Native data set environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.5.1450

Cross reference:
Citation information:
Title:
Current Distribution of Lynx in Maine

Back to Top
Data Quality Information:

Lineage:
Source information:
Source citation:
Citation information:
Title:
Current Distribution of Lynx in Maine

Process step:
Process description: fix(original)
Dataset copied.

Source used citation abbreviation:
N:\Bob\mdifw\lynx\2008-09\currentlynxdistribution_sept08

Back to Top
Spatial Data Organization Information:

*Direct spatial reference method: Vector

Point and vector object information:
SDTS terms description:
*Name: lynxdistribution_sept08
*SDTS point and vector object type: Entity point
*Point and vector object count: 14612

ESRI terms description:
*Name: lynxdistribution_sept08
*ESRI feature type: Simple
*ESRI feature geometry: Point
*ESRI topology: FALSE
*ESRI feature count: 14612
*Spatial index: TRUE
*Linear referencing: FALSE

Back to Top
Spatial Reference Information:

Horizontal coordinate system definition:
Coordinate system name:
*Projected coordinate system name: NAD_1983_UTM_Zone_19N
*Geographic coordinate system name: GCS_North_American_1983

Planar:
Grid coordinate system:
*Grid coordinate system name: Universal Transverse Mercator
Universal Transverse Mercator:
*UTM zone number: 19
Transverse mercator:
*Scale factor at central meridian: 0.999600
*Longitude of central meridian: -69.000000
*Latitude of projection origin: 0.000000
*False easting: 500000.000000
*False northing: 0.000000

Planar coordinate information:
*Planar coordinate encoding method: coordinate pair
Coordinate representation:
*Abscissa resolution: 0.000000
*Ordinate resolution: 0.000000
*Planar distance units: meters

Geodetic model:
*Horizontal datum name: North American Datum of 1983
*Ellipsoid name: Geodetic Reference System 80
*Semi-major axis: 6378137.000000
*Denominator of flattening ratio: 298.257222

Back to Top
Entity and Attribute Information:

Detailed description:
*Name: lynxdistribution_sept08

Entity type:
Entity type label: Current Distribution of Lynx in Maine
*Entity type type: Feature Class
*Entity type count: 14612

Attribute:
*Attribute label: FID
*Attribute alias: FID
*Attribute definition: fix(original)
Internal feature number.
*Attribute definition source: fix(original)
ESRI

*Attribute type: OID
*Attribute width: 4
*Attribute precision: 0
*Attribute scale: 0

Attribute domain values:
*Unrepresentable domain:
Sequential unique whole numbers that are automatically generated.

Attribute:
*Attribute label: Shape
*Attribute alias: Shape
*Attribute definition: fix(original)
Feature geometry.
*Attribute definition source: fix(original)
ESRI

*Attribute type: Geometry
*Attribute width: 0
*Attribute precision: 0
*Attribute scale: 0

Attribute domain values:
*Unrepresentable domain:
Coordinates defining the features.

Attribute:
*Attribute label: DATE_
*Attribute alias: DATE_
Attribute definition: fix(original)
Date of Observation

*Attribute type: Date
*Attribute width: 8

Attribute:
*Attribute label: TOWNGEOCOD
*Attribute alias: TOWNGEOCOD
Attribute definition: fix(original)
geocode or name of town

*Attribute type: String
*Attribute width: 17

Attribute:
*Attribute label: COUNTY
*Attribute alias: COUNTY

*Attribute type: String
*Attribute width: 11

Attribute:
*Attribute label: LOCATION
*Attribute alias: LOCATION
Attribute definition: fix(original)
general location of observation

*Attribute type: String
*Attribute width: 63

Attribute:
*Attribute label: UTME
*Attribute alias: UTME

*Attribute type: Number
*Attribute width: 16
*Attribute number of decimals: 3

Attribute:
*Attribute label: UTMN
*Attribute alias: UTMN

*Attribute type: Number
*Attribute width: 17
*Attribute number of decimals: 3

Attribute:
*Attribute label: UTMSOURCE
*Attribute alias: UTMSOURCE
Attribute definition: fix(original)
source of UTM coordinates

*Attribute type: String
*Attribute width: 13

Attribute domain values:
Enumerated domain:
Enumerated domain value: Actual
Enumerated domain value definition: fix(original)
obtained from GPS or satellites

Enumerated domain:
Enumerated domain value: Estimated
Enumerated domain value definition: fix(original)
location estimated based on a dot on a map or a reference to a road or town

Attribute:
*Attribute label: MAPDATUM
*Attribute alias: MAPDATUM

*Attribute type: String
*Attribute width: 12

Attribute:
*Attribute label: DISPOSITIO
*Attribute alias: DISPOSITIO
Attribute definition: fix(original)
disposition of lynx observed (i.e. alive or dead for visual observation, otherwise track observation)

*Attribute type: String
*Attribute width: 12

Attribute:
*Attribute label: OBSTYPE
*Attribute alias: OBSTYPE
Attribute definition: fix(original)
defines the source of the point data for each database

*Attribute type: String
*Attribute width: 21

Attribute domain values:
Enumerated domain:
Enumerated domain value: telemetry data
Enumerated domain value definition: fix(original)
lynx locations based on aerial vhf, satellite or GPS telemetry of radio collared lynx (62 lynx have been monitored to date)

Enumerated domain:
Enumerated domain value: ecoregional survey
Enumerated domain value definition: fix(original)
observations of lynx track intercepts along unplowed roads.  Each track has an associated STQ (snow track quality) rating

Enumerated domain:
Enumerated domain value: Regional Observation
Enumerated domain value definition: fix(original)
either a visual observation of lynx or observation of a track (STQ's not always reported)

Enumerated domain:
Enumerated domain value: Incidental Take
Enumerated domain value definition: fix(original)
reports of vehicle strike, incidental capture of lynx by hunters or trappers (either alive or dead), illegal take, natural mortalities

Attribute:
*Attribute label: STQ
*Attribute alias: STQ
Attribute definition: fix(original)
snow track quality (applies only to track observations)

*Attribute type: String
*Attribute width: 13

Attribute domain values:
Enumerated domain:
Enumerated domain value: STQ4
Enumerated domain value definition: fix(original)
Best; every footprint registers, and detail within prints is very clear.  Species identification is essentially absolute based on track details.

Enumerated domain:
Enumerated domain value: STQ3
Enumerated domain value definition: fix(original)
Good; every print registers, but details are weak, perhaps obscured by snow falling in print. Print details usually visible in microtopographic sites. e.g. tree wells and shadows.  Identification based on track details, but gait patterns offer needed support.

Enumerated domain:
Enumerated domain value: STQ2
Enumerated domain value definition: fix(original)
Acceptable; some prints fail to register, and footprint details, if present are visible only in microtopographic sites. Identification based primarily on gait patterns.

Enumerated domain:
Enumerated domain value: STQ1
Enumerated domain value definition: fix(original)
Poor; many prints do not register. Track details lacking. Identification is essentially by gait patterns, and may be possible only in microtopographic sites.

Enumerated domain:
Enumerated domain value: STQ0
Enumerated domain value definition: fix(original)
Unacceptable; target species does not leave enough prints to identify gait patterns left in trails.

Attribute:
*Attribute label: LOCACCURAC
*Attribute alias: LOCACCURAC
Attribute definition: fix(original)
this field defines the precision of data, most locations have an associated error based on the number of satellites used to obtain the location, however some locations were obtained before GPS and satellites were available, or in some cases a GPS unit was not available to mark the location. Those locations are estimated based on a dot on a map or reference to a road name or town.

*Attribute type: String
*Attribute width: 14

Attribute:
*Attribute label: DATABASE
*Attribute alias: DATABASE
Attribute definition: fix(original)
Data are from 4 separate databases documenting lynx observations in Maine by MDIFW staff. The 4 databases to track these data are: 1) Lynx Telemetry study, 2) Ecoregional lynx snow-track surveys, 3) MDIFW Regional biologist observations, and 4) Incidental Takes of lynx reported to MDIFW.

*Attribute type: String
*Attribute width: 17

Overview description:
Dataset overview: fix(original)
It is difficult to document the continued presence of lynx in areas with these data, as staff time and survey areas change from year to year (i.e. it is not that uncommon for areas previously visited by staff to not be visited the next year).  The fact that lynx are not observed in an area should not be inferred as absence.  In recent years, the frequency of lynx sign has precluded regional biologists from recording every observation, although staff will document the continued occurrence of lynx in areas previously occupied, as well as, any new areas.

Entity and attribute detail citation:
LYNX STUDY-TELEMETRY DATA
 
Since March of 1999, we have monitored 62 radio collared lynx in an around the Musquacook Lakes area.  The intensity of data for this area reflects an intensive field research effort (9 years) and not the value of this area to lynx, as other areas may have similar lynx densities, but lack intensive research efforts. 
 
VHF telemetry data:  From 1999-2006, aerial telemetry locations of radio collared lynx was the primary method of obtaining locational data.  Pilots marked each lynx location with a GPS and pilot telemetry error was between 50 and 100 m.  In 2006, our budget restricted the number of flights, thus we relied mostly on satellite (n=7) and GPS collars (n=7) to provide information on lynx movements.
 
Please note: 2 lynx captured by fur trappers outside the lynx study area were equipped with VHF radio collars: one animal near Smyrna Mills, ME (SE cluster of points) and the other near New Sweden, ME (NE cluster of pts). 
 
Satellite telemetry data (2004-present): Juvenile lynx are difficult to track from aircraft, thus satellite collars were placed on 1-7 juvenile lynx each year since 2004.  Satellite collars were programmed to obtain 3 fixes every 2 days.  Each satellite location is provided an associated estimated accuracy based on the successful communication with multiple satellites (up to 24 satellites are available).  Only locations with <1,000m accuracy were included.  The most accurate locations were within 150m of the animal's true location.
 
GPS telemetry data(2004-07):  Ten resident adult lynx previously monitored with VHF collars were equipped with GPS collars for 1 or more years from 2004-2007.  GPS collars were programmed to obtain between 1 and 4 locations/day cycling through the 24 hr clock. Approximately 60% of fix attempts producing a location.  Each location has an associated level of accuracy (dilution of precision (DOP).  These data have been screened for accuracy (DOP >12 removed (5% of locations); R. Moen, personal communication).
 
ECOREGIONAL SURVEYS
 
During the winters of 2003-08, standardized winter snow track surveys were conducted in 91 townships in northern, western, and central Maine to further document the current distribution of lynx in Maine.  To improve the likelihood that track identification was accurate, we only included lynx track intercepts with a snow track quality (STQ) rating greater than 2.  Sixty nine of 91 towns were surveyed under conditions that met our protocol for conducting surveys.  Lynx tracks with a STQ> 2 were observed in 27 of 69 towns.  Lynx tracks were also observed in 10 of 22 towns survey outside protocol conditions (e.g. <55 km surveyed/100km2 and/or >72 hrs after a snow/wind event); 5 of 10 towns had a STQ > 2. Thus definitive lynx tracks (STQ>2) were documented in 32 of 91 townships surveyed during the winters of 2003-2008.  This includes 89 tracks in 14 townships in 2003, 34 tracks in 7 townships in 2004, 6 tracks in 2 townships in 2005, 10 tracks in 1 township in 2006, 37 tracks in 7 towns in 2007, and 16 tracks in 5 townships in 2008. This does not equate to 192 lynx as a single lynx may have made multiple track intercepts along a road.  All these points were marked with GPS and were within < 50 m of the actual location (majority <10m error).
 
INCIDENTAL LYNX TAKE REPORTED TO MDIFW
 
This includes 77 records of reported road mortalities, incidental captures of lynx by hunters and trappers, and illegal take of lynx between 1975 and 2007. These data include dead lynx (e.g. road mortalities) and lynx released alive from traps or by hunters.  The location of most incidents were recorded with a GPS unit and were within <50 m of the true location.  On occasion, a GPS was not available to mark the location of the incident and these data are accurate within the township or specific area (e.g. road intersection) within a town.
 
LYNX SIGHTINGS REPORTED TO OR OBSERVED BY IF&W REGIONAL BIOLOGIST FROM 1992 TO MARCH 2008
 
Most observations were observed directly by the regional biologist while conducting other department activities.  The remaining observations were by an individual that the regional biologist deemed qualified to identify a lynx track (e.g. wardens).  Observations that are not verified by a biologist or other qualified individuals are not included in the database.   Accuracy varies from GPS coordinates to town level.  GPS locations are accurate within 50m; most observations were within 10 m of the true location. fix(original)

Back to Top
Distribution Information:

Distributor:
Contact information:
Contact organization primary:
Contact organization: Maine Department of Inland Fisheries and Wildlife

Contact voice telephone: 207-941-4238
Contact facsimile telephone: 207-941-4450

Contact electronic mail address: jennifer.vashon@maine.gov

Resource description: Downloadable Data

Standard order process:
Digital form:
Digital transfer information:
*Transfer size: 0.390
*Dataset size: 0.390

Back to Top
Metadata Reference Information:

*Metadata date: 20080919

*Language of metadata: en

Metadata contact:
Contact information:
Contact person primary:
Contact person: Amy Meehan
Contact organization: Maine Department of Inland Fisheries and Wildlife
Contact position: Wildlife Biologist

Contact address:
Address type: mailing and physical address
Address: fix(original)
650 State Street
City: Bangor
State or province: Maine
Postal code: 04401
Country: USA

Contact voice telephone: 207-941-4483
Contact facsimile telephone: 207-941-4450

Contact electronic mail address: amy.meehan@maine.gov

*Metadata standard name: FGDC Content Standards for Digital Geospatial Metadata
*Metadata standard version: FGDC-STD-001-1998
*Metadata time convention: local time

Metadata extensions:
*Online linkage: http://www.esri.com/metadata/esriprof80.html
*Profile name: ESRI Metadata Profile

Back to Top

 


Last updated: November 19, 2008