xBio:D Wiki - User contributions [en]

Biological Association Type Terms

2016-04-05T17:08:23Z

Matte: /* Biological Association Type Terms */

'''Introduction'''

This section contains information on the available biological association terms that are currently available in the xBio:D system. Biological associations within xBio:D represents a two-way relationship between the first organism and the second, and the association type is separated by a slash (/). For example, if you want to show a parasitoid-host relationship in which the specimen record you have is for the parasitoid (A) and the unvouchered associate (B) is its host, the association type ''emerged from egg of / host egg of'' would be read ''parasitoid (A) emerged from host (B)'' and conversely ''host (B) is a host egg of parasitoid (A)''. If you would like another biological association term added into xBio:D, please contact [mailto:cora.1@osu.edu Joe Cora] and request the addition.

== Biological Association Type Terms ==
{|
!Association Type
!Description
|-
|adult of / pupa of
|
|-
|among pieces of fallen nest of / fallen nest pieces contained
|
|-
|at base of large / large with base containing
|
|-
|between leaves of / leaves containing
|
|-
|burrowing into / contains burrowing
|
|-
|buzz pollinating / buzz pollinated by
|
|-
|collected in / contains
|
|-
|collected in drilled / drilled collecting site of
|
|-
|collected near / living near
|
|-
|collected near eggs / eggs present near
|
|-
|collected near flowering / flowering living near
|
|-
|collected near gall / gall present near
|
|-
|collected near nymph of / nymph present near
|
|-
|collected near stand of / stand present near
|
|-
|collected on / collecting site of
|
|-
|collected under / collecting site above
|
|-
|collected with / used to collect
|
|-
|collected with dung of / dung used to collect
|
|-
|collected with pheromone of / pheromone used to collect
|
|-
|collected with rotting / rotting used to collect
|
|-
|collection site of / collected on
|
|-
|egg ectoparasite of / host egg of
|
|-
|egg parasite of / host egg of
|
|-
|egg predator of / prey egg of
|
|-
|emerged from / produced
|
|-
|emerged from boring dust of / host boring dust of
|
|-
|emerged from cocoon of / host cocoon of
|
|-
|emerged from decayed / decayed host of
|
|-
|emerged from diapausing eggs of / diapausing host eggs of
|
|-
|emerged from egg of / host egg of
|
|-
|emerged from egg sac of / host egg sac of
|
|-
|emerged from freshly killed / freshly killed host of
|
|-
|emerged from fruit of / host fruit of
|
|-
|emerged from gall of / host gall of
|
|-
|emerged from immature of / host immature of
|
|-
|emerged from larva of / host larva of
|
|-
|emerged from leaf gall of / host leaf gall of
|
|-
|emerged from leaf mine of / leaf mine containing
|
|-
|emerged from leaf mine on / leaf mine containing
|
|-
|emerged from leaf of / host leaf of
|
|-
|emerged from mossy gall of / host mossy gall of
|
|-
|emerged from mummy of / host mummy of
|
|-
|emerged from nest of / host nest of
|
|-
|emerged from nymph of / host nymph of
|
|-
|emerged from ootheca of / host ootheca of
|
|-
|emerged from pod of / host pod of
|
|-
|emerged from pole of / host pole containing
|
|-
|emerged from pupa of / host pupa of
|
|-
|emerged from pupal chamber of / host pupal chamber of
|
|-
|emerged from puparium of / host puparium of
|
|-
|emerged from root crown of / host root crown of
|
|-
|emerged from root gall of / host root gall of
|
|-
|emerged from seed of / host seed of
|
|-
|emerged from sentinel egg mass of / host sentinel egg mass of
|
|-
|emerged from spongy leaf gall of / host spongy leaf gall of
|
|-
|emerged from stem gall of / host stem gall of
|
|-
|emerged from tunnel of / host tunnel of
|
|-
|emerged from twig of / host twig of
|
|-
|fed upon by / feeding on
|
|-
|feeding on / fed upon by
|
|-
|feeding on bark of / fed upon bark by
|
|-
|feeding on bud, shoot of / fed upon bud, shoot by
|
|-
|feeding on bulb of / fed upon bulb by
|
|-
|feeding on egg of / fed on egg by
|
|-
|feeding on flower of / fed on flower by
|
|-
|feeding on fruit, nut, seed of / fed on fruit, nut, seed by
|
|-
|feeding on gall of / fed on gall by
|
|-
|feeding on leaf gall of / fed upon leaf gall by
|
|-
|feeding on leaf of / fed upon leaf by
|
|-
|feeding on root of / fed upon root by
|
|-
|feeding on shoot of / fed upon shoot by
|
|-
|feeding on silk and end of ear of / fed upon silk and end of ear by
|
|-
|feeding on stem of / fed upon stem by
|
|-
|feeding on tree trunk of / fed upon tree trunk by
|
|-
|feeding on twig, branch of / fed upon twig, branch by
|
|-
|flying after / flying from
|
|-
|gregarious egg parasitoid of / host egg of
|
|-
|host egg of / emerged from egg of
|
|-
|host egg of / solitary egg parasitoid of
|
|-
|host larva of / larval parasitoid of
|
|-
|host of / parasite of
|
|-
|hyperparasite of / host of
|
|-
|in abandoned nest of / abandoned nest containing
|
|-
|in artificial colony of / artificial colony containing
|
|-
|in bark crack of / bark crack containing
|
|-
|in burrow of / burrow containing
|
|-
|in buttress of / buttress containing
|
|-
|in canopy of / canopy containing
|
|-
|in catface of living / living with catface containing
|
|-
|in center of rotten / rotten center containing
|
|-
|in clump of / clump containing
|
|-
|in cocoon of / cocoon containing
|
|-
|in colony of / colony containing
|
|-
|in culture of / culture containing
|
|-
|in dead log of / dead log containing
|
|-
|in decaying / decayed containing
|
|-
|in decaying bark of / decayed bark containing
|
|-
|in decaying fruit, nut, seed of / decayed fruit, nut, seed containing
|
|-
|in decaying log of / decayed log containing
|
|-
|in decaying mulch of / decayed mulch containing
|
|-
|in decaying root of / decayed root containing
|
|-
|in decaying tree stump of / decayed tree stump containing
|
|-
|in duff of / duff containing
|
|-
|in dunnage of / dunnage containing
|
|-
|in fallen of / fallen containing
|
|-
|in field with / in field with
|
|-
|in flower head of / flower head containing
|
|-
|in gall of / gall containing
|
|-
|in gall of flowering / flowering with gall containing
|
|-
|in galleries of / galleries containing
|
|-
|in leaf nest of / leaf nest containing
|
|-
|in leaf sheath of / leaf sheath containing
|
|-
|in litter of / litter containing
|
|-
|in litter of treehole of / litter of treehole containing
|
|-
|in litter under log of / litter under log containing
|
|-
|in litter with / in litter with
|
|-
|in log of / log containing
|
|-
|in log with / in log with
|
|-
|in manure (feces) of / manure (feces) containing
|
|-
|in mine of / mine containing
|
|-
|in moist decayed log of / moist decayed log containing
|
|-
|in nest of / nest containing
|
|-
|in nest on body of / body in nest containing
|
|-
|in nest with dead chick of / dead chick within nest with
|
|-
|in nest within / containing nest with
|
|-
|in nose of / nose containing
|
|-
|in paneling of / paneling containing
|
|-
|in petiole of / petiole containing
|
|-
|in roast of / roast containing
|
|-
|in roost of / roost containing
|
|-
|in root / root containing
|
|-
|in rotten / rotten containing
|
|-
|in rotten stump of / rotten stump containing
|
|-
|in scat of / scat containing
|
|-
|in shell of / shell containing
|
|-
|in silk tube of / silk tube containing
|
|-
|in soil with / in soil with
|
|-
|in soil with bulb of / bulb in soil with
|
|-
|in soil with root of / root in soil with
|
|-
|in square of / square containing
|
|-
|in stable with / stable containing
|
|-
|in stand of / stand containing
|
|-
|in stem of / stem containing
|
|-
|in stem gall of / stem gall containing
|
|-
|in stomach of / stomach containing
|
|-
|in straw of / straw containing
|
|-
|in stubble of / stubble containing
|
|-
|in subterranean dump of / subterranean dump containing
|
|-
|in thicket of / thicket containing
|
|-
|in treehole of / treehole containing
|
|-
|in trunk of / trunk containing
|
|-
|in tunnel of / tunnel containing
|
|-
|in vein on underside of leaf of / vein on under of leaf containing
|
|-
|in water with / in water with
|
|-
|in web of / web containing
|
|-
|in young leaf of / young leaf containing
|
|-
|infected by / infecting
|
|-
|inhabits / habitat for
|
|-
|internal parasite of / internal host of
|
|-
|larval parasite of / host larva of
|
|-
|larval parasitoid of / host larva of
|
|-
|larval predator of / prey larva of
|
|-
|living in / lived in by
|
|-
|living in colon of / lived within colon by
|
|-
|living in hypodermis of / lived within hypodermis by
|
|-
|living in pitcher of / lived within pitcher by
|
|-
|living in synovial fluid of / lived within synovial fluid by
|
|-
|living in treehole of / lived within treehole by
|
|-
|living on / lived on by
|
|-
|living on bark of / lived on bark by
|
|-
|living on body of / lived on body by
|
|-
|living on branch of / lived on branch by
|
|-
|living on bud of / lived on bud by
|
|-
|living on bulb of / lived on bulb by
|
|-
|living on feather of / lived on feather by
|
|-
|living on flower of / lived on flower by
|
|-
|living on fruit, nut, seed of / lived on fruit, nut, seed by
|
|-
|living on hair follicle of / lived on hair follicle by
|
|-
|living on hair of / lived on hair by
|
|-
|living on head of / lived on head by
|
|-
|living on leaf of / lived on leaf by
|
|-
|living on log of / lived on log by
|
|-
|living on male cone of / lived on male cone by
|
|-
|living on mosaic infected / (mosaic infected) lived on by
|
|-
|living on nut, seed of / lived on nut, seed by
|
|-
|living on pupa of / lived on pupa by
|
|-
|living on root of / lived on root by
|
|-
|living on sapflow of / lived on sapflow by
|
|-
|living on seed of / lived on seed by
|
|-
|living on shoot of / lived on shoot by
|
|-
|living on stem of / lived on stem by
|
|-
|living on tail of / lived on tail by
|
|-
|living on tree trunk of / lived on tree trunk by
|
|-
|living on twig, branch of / lived on twig, branch by
|
|-
|living on wash of / lived on wash by
|
|-
|living on wing of / lived on wing by
|
|-
|living under bark of / lived under bark by
|
|-
|living under bark of dead / lived under bark by
|
|-
|living under bark of fallen / lived under bark by
|
|-
|living under bark of living / lived under bark by
|
|-
|living under bark of rotten trunk of / lived under bark of rotten trunk by
|
|-
|living under chips of cut / lived under chips by
|
|-
|living with / living with
|
|-
|mother parasitic on / host of mother of
|
|-
|nest containing / in nest of
|
|-
|on abdomen of / abdomen containing
|
|-
|on aphid infested / aphid infested containing
|
|-
|on ball of / ball containing
|
|-
|on bark of / bark containing
|
|-
|on bark of dead / dead with bark containing
|
|-
|on bark of living / living with bark containing
|
|-
|on bloom of / bloom containing
|
|-
|on blossom of / blossom containing
|
|-
|on body of / body containing
|
|-
|on branch of / branch containing
|
|-
|on bulb of / bulb containing
|
|-
|on cadaver of / cadaver containing
|
|-
|on cone of / cone containing
|
|-
|on cone flower of / cone flower containing
|
|-
|on coppice of / coppice containing
|
|-
|on corrigated & crumpled leaf of dwarfed / (dwarfed) corrigated & crumpled leaf containing
|
|-
|on dead / dead containing
|
|-
|on dead branch of / dead branch containing
|
|-
|on dead leaf of / dead leaf containing
|
|-
|on dead limb of / dead limb containing
|
|-
|on dead limb or trunk of / dead limb or trunk containing
|
|-
|on dead or dying twig of / dead or dying twig containing
|
|-
|on dead remains of / upon dead remains by
|
|-
|on dead twig of / dead twig containing
|
|-
|on dead vine of / dead vine containing
|
|-
|on dead, standing / dead, standing containing
|
|-
|on decayed / decayed containing
|
|-
|on decayed log of / decayed log containing
|
|-
|on decayed stump of / decayed stump containing
|
|-
|on decaying of / decaying containing
|
|-
|on deep sear of living / living with deep sear containing
|
|-
|on dense growth of / dense growth containing
|
|-
|on dry / dry containing
|
|-
|on dry dung of / dry dung containing
|
|-
|on dung of / dung containing
|
|-
|on ear of / ear containing
|
|-
|on egg of / egg containing
|
|-
|on egg sac of / egg sac containing
|
|-
|on eye of / eye containing
|
|-
|on female adult of / female adult containing
|
|-
|on fire scorched of / fire scorched containing
|
|-
|on flower bud of / flower bud containing
|
|-
|on flower of / flower containing
|
|-
|on flower stalk of / flower stalk containing
|
|-
|on flowering / flowering containing
|
|-
|on flowerless / flowerless containing
|
|-
|on foliage of / foliage containing
|
|-
|on fresh wound of / fresh wound containing
|
|-
|on freshly cut / freshly cut containing
|
|-
|on frond of / frond containing
|
|-
|on fruit of / fruit containing
|
|-
|on fruiting / fruiting containing
|
|-
|on gills of / gills containing
|
|-
|on guano of / guano contaning
|
|-
|on heavily curled leaf of / heavily curled leaf containing
|
|-
|on inflorescence of / inflorescence containing
|
|-
|on lamina of / lamina containing
|
|-
|on large, hollow / large, hollow containing
|
|-
|on leaf axil of / leaf axil containing
|
|-
|on leaf of / leaf containing
|
|-
|on leaf petiole of / leaf petiole containing
|
|-
|on leaflet of / leaflet containing
|
|-
|on log of / log containing
|
|-
|on midrib of / midrib containing
|
|-
|on moldy, shelled / moldy, shelled containing
|
|-
|on needle of / needle containing
|
|-
|on or near / containing or near
|
|-
|on or near flowering / flowering containing or near
|
|-
|on or near flowers of / flowers containing or near
|
|-
|on overripe fruit of / overripe fruit containing
|
|-
|on paddy edge of / paddy edge containing
|
|-
|on paddy of / paddy containing
|
|-
|on pod of / pod containing
|
|-
|on rosette / rosette containing
|
|-
|on rotten / rotten containing
|
|-
|on rotten fruit of / rotten fruit containing
|
|-
|on rotten log of / rotten log containing
|
|-
|on rotting / rotting containing
|
|-
|on scrub / scrub containing
|
|-
|on seed of / seed containing
|
|-
|on seedling of / seedling containing
|
|-
|on short / short containing
|
|-
|on skin of / skin containing
|
|-
|on stalk of / stalk containing
|
|-
|on stem of / stem containing
|
|-
|on sticky seed of / sticky seed containing
|
|-
|on stomach of cadaver of / stomach of cadaver containing
|
|-
|on stored product of / stored product containing
|
|-
|on stump of / stump containing
|
|-
|on thorax of / thorax containing
|
|-
|on top of flower of / top of flower containing
|
|-
|on tree of / tree containing
|
|-
|on trunk of / trunk containing
|
|-
|on trunk of dead / dead with trunk containing
|
|-
|on trunk of dying / dying with trunk containing
|
|-
|on twig of / twig containing
|
|-
|on underside of frond of / underside of frond containing
|
|-
|on unflowered / unflowered containing
|
|-
|on vine of / vine containing
|
|-
|on wild of / wild containing
|
|-
|on wing of / wing containing
|
|-
|on wound of twig of / wound of twig containing
|
|-
|on young / young containing
|
|-
|ovipositing into bud of / host bud of
|
|-
|ovipositing into egg of / host egg of
|
|-
|ovipositing into gall of / host gall of
|
|-
|ovipositing into young sprout of / young sprout containing
|
|-
|paraphage on / host of
|
|-
|parasite of / host of
|
|-
|parasitic in ear of / host ear of
|
|-
|parasitic in nose of / host nose of
|
|-
|parasitic in skin of / host skin of
|
|-
|parasitic on abdomen of / host abdomen of
|
|-
|parasitic on body of / host body of
|
|-
|parasitic on branchial chamber of / host branchial chamber of
|
|-
|parasitic on cloaca of / host cloaca of
|
|-
|parasitic on coxa of / host coxa of
|
|-
|parasitic on ear of / host ear of
|
|-
|parasitic on egg of / host egg of
|
|-
|parasitic on eye of / host eye of
|
|-
|parasitic on genitalia of / host genitalia of
|
|-
|parasitic on gills of / host gills of
|
|-
|parasitic on hair follicle of / host hair follicle of
|
|-
|parasitic on hair of / host hair of
|
|-
|parasitic on head of / host head of
|
|-
|parasitic on hypodermis of / host hypodermis of
|
|-
|parasitic on larva of / host larva of
|
|-
|parasitic on limb of / host limb of
|
|-
|parasitic on lung of / host lung of
|
|-
|parasitic on mouth of / host mouth of
|
|-
|parasitic on nipple of / host nipple of
|
|-
|parasitic on nose of / host nose of
|
|-
|parasitic on pupa of / host pupa of
|
|-
|parasitic on quill feather (covert) of / host quill feather (covert) of
|
|-
|parasitic on quill feather (flight feather) of / host quill feather (flight feather) of
|
|-
|parasitic on quill feather (tail feather) of / host quill feather (tail feather) of
|
|-
|parasitic on quill feather of / host quill feather of
|
|-
|parasitic on sentinel egg of / host sentinel egg of
|
|-
|parasitic on shoot of / host shoot of
|
|-
|parasitic on skin of / host skin of
|
|-
|parasitic on stomach of / host stomach of
|
|-
|parasitic on tail of / host tail of
|
|-
|parasitic on thorax of / host thorax of
|
|-
|parasitic on trachea of / host trachea of
|
|-
|parasitic on wash of / host wash of
|
|-
|parasitic on wing of / host wing of
|
|-
|parasitic under elytra of / under elytral host of
|
|-
|parasitic under scales of / under scales host of
|
|-
|parasitoid of / host of
|
|-
|patolling on / patrolled by
|
|-
|phoretic on / host of
|
|-
|phoretic on abdomen of / host abdomen of
|
|-
|phoretic on alate / alate host of
|
|-
|phoretic on antenna of / host antenna of
|
|-
|phoretic on body of / host body of
|
|-
|phoretic on coxa of / host coxa of
|
|-
|phoretic on eye of / host eye of
|
|-
|phoretic on hair follicle of / host hair follicle of
|
|-
|phoretic on head of / host head of
|
|-
|phoretic on leg of / host leg of
|
|-
|phoretic on limb of / host limb of
|
|-
|phoretic on tail of / host tail of
|
|-
|phoretic on thorax of / host thorax of
|
|-
|phoretic on wing of / host wing of
|
|-
|phoretic under elytra of / under elytral host of
|
|-
|phoretic under supra-anal plate of / under supra-anal plate host of
|
|-
|pollinating / pollinated by
|
|-
|predator of / prey of
|
|-
|prey of / predator of
|
|-
|pupa of / adult of
|
|-
|recorded in background with / in background for recording of
|
|-
|solitary egg parasitoid of / host egg of
|
|-
|stinging neck of / neck being stung by
|
|-
|stomach parasite of / host stomach of
|
|-
|subcortically living in dead / dead subcortically living in by
|
|-
|subcutaneous parasite of / subcutaneous host of
|
|-
|subcutaneously living in / subcutaneously lived in by
|
|-
|tracheal parasite of / tracheal host of
|
|-
|under bark of / under bark by
|
|-
|under bark of dead / dead under bark by
|
|-
|under bark of dead or dying twig or branch / dead or dying twig or branch under bark by
|
|-
|under bark of freshly killed / freshly killed under bark by
|
|-
|under bark of log of / log under bark by
|
|-
|under bark of stump of / stump under bark by
|
|-
|under bark of trunk of dead / dead under bark of trunk by
|
|-
|under dead / under dead by
|
|-
|under dead stem of / under dead stem by
|
|-
|under dry dung of / under dry dung by
|
|-
|under dung of / under dung by
|
|-
|under loose bark of / under loose bark by
|
|-
|under manure (feces) of / under manure (feces) by
|
|-
|under rocks with / under rocks with
|
|-
|under seed of / under seed by
|
|-
|unspecified association / unspecified association
|
|-
|wing parasite of / host wing of
|
|-
|with eggs of / eggs with
|
|-
|with roots of / roots with
|
|}

[[Category:Data Entry Assistant]]
[[Category:xBio:D Controlled Vocabularies]]

Locality Georeferencing and Generation

2016-04-01T18:56:36Z

Matte: /* Formatting Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained within [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Twp., sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::"jct." for the junction of two roads
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::Directions from localities should be abbreviated (e.g. N of Papallacta, 4km S Sálakos)
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
***Isl. is the proper abbreviation for Island
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*A locality name should start with a specific containing entity, if the most specific containing entity is a county or state, use the most specific locality information.
**e.g. the locality name for "CO:Moffat Co. Rt. 40, 9.8 miles W Maybell" would be "US-40, 9.8mi W Maybell, Moffat Co., CO". However, "CO:Moffat Co. 9.8 miles W Maybell" would yield a locality name of "9.8mi W Maybell, Moffat Co., CO" as 9.8mi W Maybell is specific locality information, but is not a containing entity. Roads can be considered as containing entities since the specimen is collected along the road.
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*Information that relates directly to an aspect of a feature/place should be formatted as follows:
**“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
**“Slopes” and “summits” of mountains should follow the same format (e.g. W slope of Clyde Mountain, NSW, Australia; summit of Fairview Canyon, Sanpete Co., UT)
**“Sides” and compass directions of locales follow the same format (e.g. E side of Lake Jennings, San Diego Co., CA; N of Belmont, Brown Co., IN)

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2016-04-01T18:08:53Z

Matte: /* Formatting Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained within [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Twp., sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::"jct." for the junction of two roads
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::Directions from localities should be abbreviated (e.g. N of Papallacta, 4km S Sálakos)
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
***Isl. is the proper abbreviation for Island
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*A locality name should start with a specific containing entity, if the most specific containing entity is a county or state, use the most specific locality information.
**e.g. the locality name for "CO:Moffat Co. Rt. 40, 9.8 miles W Maybell" would be "US-40, 9.8mi W Maybell, Moffat Co., CO". However, "CO:Moffat Co. 9.8 miles W Maybell" would yield a locality name of "9.8mi W Maybell, Moffat Co., CO" as 9.8mi W Maybell is specific locality information, but is not a containing entity. Roads can be considered as containing entities since the specimen is collected along the road.
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*Information that relates directly to a specific place within a locality should be formatted as follows:
**“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
**“Slopes” and “summits” of mountains should follow the same format (e.g. W slope of Clyde Mountain, NSW, Australia; summit of Fairview Canyon, Sanpete Co., UT)
**“Sides” and compass directions of locales follow the same format (e.g. E side of Lake Jennings, San Diego Co., CA; N of Belmont, Brown Co., IN)

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2016-03-30T15:17:49Z

Matte: /* Formatting Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained within [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Twp., sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::"jct." for the junction of two roads
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::Directions from localities should be abbreviated (e.g. N of Papallacta, 4km S Sálakos)
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
***Isl. is the proper abbreviation for Island
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*A locality name should start with a specific containing entity, if the most specific containing entity is a county or state, use the most specific locality information.
**e.g. the locality name for "CO:Moffat Co. Rt. 40, 9.8 miles W Maybell" would be "US-40, 9.8mi W Maybell, Moffat Co., CO". However, "CO:Moffat Co. 9.8 miles W Maybell" would yield a locality name of "9.8mi W Maybell, Moffat Co., CO" as 9.8mi W Maybell is specific locality information, but is not a containing entity. Roads can be considered as containing entities since the specimen is collected along the road.
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2016-03-30T15:12:01Z

Matte: /* Formatting Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained within [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Twp., sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::"jct." for the junction of two roads
::"Isl." for island
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::Directions from localities should be abbreviated (e.g. N of Papallacta, 4km S Sálakos)
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*A locality name should start with a specific containing entity, if the most specific containing entity is a county or state, use the most specific locality information.
**e.g. the locality name for "CO:Moffat Co. Rt. 40, 9.8 miles W Maybell" would be "US-40, 9.8mi W Maybell, Moffat Co., CO". However, "CO:Moffat Co. 9.8 miles W Maybell" would yield a locality name of "9.8mi W Maybell, Moffat Co., CO" as 9.8mi W Maybell is specific locality information, but is not a containing entity. Roads can be considered as containing entities since the specimen is collected along the road.
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2016-03-30T15:09:52Z

Matte: /* Formatting Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained within [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Twp., sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
::"Isl." for island
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*A locality name should start with a specific containing entity, if the most specific containing entity is a county or state, use the most specific locality information.
**e.g. the locality name for "CO:Moffat Co. Rt. 40, 9.8 miles W Maybell" would be "US-40, 9.8mi W Maybell, Moffat Co., CO". However, "CO:Moffat Co. 9.8 miles W Maybell" would yield a locality name of "9.8mi W Maybell, Moffat Co., CO" as 9.8mi W Maybell is specific locality information, but is not a containing entity. Roads can be considered as containing entities since the specimen is collected along the road.
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Biological Association Type Terms

2016-03-25T17:21:16Z

Matte: /* Biological Association Type Terms */

'''Introduction'''

This section contains information on the available biological association terms that are currently available in the xBio:D system. Biological associations within xBio:D represents a two-way relationship between the first organism and the second, and the association type is separated by a slash (/). For example, if you want to show a parasitoid-host relationship in which the specimen record you have is for the parasitoid (A) and the unvouchered associate (B) is its host, the association type ''emerged from egg of / host egg of'' would be read ''parasitoid (A) emerged from host (B)'' and conversely ''host (B) is a host egg of parasitoid (A)''. If you would like another biological association term added into xBio:D, please contact [mailto:cora.1@osu.edu Joe Cora] and request the addition.

== Biological Association Type Terms ==
{|
!Association Type
!Description
|-
|adult of / pupa of
|
|-
|among pieces of fallen nest of / fallen nest pieces contained
|
|-
|at base of large / large with base containing
|
|-
|between leaves of / leaves containing
|
|-
|burrowing into / contains burrowing
|
|-
|buzz pollinating / buzz pollinated by
|
|-
|collected in / contains
|
|-
|collected in drilled / drilled collecting site of
|
|-
|collected near / living near
|
|-
|collected near eggs / eggs present near
|
|-
|collected near flowering / flowering living near
|
|-
|collected near gall / gall present near
|
|-
|collected near nymph of / nymph present near
|
|-
|collected near stand of / stand present near
|
|-
|collected on / collecting site of
|
|-
|collected under / collecting site above
|
|-
|collected with / used to collect
|
|-
|collected with dung of / dung used to collect
|
|-
|collected with pheromone of / pheromone used to collect
|
|-
|collected with rotting / rotting used to collect
|
|-
|collection site of / collected on
|
|-
|egg ectoparasite of / host egg of
|
|-
|egg parasite of / host egg of
|
|-
|egg predator of / prey egg of
|
|-
|emerged from / produced
|
|-
|emerged from cocoon of / host cocoon of
|
|-
|emerged from decayed / decayed host of
|
|-
|emerged from diapausing eggs of / diapausing host eggs of
|
|-
|emerged from egg of / host egg of
|
|-
|emerged from egg sac of / host egg sac of
|
|-
|emerged from freshly killed / freshly killed host of
|
|-
|emerged from fruit of / host fruit of
|
|-
|emerged from gall of / host gall of
|
|-
|emerged from immature of / host immature of
|
|-
|emerged from larva of / host larva of
|
|-
|emerged from leaf gall of / host leaf gall of
|
|-
|emerged from leaf mine of / leaf mine containing
|
|-
|emerged from leaf mine on / leaf mine containing
|
|-
|emerged from leaf of / host leaf of
|
|-
|emerged from mossy gall of / host mossy gall of
|
|-
|emerged from mummy of / host mummy of
|
|-
|emerged from nest of / host nest of
|
|-
|emerged from nymph of / host nymph of
|
|-
|emerged from ootheca of / host ootheca of
|
|-
|emerged from pod of / host pod of
|
|-
|emerged from pole of / host pole containing
|
|-
|emerged from pupa of / host pupa of
|
|-
|emerged from pupal chamber of / host pupal chamber of
|
|-
|emerged from puparium of / host puparium of
|
|-
|emerged from root crown of / host root crown of
|
|-
|emerged from root gall of / host root gall of
|
|-
|emerged from seed of / host seed of
|
|-
|emerged from sentinel egg mass of / host sentinel egg mass of
|
|-
|emerged from spongy leaf gall of / host spongy leaf gall of
|
|-
|emerged from stem gall of / host stem gall of
|
|-
|emerged from tunnel of / host tunnel of
|
|-
|emerged from twig of / host twig of
|
|-
|fed upon by / feeding on
|
|-
|feeding on / fed upon by
|
|-
|feeding on bark of / fed upon bark by
|
|-
|feeding on bud, shoot of / fed upon bud, shoot by
|
|-
|feeding on bulb of / fed upon bulb by
|
|-
|feeding on egg of / fed on egg by
|
|-
|feeding on flower of / fed on flower by
|
|-
|feeding on fruit, nut, seed of / fed on fruit, nut, seed by
|
|-
|feeding on gall of / fed on gall by
|
|-
|feeding on leaf gall of / fed upon leaf gall by
|
|-
|feeding on leaf of / fed upon leaf by
|
|-
|feeding on root of / fed upon root by
|
|-
|feeding on shoot of / fed upon shoot by
|
|-
|feeding on silk and end of ear of / fed upon silk and end of ear by
|
|-
|feeding on stem of / fed upon stem by
|
|-
|feeding on tree trunk of / fed upon tree trunk by
|
|-
|feeding on twig, branch of / fed upon twig, branch by
|
|-
|flying after / flying from
|
|-
|gregarious egg parasitoid of / host egg of
|
|-
|host egg of / emerged from egg of
|
|-
|host egg of / solitary egg parasitoid of
|
|-
|host larva of / larval parasitoid of
|
|-
|host of / parasite of
|
|-
|hyperparasite of / host of
|
|-
|in abandoned nest of / abandoned nest containing
|
|-
|in artificial colony of / artificial colony containing
|
|-
|in bark crack of / bark crack containing
|
|-
|in burrow of / burrow containing
|
|-
|in buttress of / buttress containing
|
|-
|in canopy of / canopy containing
|
|-
|in catface of living / living with catface containing
|
|-
|in center of rotten / rotten center containing
|
|-
|in clump of / clump containing
|
|-
|in cocoon of / cocoon containing
|
|-
|in colony of / colony containing
|
|-
|in culture of / culture containing
|
|-
|in dead log of / dead log containing
|
|-
|in decaying / decayed containing
|
|-
|in decaying bark of / decayed bark containing
|
|-
|in decaying fruit, nut, seed of / decayed fruit, nut, seed containing
|
|-
|in decaying log of / decayed log containing
|
|-
|in decaying mulch of / decayed mulch containing
|
|-
|in decaying root of / decayed root containing
|
|-
|in decaying tree stump of / decayed tree stump containing
|
|-
|in duff of / duff containing
|
|-
|in dunnage of / dunnage containing
|
|-
|in fallen of / fallen containing
|
|-
|in field with / in field with
|
|-
|in flower head of / flower head containing
|
|-
|in gall of / gall containing
|
|-
|in gall of flowering / flowering with gall containing
|
|-
|in galleries of / galleries containing
|
|-
|in leaf nest of / leaf nest containing
|
|-
|in leaf sheath of / leaf sheath containing
|
|-
|in litter of / litter containing
|
|-
|in litter of treehole of / litter of treehole containing
|
|-
|in litter under log of / litter under log containing
|
|-
|in litter with / in litter with
|
|-
|in log of / log containing
|
|-
|in log with / in log with
|
|-
|in manure (feces) of / manure (feces) containing
|
|-
|in mine of / mine containing
|
|-
|in moist decayed log of / moist decayed log containing
|
|-
|in nest of / nest containing
|
|-
|in nest on body of / body in nest containing
|
|-
|in nest with dead chick of / dead chick within nest with
|
|-
|in nest within / containing nest with
|
|-
|in nose of / nose containing
|
|-
|in paneling of / paneling containing
|
|-
|in petiole of / petiole containing
|
|-
|in roast of / roast containing
|
|-
|in roost of / roost containing
|
|-
|in root / root containing
|
|-
|in rotten / rotten containing
|
|-
|in rotten stump of / rotten stump containing
|
|-
|in scat of / scat containing
|
|-
|in shell of / shell containing
|
|-
|in silk tube of / silk tube containing
|
|-
|in soil with / in soil with
|
|-
|in soil with bulb of / bulb in soil with
|
|-
|in soil with root of / root in soil with
|
|-
|in square of / square containing
|
|-
|in stable with / stable containing
|
|-
|in stand of / stand containing
|
|-
|in stem of / stem containing
|
|-
|in stem gall of / stem gall containing
|
|-
|in stomach of / stomach containing
|
|-
|in straw of / straw containing
|
|-
|in stubble of / stubble containing
|
|-
|in subterranean dump of / subterranean dump containing
|
|-
|in thicket of / thicket containing
|
|-
|in treehole of / treehole containing
|
|-
|in trunk of / trunk containing
|
|-
|in tunnel of / tunnel containing
|
|-
|in vein on underside of leaf of / vein on under of leaf containing
|
|-
|in water with / in water with
|
|-
|in web of / web containing
|
|-
|in young leaf of / young leaf containing
|
|-
|infected by / infecting
|
|-
|inhabits / habitat for
|
|-
|internal parasite of / internal host of
|
|-
|larval parasite of / host larva of
|
|-
|larval parasitoid of / host larva of
|
|-
|larval predator of / prey larva of
|
|-
|living in / lived in by
|
|-
|living in colon of / lived within colon by
|
|-
|living in hypodermis of / lived within hypodermis by
|
|-
|living in pitcher of / lived within pitcher by
|
|-
|living in synovial fluid of / lived within synovial fluid by
|
|-
|living in treehole of / lived within treehole by
|
|-
|living on / lived on by
|
|-
|living on bark of / lived on bark by
|
|-
|living on body of / lived on body by
|
|-
|living on branch of / lived on branch by
|
|-
|living on bud of / lived on bud by
|
|-
|living on bulb of / lived on bulb by
|
|-
|living on feather of / lived on feather by
|
|-
|living on flower of / lived on flower by
|
|-
|living on fruit, nut, seed of / lived on fruit, nut, seed by
|
|-
|living on hair follicle of / lived on hair follicle by
|
|-
|living on hair of / lived on hair by
|
|-
|living on head of / lived on head by
|
|-
|living on leaf of / lived on leaf by
|
|-
|living on log of / lived on log by
|
|-
|living on male cone of / lived on male cone by
|
|-
|living on mosaic infected / (mosaic infected) lived on by
|
|-
|living on nut, seed of / lived on nut, seed by
|
|-
|living on pupa of / lived on pupa by
|
|-
|living on root of / lived on root by
|
|-
|living on sapflow of / lived on sapflow by
|
|-
|living on seed of / lived on seed by
|
|-
|living on shoot of / lived on shoot by
|
|-
|living on stem of / lived on stem by
|
|-
|living on tail of / lived on tail by
|
|-
|living on tree trunk of / lived on tree trunk by
|
|-
|living on twig, branch of / lived on twig, branch by
|
|-
|living on wash of / lived on wash by
|
|-
|living on wing of / lived on wing by
|
|-
|living under bark of / lived under bark by
|
|-
|living under bark of dead / lived under bark by
|
|-
|living under bark of fallen / lived under bark by
|
|-
|living under bark of living / lived under bark by
|
|-
|living under bark of rotten trunk of / lived under bark of rotten trunk by
|
|-
|living under chips of cut / lived under chips by
|
|-
|living with / living with
|
|-
|mother parasitic on / host of mother of
|
|-
|nest containing / in nest of
|
|-
|on abdomen of / abdomen containing
|
|-
|on aphid infested / aphid infested containing
|
|-
|on ball of / ball containing
|
|-
|on bark of / bark containing
|
|-
|on bark of dead / dead with bark containing
|
|-
|on bark of living / living with bark containing
|
|-
|on bloom of / bloom containing
|
|-
|on blossom of / blossom containing
|
|-
|on body of / body containing
|
|-
|on branch of / branch containing
|
|-
|on bulb of / bulb containing
|
|-
|on cadaver of / cadaver containing
|
|-
|on cone of / cone containing
|
|-
|on cone flower of / cone flower containing
|
|-
|on coppice of / coppice containing
|
|-
|on corrigated & crumpled leaf of dwarfed / (dwarfed) corrigated & crumpled leaf containing
|
|-
|on dead / dead containing
|
|-
|on dead branch of / dead branch containing
|
|-
|on dead leaf of / dead leaf containing
|
|-
|on dead limb of / dead limb containing
|
|-
|on dead limb or trunk of / dead limb or trunk containing
|
|-
|on dead or dying twig of / dead or dying twig containing
|
|-
|on dead remains of / upon dead remains by
|
|-
|on dead twig of / dead twig containing
|
|-
|on dead vine of / dead vine containing
|
|-
|on dead, standing / dead, standing containing
|
|-
|on decayed / decayed containing
|
|-
|on decayed log of / decayed log containing
|
|-
|on decayed stump of / decayed stump containing
|
|-
|on decaying of / decaying containing
|
|-
|on deep sear of living / living with deep sear containing
|
|-
|on dense growth of / dense growth containing
|
|-
|on dry / dry containing
|
|-
|on dry dung of / dry dung containing
|
|-
|on dung of / dung containing
|
|-
|on ear of / ear containing
|
|-
|on egg of / egg containing
|
|-
|on egg sac of / egg sac containing
|
|-
|on eye of / eye containing
|
|-
|on female adult of / female adult containing
|
|-
|on fire scorched of / fire scorched containing
|
|-
|on flower bud of / flower bud containing
|
|-
|on flower of / flower containing
|
|-
|on flower stalk of / flower stalk containing
|
|-
|on flowering / flowering containing
|
|-
|on flowerless / flowerless containing
|
|-
|on foliage of / foliage containing
|
|-
|on fresh wound of / fresh wound containing
|
|-
|on freshly cut / freshly cut containing
|
|-
|on frond of / frond containing
|
|-
|on fruit of / fruit containing
|
|-
|on fruiting / fruiting containing
|
|-
|on gills of / gills containing
|
|-
|on guano of / guano contaning
|
|-
|on heavily curled leaf of / heavily curled leaf containing
|
|-
|on inflorescence of / inflorescence containing
|
|-
|on lamina of / lamina containing
|
|-
|on large, hollow / large, hollow containing
|
|-
|on leaf axil of / leaf axil containing
|
|-
|on leaf of / leaf containing
|
|-
|on leaf petiole of / leaf petiole containing
|
|-
|on leaflet of / leaflet containing
|
|-
|on log of / log containing
|
|-
|on midrib of / midrib containing
|
|-
|on moldy, shelled / moldy, shelled containing
|
|-
|on needle of / needle containing
|
|-
|on or near / containing or near
|
|-
|on or near flowering / flowering containing or near
|
|-
|on or near flowers of / flowers containing or near
|
|-
|on overripe fruit of / overripe fruit containing
|
|-
|on paddy edge of / paddy edge containing
|
|-
|on paddy of / paddy containing
|
|-
|on pod of / pod containing
|
|-
|on rosette / rosette containing
|
|-
|on rotten / rotten containing
|
|-
|on rotten fruit of / rotten fruit containing
|
|-
|on rotten log of / rotten log containing
|
|-
|on rotting / rotting containing
|
|-
|on scrub / scrub containing
|
|-
|on seed of / seed containing
|
|-
|on seedling of / seedling containing
|
|-
|on short / short containing
|
|-
|on skin of / skin containing
|
|-
|on stalk of / stalk containing
|
|-
|on stem of / stem containing
|
|-
|on sticky seed of / sticky seed containing
|
|-
|on stomach of cadaver of / stomach of cadaver containing
|
|-
|on stored product of / stored product containing
|
|-
|on stump of / stump containing
|
|-
|on thorax of / thorax containing
|
|-
|on top of flower of / top of flower containing
|
|-
|on tree of / tree containing
|
|-
|on trunk of / trunk containing
|
|-
|on trunk of dead / dead with trunk containing
|
|-
|on trunk of dying / dying with trunk containing
|
|-
|on twig of / twig containing
|
|-
|on underside of frond of / underside of frond containing
|
|-
|on unflowered / unflowered containing
|
|-
|on vine of / vine containing
|
|-
|on wild of / wild containing
|
|-
|on wing of / wing containing
|
|-
|on wound of twig of / wound of twig containing
|
|-
|on young / young containing
|
|-
|ovipositing into bud of / host bud of
|
|-
|ovipositing into egg of / host egg of
|
|-
|ovipositing into gall of / host gall of
|
|-
|ovipositing into young sprout of / young sprout containing
|
|-
|paraphage on / host of
|
|-
|parasite of / host of
|
|-
|parasitic in ear of / host ear of
|
|-
|parasitic in nose of / host nose of
|
|-
|parasitic in skin of / host skin of
|
|-
|parasitic on abdomen of / host abdomen of
|
|-
|parasitic on body of / host body of
|
|-
|parasitic on branchial chamber of / host branchial chamber of
|
|-
|parasitic on cloaca of / host cloaca of
|
|-
|parasitic on coxa of / host coxa of
|
|-
|parasitic on ear of / host ear of
|
|-
|parasitic on egg of / host egg of
|
|-
|parasitic on eye of / host eye of
|
|-
|parasitic on genitalia of / host genitalia of
|
|-
|parasitic on gills of / host gills of
|
|-
|parasitic on hair follicle of / host hair follicle of
|
|-
|parasitic on hair of / host hair of
|
|-
|parasitic on head of / host head of
|
|-
|parasitic on hypodermis of / host hypodermis of
|
|-
|parasitic on larva of / host larva of
|
|-
|parasitic on limb of / host limb of
|
|-
|parasitic on lung of / host lung of
|
|-
|parasitic on mouth of / host mouth of
|
|-
|parasitic on nipple of / host nipple of
|
|-
|parasitic on nose of / host nose of
|
|-
|parasitic on pupa of / host pupa of
|
|-
|parasitic on quill feather (covert) of / host quill feather (covert) of
|
|-
|parasitic on quill feather (flight feather) of / host quill feather (flight feather) of
|
|-
|parasitic on quill feather (tail feather) of / host quill feather (tail feather) of
|
|-
|parasitic on quill feather of / host quill feather of
|
|-
|parasitic on sentinel egg of / host sentinel egg of
|
|-
|parasitic on shoot of / host shoot of
|
|-
|parasitic on skin of / host skin of
|
|-
|parasitic on stomach of / host stomach of
|
|-
|parasitic on tail of / host tail of
|
|-
|parasitic on thorax of / host thorax of
|
|-
|parasitic on trachea of / host trachea of
|
|-
|parasitic on wash of / host wash of
|
|-
|parasitic on wing of / host wing of
|
|-
|parasitic under elytra of / under elytral host of
|
|-
|parasitic under scales of / under scales host of
|
|-
|parasitoid of / host of
|
|-
|patolling on / patrolled by
|
|-
|phoretic on / host of
|
|-
|phoretic on abdomen of / host abdomen of
|
|-
|phoretic on alate / alate host of
|
|-
|phoretic on antenna of / host antenna of
|
|-
|phoretic on body of / host body of
|
|-
|phoretic on coxa of / host coxa of
|
|-
|phoretic on eye of / host eye of
|
|-
|phoretic on hair follicle of / host hair follicle of
|
|-
|phoretic on head of / host head of
|
|-
|phoretic on leg of / host leg of
|
|-
|phoretic on limb of / host limb of
|
|-
|phoretic on tail of / host tail of
|
|-
|phoretic on thorax of / host thorax of
|
|-
|phoretic on wing of / host wing of
|
|-
|phoretic under elytra of / under elytral host of
|
|-
|phoretic under supra-anal plate of / under supra-anal plate host of
|
|-
|pollinating / pollinated by
|
|-
|predator of / prey of
|
|-
|prey of / predator of
|
|-
|pupa of / adult of
|
|-
|recorded in background with / in background for recording of
|
|-
|solitary egg parasitoid of / host egg of
|
|-
|stinging neck of / neck being stung by
|
|-
|stomach parasite of / host stomach of
|
|-
|subcortically living in dead / dead subcortically living in by
|
|-
|subcutaneous parasite of / subcutaneous host of
|
|-
|subcutaneously living in / subcutaneously lived in by
|
|-
|tracheal parasite of / tracheal host of
|
|-
|under bark of / under bark by
|
|-
|under bark of dead / dead under bark by
|
|-
|under bark of dead or dying twig or branch / dead or dying twig or branch under bark by
|
|-
|under bark of freshly killed / freshly killed under bark by
|
|-
|under bark of log of / log under bark by
|
|-
|under bark of stump of / stump under bark by
|
|-
|under bark of trunk of dead / dead under bark of trunk by
|
|-
|under dead / under dead by
|
|-
|under dead stem of / under dead stem by
|
|-
|under dry dung of / under dry dung by
|
|-
|under dung of / under dung by
|
|-
|under loose bark of / under loose bark by
|
|-
|under manure (feces) of / under manure (feces) by
|
|-
|under rocks with / under rocks with
|
|-
|under seed of / under seed by
|
|-
|unspecified association / unspecified association
|
|-
|wing parasite of / host wing of
|
|-
|with eggs of / eggs with
|
|-
|with roots of / roots with
|
|}

[[Category:Data Entry Assistant]]
[[Category:xBio:D Controlled Vocabularies]]

Biological Association Type Terms

2016-03-25T17:18:48Z

Matte: /* Biological Association Type Terms */

'''Introduction'''

This section contains information on the available biological association terms that are currently available in the xBio:D system. Biological associations within xBio:D represents a two-way relationship between the first organism and the second, and the association type is separated by a slash (/). For example, if you want to show a parasitoid-host relationship in which the specimen record you have is for the parasitoid (A) and the unvouchered associate (B) is its host, the association type ''emerged from egg of / host egg of'' would be read ''parasitoid (A) emerged from host (B)'' and conversely ''host (B) is a host egg of parasitoid (A)''. If you would like another biological association term added into xBio:D, please contact [mailto:cora.1@osu.edu Joe Cora] and request the addition.

== Biological Association Type Terms ==
{|
!Association Type
!Description
|-
|adult of / pupa of
|
|-
|among pieces of fallen nest of / fallen nest pieces contained
|
|-
|at base of large / large with base containing
|
|-
|between leaves of / leaves containing
|
|-
|burrowing into / contains burrowing
|
|-
|buzz pollinating / buzz pollinated by
|
|-
|collected in / contains
|
|-
|collected in drilled / drilled collecting site of
|
|-
|collected near / living near
|
|-
|collected near eggs / eggs present near
|
|-
|collected near flowering / flowering living near
|
|-
|collected near gall / gall present near
|
|-
|collected near nymph of / nymph present near
|
|-
|collected near stand of / stand present near
|
|-
|collected on / collecting site of
|
|-
|collected under / collecting site above
|
|-
|collected with / used to collect
|
|-
|collected with dung of / dung used to collect
|
|-
|collected with pheromone of / pheromone used to collect
|
|-
|collected with rotting / rotting used to collect
|
|-
|collection site of / collected on
|
|-
|egg ectoparasite of / host egg of
|
|-
|egg parasite of / host egg of
|
|-
|egg predator of / prey egg of
|
|-
|emerged from / produced
|
|-
|emerged from cocoon of / host cocoon of
|
|-
|emerged from decayed / decayed host of
|
|-
|emerged from diapausing eggs of / diapausing host eggs of
|
|-
|emerged from egg of / host egg of
|
|-
|emerged from egg sac of / host egg sac of
|
|-
|emerged from freshly killed / freshly killed host of
|
|-
|emerged from fruit of / host fruit of
|
|-
|emerged from gall of / host gall of
|
|-
|emerged from immature of / host immature of
|
|-
|emerged from larva of / host larva of
|
|-
|emerged from leaf gall of / host leaf gall of
|
|-
|emerged from leaf mine of / leaf mine containing
|
|-
|emerged from leaf mine on / leaf mine containing
|
|-
|emerged from leaf of / host leaf of
|
|-
|emerged from mossy gall of / host mossy gall of
|
|-
|emerged from mummy of / host mummy of
|
|-
|emerged from nest of / host nest of
|
|-
|emerged from nymph of / host nymph of
|
|-
|emerged from ootheca of / host ootheca of
|
|-
|emerged from pod of / host pod of
|
|-
|emerged from pole of / host pole containing
|
|-
|emerged from pupa of / host pupa of
|
|-
|emerged from pupal chamber of / host pupal chamber of
|
|-
|emerged from puparium of / host puparium of
|
|-
|emerged from root crown of / host root crown of
|
|-
|emerged from root gall of / host root gall of
|
|-
|emerged from seed of / host seed of
|
|-
|emerged from sentinel egg mass of / host sentinel egg mass of
|
|-
|emerged from spongy leaf gall of / host spongy leaf gall of
|
|-
|emerged from stem gall of / host stem gall of
|
|-
|emerged from tunnel of / host tunnel of
|
|-
|emerged from twig of / host twig of
|
|-
|fed upon by / feeding on
|
|-
|feeding on / fed upon by
|
|-
|feeding on bark of / fed upon bark by
|
|-
|feeding on bud, shoot of / fed upon bud, shoot by
|
|-
|feeding on bulb of / fed upon bulb by
|
|-
|feeding on egg of / fed on egg by
|
|-
|feeding on flower of / fed on flower by
|
|-
|feeding on fruit, nut, seed of / fed on fruit, nut, seed by
|
|-
|feeding on gall of / fed on gall by
|
|-
|feeding on leaf gall of / fed upon leaf gall by
|
|-
|feeding on leaf of / fed upon leaf by
|
|-
|feeding on root of / fed upon root by
|
|-
|feeding on shoot of / fed upon shoot by
|
|-
|feeding on silk and end of ear of / fed upon silk and end of ear by
|
|-
|feeding on stem of / fed upon stem by
|
|-
|feeding on tree trunk of / fed upon tree trunk by
|
|-
|feeding on twig, branch of / fed upon twig, branch by
|
|-
|flying after / flying from
|
|-
|gregarious egg parasitoid of / host egg of
|
|-
|host egg of / emerged from egg of
|
|-
|host egg of / solitary egg parasitoid of
|
|-
|host larva of / larval parasitoid of
|
|-
|host of / parasite of
|
|-
|hyperparasite of / host of
|
|-
|in abandoned nest of / abandoned nest containing
|
|-
|in artificial colony of / artificial colony containing
|
|-
|in bark crack of / bark crack containing
|
|-
|in burrow of / burrow containing
|
|-
|in buttress of / buttress containing
|
|-
|in canopy of / canopy containing
|
|-
|in catface of living / living with catface containing
|
|-
|in center of rotten / rotten center containing
|
|-
|in clump of / clump containing
|
|-
|in cocoon of / cocoon containing
|
|-
|in colony of / colony containing
|
|-
|in culture of / culture containing
|
|-
|in dead log of / dead log containing
|
|-
|in decaying / decayed containing
|
|-
|in decaying bark of / decayed bark containing
|
|-
|in decaying fruit, nut, seed of / decayed fruit, nut, seed containing
|
|-
|in decaying log of / decayed log containing
|
|-
|in decaying mulch of / decayed mulch containing
|
|-
|in decaying root of / decayed root containing
|
|-
|in decaying tree stump of / decayed tree stump containing
|
|-
|in duff of / duff containing
|
|-
|in dunnage of / dunnage containing
|
|-
|in fallen of / fallen containing
|
|-
|in field with / in field with
|
|-
|in flower head of / flower head containing
|
|-
|in gall of / gall containing
|
|-
|in gall of flowering / flowering with gall containing
|
|-
|in galleries of / galleries containing
|
|-
|in leaf nest of / leaf nest containing
|
|-
|in leaf sheath of / leaf sheath containing
|
|-
|in litter of / litter containing
|
|-
|in litter of treehole of / litter of treehole containing
|
|-
|in litter under log of / litter under log containing
|
|-
|in litter with / in litter with
|
|-
|in log of / log containing
|
|-
|in log with / in log with
|
|-
|in manure (feces) of / manure (feces) containing
|
|-
|in mine of / mine containing
|
|-
|in moist decayed log of / moist decayed log containing
|
|-
|in nest of / nest containing
|
|-
|in nest on body of / body in nest containing
|
|-
|in nest with dead chick of / dead chick within nest with
|
|-
|in nest within / containing nest with
|
|-
|in nose of / nose containing
|
|-
|in paneling of / paneling containing
|
|-
|in petiole of / petiole containing
|
|-
|in roast of / roast containing
|
|-
|in roost of / roost containing
|
|-
|in root / root containing
|
|-
|in rotten / rotten containing
|
|-
|in rotten stump of / rotten stump containing
|
|-
|in scat of / scat containing
|
|-
|in shell of / shell containing
|
|-
|in silk tube of / silk tube containing
|
|-
|in soil with / in soil with
|
|-
|in soil with bulb of / bulb in soil with
|
|-
|in soil with root of / root in soil with
|
|-
|in square of / square containing
|
|-
|in stable with / stable containing
|
|-
|in stand of / stand containing
|
|-
|in stem of / stem containing
|
|-
|in stem gall of / stem gall containing
|
|-
|in stomach of / stomach containing
|
|-
|in straw of / straw containing
|
|-
|in stubble of / stubble containing
|
|-
|in subterranean dump of / subterranean dump containing
|
|-
|in thicket of / thicket containing
|
|-
|in treehole of / treehole containing
|
|-
|in trunk of / trunk containing
|
|-
|in tunnel of / tunnel containing
|
|-
|in vein on underside of leaf of / vein on under of leaf containing
|
|-
|in water with / in water with
|
|-
|in web of / web containing
|
|-
|in young leaf of / young leaf containing
|
|-
|infected by / infecting
|
|-
|inhabits / habitat for
|
|-
|internal parasite of / internal host of
|
|-
|larval parasite of / host larva of
|
|-
|larval parasitoid of / host larva of
|
|-
|larval predator of / prey larva of
|
|-
|living in / lived in by
|
|-
|living in colon of / lived within colon by
|
|-
|living in hypodermis of / lived within hypodermis by
|
|-
|living in pitcher of / lived within pitcher by
|
|-
|living in synovial fluid of / lived within synovial fluid by
|
|-
|living in treehole of / lived within treehole by
|
|-
|living on / lived on by
|
|-
|living on bark of / lived on bark by
|
|-
|living on body of / lived on body by
|
|-
|living on branch of / lived on branch by
|
|-
|living on bud of / lived on bud by
|
|-
|living on bulb of / lived on bulb by
|
|-
|living on feather of / lived on feather by
|
|-
|living on flower of / lived on flower by
|
|-
|living on fruit, nut, seed of / lived on fruit, nut, seed by
|
|-
|living on hair follicle of / lived on hair follicle by
|
|-
|living on hair of / lived on hair by
|
|-
|living on head of / lived on head by
|
|-
|living on leaf of / lived on leaf by
|
|-
|living on log of / lived on log by
|
|-
|living on male cone of / lived on male cone by
|
|-
|living on mosaic infected / (mosaic infected) lived on by
|
|-
|living on nut, seed of / lived on nut, seed by
|
|-
|living on pupa of / lived on pupa by
|
|-
|living on root of / lived on root by
|
|-
|living on sapflow of / lived on sapflow by
|
|-
|living on seed of / lived on seed by
|
|-
|living on shoot of / lived on shoot by
|
|-
|living on stem of / lived on stem by
|
|-
|living on tail of / lived on tail by
|
|-
|living on tree trunk of / lived on tree trunk by
|
|-
|living on twig, branch of / lived on twig, branch by
|
|-
|living on wash of / lived on wash by
|
|-
|living on wing of / lived on wing by
|
|-
|living under bark of / lived under bark by
|
|-
|living under bark of dead / lived under bark by
|
|-
|living under bark of fallen / lived under bark by
|
|-
|living under bark of living / lived under bark by
|
|-
|living under bark of rotten trunk of / lived under bark of rotten trunk by
|
|-
|living under chips of cut / lived under chips by
|
|-
|living with / living with
|
|-
|mother parasitic on / host of mother of
|
|-
|nest containing / in nest of
|
|-
|on abdomen of / abdomen containing
|
|-
|on aphid infested / aphid infested containing
|
|-
|on ball of / ball containing
|
|-
|on bark of / bark containing
|
|-
|on bark of dead / dead with bark containing
|
|-
|on bark of living / living with bark containing
|
|-
|on bloom of / bloom containing
|
|-
|on blossom of / blossom containing
|
|-
|on body of / body containing
|
|-
|on branch of / branch containing
|
|-
|on bulb of / bulb containing
|
|-
|on cadaver of / cadaver containing
|
|-
|on cone of / cone containing
|
|-
|on cone flower of / cone flower containing
|
|-
|on coppice of / coppice containing
|
|-
|on corrigated & crumpled leaf of dwarfed / (dwarfed) corrigated & crumpled leaf containing
|
|-
|on dead / dead containing
|
|-
|on dead branch of / dead branch containing
|
|-
|on dead leaf of / dead leaf containing
|
|-
|on dead limb of / dead limb containing
|
|-
|on dead limb or trunk of / dead limb or trunk containing
|
|-
|on dead or dying twig of / dead or dying twig containing
|
|-
|on dead remains of / upon dead remains by
|
|-
|on dead twig of / dead twig containing
|
|-
|on dead vine of / dead vine containing
|
|-
|on dead, standing / dead, standing containing
|
|-
|on decayed / decayed containing
|
|-
|on decayed log of / decayed log containing
|
|-
|on decayed stump of / decayed stump containing
|
|-
|on decaying of / decaying containing
|
|-
|on deep sear of living / living with deep sear containing
|
|-
|on dense growth of / dense growth containing
|
|-
|on dry / dry containing
|
|-
|on dry dung of / dry dung containing
|
|-
|on dung of / dung containing
|
|-
|on ear of / ear containing
|
|-
|on egg of / egg containing
|
|-
|on egg sac of / egg sac containing
|
|-
|on eye of / eye containing
|
|-
|on female adult of / female adult containing
|
|-
|on fire scorched of / fire scorched containing
|
|-
|on flower bud of / flower bud containing
|
|-
|on flower of / flower containing
|
|-
|on flower stalk of / flower stalk containing
|
|-
|on flowering / flowering containing
|
|-
|on flowerless / flowerless containing
|
|-
|on foliage of / foliage containing
|
|-
|on fresh wound of / fresh wound containing
|
|-
|on freshly cut / freshly cut containing
|
|-
|on frond of / frond containing
|
|-
|on fruit of / fruit containing
|
|-
|on fruiting / fruiting containing
|
|-
|on gills of / gills containing
|
|-
|on guano of / guano contaning
|
|-
|on heavily curled leaf of / heavily curled leaf containing
|
|-
|on inflorescence of / inflorescence containing
|
|-
|on lamina of / lamina containing
|
|-
|on large, hollow / large, hollow containing
|
|-
|on leaf axil of / leaf axil containing
|
|-
|on leaf of / leaf containing
|
|-
|on leaf petiole of / leaf petiole containing
|
|-
|on leaflet of / leaflet containing
|
|-
|on log of / log containing
|
|-
|on midrib of / midrib containing
|
|-
|on moldy, shelled / moldy, shelled containing
|
|-
|on needle of / needle containing
|
|-
|on or near / containing or near
|
|-
|on or near flowering / flowering containing or near
|
|-
|on or near flowers of / flowers containing or near
|
|-
|on overripe fruit of / overripe fruit containing
|
|-
|on paddy edge of / paddy edge containing
|
|-
|on paddy of / paddy containing
|
|-
|on pod of / pod containing
|
|-
|on rosette / rosette containing
|
|-
|on rotten / rotten containing
|
|-
|on rotten fruit of / rotten fruit containing
|
|-
|on rotten log of / rotten log containing
|
|-
|on rotting / rotting containing
|
|-
|on scrub / scrub containing
|
|-
|on seed of / seed containing
|
|-
|on seedling of / seedling containing
|
|-
|on short / short containing
|
|-
|on skin of / skin containing
|
|-
|on stalk of / stalk containing
|
|-
|on stem of / stem containing
|
|-
|on sticky seed of / sticky seed containing
|
|-
|on stomach of cadaver of / stomach of cadaver containing
|
|-
|on stored product of / stored product containing
|
|-
|on stump of / stump containing
|
|-
|on thorax of / thorax containing
|
|-
|on top of flower of / top of flower containing
|
|-
|on tree of / tree containing
|
|-
|on trunk of / trunk containing
|
|-
|on trunk of dead / dead with trunk containing
|
|-
|on trunk of dying / dying with trunk containing
|
|-
|on twig of / twig containing
|
|-
|on underside of frond of / underside of frond containing
|
|-
|on unflowered / unflowered containing
|
|-
|on vine of / vine containing
|
|-
|on wild of / wild containing
|
|-
|on wing of / wing containing
|
|-
|on wound of twig of / wound of twig containing
|
|-
|on young / young containing
|
|-
|ovipositing into bud of / host bud of
|
|-
|ovipositing into egg of / host egg of
|
|-
|ovipositing into gall of / host gall of
|
|-
|ovipositing into young sprout of / young sprout containing
|
|-
|paraphage on / host of
|
|-
|parasite of / host of
|
|-
|parasitic in ear of / host ear of
|
|-
|parasitic in nose of / host nose of
|
|-
|parasitic in skin of / host skin of
|
|-
|parasitic on abdomen of / host abdomen of
|
|-
|parasitic on body of / host body of
|
|-
|parasitic on branchial chamber of / host branchial chamber of
|
|-
|parasitic on cloaca of / host cloaca of
|
|-
|parasitic on coxa of / host coxa of
|
|-
|parasitic on ear of / host ear of
|
|-
|parasitic on egg of / host egg of
|
|-
|parasitic on eye of / host eye of
|
|-
|parasitic on genitalia of / host genitalia of
|
|-
|parasitic on gills of / host gills of
|
|-
|parasitic on hair follicle of / host hair follicle of
|
|-
|parasitic on hair of / host hair of
|
|-
|parasitic on head of / host head of
|
|-
|parasitic on hypodermis of / host hypodermis of
|
|-
|parasitic on larva of / host larva of
|
|-
|parasitic on limb of / host limb of
|
|-
|parasitic on lung of / host lung of
|
|-
|parasitic on mouth of / host mouth of
|
|-
|parasitic on nipple of / host nipple of
|
|-
|parasitic on nose of / host nose of
|
|-
|parasitic on pupa of / host pupa of
|
|-
|parasitic on quill feather (covert) of / host quill feather (covert) of
|
|-
|parasitic on quill feather (flight feather) of / host quill feather (flight feather) of
|
|-
|parasitic on quill feather (tail feather) of / host quill feather (tail feather) of
|
|-
|parasitic on quill feather of / host quill feather of
|
|-
|parasitic on sentinel egg of / host sentinel egg of
|
|-
|parasitic on shoot of / host shoot of
|
|-
|parasitic on skin of / host skin of
|
|-
|parasitic on stomach of / host stomach of
|
|-
|parasitic on tail of / host tail of
|
|-
|parasitic on thorax of / host thorax of
|
|-
|parasitic on trachea of / host trachea of
|
|-
|parasitic on wash of / host wash of
|
|-
|parasitic on wing of / host wing of
|
|-
|parasitic under elytra of / under elytral host of
|
|-
|parasitic under scales of / under scales host of
|
|-
|parasitoid of / host of
|
|-
|patolling on / patrolled by
|
|-
|phoretic on / host of
|
|-
|phoretic on abdomen of / host abdomen of
|
|-
|phoretic on alate / alate host of
|
|-
|phoretic on antenna of / host antenna of
|
|-
|phoretic on body of / host body of
|
|-
|phoretic on coxa of / host coxa of
|
|-
|phoretic on eye of / host eye of
|
|-
|phoretic on hair follicle of / host hair follicle of
|
|-
|phoretic on head of / host head of
|
|-
|phoretic on leg of / host leg of
|
|-
|phoretic on limb of / host limb of
|
|-
|phoretic on tail of / host tail of
|
|-
|phoretic on thorax of / host thorax of
|
|-
|phoretic on wing of / host wing of
|
|-
|phoretic under elytra of / under elytral host of
|
|-
|phoretic under supra-anal plate of / under supra-anal plate host of
|
|-
|pollinating / pollinated by
|
|-
|predator of / prey of
|
|-
|prey of / predator of
|
|-
|pupa of / adult of
|
|-
|recorded in background with / in background for recording of
|
|-
|solitary egg parasitoid of / host egg of
|
|-
|stinging neck of / neck being stung by
|
|-
|stomach parasite of / host stomach of
|
|-
|subcortically living in dead / dead subcortically living in by
|
|-
|subcutaneous parasite of / subcutaneous host of
|
|-
|subcutaneously living in / subcutaneously lived in by
|
|-
|tracheal parasite of / tracheal host of
|
|-
|under bark of / under bark by
|
|-
|under bark of dead / dead under bark by
|
|-
|under bark of dead or dying twig or branch / dead or dying twig or branch under bark by
|
|-
|under bark of freshly killed / freshly killed under bark by
|
|-
|under bark of log of / log under bark by
|
|-
|under bark of stump of / stump under bark by
|
|-
|under bark of trunk of dead / dead under bark of trunk by
|
|-
|under dead / under dead by
|
|-
|under dead stem of / under dead stem by
|
|-
|under dry dung of / under dry dung by
|
|-
|under loose bark of / under loose bark by
|
|-
|under manure (feces) of / under manure (feces) by
|
|-
|under rocks with / under rocks with
|
|-
|under seed of / under seed by
|
|-
|unspecified association / unspecified association
|
|-
|wing parasite of / host wing of
|
|-
|with eggs of / eggs with
|
|-
|with roots of / roots with
|
|}

[[Category:Data Entry Assistant]]
[[Category:xBio:D Controlled Vocabularies]]

Biological Association Type Terms

2016-03-23T12:45:04Z

Matte: /* Biological Association Type Terms */

'''Introduction'''

This section contains information on the available biological association terms that are currently available in the xBio:D system. Biological associations within xBio:D represents a two-way relationship between the first organism and the second, and the association type is separated by a slash (/). For example, if you want to show a parasitoid-host relationship in which the specimen record you have is for the parasitoid (A) and the unvouchered associate (B) is its host, the association type ''emerged from egg of / host egg of'' would be read ''parasitoid (A) emerged from host (B)'' and conversely ''host (B) is a host egg of parasitoid (A)''. If you would like another biological association term added into xBio:D, please contact [mailto:cora.1@osu.edu Joe Cora] and request the addition.

== Biological Association Type Terms ==
{|
!Association Type
!Description
|-
|adult of / pupa of
|
|-
|among pieces of fallen nest of / fallen nest pieces contained
|
|-
|at base of large / large with base containing
|
|-
|between leaves of / leaves containing
|
|-
|burrowing into / contains burrowing
|
|-
|buzz pollinating / buzz pollinated by
|
|-
|collected in / contains
|
|-
|collected in drilled / drilled collecting site of
|
|-
|collected near / living near
|
|-
|collected near eggs / eggs present near
|
|-
|collected near flowering / flowering living near
|
|-
|collected near gall / gall present near
|
|-
|collected near nymph of / nymph present near
|
|-
|collected near stand of / stand present near
|
|-
|collected on / collecting site of
|
|-
|collected under / collecting site above
|
|-
|collected with / used to collect
|
|-
|collected with dung of / dung used to collect
|
|-
|collected with pheromone of / pheromone used to collect
|
|-
|collected with rotting / rotting used to collect
|
|-
|collection site of / collected on
|
|-
|egg ectoparasite of / host egg of
|
|-
|egg parasite of / host egg of
|
|-
|egg predator of / prey egg of
|
|-
|emerged from / produced
|
|-
|emerged from cocoon of / host cocoon of
|
|-
|emerged from diapausing eggs of / diapausing host eggs of
|
|-
|emerged from egg of / host egg of
|
|-
|emerged from egg sac of / host egg sac of
|
|-
|emerged from freshly killed / freshly killed host of
|
|-
|emerged from fruit of / host fruit of
|
|-
|emerged from gall of / host gall of
|
|-
|emerged from immature of / host immature of
|
|-
|emerged from larva of / host larva of
|
|-
|emerged from leaf gall of / host leaf gall of
|
|-
|emerged from leaf mine of / leaf mine containing
|
|-
|emerged from leaf mine on / leaf mine containing
|
|-
|emerged from leaf of / host leaf of
|
|-
|emerged from mossy gall of / host mossy gall of
|
|-
|emerged from mummy of / host mummy of
|
|-
|emerged from nest of / host nest of
|
|-
|emerged from nymph of / host nymph of
|
|-
|emerged from ootheca of / host ootheca of
|
|-
|emerged from pod of / host pod of
|
|-
|emerged from pole of / host pole containing
|
|-
|emerged from pupa of / host pupa of
|
|-
|emerged from pupal chamber of / host pupal chamber of
|
|-
|emerged from puparium of / host puparium of
|
|-
|emerged from root crown of / host root crown of
|
|-
|emerged from root gall of / host root gall of
|
|-
|emerged from seed of / host seed of
|
|-
|emerged from sentinel egg mass of / host sentinel egg mass of
|
|-
|emerged from spongy leaf gall of / host spongy leaf gall of
|
|-
|emerged from stem gall of / host stem gall of
|
|-
|emerged from tunnel of / host tunnel of
|
|-
|emerged from twig of / host twig of
|
|-
|fed upon by / feeding on
|
|-
|feeding on / fed upon by
|
|-
|feeding on bark of / fed upon bark by
|
|-
|feeding on bud, shoot of / fed upon bud, shoot by
|
|-
|feeding on bulb of / fed upon bulb by
|
|-
|feeding on egg of / fed on egg by
|
|-
|feeding on flower of / fed on flower by
|
|-
|feeding on fruit, nut, seed of / fed on fruit, nut, seed by
|
|-
|feeding on gall of / fed on gall by
|
|-
|feeding on leaf gall of / fed upon leaf gall by
|
|-
|feeding on leaf of / fed upon leaf by
|
|-
|feeding on root of / fed upon root by
|
|-
|feeding on shoot of / fed upon shoot by
|
|-
|feeding on silk and end of ear of / fed upon silk and end of ear by
|
|-
|feeding on stem of / fed upon stem by
|
|-
|feeding on tree trunk of / fed upon tree trunk by
|
|-
|feeding on twig, branch of / fed upon twig, branch by
|
|-
|flying after / flying from
|
|-
|gregarious egg parasitoid of / host egg of
|
|-
|host egg of / emerged from egg of
|
|-
|host egg of / solitary egg parasitoid of
|
|-
|host larva of / larval parasitoid of
|
|-
|host of / parasite of
|
|-
|hyperparasite of / host of
|
|-
|in abandoned nest of / abandoned nest containing
|
|-
|in artificial colony of / artificial colony containing
|
|-
|in bark crack of / bark crack containing
|
|-
|in burrow of / burrow containing
|
|-
|in buttress of / buttress containing
|
|-
|in canopy of / canopy containing
|
|-
|in catface of living / living with catface containing
|
|-
|in center of rotten / rotten center containing
|
|-
|in clump of / clump containing
|
|-
|in cocoon of / cocoon containing
|
|-
|in colony of / colony containing
|
|-
|in culture of / culture containing
|
|-
|in dead log of / dead log containing
|
|-
|in decaying / decayed containing
|
|-
|in decaying bark of / decayed bark containing
|
|-
|in decaying fruit, nut, seed of / decayed fruit, nut, seed containing
|
|-
|in decaying log of / decayed log containing
|
|-
|in decaying mulch of / decayed mulch containing
|
|-
|in decaying root of / decayed root containing
|
|-
|in decaying tree stump of / decayed tree stump containing
|
|-
|in duff of / duff containing
|
|-
|in dunnage of / dunnage containing
|
|-
|in fallen of / fallen containing
|
|-
|in field with / in field with
|
|-
|in flower head of / flower head containing
|
|-
|in gall of / gall containing
|
|-
|in gall of flowering / flowering with gall containing
|
|-
|in galleries of / galleries containing
|
|-
|in leaf nest of / leaf nest containing
|
|-
|in leaf sheath of / leaf sheath containing
|
|-
|in litter of / litter containing
|
|-
|in litter of treehole of / litter of treehole containing
|
|-
|in litter under log of / litter under log containing
|
|-
|in litter with / in litter with
|
|-
|in log of / log containing
|
|-
|in log with / in log with
|
|-
|in manure (feces) of / manure (feces) containing
|
|-
|in mine of / mine containing
|
|-
|in moist decayed log of / moist decayed log containing
|
|-
|in nest of / nest containing
|
|-
|in nest on body of / body in nest containing
|
|-
|in nest with dead chick of / dead chick within nest with
|
|-
|in nest within / containing nest with
|
|-
|in nose of / nose containing
|
|-
|in paneling of / paneling containing
|
|-
|in petiole of / petiole containing
|
|-
|in roast of / roast containing
|
|-
|in roost of / roost containing
|
|-
|in root / root containing
|
|-
|in rotten / rotten containing
|
|-
|in rotten stump of / rotten stump containing
|
|-
|in scat of / scat containing
|
|-
|in shell of / shell containing
|
|-
|in silk tube of / silk tube containing
|
|-
|in soil with / in soil with
|
|-
|in soil with bulb of / bulb in soil with
|
|-
|in soil with root of / root in soil with
|
|-
|in square of / square containing
|
|-
|in stable with / stable containing
|
|-
|in stand of / stand containing
|
|-
|in stem of / stem containing
|
|-
|in stem gall of / stem gall containing
|
|-
|in stomach of / stomach containing
|
|-
|in straw of / straw containing
|
|-
|in stubble of / stubble containing
|
|-
|in subterranean dump of / subterranean dump containing
|
|-
|in thicket of / thicket containing
|
|-
|in treehole of / treehole containing
|
|-
|in trunk of / trunk containing
|
|-
|in tunnel of / tunnel containing
|
|-
|in vein on underside of leaf of / vein on under of leaf containing
|
|-
|in water with / in water with
|
|-
|in web of / web containing
|
|-
|in young leaf of / young leaf containing
|
|-
|infected by / infecting
|
|-
|inhabits / habitat for
|
|-
|internal parasite of / internal host of
|
|-
|larval parasite of / host larva of
|
|-
|larval parasitoid of / host larva of
|
|-
|larval predator of / prey larva of
|
|-
|living in / lived in by
|
|-
|living in colon of / lived within colon by
|
|-
|living in hypodermis of / lived within hypodermis by
|
|-
|living in pitcher of / lived within pitcher by
|
|-
|living in synovial fluid of / lived within synovial fluid by
|
|-
|living in treehole of / lived within treehole by
|
|-
|living on / lived on by
|
|-
|living on bark of / lived on bark by
|
|-
|living on body of / lived on body by
|
|-
|living on branch of / lived on branch by
|
|-
|living on bud of / lived on bud by
|
|-
|living on bulb of / lived on bulb by
|
|-
|living on feather of / lived on feather by
|
|-
|living on flower of / lived on flower by
|
|-
|living on fruit, nut, seed of / lived on fruit, nut, seed by
|
|-
|living on hair follicle of / lived on hair follicle by
|
|-
|living on hair of / lived on hair by
|
|-
|living on head of / lived on head by
|
|-
|living on leaf of / lived on leaf by
|
|-
|living on log of / lived on log by
|
|-
|living on male cone of / lived on male cone by
|
|-
|living on mosaic infected / (mosaic infected) lived on by
|
|-
|living on nut, seed of / lived on nut, seed by
|
|-
|living on pupa of / lived on pupa by
|
|-
|living on root of / lived on root by
|
|-
|living on sapflow of / lived on sapflow by
|
|-
|living on seed of / lived on seed by
|
|-
|living on shoot of / lived on shoot by
|
|-
|living on stem of / lived on stem by
|
|-
|living on tail of / lived on tail by
|
|-
|living on tree trunk of / lived on tree trunk by
|
|-
|living on twig, branch of / lived on twig, branch by
|
|-
|living on wash of / lived on wash by
|
|-
|living on wing of / lived on wing by
|
|-
|living under bark of / lived under bark by
|
|-
|living under bark of dead / lived under bark by
|
|-
|living under bark of fallen / lived under bark by
|
|-
|living under bark of living / lived under bark by
|
|-
|living under bark of rotten trunk of / lived under bark of rotten trunk by
|
|-
|living under chips of cut / lived under chips by
|
|-
|living with / living with
|
|-
|mother parasitic on / host of mother of
|
|-
|nest containing / in nest of
|
|-
|on abdomen of / abdomen containing
|
|-
|on aphid infested / aphid infested containing
|
|-
|on ball of / ball containing
|
|-
|on bark of / bark containing
|
|-
|on bark of dead / dead with bark containing
|
|-
|on bark of living / living with bark containing
|
|-
|on bloom of / bloom containing
|
|-
|on blossom of / blossom containing
|
|-
|on body of / body containing
|
|-
|on branch of / branch containing
|
|-
|on bulb of / bulb containing
|
|-
|on cadaver of / cadaver containing
|
|-
|on cone of / cone containing
|
|-
|on cone flower of / cone flower containing
|
|-
|on coppice of / coppice containing
|
|-
|on corrigated & crumpled leaf of dwarfed / (dwarfed) corrigated & crumpled leaf containing
|
|-
|on dead / dead containing
|
|-
|on dead branch of / dead branch containing
|
|-
|on dead leaf of / dead leaf containing
|
|-
|on dead limb of / dead limb containing
|
|-
|on dead limb or trunk of / dead limb or trunk containing
|
|-
|on dead or dying twig of / dead or dying twig containing
|
|-
|on dead remains of / upon dead remains by
|
|-
|on dead twig of / dead twig containing
|
|-
|on dead vine of / dead vine containing
|
|-
|on dead, standing / dead, standing containing
|
|-
|on decayed / decayed containing
|
|-
|on decayed log of / decayed log containing
|
|-
|on decayed stump of / decayed stump containing
|
|-
|on decaying of / decaying containing
|
|-
|on deep sear of living / living with deep sear containing
|
|-
|on dense growth of / dense growth containing
|
|-
|on dry / dry containing
|
|-
|on dry dung of / dry dung containing
|
|-
|on dung of / dung containing
|
|-
|on ear of / ear containing
|
|-
|on egg of / egg containing
|
|-
|on egg sac of / egg sac containing
|
|-
|on eye of / eye containing
|
|-
|on female adult of / female adult containing
|
|-
|on fire scorched of / fire scorched containing
|
|-
|on flower bud of / flower bud containing
|
|-
|on flower of / flower containing
|
|-
|on flower stalk of / flower stalk containing
|
|-
|on flowering / flowering containing
|
|-
|on flowerless / flowerless containing
|
|-
|on foliage of / foliage containing
|
|-
|on fresh wound of / fresh wound containing
|
|-
|on freshly cut / freshly cut containing
|
|-
|on frond of / frond containing
|
|-
|on fruit of / fruit containing
|
|-
|on fruiting / fruiting containing
|
|-
|on gills of / gills containing
|
|-
|on guano of / guano contaning
|
|-
|on heavily curled leaf of / heavily curled leaf containing
|
|-
|on inflorescence of / inflorescence containing
|
|-
|on lamina of / lamina containing
|
|-
|on large, hollow / large, hollow containing
|
|-
|on leaf axil of / leaf axil containing
|
|-
|on leaf of / leaf containing
|
|-
|on leaf petiole of / leaf petiole containing
|
|-
|on leaflet of / leaflet containing
|
|-
|on log of / log containing
|
|-
|on midrib of / midrib containing
|
|-
|on moldy, shelled / moldy, shelled containing
|
|-
|on needle of / needle containing
|
|-
|on or near / containing or near
|
|-
|on or near flowering / flowering containing or near
|
|-
|on or near flowers of / flowers containing or near
|
|-
|on overripe fruit of / overripe fruit containing
|
|-
|on paddy edge of / paddy edge containing
|
|-
|on paddy of / paddy containing
|
|-
|on pod of / pod containing
|
|-
|on rosette / rosette containing
|
|-
|on rotten / rotten containing
|
|-
|on rotten fruit of / rotten fruit containing
|
|-
|on rotten log of / rotten log containing
|
|-
|on rotting / rotting containing
|
|-
|on scrub / scrub containing
|
|-
|on seed of / seed containing
|
|-
|on seedling of / seedling containing
|
|-
|on short / short containing
|
|-
|on skin of / skin containing
|
|-
|on stalk of / stalk containing
|
|-
|on stem of / stem containing
|
|-
|on sticky seed of / sticky seed containing
|
|-
|on stomach of cadaver of / stomach of cadaver containing
|
|-
|on stored product of / stored product containing
|
|-
|on stump of / stump containing
|
|-
|on thorax of / thorax containing
|
|-
|on top of flower of / top of flower containing
|
|-
|on tree of / tree containing
|
|-
|on trunk of / trunk containing
|
|-
|on trunk of dead / dead with trunk containing
|
|-
|on trunk of dying / dying with trunk containing
|
|-
|on twig of / twig containing
|
|-
|on underside of frond of / underside of frond containing
|
|-
|on unflowered / unflowered containing
|
|-
|on vine of / vine containing
|
|-
|on wild of / wild containing
|
|-
|on wing of / wing containing
|
|-
|on wound of twig of / wound of twig containing
|
|-
|on young / young containing
|
|-
|ovipositing into bud of / host bud of
|
|-
|ovipositing into egg of / host egg of
|
|-
|ovipositing into gall of / host gall of
|
|-
|ovipositing into young sprout of / young sprout containing
|
|-
|paraphage on / host of
|
|-
|parasite of / host of
|
|-
|parasitic in ear of / host ear of
|
|-
|parasitic in nose of / host nose of
|
|-
|parasitic in skin of / host skin of
|
|-
|parasitic on abdomen of / host abdomen of
|
|-
|parasitic on body of / host body of
|
|-
|parasitic on branchial chamber of / host branchial chamber of
|
|-
|parasitic on cloaca of / host cloaca of
|
|-
|parasitic on coxa of / host coxa of
|
|-
|parasitic on ear of / host ear of
|
|-
|parasitic on egg of / host egg of
|
|-
|parasitic on eye of / host eye of
|
|-
|parasitic on genitalia of / host genitalia of
|
|-
|parasitic on gills of / host gills of
|
|-
|parasitic on hair follicle of / host hair follicle of
|
|-
|parasitic on hair of / host hair of
|
|-
|parasitic on head of / host head of
|
|-
|parasitic on hypodermis of / host hypodermis of
|
|-
|parasitic on larva of / host larva of
|
|-
|parasitic on limb of / host limb of
|
|-
|parasitic on lung of / host lung of
|
|-
|parasitic on mouth of / host mouth of
|
|-
|parasitic on nipple of / host nipple of
|
|-
|parasitic on nose of / host nose of
|
|-
|parasitic on pupa of / host pupa of
|
|-
|parasitic on quill feather (covert) of / host quill feather (covert) of
|
|-
|parasitic on quill feather (flight feather) of / host quill feather (flight feather) of
|
|-
|parasitic on quill feather (tail feather) of / host quill feather (tail feather) of
|
|-
|parasitic on quill feather of / host quill feather of
|
|-
|parasitic on sentinel egg of / host sentinel egg of
|
|-
|parasitic on shoot of / host shoot of
|
|-
|parasitic on skin of / host skin of
|
|-
|parasitic on stomach of / host stomach of
|
|-
|parasitic on tail of / host tail of
|
|-
|parasitic on thorax of / host thorax of
|
|-
|parasitic on trachea of / host trachea of
|
|-
|parasitic on wash of / host wash of
|
|-
|parasitic on wing of / host wing of
|
|-
|parasitic under elytra of / under elytral host of
|
|-
|parasitic under scales of / under scales host of
|
|-
|parasitoid of / host of
|
|-
|patolling on / patrolled by
|
|-
|phoretic on / host of
|
|-
|phoretic on abdomen of / host abdomen of
|
|-
|phoretic on alate / alate host of
|
|-
|phoretic on antenna of / host antenna of
|
|-
|phoretic on body of / host body of
|
|-
|phoretic on coxa of / host coxa of
|
|-
|phoretic on eye of / host eye of
|
|-
|phoretic on hair follicle of / host hair follicle of
|
|-
|phoretic on head of / host head of
|
|-
|phoretic on leg of / host leg of
|
|-
|phoretic on limb of / host limb of
|
|-
|phoretic on tail of / host tail of
|
|-
|phoretic on thorax of / host thorax of
|
|-
|phoretic on wing of / host wing of
|
|-
|phoretic under elytra of / under elytral host of
|
|-
|phoretic under supra-anal plate of / under supra-anal plate host of
|
|-
|pollinating / pollinated by
|
|-
|predator of / prey of
|
|-
|prey of / predator of
|
|-
|pupa of / adult of
|
|-
|recorded in background with / in background for recording of
|
|-
|solitary egg parasitoid of / host egg of
|
|-
|stinging neck of / neck being stung by
|
|-
|stomach parasite of / host stomach of
|
|-
|subcortically living in dead / dead subcortically living in by
|
|-
|subcutaneous parasite of / subcutaneous host of
|
|-
|subcutaneously living in / subcutaneously lived in by
|
|-
|tracheal parasite of / tracheal host of
|
|-
|under bark of / under bark by
|
|-
|under bark of dead / dead under bark by
|
|-
|under bark of dead or dying twig or branch / dead or dying twig or branch under bark by
|
|-
|under bark of freshly killed / freshly killed under bark by
|
|-
|under bark of log of / log under bark by
|
|-
|under bark of stump of / stump under bark by
|
|-
|under bark of trunk of dead / dead under bark of trunk by
|
|-
|under dead / under dead by
|
|-
|under dead stem of / under dead stem by
|
|-
|under dry dung of / under dry dung by
|
|-
|under loose bark of / under loose bark by
|
|-
|under manure (feces) of / under manure (feces) by
|
|-
|under rocks with / under rocks with
|
|-
|under seed of / under seed by
|
|-
|unspecified association / unspecified association
|
|-
|wing parasite of / host wing of
|
|-
|with eggs of / eggs with
|
|-
|with roots of / roots with
|
|}

[[Category:Data Entry Assistant]]
[[Category:xBio:D Controlled Vocabularies]]

Biological Association Type Terms

2016-03-09T16:11:03Z

Matte: /* Biological Association Type Terms */

'''Introduction'''

This section contains information on the available biological association terms that are currently available in the xBio:D system. Biological associations within xBio:D represents a two-way relationship between the first organism and the second, and the association type is separated by a slash (/). For example, if you want to show a parasitoid-host relationship in which the specimen record you have is for the parasitoid (A) and the unvouchered associate (B) is its host, the association type ''emerged from egg of / host egg of'' would be read ''parasitoid (A) emerged from host (B)'' and conversely ''host (B) is a host egg of parasitoid (A)''. If you would like another biological association term added into xBio:D, please contact [mailto:cora.1@osu.edu Joe Cora] and request the addition.

== Biological Association Type Terms ==
{|
!Association Type
!Description
|-
|adult of / pupa of
|
|-
|among pieces of fallen nest of / fallen nest pieces contained
|
|-
|at base of large / large with base containing
|
|-
|between leaves of / leaves containing
|
|-
|burrowing into / contains burrowing
|
|-
|buzz pollinating / buzz pollinated by
|
|-
|collected in / contains
|
|-
|collected in drilled / drilled collecting site of
|
|-
|collected near / living near
|
|-
|collected near eggs / eggs present near
|
|-
|collected near flowering / flowering living near
|
|-
|collected near gall / gall present near
|
|-
|collected near nymph of / nymph present near
|
|-
|collected near stand of / stand present near
|
|-
|collected on / collecting site of
|
|-
|collected under / collecting site above
|
|-
|collected with / used to collect
|
|-
|collected with dung of / dung used to collect
|
|-
|collected with pheromone of / pheromone used to collect
|
|-
|collected with rotting / rotting used to collect
|
|-
|collection site of / collected on
|
|-
|egg ectoparasite of / host egg of
|
|-
|egg parasite of / host egg of
|
|-
|egg predator of / prey egg of
|
|-
|emerged from / produced
|
|-
|emerged from cocoon of / host cocoon of
|
|-
|emerged from diapausing eggs of / diapausing host eggs of
|
|-
|emerged from egg of / host egg of
|
|-
|emerged from egg sac of / host egg sac of
|
|-
|emerged from freshly killed / freshly killed host of
|
|-
|emerged from gall of / host gall of
|
|-
|emerged from immature of / host immature of
|
|-
|emerged from larva of / host larva of
|
|-
|emerged from leaf mine of / leaf mine containing
|
|-
|emerged from leaf mine on / leaf mine containing
|
|-
|emerged from leaf of / host leaf of
|
|-
|emerged from mossy gall of / host mossy gall of
|
|-
|emerged from mummy of / host mummy of
|
|-
|emerged from nest of / host nest of
|
|-
|emerged from nymph of / host nymph of
|
|-
|emerged from ootheca of / host ootheca of
|
|-
|emerged from pod of / host pod of
|
|-
|emerged from pole of / host pole containing
|
|-
|emerged from pupa of / host pupa of
|
|-
|emerged from pupal chamber of / host pupal chamber of
|
|-
|emerged from puparium of / host puparium of
|
|-
|emerged from root crown of / host root crown of
|
|-
|emerged from seed of / host seed of
|
|-
|emerged from sentinel egg mass of / host sentinel egg mass of
|
|-
|emerged from tunnel of / host tunnel of
|
|-
|emerged from twig of / host twig of
|
|-
|fed upon by / feeding on
|
|-
|feeding on / fed upon by
|
|-
|feeding on bark of / fed upon bark by
|
|-
|feeding on bud, shoot of / fed upon bud, shoot by
|
|-
|feeding on bulb of / fed upon bulb by
|
|-
|feeding on egg of / fed on egg by
|
|-
|feeding on flower of / fed on flower by
|
|-
|feeding on fruit, nut, seed of / fed on fruit, nut, seed by
|
|-
|feeding on gall of / fed on gall by
|
|-
|feeding on leaf gall of / fed upon leaf gall by
|
|-
|feeding on leaf of / fed upon leaf by
|
|-
|feeding on root of / fed upon root by
|
|-
|feeding on shoot of / fed upon shoot by
|
|-
|feeding on silk and end of ear of / fed upon silk and end of ear by
|
|-
|feeding on stem of / fed upon stem by
|
|-
|feeding on tree trunk of / fed upon tree trunk by
|
|-
|feeding on twig, branch of / fed upon twig, branch by
|
|-
|flying after / flying from
|
|-
|gregarious egg parasitoid of / host egg of
|
|-
|host egg of / emerged from egg of
|
|-
|host egg of / solitary egg parasitoid of
|
|-
|host larva of / larval parasitoid of
|
|-
|host of / parasite of
|
|-
|hyperparasite of / host of
|
|-
|in abandoned nest of / abandoned nest containing
|
|-
|in artificial colony of / artificial colony containing
|
|-
|in bark crack of / bark crack containing
|
|-
|in burrow of / burrow containing
|
|-
|in buttress of / buttress containing
|
|-
|in canopy of / canopy containing
|
|-
|in catface of living / living with catface containing
|
|-
|in center of rotten / rotten center containing
|
|-
|in clump of / clump containing
|
|-
|in cocoon of / cocoon containing
|
|-
|in colony of / colony containing
|
|-
|in culture of / culture containing
|
|-
|in dead log of / dead log containing
|
|-
|in decaying / decayed containing
|
|-
|in decaying bark of / decayed bark containing
|
|-
|in decaying fruit, nut, seed of / decayed fruit, nut, seed containing
|
|-
|in decaying log of / decayed log containing
|
|-
|in decaying mulch of / decayed mulch containing
|
|-
|in decaying root of / decayed root containing
|
|-
|in decaying tree stump of / decayed tree stump containing
|
|-
|in duff of / duff containing
|
|-
|in dunnage of / dunnage containing
|
|-
|in fallen of / fallen containing
|
|-
|in field with / in field with
|
|-
|in flower head of / flower head containing
|
|-
|in gall of / gall containing
|
|-
|in gall of flowering / flowering with gall containing
|
|-
|in galleries of / galleries containing
|
|-
|in leaf nest of / leaf nest containing
|
|-
|in leaf sheath of / leaf sheath containing
|
|-
|in litter of / litter containing
|
|-
|in litter of treehole of / litter of treehole containing
|
|-
|in litter under log of / litter under log containing
|
|-
|in litter with / in litter with
|
|-
|in log of / log containing
|
|-
|in log with / in log with
|
|-
|in manure (feces) of / manure (feces) containing
|
|-
|in mine of / mine containing
|
|-
|in moist decayed log of / moist decayed log containing
|
|-
|in nest of / nest containing
|
|-
|in nest on body of / body in nest containing
|
|-
|in nest with dead chick of / dead chick within nest with
|
|-
|in nest within / containing nest with
|
|-
|in nose of / nose containing
|
|-
|in paneling of / paneling containing
|
|-
|in petiole of / petiole containing
|
|-
|in roast of / roast containing
|
|-
|in roost of / roost containing
|
|-
|in root / root containing
|
|-
|in rotten / rotten containing
|
|-
|in rotten stump of / rotten stump containing
|
|-
|in scat of / scat containing
|
|-
|in shell of / shell containing
|
|-
|in silk tube of / silk tube containing
|
|-
|in soil with / in soil with
|
|-
|in soil with bulb of / bulb in soil with
|
|-
|in soil with root of / root in soil with
|
|-
|in square of / square containing
|
|-
|in stable with / stable containing
|
|-
|in stand of / stand containing
|
|-
|in stem of / stem containing
|
|-
|in stem gall of / stem gall containing
|
|-
|in stomach of / stomach containing
|
|-
|in straw of / straw containing
|
|-
|in stubble of / stubble containing
|
|-
|in subterranean dump of / subterranean dump containing
|
|-
|in thicket of / thicket containing
|
|-
|in treehole of / treehole containing
|
|-
|in trunk of / trunk containing
|
|-
|in tunnel of / tunnel containing
|
|-
|in vein on underside of leaf of / vein on under of leaf containing
|
|-
|in water with / in water with
|
|-
|in web of / web containing
|
|-
|in young leaf of / young leaf containing
|
|-
|infected by / infecting
|
|-
|inhabits / habitat for
|
|-
|internal parasite of / internal host of
|
|-
|larval parasite of / host larva of
|
|-
|larval parasitoid of / host larva of
|
|-
|larval predator of / prey larva of
|
|-
|living in / lived in by
|
|-
|living in colon of / lived within colon by
|
|-
|living in hypodermis of / lived within hypodermis by
|
|-
|living in pitcher of / lived within pitcher by
|
|-
|living in synovial fluid of / lived within synovial fluid by
|
|-
|living in treehole of / lived within treehole by
|
|-
|living on / lived on by
|
|-
|living on bark of / lived on bark by
|
|-
|living on body of / lived on body by
|
|-
|living on branch of / lived on branch by
|
|-
|living on bud of / lived on bud by
|
|-
|living on bulb of / lived on bulb by
|
|-
|living on feather of / lived on feather by
|
|-
|living on flower of / lived on flower by
|
|-
|living on fruit, nut, seed of / lived on fruit, nut, seed by
|
|-
|living on hair follicle of / lived on hair follicle by
|
|-
|living on hair of / lived on hair by
|
|-
|living on head of / lived on head by
|
|-
|living on leaf of / lived on leaf by
|
|-
|living on log of / lived on log by
|
|-
|living on male cone of / lived on male cone by
|
|-
|living on mosaic infected / (mosaic infected) lived on by
|
|-
|living on nut, seed of / lived on nut, seed by
|
|-
|living on pupa of / lived on pupa by
|
|-
|living on root of / lived on root by
|
|-
|living on sapflow of / lived on sapflow by
|
|-
|living on seed of / lived on seed by
|
|-
|living on shoot of / lived on shoot by
|
|-
|living on stem of / lived on stem by
|
|-
|living on tail of / lived on tail by
|
|-
|living on tree trunk of / lived on tree trunk by
|
|-
|living on twig, branch of / lived on twig, branch by
|
|-
|living on wash of / lived on wash by
|
|-
|living on wing of / lived on wing by
|
|-
|living under bark of / lived under bark by
|
|-
|living under bark of dead / lived under bark by
|
|-
|living under bark of fallen / lived under bark by
|
|-
|living under bark of living / lived under bark by
|
|-
|living under bark of rotten trunk of / lived under bark of rotten trunk by
|
|-
|living under chips of cut / lived under chips by
|
|-
|living with / living with
|
|-
|mother parasitic on / host of mother of
|
|-
|nest containing / in nest of
|
|-
|on abdomen of / abdomen containing
|
|-
|on aphid infested / aphid infested containing
|
|-
|on ball of / ball containing
|
|-
|on bark of / bark containing
|
|-
|on bark of dead / dead with bark containing
|
|-
|on bark of living / living with bark containing
|
|-
|on bloom of / bloom containing
|
|-
|on blossom of / blossom containing
|
|-
|on body of / body containing
|
|-
|on branch of / branch containing
|
|-
|on bulb of / bulb containing
|
|-
|on cadaver of / cadaver containing
|
|-
|on cone of / cone containing
|
|-
|on cone flower of / cone flower containing
|
|-
|on coppice of / coppice containing
|
|-
|on corrigated & crumpled leaf of dwarfed / (dwarfed) corrigated & crumpled leaf containing
|
|-
|on dead / dead containing
|
|-
|on dead branch of / dead branch containing
|
|-
|on dead leaf of / dead leaf containing
|
|-
|on dead limb of / dead limb containing
|
|-
|on dead limb or trunk of / dead limb or trunk containing
|
|-
|on dead or dying twig of / dead or dying twig containing
|
|-
|on dead remains of / upon dead remains by
|
|-
|on dead twig of / dead twig containing
|
|-
|on dead vine of / dead vine containing
|
|-
|on dead, standing / dead, standing containing
|
|-
|on decayed / decayed containing
|
|-
|on decayed log of / decayed log containing
|
|-
|on decayed stump of / decayed stump containing
|
|-
|on decaying of / decaying containing
|
|-
|on deep sear of living / living with deep sear containing
|
|-
|on dense growth of / dense growth containing
|
|-
|on dry / dry containing
|
|-
|on dry dung of / dry dung containing
|
|-
|on dung of / dung containing
|
|-
|on ear of / ear containing
|
|-
|on egg of / egg containing
|
|-
|on egg sac of / egg sac containing
|
|-
|on eye of / eye containing
|
|-
|on female adult of / female adult containing
|
|-
|on fire scorched of / fire scorched containing
|
|-
|on flower bud of / flower bud containing
|
|-
|on flower of / flower containing
|
|-
|on flower stalk of / flower stalk containing
|
|-
|on flowering / flowering containing
|
|-
|on flowerless / flowerless containing
|
|-
|on foliage of / foliage containing
|
|-
|on fresh wound of / fresh wound containing
|
|-
|on freshly cut / freshly cut containing
|
|-
|on frond of / frond containing
|
|-
|on fruit of / fruit containing
|
|-
|on fruiting / fruiting containing
|
|-
|on gills of / gills containing
|
|-
|on guano of / guano contaning
|
|-
|on heavily curled leaf of / heavily curled leaf containing
|
|-
|on inflorescence of / inflorescence containing
|
|-
|on lamina of / lamina containing
|
|-
|on large, hollow / large, hollow containing
|
|-
|on leaf axil of / leaf axil containing
|
|-
|on leaf of / leaf containing
|
|-
|on leaf petiole of / leaf petiole containing
|
|-
|on leaflet of / leaflet containing
|
|-
|on log of / log containing
|
|-
|on midrib of / midrib containing
|
|-
|on moldy, shelled / moldy, shelled containing
|
|-
|on needle of / needle containing
|
|-
|on or near / containing or near
|
|-
|on or near flowering / flowering containing or near
|
|-
|on or near flowers of / flowers containing or near
|
|-
|on overripe fruit of / overripe fruit containing
|
|-
|on paddy edge of / paddy edge containing
|
|-
|on paddy of / paddy containing
|
|-
|on pod of / pod containing
|
|-
|on rosette / rosette containing
|
|-
|on rotten / rotten containing
|
|-
|on rotten fruit of / rotten fruit containing
|
|-
|on rotten log of / rotten log containing
|
|-
|on rotting / rotting containing
|
|-
|on scrub / scrub containing
|
|-
|on seed of / seed containing
|
|-
|on seedling of / seedling containing
|
|-
|on short / short containing
|
|-
|on skin of / skin containing
|
|-
|on stalk of / stalk containing
|
|-
|on stem of / stem containing
|
|-
|on sticky seed of / sticky seed containing
|
|-
|on stomach of cadaver of / stomach of cadaver containing
|
|-
|on stored product of / stored product containing
|
|-
|on stump of / stump containing
|
|-
|on thorax of / thorax containing
|
|-
|on top of flower of / top of flower containing
|
|-
|on tree of / tree containing
|
|-
|on trunk of / trunk containing
|
|-
|on trunk of dead / dead with trunk containing
|
|-
|on trunk of dying / dying with trunk containing
|
|-
|on twig of / twig containing
|
|-
|on underside of frond of / underside of frond containing
|
|-
|on unflowered / unflowered containing
|
|-
|on vine of / vine containing
|
|-
|on wild of / wild containing
|
|-
|on wing of / wing containing
|
|-
|on wound of twig of / wound of twig containing
|
|-
|on young / young containing
|
|-
|ovipositing into bud of / host bud of
|
|-
|ovipositing into egg of / host egg of
|
|-
|ovipositing into gall of / host gall of
|
|-
|ovipositing into young sprout of / young sprout containing
|
|-
|paraphage on / host of
|
|-
|parasite of / host of
|
|-
|parasitic in ear of / host ear of
|
|-
|parasitic in nose of / host nose of
|
|-
|parasitic in skin of / host skin of
|
|-
|parasitic on abdomen of / host abdomen of
|
|-
|parasitic on body of / host body of
|
|-
|parasitic on branchial chamber of / host branchial chamber of
|
|-
|parasitic on cloaca of / host cloaca of
|
|-
|parasitic on coxa of / host coxa of
|
|-
|parasitic on ear of / host ear of
|
|-
|parasitic on egg of / host egg of
|
|-
|parasitic on eye of / host eye of
|
|-
|parasitic on genitalia of / host genitalia of
|
|-
|parasitic on gills of / host gills of
|
|-
|parasitic on hair follicle of / host hair follicle of
|
|-
|parasitic on hair of / host hair of
|
|-
|parasitic on head of / host head of
|
|-
|parasitic on hypodermis of / host hypodermis of
|
|-
|parasitic on larva of / host larva of
|
|-
|parasitic on limb of / host limb of
|
|-
|parasitic on lung of / host lung of
|
|-
|parasitic on mouth of / host mouth of
|
|-
|parasitic on nipple of / host nipple of
|
|-
|parasitic on nose of / host nose of
|
|-
|parasitic on pupa of / host pupa of
|
|-
|parasitic on quill feather (covert) of / host quill feather (covert) of
|
|-
|parasitic on quill feather (flight feather) of / host quill feather (flight feather) of
|
|-
|parasitic on quill feather (tail feather) of / host quill feather (tail feather) of
|
|-
|parasitic on quill feather of / host quill feather of
|
|-
|parasitic on sentinel egg of / host sentinel egg of
|
|-
|parasitic on shoot of / host shoot of
|
|-
|parasitic on skin of / host skin of
|
|-
|parasitic on stomach of / host stomach of
|
|-
|parasitic on tail of / host tail of
|
|-
|parasitic on thorax of / host thorax of
|
|-
|parasitic on trachea of / host trachea of
|
|-
|parasitic on wash of / host wash of
|
|-
|parasitic on wing of / host wing of
|
|-
|parasitic under elytra of / under elytral host of
|
|-
|parasitic under scales of / under scales host of
|
|-
|parasitoid of / host of
|
|-
|patolling on / patrolled by
|
|-
|phoretic on / host of
|
|-
|phoretic on abdomen of / host abdomen of
|
|-
|phoretic on alate / alate host of
|
|-
|phoretic on antenna of / host antenna of
|
|-
|phoretic on body of / host body of
|
|-
|phoretic on coxa of / host coxa of
|
|-
|phoretic on eye of / host eye of
|
|-
|phoretic on hair follicle of / host hair follicle of
|
|-
|phoretic on head of / host head of
|
|-
|phoretic on leg of / host leg of
|
|-
|phoretic on limb of / host limb of
|
|-
|phoretic on tail of / host tail of
|
|-
|phoretic on thorax of / host thorax of
|
|-
|phoretic on wing of / host wing of
|
|-
|phoretic under elytra of / under elytral host of
|
|-
|phoretic under supra-anal plate of / under supra-anal plate host of
|
|-
|pollinating / pollinated by
|
|-
|predator of / prey of
|
|-
|prey of / predator of
|
|-
|pupa of / adult of
|
|-
|recorded in background with / in background for recording of
|
|-
|solitary egg parasitoid of / host egg of
|
|-
|stinging neck of / neck being stung by
|
|-
|stomach parasite of / host stomach of
|
|-
|subcortically living in dead / dead subcortically living in by
|
|-
|subcutaneous parasite of / subcutaneous host of
|
|-
|subcutaneously living in / subcutaneously lived in by
|
|-
|tracheal parasite of / tracheal host of
|
|-
|under bark of / under bark by
|
|-
|under bark of dead / dead under bark by
|
|-
|under bark of dead or dying twig or branch / dead or dying twig or branch under bark by
|
|-
|under bark of freshly killed / freshly killed under bark by
|
|-
|under bark of log of / log under bark by
|
|-
|under bark of trunk of dead / dead under bark of trunk by
|
|-
|under dead / under dead by
|
|-
|under dead stem of / under dead stem by
|
|-
|under dry dung of / under dry dung by
|
|-
|under loose bark of / under loose bark by
|
|-
|under manure (feces) of / under manure (feces) by
|
|-
|under rocks with / under rocks with
|
|-
|under seed of / under seed by
|
|-
|unspecified association / unspecified association
|
|-
|wing parasite of / host wing of
|
|-
|with eggs of / eggs with
|
|-
|with roots of / roots with
|
|}

[[Category:Data Entry Assistant]]
[[Category:xBio:D Controlled Vocabularies]]

Biological Association Type Terms

2016-03-09T16:05:33Z

Matte: /* Biological Association Type Terms */

'''Introduction'''

This section contains information on the available biological association terms that are currently available in the xBio:D system. Biological associations within xBio:D represents a two-way relationship between the first organism and the second, and the association type is separated by a slash (/). For example, if you want to show a parasitoid-host relationship in which the specimen record you have is for the parasitoid (A) and the unvouchered associate (B) is its host, the association type ''emerged from egg of / host egg of'' would be read ''parasitoid (A) emerged from host (B)'' and conversely ''host (B) is a host egg of parasitoid (A)''. If you would like another biological association term added into xBio:D, please contact [mailto:cora.1@osu.edu Joe Cora] and request the addition.

== Biological Association Type Terms ==
{|
!Association Type
!Description
|-
|adult of / pupa of
|
|-
|among pieces of fallen nest of / fallen nest pieces contained
|
|-
|at base of large / large with base containing
|
|-
|between leaves of / leaves containing
|
|-
|burrowing into / contains burrowing
|
|-
|buzz pollinating / buzz pollinated by
|
|-
|collected in / contains
|
|-
|collected in drilled / drilled collecting site of
|
|-
|collected near / living near
|
|-
|collected near eggs / eggs present near
|
|-
|collected near flowering / flowering living near
|
|-
|collected near gall / gall present near
|
|-
|collected near nymph of / nymph present near
|
|-
|collected near stand of / stand present near
|
|-
|collected on / collecting site of
|
|-
|collected under / collecting site above
|
|-
|collected with / used to collect
|
|-
|collected with dung of / dung used to collect
|
|-
|collected with pheromone of / pheromone used to collect
|
|-
|collected with rotting / rotting used to collect
|
|-
|collection site of / collected on
|
|-
|egg ectoparasite of / host egg of
|
|-
|egg parasite of / host egg of
|
|-
|egg predator of / prey egg of
|
|-
|emerged from / produced
|
|-
|emerged from cocoon of / host cocoon of
|
|-
|emerged from diapausing eggs of / diapausing host eggs of
|
|-
|emerged from egg of / host egg of
|
|-
|emerged from egg sac of / host egg sac of
|
|-
|emerged from freshly killed / freshly killed host of
|
|-
|emerged from gall of / host gall of
|
|-
|emerged from immature of / host immature of
|
|-
|emerged from larva of / host larva of
|
|-
|emerged from leaf mine of / leaf mine containing
|
|-
|emerged from leaf mine on / leaf mine containing
|
|-
|emerged from leaf of / host leaf of
|
|-
|emerged from mossy gall of / host mossy gall of
|
|-
|emerged from mummy of / host mummy of
|
|-
|emerged from nest of / host nest of
|
|-
|emerged from nymph of / host nymph of
|
|-
|emerged from ootheca of / host ootheca of
|
|-
|emerged from pod of / host pod of
|
|-
|emerged from pole of / host pole containing
|
|-
|emerged from pupa of / host pupa of
|
|-
|emerged from pupal chamber of / host pupal chamber of
|
|-
|emerged from puparium of / host puparium of
|
|-
|emerged from root crown of / host root crown of
|
|-
|emerged from seed of / host seed of
|
|-
|emerged from sentinel egg mass of / host sentinel egg mass of
|
|-
|emerged from tunnel of / host tunnel of
|
|-
|emerged from twig of / host twig of
|
|-
|fed upon by / feeding on
|
|-
|feeding on / fed upon by
|
|-
|feeding on bark of / fed upon bark by
|
|-
|feeding on bud, shoot of / fed upon bud, shoot by
|
|-
|feeding on bulb of / fed upon bulb by
|
|-
|feeding on egg of / fed on egg by
|
|-
|feeding on flower of / fed on flower by
|
|-
|feeding on fruit, nut, seed of / fed on fruit, nut, seed by
|
|-
|feeding on gall of / fed on gall by
|
|-
|feeding on leaf gall of / fed upon leaf gall by
|
|-
|feeding on leaf of / fed upon leaf by
|
|-
|feeding on root of / fed upon root by
|
|-
|feeding on shoot of / fed upon shoot by
|
|-
|feeding on silk and end of ear of / fed upon silk and end of ear by
|
|-
|feeding on stem of / fed upon stem by
|
|-
|feeding on tree trunk of / fed upon tree trunk by
|
|-
|feeding on twig, branch of / fed upon twig, branch by
|
|-
|flying after / flying from
|
|-
|gregarious egg parasitoid of / host egg of
|
|-
|host egg of / emerged from egg of
|
|-
|host egg of / solitary egg parasitoid of
|
|-
|host larva of / larval parasitoid of
|
|-
|host of / parasite of
|
|-
|hyperparasite of / host of
|
|-
|in abandoned nest of / abandoned nest containing
|
|-
|in artificial colony of / artificial colony containing
|
|-
|in bark crack of / bark crack containing
|
|-
|in burrow of / burrow containing
|
|-
|in buttress of / buttress containing
|
|-
|in canopy of / canopy containing
|
|-
|in catface of living / living with catface containing
|
|-
|in center of rotten / rotten center containing
|
|-
|in clump of / clump containing
|
|-
|in cocoon of / cocoon containing
|
|-
|in colony of / colony containing
|
|-
|in culture of / culture containing
|
|-
|in dead log of / dead log containing
|
|-
|in decaying / decayed containing
|
|-
|in decaying bark of / decayed bark containing
|
|-
|in decaying fruit, nut, seed of / decayed fruit, nut, seed containing
|
|-
|in decaying log of / decayed log containing
|
|-
|in decaying mulch of / decayed mulch containing
|
|-
|in decaying root of / decayed root containing
|
|-
|in decaying tree stump of / decayed tree stump containing
|
|-
|in duff of / duff containing
|
|-
|in dunnage of / dunnage containing
|
|-
|in fallen of / fallen containing
|
|-
|in field with / in field with
|
|-
|in flower head of / flower head containing
|
|-
|in gall of / gall containing
|
|-
|in gall of flowering / flowering with gall containing
|
|-
|in galleries of / galleries containing
|
|-
|in leaf nest of / leaf nest containing
|
|-
|in leaf sheath of / leaf sheath containing
|
|-
|in litter of / litter containing
|
|-
|in litter of treehole of / litter of treehole containing
|
|-
|in litter under log of / litter under log containing
|
|-
|in litter with / in litter with
|
|-
|in log of / log containing
|
|-
|in log with / in log with
|
|-
|in manure (feces) of / manure (feces) containing
|
|-
|in mine of / mine containing
|
|-
|in moist decayed log of / moist decayed log containing
|
|-
|in nest of / nest containing
|
|-
|in nest on body of / body in nest containing
|
|-
|in nest with dead chick of / dead chick within nest with
|
|-
|in nest within / containing nest with
|
|-
|in nose of / nose containing
|
|-
|in paneling of / paneling containing
|
|-
|in petiole of / petiole containing
|
|-
|in roast of / roast containing
|
|-
|in roost of / roost containing
|
|-
|in root / root containing
|
|-
|in rotten / rotten containing
|
|-
|in rotten stump of / rotten stump containing
|
|-
|in scat of / scat containing
|
|-
|in shell of / shell containing
|
|-
|in silk tube of / silk tube containing
|
|-
|in soil with / in soil with
|
|-
|in soil with bulb of / bulb in soil with
|
|-
|in soil with root of / root in soil with
|
|-
|in square of / square containing
|
|-
|in stable with / stable containing
|
|-
|in stand of / stand containing
|
|-
|in stem of / stem containing
|
|-
|in stem gall of / stem gall containing
|
|-
|in stomach of / stomach containing
|
|-
|in straw of / straw containing
|
|-
|in stubble of / stubble containing
|
|-
|in subterranean dump of / subterranean dump containing
|
|-
|in thicket of / thicket containing
|
|-
|in treehole of / treehole containing
|
|-
|in trunk of / trunk containing
|
|-
|in tunnel of / tunnel containing
|
|-
|in vein on underside of leaf of / vein on under of leaf containing
|
|-
|in water with / in water with
|
|-
|in web of / web containing
|
|-
|in young leaf of / young leaf containing
|
|-
|infected by / infecting
|
|-
|inhabits / habitat for
|
|-
|internal parasite of / internal host of
|
|-
|larval parasite of / host larva of
|
|-
|larval parasitoid of / host larva of
|
|-
|larval predator of / prey larva of
|
|-
|living in / lived in by
|
|-
|living in colon of / lived within colon by
|
|-
|living in hypodermis of / lived within hypodermis by
|
|-
|living in pitcher of / lived within pitcher by
|
|-
|living in synovial fluid of / lived within synovial fluid by
|
|-
|living in treehole of / lived within treehole by
|
|-
|living on / lived on by
|
|-
|living on bark of / lived on bark by
|
|-
|living on body of / lived on body by
|
|-
|living on branch of / lived on branch by
|
|-
|living on bud of / lived on bud by
|
|-
|living on bulb of / lived on bulb by
|
|-
|living on feather of / lived on feather by
|
|-
|living on flower of / lived on flower by
|
|-
|living on fruit, nut, seed of / lived on fruit, nut, seed by
|
|-
|living on hair follicle of / lived on hair follicle by
|
|-
|living on hair of / lived on hair by
|
|-
|living on head of / lived on head by
|
|-
|living on leaf of / lived on leaf by
|
|-
|living on log of / lived on log by
|
|-
|living on male cone of / lived on male cone by
|
|-
|living on mosaic infected / (mosaic infected) lived on by
|
|-
|living on nut, seed of / lived on nut, seed by
|
|-
|living on pupa of / lived on pupa by
|
|-
|living on root of / lived on root by
|
|-
|living on sapflow of / lived on sapflow by
|
|-
|living on seed of / lived on seed by
|
|-
|living on shoot of / lived on shoot by
|
|-
|living on stem of / lived on stem by
|
|-
|living on tail of / lived on tail by
|
|-
|living on tree trunk of / lived on tree trunk by
|
|-
|living on twig, branch of / lived on twig, branch by
|
|-
|living on wash of / lived on wash by
|
|-
|living on wing of / lived on wing by
|
|-
|living under bark of / lived under bark by
|
|-
|living under bark of dead / lived under bark by
|
|-
|living under bark of fallen / lived under bark by
|
|-
|living under bark of living / lived under bark by
|
|-
|living under bark of rotten trunk of / lived under bark of rotten trunk by
|
|-
|living under chips of cut / lived under chips by
|
|-
|living with / living with
|
|-
|mother parasitic on / host of mother of
|
|-
|nest containing / in nest of
|
|-
|on abdomen of / abdomen containing
|
|-
|on aphid infested / aphid infested containing
|
|-
|on ball of / ball containing
|
|-
|on bark of / bark containing
|
|-
|on bark of dead / dead with bark containing
|
|-
|on bark of living / living with bark containing
|
|-
|on bloom of / bloom containing
|
|-
|on blossom of / blossom containing
|
|-
|on body of / body containing
|
|-
|on branch of / branch containing
|
|-
|on bulb of / bulb containing
|
|-
|on cadaver of / cadaver containing
|
|-
|on cone of / cone containing
|
|-
|on cone flower of / cone flower containing
|
|-
|on coppice of / coppice containing
|
|-
|on corrigated & crumpled leaf of dwarfed / (dwarfed) corrigated & crumpled leaf containing
|
|-
|on dead / dead containing
|
|-
|on dead branch of / dead branch containing
|
|-
|on dead leaf of / dead leaf containing
|
|-
|on dead limb of / dead limb containing
|
|-
|on dead limb or trunk of / dead limb or trunk containing
|
|-
|on dead or dying twig of / dead or dying twig containing
|
|-
|on dead remains of / upon dead remains by
|
|-
|on dead twig of / dead twig containing
|
|-
|on dead vine of / dead vine containing
|
|-
|on dead, standing / dead, standing containing
|
|-
|on decayed / decayed containing
|
|-
|on decayed log of / decayed log containing
|
|-
|on decayed stump of / decayed stump containing
|
|-
|on decaying of / decaying containing
|
|-
|on deep sear of living / living with deep sear containing
|
|-
|on dense growth of / dense growth containing
|
|-
|on dry / dry containing
|
|-
|on dry dung of / dry dung containing
|
|-
|on dung of / dung containing
|
|-
|on ear of / ear containing
|
|-
|on egg of / egg containing
|
|-
|on egg sac of / egg sac containing
|
|-
|on eye of / eye containing
|
|-
|on female adult of / female adult containing
|
|-
|on fire scorched of / fire scorched containing
|
|-
|on flower bud of / flower bud containing
|
|-
|on flower of / flower containing
|
|-
|on flower stalk of / flower stalk containing
|
|-
|on flowering / flowering containing
|
|-
|on flowerless / flowerless containing
|
|-
|on foliage of / foliage containing
|
|-
|on fresh wound of / fresh wound containing
|
|-
|on freshly cut / freshly cut containing
|
|-
|on frond of / frond containing
|
|-
|on fruit of / fruit containing
|
|-
|on fruiting / fruiting containing
|
|-
|on gills of / gills containing
|
|-
|on guano of / guano contaning
|
|-
|on heavily curled leaf of / heavily curled leaf containing
|
|-
|on inflorescence of / inflorescence containing
|
|-
|on lamina of / lamina containing
|
|-
|on large, hollow / large, hollow containing
|
|-
|on leaf axil of / leaf axil containing
|
|-
|on leaf of / leaf containing
|
|-
|on leaf petiole of / leaf petiole containing
|
|-
|on leaflet of / leaflet containing
|
|-
|on log of / log containing
|
|-
|on midrib of / midrib containing
|
|-
|on moldy, shelled / moldy, shelled containing
|
|-
|on needle of / needle containing
|
|-
|on or near / containing or near
|
|-
|on or near flowering / flowering containing or near
|
|-
|on or near flowers of / flowers containing or near
|
|-
|on overripe fruit of / overripe fruit containing
|
|-
|on paddy edge of / paddy edge containing
|
|-
|on paddy of / paddy containing
|
|-
|on pod of / pod containing
|
|-
|on rosette / rosette containing
|
|-
|on rotten / rotten containing
|
|-
|on rotten fruit of / rotten fruit containing
|
|-
|on rotten log of / rotten log containing
|
|-
|on rotting / rotting containing
|
|-
|on scrub / scrub containing
|
|-
|on seed of / seed containing
|
|-
|on seedling of / seedling containing
|
|-
|on short / short containing
|
|-
|on skin of / skin containing
|
|-
|on stalk of / stalk containing
|
|-
|on stem of / stem containing
|
|-
|on sticky seed of / sticky seed containing
|
|-
|on stomach of cadaver of / stomach of cadaver containing
|
|-
|on stored product of / stored product containing
|
|-
|on stump of / stump containing
|
|-
|on thorax of / thorax containing
|
|-
|on top of flower of / top of flower containing
|
|-
|on tree of / tree containing
|
|-
|on trunk of / trunk containing
|
|-
|on trunk of dead / dead with trunk containing
|
|-
|on trunk of dying / dying with trunk containing
|
|-
|on twig of / twig containing
|
|-
|on underside of frond of / underside of frond containing
|
|-
|on unflowered / unflowered containing
|
|-
|on vine of / vine containing
|
|-
|on wild of / wild containing
|
|-
|on wing of / wing containing
|
|-
|on wound of twig of / wound of twig containing
|
|-
|on young / young containing
|
|-
|ovipositing into bud of / host bud of
|
|-
|ovipositing into egg of / host egg of
|
|-
|ovipositing into gall of / host gall of
|
|-
|ovipositing into young sprout of / young sprout containing
|
|-
|paraphage on / host of
|
|-
|parasite of / host of
|
|-
|parasitic in ear of / host ear of
|
|-
|parasitic in nose of / host nose of
|
|-
|parasitic in skin of / host skin of
|
|-
|parasitic on abdomen of / host abdomen of
|
|-
|parasitic on body of / host body of
|
|-
|parasitic on branchial chamber of / host branchial chamber of
|
|-
|parasitic on cloaca of / host cloaca of
|
|-
|parasitic on coxa of / host coxa of
|
|-
|parasitic on ear of / host ear of
|
|-
|parasitic on egg of / host egg of
|
|-
|parasitic on eye of / host eye of
|
|-
|parasitic on genitalia of / host genitalia of
|
|-
|parasitic on gills of / host gills of
|
|-
|parasitic on hair follicle of / host hair follicle of
|
|-
|parasitic on hair of / host hair of
|
|-
|parasitic on head of / host head of
|
|-
|parasitic on hypodermis of / host hypodermis of
|
|-
|parasitic on larva of / host larva of
|
|-
|parasitic on limb of / host limb of
|
|-
|parasitic on lung of / host lung of
|
|-
|parasitic on mouth of / host mouth of
|
|-
|parasitic on nipple of / host nipple of
|
|-
|parasitic on nose of / host nose of
|
|-
|parasitic on pupa of / host pupa of
|
|-
|parasitic on quill feather (covert) of / host quill feather (covert) of
|
|-
|parasitic on quill feather (flight feather) of / host quill feather (flight feather) of
|
|-
|parasitic on quill feather (tail feather) of / host quill feather (tail feather) of
|
|-
|parasitic on quill feather of / host quill feather of
|
|-
|parasitic on sentinel egg of / host sentinel egg of
|
|-
|parasitic on shoot of / host shoot of
|
|-
|parasitic on skin of / host skin of
|
|-
|parasitic on stomach of / host stomach of
|
|-
|parasitic on tail of / host tail of
|
|-
|parasitic on thorax of / host thorax of
|
|-
|parasitic on trachea of / host trachea of
|
|-
|parasitic on wash of / host wash of
|
|-
|parasitic on wing of / host wing of
|
|-
|parasitic under elytra of / under elytral host of
|
|-
|parasitic under scales of / under scales host of
|
|-
|parasitoid of / host of
|
|-
|patolling on / patrolled by
|
|-
|phoretic on / host of
|
|-
|phoretic on abdomen of / host abdomen of
|
|-
|phoretic on alate / alate host of
|
|-
|phoretic on antenna of / host antenna of
|
|-
|phoretic on body of / host body of
|
|-
|phoretic on coxa of / host coxa of
|
|-
|phoretic on eye of / host eye of
|
|-
|phoretic on hair follicle of / host hair follicle of
|
|-
|phoretic on head of / host head of
|
|-
|phoretic on leg of / host leg of
|
|-
|phoretic on limb of / host limb of
|
|-
|phoretic on tail of / host tail of
|
|-
|phoretic on thorax of / host thorax of
|
|-
|phoretic on wing of / host wing of
|
|-
|phoretic under elytra of / under elytral host of
|
|-
|phoretic under supra-anal plate of / under supra-anal plate host of
|
|-
|pollinating / pollinated by
|
|-
|predator of / prey of
|
|-
|prey of / predator of
|
|-
|pupa of / adult of
|
|-
|recorded in background with / in background for recording of
|
|-
|solitary egg parasitoid of / host egg of
|
|-
|stinging neck of / neck being stung by
|
|-
|stomach parasite of / host stomach of
|
|-
|subcortically living in dead / dead subcortically living in by
|
|-
|subcutaneous parasite of / subcutaneous host of
|
|-
|subcutaneously living in / subcutaneously lived in by
|
|-
|tracheal parasite of / tracheal host of
|
|-
|under bark of / under bark by
|
|-
|under bark of dead / dead under bark by
|
|-
|under bark of dead or dying twig or branch / dead or dying twig or branch under bark by
|
|-
|under bark of log of / log under bark by
|
|-
|under bark of trunk of dead / dead under bark of trunk by
|
|-
|under dead / under dead by
|
|-
|under dead stem of / under dead stem by
|
|-
|under dry dung of / under dry dung by
|
|-
|under loose bark of / under loose bark by
|
|-
|under manure (feces) of / under manure (feces) by
|
|-
|under rocks with / under rocks with
|
|-
|under seed of / under seed by
|
|-
|unspecified association / unspecified association
|
|-
|wing parasite of / host wing of
|
|-
|with eggs of / eggs with
|
|-
|with roots of / roots with
|
|}

[[Category:Data Entry Assistant]]
[[Category:xBio:D Controlled Vocabularies]]

Biological Association Type Terms

2016-03-07T14:27:00Z

Matte: /* Biological Association Type Terms */

'''Introduction'''

This section contains information on the available biological association terms that are currently available in the xBio:D system. Biological associations within xBio:D represents a two-way relationship between the first organism and the second, and the association type is separated by a slash (/). For example, if you want to show a parasitoid-host relationship in which the specimen record you have is for the parasitoid (A) and the unvouchered associate (B) is its host, the association type ''emerged from egg of / host egg of'' would be read ''parasitoid (A) emerged from host (B)'' and conversely ''host (B) is a host egg of parasitoid (A)''. If you would like another biological association term added into xBio:D, please contact [mailto:cora.1@osu.edu Joe Cora] and request the addition.

== Biological Association Type Terms ==
{|
!Association Type
!Description
|-
|adult of / pupa of
|
|-
|among pieces of fallen nest of / fallen nest pieces contained
|
|-
|at base of large / large with base containing
|
|-
|between leaves of / leaves containing
|
|-
|burrowing into / contains burrowing
|
|-
|buzz pollinating / buzz pollinated by
|
|-
|collected in / contains
|
|-
|collected in drilled / drilled collecting site of
|
|-
|collected near / living near
|
|-
|collected near eggs / eggs present near
|
|-
|collected near flowering / flowering living near
|
|-
|collected near gall / gall present near
|
|-
|collected near nymph of / nymph present near
|
|-
|collected near stand of / stand present near
|
|-
|collected on / collecting site of
|
|-
|collected under / collecting site above
|
|-
|collected with / used to collect
|
|-
|collected with dung of / dung used to collect
|
|-
|collected with pheromone of / pheromone used to collect
|
|-
|collected with rotting / rotting used to collect
|
|-
|collection site of / collected on
|
|-
|egg ectoparasite of / host egg of
|
|-
|egg parasite of / host egg of
|
|-
|egg predator of / prey egg of
|
|-
|emerged from / produced
|
|-
|emerged from cocoon of / host cocoon of
|
|-
|emerged from diapausing eggs of / diapausing host eggs of
|
|-
|emerged from egg of / host egg of
|
|-
|emerged from egg sac of / host egg sac of
|
|-
|emerged from freshly killed / freshly killed host of
|
|-
|emerged from gall of / host gall of
|
|-
|emerged from immature of / host immature of
|
|-
|emerged from larva of / host larva of
|
|-
|emerged from leaf mine of / leaf mine containing
|
|-
|emerged from leaf mine on / leaf mine containing
|
|-
|emerged from leaf of / host leaf of
|
|-
|emerged from mossy gall of / host mossy gall of
|
|-
|emerged from mummy of / host mummy of
|
|-
|emerged from nest of / host nest of
|
|-
|emerged from nymph of / host nymph of
|
|-
|emerged from ootheca of / host ootheca of
|
|-
|emerged from pod of / host pod of
|
|-
|emerged from pole of / host pole containing
|
|-
|emerged from pupa of / host pupa of
|
|-
|emerged from pupal chamber of / host pupal chamber of
|
|-
|emerged from puparium of / host puparium of
|
|-
|emerged from root crown of / host root crown of
|
|-
|emerged from seed of / host seed of
|
|-
|emerged from sentinel egg mass of / host sentinel egg mass of
|
|-
|emerged from tunnel of / host tunnel of
|
|-
|emerged from twig of / host twig of
|
|-
|fed upon by / feeding on
|
|-
|feeding on / fed upon by
|
|-
|feeding on bark of / fed upon bark by
|
|-
|feeding on bud, shoot of / fed upon bud, shoot by
|
|-
|feeding on bulb of / fed upon bulb by
|
|-
|feeding on egg of / fed on egg by
|
|-
|feeding on flower of / fed on flower by
|
|-
|feeding on fruit, nut, seed of / fed on fruit, nut, seed by
|
|-
|feeding on gall of / fed on gall by
|
|-
|feeding on leaf gall of / fed upon leaf gall by
|
|-
|feeding on leaf of / fed upon leaf by
|
|-
|feeding on root of / fed upon root by
|
|-
|feeding on shoot of / fed upon shoot by
|
|-
|feeding on silk and end of ear of / fed upon silk and end of ear by
|
|-
|feeding on stem of / fed upon stem by
|
|-
|feeding on tree trunk of / fed upon tree trunk by
|
|-
|feeding on twig, branch of / fed upon twig, branch by
|
|-
|flying after / flying from
|
|-
|gregarious egg parasitoid of / host egg of
|
|-
|host egg of / emerged from egg of
|
|-
|host egg of / solitary egg parasitoid of
|
|-
|host larva of / larval parasitoid of
|
|-
|host of / parasite of
|
|-
|hyperparasite of / host of
|
|-
|in abandoned nest of / abandoned nest containing
|
|-
|in artificial colony of / artificial colony containing
|
|-
|in bark crack of / bark crack containing
|
|-
|in burrow of / burrow containing
|
|-
|in buttress of / buttress containing
|
|-
|in canopy of / canopy containing
|
|-
|in catface of living / living with catface containing
|
|-
|in center of rotten / rotten center containing
|
|-
|in clump of / clump containing
|
|-
|in cocoon of / cocoon containing
|
|-
|in colony of / colony containing
|
|-
|in culture of / culture containing
|
|-
|in dead log of / dead log containing
|
|-
|in decaying / decayed containing
|
|-
|in decaying bark of / decayed bark containing
|
|-
|in decaying fruit, nut, seed of / decayed fruit, nut, seed containing
|
|-
|in decaying log of / decayed log containing
|
|-
|in decaying mulch of / decayed mulch containing
|
|-
|in decaying root of / decayed root containing
|
|-
|in decaying tree stump of / decayed tree stump containing
|
|-
|in duff of / duff containing
|
|-
|in dunnage of / dunnage containing
|
|-
|in fallen of / fallen containing
|
|-
|in field with / in field with
|
|-
|in flower head of / flower head containing
|
|-
|in gall of / gall containing
|
|-
|in gall of flowering / flowering with gall containing
|
|-
|in galleries of / galleries containing
|
|-
|in leaf nest of / leaf nest containing
|
|-
|in leaf sheath of / leaf sheath containing
|
|-
|in litter of / litter containing
|
|-
|in litter of treehole of / litter of treehole containing
|
|-
|in litter under log of / litter under log containing
|
|-
|in litter with / in litter with
|
|-
|in log of / log containing
|
|-
|in log with / in log with
|
|-
|in manure (feces) of / manure (feces) containing
|
|-
|in mine of / mine containing
|
|-
|in moist decayed log of / moist decayed log containing
|
|-
|in nest of / nest containing
|
|-
|in nest on body of / body in nest containing
|
|-
|in nest with dead chick of / dead chick within nest with
|
|-
|in nest within / containing nest with
|
|-
|in nose of / nose containing
|
|-
|in paneling of / paneling containing
|
|-
|in petiole of / petiole containing
|
|-
|in roast of / roast containing
|
|-
|in roost of / roost containing
|
|-
|in root / root containing
|
|-
|in rotten / rotten containing
|
|-
|in rotten stump of / rotten stump containing
|
|-
|in scat of / scat containing
|
|-
|in shell of / shell containing
|
|-
|in silk tube of / silk tube containing
|
|-
|in soil with / in soil with
|
|-
|in soil with bulb of / bulb in soil with
|
|-
|in soil with root of / root in soil with
|
|-
|in square of / square containing
|
|-
|in stable with / stable containing
|
|-
|in stand of / stand containing
|
|-
|in stem of / stem containing
|
|-
|in stem gall of / stem gall containing
|
|-
|in stomach of / stomach containing
|
|-
|in straw of / straw containing
|
|-
|in stubble of / stubble containing
|
|-
|in subterranean dump of / subterranean dump containing
|
|-
|in thicket of / thicket containing
|
|-
|in treehole of / treehole containing
|
|-
|in trunk of / trunk containing
|
|-
|in tunnel of / tunnel containing
|
|-
|in vein on underside of leaf of / vein on under of leaf containing
|
|-
|in water with / in water with
|
|-
|in web of / web containing
|
|-
|in young leaf of / young leaf containing
|
|-
|infected by / infecting
|
|-
|inhabits / habitat for
|
|-
|internal parasite of / internal host of
|
|-
|larval parasite of / host larva of
|
|-
|larval parasitoid of / host larva of
|
|-
|larval predator of / prey larva of
|
|-
|living in / lived in by
|
|-
|living in colon of / lived within colon by
|
|-
|living in hypodermis of / lived within hypodermis by
|
|-
|living in pitcher of / lived within pitcher by
|
|-
|living in synovial fluid of / lived within synovial fluid by
|
|-
|living in treehole of / lived within treehole by
|
|-
|living on / lived on by
|
|-
|living on bark of / lived on bark by
|
|-
|living on body of / lived on body by
|
|-
|living on branch of / lived on branch by
|
|-
|living on bud of / lived on bud by
|
|-
|living on bulb of / lived on bulb by
|
|-
|living on feather of / lived on feather by
|
|-
|living on flower of / lived on flower by
|
|-
|living on fruit, nut, seed of / lived on fruit, nut, seed by
|
|-
|living on hair follicle of / lived on hair follicle by
|
|-
|living on hair of / lived on hair by
|
|-
|living on head of / lived on head by
|
|-
|living on leaf of / lived on leaf by
|
|-
|living on log of / lived on log by
|
|-
|living on male cone of / lived on male cone by
|
|-
|living on mosaic infected / (mosaic infected) lived on by
|
|-
|living on nut, seed of / lived on nut, seed by
|
|-
|living on pupa of / lived on pupa by
|
|-
|living on root of / lived on root by
|
|-
|living on sapflow of / lived on sapflow by
|
|-
|living on seed of / lived on seed by
|
|-
|living on shoot of / lived on shoot by
|
|-
|living on stem of / lived on stem by
|
|-
|living on tail of / lived on tail by
|
|-
|living on tree trunk of / lived on tree trunk by
|
|-
|living on twig, branch of / lived on twig, branch by
|
|-
|living on wash of / lived on wash by
|
|-
|living on wing of / lived on wing by
|
|-
|living under bark of / lived under bark by
|
|-
|living under bark of dead / lived under bark by
|
|-
|living under bark of fallen / lived under bark by
|
|-
|living under bark of living / lived under bark by
|
|-
|living under bark of rotten trunk of / lived under bark of rotten trunk by
|
|-
|living under chips of cut / lived under chips by
|
|-
|living with / living with
|
|-
|mother parasitic on / host of mother of
|
|-
|nest containing / in nest of
|
|-
|on abdomen of / abdomen containing
|
|-
|on aphid infested / aphid infested containing
|
|-
|on ball of / ball containing
|
|-
|on bark of / bark containing
|
|-
|on bark of dead / dead with bark containing
|
|-
|on bark of living / living with bark containing
|
|-
|on bloom of / bloom containing
|
|-
|on blossom of / blossom containing
|
|-
|on body of / body containing
|
|-
|on branch of / branch containing
|
|-
|on bulb of / bulb containing
|
|-
|on cadaver of / cadaver containing
|
|-
|on cone of / cone containing
|
|-
|on cone flower of / cone flower containing
|
|-
|on coppice of / coppice containing
|
|-
|on corrigated & crumpled leaf of dwarfed / (dwarfed) corrigated & crumpled leaf containing
|
|-
|on dead / dead containing
|
|-
|on dead branch of / dead branch containing
|
|-
|on dead leaf of / dead leaf containing
|
|-
|on dead limb of / dead limb containing
|
|-
|on dead limb or trunk of / dead limb or trunk containing
|
|-
|on dead or dying twig of / dead or dying twig containing
|
|-
|on dead remains of / upon dead remains by
|
|-
|on dead twig of / dead twig containing
|
|-
|on dead vine of / dead vine containing
|
|-
|on dead, standing / dead, standing containing
|
|-
|on decayed / decayed containing
|
|-
|on decayed log of / decayed log containing
|
|-
|on decayed stump of / decayed stump containing
|
|-
|on decaying of / decaying containing
|
|-
|on deep sear of living / living with deep sear containing
|
|-
|on dense growth of / dense growth containing
|
|-
|on dry / dry containing
|
|-
|on dry dung of / dry dung containing
|
|-
|on dung of / dung containing
|
|-
|on ear of / ear containing
|
|-
|on egg of / egg containing
|
|-
|on egg sac of / egg sac containing
|
|-
|on eye of / eye containing
|
|-
|on female adult of / female adult containing
|
|-
|on fire scorched of / fire scorched containing
|
|-
|on flower bud of / flower bud containing
|
|-
|on flower of / flower containing
|
|-
|on flower stalk of / flower stalk containing
|
|-
|on flowering / flowering containing
|
|-
|on flowerless / flowerless containing
|
|-
|on foliage of / foliage containing
|
|-
|on fresh wound of / fresh wound containing
|
|-
|on freshly cut / freshly cut containing
|
|-
|on frond of / frond containing
|
|-
|on fruit of / fruit containing
|
|-
|on fruiting / fruiting containing
|
|-
|on gills of / gills containing
|
|-
|on guano of / guano contaning
|
|-
|on heavily curled leaf of / heavily curled leaf containing
|
|-
|on inflorescence of / inflorescence containing
|
|-
|on lamina of / lamina containing
|
|-
|on large, hollow / large, hollow containing
|
|-
|on leaf axil of / leaf axil containing
|
|-
|on leaf of / leaf containing
|
|-
|on leaf petiole of / leaf petiole containing
|
|-
|on leaflet of / leaflet containing
|
|-
|on log of / log containing
|
|-
|on midrib of / midrib containing
|
|-
|on moldy, shelled / moldy, shelled containing
|
|-
|on needle of / needle containing
|
|-
|on or near / containing or near
|
|-
|on or near flowering / flowering containing or near
|
|-
|on or near flowers of / flowers containing or near
|
|-
|on overripe fruit of / overripe fruit containing
|
|-
|on paddy edge of / paddy edge containing
|
|-
|on paddy of / paddy containing
|
|-
|on pod of / pod containing
|
|-
|on rosette / rosette containing
|
|-
|on rotten / rotten containing
|
|-
|on rotten fruit of / rotten fruit containing
|
|-
|on rotten log of / rotten log containing
|
|-
|on rotting / rotting containing
|
|-
|on scrub / scrub containing
|
|-
|on seed of / seed containing
|
|-
|on seedling of / seedling containing
|
|-
|on short / short containing
|
|-
|on skin of / skin containing
|
|-
|on stalk of / stalk containing
|
|-
|on stem of / stem containing
|
|-
|on sticky seed of / sticky seed containing
|
|-
|on stomach of cadaver of / stomach of cadaver containing
|
|-
|on stored product of / stored product containing
|
|-
|on stump of / stump containing
|
|-
|on thorax of / thorax containing
|
|-
|on top of flower of / top of flower containing
|
|-
|on tree of / tree containing
|
|-
|on trunk of / trunk containing
|
|-
|on trunk of dead / dead with trunk containing
|
|-
|on trunk of dying / dying with trunk containing
|
|-
|on twig of / twig containing
|
|-
|on underside of frond of / underside of frond containing
|
|-
|on unflowered / unflowered containing
|
|-
|on vine of / vine containing
|
|-
|on wild of / wild containing
|
|-
|on wing of / wing containing
|
|-
|on wound of twig of / wound of twig containing
|
|-
|on young / young containing
|
|-
|ovipositing into bud of / host bud of
|
|-
|ovipositing into egg of / host egg of
|
|-
|ovipositing into gall of / host gall of
|
|-
|ovipositing into young sprout of / young sprout containing
|
|-
|paraphage on / host of
|
|-
|parasite of / host of
|
|-
|parasitic in ear of / host ear of
|
|-
|parasitic in nose of / host nose of
|
|-
|parasitic in skin of / host skin of
|
|-
|parasitic on abdomen of / host abdomen of
|
|-
|parasitic on body of / host body of
|
|-
|parasitic on branchial chamber of / host branchial chamber of
|
|-
|parasitic on cloaca of / host cloaca of
|
|-
|parasitic on coxa of / host coxa of
|
|-
|parasitic on ear of / host ear of
|
|-
|parasitic on egg of / host egg of
|
|-
|parasitic on eye of / host eye of
|
|-
|parasitic on genitalia of / host genitalia of
|
|-
|parasitic on gills of / host gills of
|
|-
|parasitic on hair follicle of / host hair follicle of
|
|-
|parasitic on hair of / host hair of
|
|-
|parasitic on head of / host head of
|
|-
|parasitic on hypodermis of / host hypodermis of
|
|-
|parasitic on larva of / host larva of
|
|-
|parasitic on limb of / host limb of
|
|-
|parasitic on lung of / host lung of
|
|-
|parasitic on mouth of / host mouth of
|
|-
|parasitic on nipple of / host nipple of
|
|-
|parasitic on nose of / host nose of
|
|-
|parasitic on pupa of / host pupa of
|
|-
|parasitic on quill feather (covert) of / host quill feather (covert) of
|
|-
|parasitic on quill feather (flight feather) of / host quill feather (flight feather) of
|
|-
|parasitic on quill feather (tail feather) of / host quill feather (tail feather) of
|
|-
|parasitic on quill feather of / host quill feather of
|
|-
|parasitic on sentinel egg of / host sentinel egg of
|
|-
|parasitic on shoot of / host shoot of
|
|-
|parasitic on skin of / host skin of
|
|-
|parasitic on stomach of / host stomach of
|
|-
|parasitic on tail of / host tail of
|
|-
|parasitic on thorax of / host thorax of
|
|-
|parasitic on trachea of / host trachea of
|
|-
|parasitic on wash of / host wash of
|
|-
|parasitic on wing of / host wing of
|
|-
|parasitic under elytra of / under elytral host of
|
|-
|parasitic under scales of / under scales host of
|
|-
|parasitoid of / host of
|
|-
|patolling on / patrolled by
|
|-
|phoretic on / host of
|
|-
|phoretic on abdomen of / host abdomen of
|
|-
|phoretic on alate / alate host of
|
|-
|phoretic on antenna of / host antenna of
|
|-
|phoretic on body of / host body of
|
|-
|phoretic on coxa of / host coxa of
|
|-
|phoretic on eye of / host eye of
|
|-
|phoretic on hair follicle of / host hair follicle of
|
|-
|phoretic on head of / host head of
|
|-
|phoretic on leg of / host leg of
|
|-
|phoretic on limb of / host limb of
|
|-
|phoretic on tail of / host tail of
|
|-
|phoretic on thorax of / host thorax of
|
|-
|phoretic on wing of / host wing of
|
|-
|phoretic under elytra of / under elytral host of
|
|-
|phoretic under supra-anal plate of / under supra-anal plate host of
|
|-
|pollinating / pollinated by
|
|-
|predator of / prey of
|
|-
|prey of / predator of
|
|-
|pupa of / adult of
|
|-
|recorded in background with / in background for recording of
|
|-
|solitary egg parasitoid of / host egg of
|
|-
|stinging neck of / neck being stung by
|
|-
|stomach parasite of / host stomach of
|
|-
|subcortically living in dead / dead subcortically living in by
|
|-
|subcutaneous parasite of / subcutaneous host of
|
|-
|subcutaneously living in / subcutaneously lived in by
|
|-
|tracheal parasite of / tracheal host of
|
|-
|under bark of / under bark by
|
|-
|under bark of dead / dead under bark by
|
|-
|under bark of dead or dying twig or branch / dead or dying twig or branch under bark by
|
|-
|under bark of trunk of dead / dead under bark of trunk by
|
|-
|under dead / under dead by
|
|-
|under dead stem of / under dead stem by
|
|-
|under dry dung of / under dry dung by
|
|-
|under loose bark of / under loose bark by
|
|-
|under manure (feces) of / under manure (feces) by
|
|-
|under rocks with / under rocks with
|
|-
|under seed of / under seed by
|
|-
|unspecified association / unspecified association
|
|-
|wing parasite of / host wing of
|
|-
|with eggs of / eggs with
|
|-
|with roots of / roots with
|
|}

[[Category:Data Entry Assistant]]
[[Category:xBio:D Controlled Vocabularies]]

Locality Georeferencing and Generation

2016-02-11T21:03:10Z

Matte: /* Locality Comments */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained within [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Twp., sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*A locality name should start with a specific containing entity, if the most specific containing entity is a county or state, use the most specific locality information.
**e.g. the locality name for "CO:Moffat Co. Rt. 40, 9.8 miles W Maybell" would be "US-40, 9.8mi W Maybell, Moffat Co., CO". However, "CO:Moffat Co. 9.8 miles W Maybell" would yield a locality name of "9.8mi W Maybell, Moffat Co., CO" as 9.8mi W Maybell is specific locality information, but is not a containing entity. Roads can be considered as containing entities since the specimen is collected along the road.
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-12-21T16:10:31Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained in [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Twp., sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*A locality name should start with a specific containing entity, if the most specific containing entity is a county or state, use the most specific locality information.
**e.g. the locality name for "CO:Moffat Co. Rt. 40, 9.8 miles W Maybell" would be "US-40, 9.8mi W Maybell, Moffat Co., CO". However, "CO:Moffat Co. 9.8 miles W Maybell" would yield a locality name of "9.8mi W Maybell, Moffat Co., CO" as 9.8mi W Maybell is specific locality information, but is not a containing entity. Roads can be considered as containing entities since the specimen is collected along the road.
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Geographic Resources / Gazetteers

2015-08-20T18:30:27Z

Matte: /* Geographic Tools */

'''Introduction'''

This page is designed to provide a useful list of country-level or international gazetteers as well as other geographic resources for verifying place names and/or geopolitical units.

== Gazetteers ==
{|
!Name
!URL
!Description
|-
|GEOnet
|[http://geonames.nga.mil/namesgaz/ http://geonames.nga.mil/namesgaz/]
|Find coordinates for places outside of the U.S. as well as the political division it is located within.
|-
|USGS-GNIS
|[http://geonames.usgs.gov/pls/gnispublic/ http://geonames.usgs.gov/pls/gnispublic/]
|Find coordinates for places within the U.S. and its territories as well as on Antarctica.
|-
|WDPA-UN
|[http://www.wdpa.org/ http://www.wdpa.org/]
|Find national parks, reserves & protected areas along with their respective coordinates and areas.
|-
|Fuzzy Gazetteer
|[http://dma.jrc.it/services/fuzzyg/ http://dma.jrc.it/services/fuzzyg/]
|Find places around the world mainly utilizing GEOnet data by performing fuzzy searching. Useful for place name misspellings.
|-
|CGNDB
|[http://www4.rncan.gc.ca/search-place-names/search?lang=en http://www4.rncan.gc.ca/search-place-names/search?lang=en]
|Find coordinates for places within Canada.
|-
|Geoscience Australia
|[http://www.ga.gov.au/map/names/ http://www.ga.gov.au/map/names/]
|Find coordinates for places within Australia.
|-
|Ordnance Survey
|[http://www.ordnancesurvey.co.uk/oswebsite/ http://www.ordnancesurvey.co.uk/oswebsite/]
|Find towns within the UK but no coordinates available.
|-
|streetmap
|[http://www.streetmap.co.uk/ http://www.streetmap.co.uk/]
|Find places within Great Britain but no coordinates available.
|-
|diddlefinger
|[http://diddlefinger.com/ http://diddlefinger.com/]
|Find coordinates for places within Japan in English.
|-
|Geospatial Information Authority of Japan (GSI)
|[http://www.gsi.go.jp/ENGLISH/pape_e300284.html http://www.gsi.go.jp/ENGLISH/pape_e300284.html]
|Find coordinates for places within Japan in English and Japanese (Kanji & Hiragana) (PDF)
|-
|Géoportail
|[http://www.geoportail.fr http://www.geoportail.fr]
|Find coordinates for places within France and its territories.
|-
|NZGPD
|[http://www.linz.govt.nz/placenames/find-names/ http://www.linz.govt.nz/placenames/find-names/]
|Find coordinates for places within New Zealand. New gazetteer is in a spreadsheet but the old resource is a database that is many times more informative.
|-
|INEGI
|[http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx]
|Find coordinates for places within Mexico in Spanish.
|-
|Mapa Digital de México
|[http://gaia.inegi.org.mx/mdm6/ http://gaia.inegi.org.mx/mdm6/]
|Find locations for places and features within Mexico in Spanish.
|-
|GeoDatenZentrum
|[http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html]
|Find coordinates for places within Germany.
|-
|Lantmäteriet
|[http://kso.lantmateriet.se http://kso.lantmateriet.se]
|Find places within Sweden in Swedish but no coordinates available.
|-
|GeoArgentina
|[http://ventas.ign.gob.ar/catalog/searchadv.htm http://ventas.ign.gob.ar/catalog/searchadv.htm]
|Find coordinates for places within Argentina in Spanish.
|-
|BEV
|[http://www.austrianmap.at/amap/ http://www.austrianmap.at/amap/]
|Find coordinates for places within Austria in German.
|-
|Wikimapia
|[http://wikimapia.org/ http://wikimapia.org/]
|Find coordinates for places via user-tagged records around the world. Useful for some obscure places in particular in India.
|-
|HCSO
|[http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer]
|Find places within Hungary but no coordinates available.
|-
|PSGC
|[http://www.nscb.gov.ph/activestats/psgc/ http://www.nscb.gov.ph/activestats/psgc/]
|Find places within the Philippines but no coordinates available.
|-
|Placenames Database of Ireland
|[http://www.logainm.ie http://www.logainm.ie]
|Find coordinates for places within Ireland but coordinates need converted into WGS 84 units.
|-
|Cadastre GeoMeta
|[http://www.geometa.ch http://www.geometa.ch]
|Find coordinates for places within Switzerland but coordinates need converted into WGS 84 units.
|-
|CNIG
|[http://www.cnig.es http://www.cnig.es]
|Find coordinates for places within Spain but coordinates need converted into WGS 84 units. Click on "búsqueda avanzada (advanced search" at the top to search for a place name.
|-
|Stednavne
|[http://www.stednavne.info http://www.stednavne.info]
|Find places within Denmark in Danish but no coordinates available.
|-
|Norgeskart
|[http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1 http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1]
|Find places within Norway in Norwegian
|-
|Catalogo IGM
|[http://www.igmi.org/ware/ http://www.igmi.org/ware/]
|Find coordinates for places within Italy in Italian
|-
|National Land Survey of Finland (NLS)
|[http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en]
|Find coordinates for places within Finland
|-
|Locatienet
|[http://routenet.nl http://routenet.nl]
|Find coordinates for places within the Netherlands. First, search in Route Planner. Then after locating the locality, go back to Route Planner, select GPS above the search, then find the coordinates for the locality.
|-
|Český úřad zeměměřický a katastrální (CUZK)
|[http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx]
|Find coordinates for places within the Czech Republic in Czech
|-
|Instituto Geográfico Nacional del Perú (IGN)
|[http://www.ign.gob.pe/nomenclatorDigital/datos.php http://www.ign.gob.pe/nomenclatorDigital/datos.php]
|Find coordinates for places within Peru in Spanish
|-
|Ministry of Infrastructure and Spatial Planning (MISP)
|[http://prostor3.gov.si/iokno_ang/iokno.jsp http://prostor3.gov.si/iokno_ang/iokno.jsp]
|Find coordinates for places within Slovenia but coordinates need converted into WGS 84 units.
|-
|Mapový klient (ZBGIS)
|[https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en]
|Find coordinates for places within Slovakia
|-
|Geoportal (DGU)
|[http://geoportal.dgu.hr/viewer/ http://geoportal.dgu.hr/viewer/]
|Find coordinates for places within Croatia in Croatian. First, click on "Pretraga" in the left menu, then select the lower search type "Vrsta prostorne jedinice". The upper box "Vrsta prostorne jedinice" is the location type and the lower box "Ime prostorne jedinice" is the location name.
|}

== Geographic Tools ==
{|
!Name
!URL
!Description
|-
|Earth Point
|[http://www.earthpoint.us/TownshipsSearchByDescription.aspx http://www.earthpoint.us/TownshipsSearchByDescription.aspx]
|Convert from U.S. TRS (Township Range Section) designation to WGS coordinates
|-
|The World Coordinate Converter
|[http://twcc.fr/# http://twcc.fr/#]
|Convert most coordinate system into WGS coordinates
|-
|nearby.org.uk
|[http://www.nearby.org.uk/conversions.cgi http://www.nearby.org.uk/conversions.cgi]
|Convert UK and Irish map coordinate as well as other coordinate systems into WGS coordinates
|-
|DFS-map Coordinate Tool
|[http://ibot.sav.sk/dfs/stvorce/index.html http://ibot.sav.sk/dfs/stvorce/index.html]
|Find DFS squares in Slovakia Note: Slovakian flag in upper right must be clicked as application will not work in English
|}

[[Category:Data Entry Assistant]]
[[Category:References]]

Locality Georeferencing and Generation

2015-07-30T14:20:30Z

Matte: /* Formatting Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained in [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*A locality name should start with a specific containing entity, if the most specific containing entity is a county or state, use the most specific locality information.
**e.g. the locality name for "CO:Moffat Co. Rt. 40, 9.8 miles W Maybell" would be "US-40, 9.8mi W Maybell, Moffat Co., CO". However, "CO:Moffat Co. 9.8 miles W Maybell" would yield a locality name of "9.8mi W Maybell, Moffat Co., CO" as 9.8mi W Maybell is specific locality information, but is not a containing entity. Roads can be considered as containing entities since the specimen is collected along the road.
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-30T14:19:05Z

Matte: /* Formatting Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained in [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*A locality name should start with a specific containing entity, if the most specific containing entity is a county or state, use the most specific locality information.
**e.g. the locality name of "CO:Moffat Co. Rt. 40, 9.8 miles W Maybell" would be "US-40, 9.8mi W Maybell, Moffat Co., CO". However, "CO:Moffat Co. 9.8 miles W Maybell" would yield a locality of "9.8mi W Maybell, Moffat Co., CO" as 9.8mi W Maybell is specific locality information, but is not a containing entity. Roads can be considered as containing entities since the specimen is collected along the road.
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-23T15:26:28Z

Matte: /* General Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained in [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Plural habitats (e.g. under stones, or under logs) should be left plural in the locality name. However, associations should be changed to singular (using Association Terms).
[[Category:Data Entry Assistant]]

Geographic Resources / Gazetteers

2015-07-16T17:54:23Z

Matte: /* Geographic Tools */

'''Introduction'''

This page is designed to provide a useful list of country-level or international gazetteers as well as other geographic resources for verifying place names and/or geopolitical units.

== Gazetteers ==
{|
!Name
!URL
!Description
|-
|GEOnet
|[http://geonames.nga.mil/namesgaz/ http://geonames.nga.mil/namesgaz/]
|Find coordinates for places outside of the U.S. as well as the political division it is located within.
|-
|USGS-GNIS
|[http://geonames.usgs.gov/pls/gnispublic/ http://geonames.usgs.gov/pls/gnispublic/]
|Find coordinates for places within the U.S. and its territories as well as on Antarctica.
|-
|WDPA-UN
|[http://www.wdpa.org/ http://www.wdpa.org/]
|Find national parks, reserves & protected areas along with their respective coordinates and areas.
|-
|Fuzzy Gazetteer
|[http://dma.jrc.it/services/fuzzyg/ http://dma.jrc.it/services/fuzzyg/]
|Find places around the world mainly utilizing GEOnet data by performing fuzzy searching. Useful for place name misspellings.
|-
|CGNDB
|[http://www4.rncan.gc.ca/search-place-names/search?lang=en http://www4.rncan.gc.ca/search-place-names/search?lang=en]
|Find coordinates for places within Canada.
|-
|Geoscience Australia
|[http://www.ga.gov.au/map/names/ http://www.ga.gov.au/map/names/]
|Find coordinates for places within Australia.
|-
|Ordnance Survey
|[http://www.ordnancesurvey.co.uk/oswebsite/ http://www.ordnancesurvey.co.uk/oswebsite/]
|Find towns within the UK but no coordinates available.
|-
|streetmap
|[http://www.streetmap.co.uk/ http://www.streetmap.co.uk/]
|Find places within Great Britain but no coordinates available.
|-
|diddlefinger
|[http://diddlefinger.com/ http://diddlefinger.com/]
|Find coordinates for places within Japan in English.
|-
|Geospatial Information Authority of Japan (GSI)
|[http://www.gsi.go.jp/ENGLISH/pape_e300284.html http://www.gsi.go.jp/ENGLISH/pape_e300284.html]
|Find coordinates for places within Japan in English and Japanese (Kanji & Hiragana) (PDF)
|-
|Géoportail
|[http://www.geoportail.fr http://www.geoportail.fr]
|Find coordinates for places within France and its territories.
|-
|NZGPD
|[http://www.linz.govt.nz/placenames/find-names/ http://www.linz.govt.nz/placenames/find-names/]
|Find coordinates for places within New Zealand. New gazetteer is in a spreadsheet but the old resource is a database that is many times more informative.
|-
|INEGI
|[http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx]
|Find coordinates for places within Mexico in Spanish.
|-
|Mapa Digital de México
|[http://gaia.inegi.org.mx/mdm6/ http://gaia.inegi.org.mx/mdm6/]
|Find locations for places and features within Mexico in Spanish.
|-
|GeoDatenZentrum
|[http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html]
|Find coordinates for places within Germany.
|-
|Lantmäteriet
|[http://kso.lantmateriet.se http://kso.lantmateriet.se]
|Find places within Sweden in Swedish but no coordinates available.
|-
|GeoArgentina
|[http://ventas.ign.gob.ar/catalog/searchadv.htm http://ventas.ign.gob.ar/catalog/searchadv.htm]
|Find coordinates for places within Argentina in Spanish.
|-
|BEV
|[http://www.austrianmap.at/amap/ http://www.austrianmap.at/amap/]
|Find coordinates for places within Austria in German.
|-
|Wikimapia
|[http://wikimapia.org/ http://wikimapia.org/]
|Find coordinates for places via user-tagged records around the world. Useful for some obscure places in particular in India.
|-
|HCSO
|[http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer]
|Find places within Hungary but no coordinates available.
|-
|PSGC
|[http://www.nscb.gov.ph/activestats/psgc/ http://www.nscb.gov.ph/activestats/psgc/]
|Find places within the Philippines but no coordinates available.
|-
|Placenames Database of Ireland
|[http://www.logainm.ie http://www.logainm.ie]
|Find coordinates for places within Ireland but coordinates need converted into WGS 84 units.
|-
|Cadastre GeoMeta
|[http://www.geometa.ch http://www.geometa.ch]
|Find coordinates for places within Switzerland but coordinates need converted into WGS 84 units.
|-
|CNIG
|[http://www.cnig.es http://www.cnig.es]
|Find coordinates for places within Spain but coordinates need converted into WGS 84 units. Click on "búsqueda avanzada (advanced search" at the top to search for a place name.
|-
|Stednavne
|[http://www.stednavne.info http://www.stednavne.info]
|Find places within Denmark in Danish but no coordinates available.
|-
|Norgeskart
|[http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1 http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1]
|Find places within Norway in Norwegian
|-
|Catalogo IGM
|[http://www.igmi.org/ware/ http://www.igmi.org/ware/]
|Find coordinates for places within Italy in Italian
|-
|National Land Survey of Finland (NLS)
|[http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en]
|Find coordinates for places within Finland
|-
|Locatienet
|[http://routenet.nl http://routenet.nl]
|Find coordinates for places within the Netherlands. First, search in Route Planner. Then after locating the locality, go back to Route Planner, select GPS above the search, then find the coordinates for the locality.
|-
|Český úřad zeměměřický a katastrální (CUZK)
|[http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx]
|Find coordinates for places within the Czech Republic in Czech
|-
|Instituto Geográfico Nacional del Perú (IGN)
|[http://www.ign.gob.pe/nomenclatorDigital/datos.php http://www.ign.gob.pe/nomenclatorDigital/datos.php]
|Find coordinates for places within Peru in Spanish
|-
|Ministry of Infrastructure and Spatial Planning (MISP)
|[http://prostor3.gov.si/iokno_ang/iokno.jsp http://prostor3.gov.si/iokno_ang/iokno.jsp]
|Find coordinates for places within Slovenia but coordinates need converted into WGS 84 units.
|-
|Mapový klient (ZBGIS)
|[https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en]
|Find coordinates for places within Slovakia
|-
|Geoportal (DGU)
|[http://geoportal.dgu.hr/viewer/ http://geoportal.dgu.hr/viewer/]
|Find coordinates for places within Croatia in Croatian. First, click on "Pretraga" in the left menu, then select the lower search type "Vrsta prostorne jedinice". The upper box "Vrsta prostorne jedinice" is the location type and the lower box "Ime prostorne jedinice" is the location name.
|}

== Geographic Tools ==
{|
!Name
!URL
!Description
|-
|Earth Point
|[http://www.earthpoint.us/TownshipsSearchByDescription.aspx http://www.earthpoint.us/TownshipsSearchByDescription.aspx]
|Convert from U.S. TRS (Township Range Section) designation to WGS coordinates
|-
|The World Coordinate Converter
|[http://twcc.free.fr/ http://twcc.free.fr/]
|Convert most coordinate system into WGS coordinates
|-
|nearby.org.uk
|[http://www.nearby.org.uk/conversions.cgi http://www.nearby.org.uk/conversions.cgi]
|Convert UK and Irish map coordinate as well as other coordinate systems into WGS coordinates
|-
|DFS-map Coordinate Tool
|[http://ibot.sav.sk/dfs/stvorce/index.html http://ibot.sav.sk/dfs/stvorce/index.html]
|Find DFS squares in Slovakia Note: Slovakian flag in upper right must be clicked as application will not work in English
|}

[[Category:Data Entry Assistant]]
[[Category:References]]

Locality Georeferencing and Generation

2015-07-16T17:52:28Z

Matte: /* Gazetteer Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained in [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
*To find DFS squares in Slovakia use http://ibot.sav.sk/dfs/stvorce/index.html Note: Slovakian flag in upper right must be clicked as application will not work in English

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Geographic Resources / Gazetteers

2015-07-15T15:26:45Z

Matte: /* Geographic Tools */

'''Introduction'''

This page is designed to provide a useful list of country-level or international gazetteers as well as other geographic resources for verifying place names and/or geopolitical units.

== Gazetteers ==
{|
!Name
!URL
!Description
|-
|GEOnet
|[http://geonames.nga.mil/namesgaz/ http://geonames.nga.mil/namesgaz/]
|Find coordinates for places outside of the U.S. as well as the political division it is located within.
|-
|USGS-GNIS
|[http://geonames.usgs.gov/pls/gnispublic/ http://geonames.usgs.gov/pls/gnispublic/]
|Find coordinates for places within the U.S. and its territories as well as on Antarctica.
|-
|WDPA-UN
|[http://www.wdpa.org/ http://www.wdpa.org/]
|Find national parks, reserves & protected areas along with their respective coordinates and areas.
|-
|Fuzzy Gazetteer
|[http://dma.jrc.it/services/fuzzyg/ http://dma.jrc.it/services/fuzzyg/]
|Find places around the world mainly utilizing GEOnet data by performing fuzzy searching. Useful for place name misspellings.
|-
|CGNDB
|[http://www4.rncan.gc.ca/search-place-names/search?lang=en http://www4.rncan.gc.ca/search-place-names/search?lang=en]
|Find coordinates for places within Canada.
|-
|Geoscience Australia
|[http://www.ga.gov.au/map/names/ http://www.ga.gov.au/map/names/]
|Find coordinates for places within Australia.
|-
|Ordnance Survey
|[http://www.ordnancesurvey.co.uk/oswebsite/ http://www.ordnancesurvey.co.uk/oswebsite/]
|Find towns within the UK but no coordinates available.
|-
|streetmap
|[http://www.streetmap.co.uk/ http://www.streetmap.co.uk/]
|Find places within Great Britain but no coordinates available.
|-
|diddlefinger
|[http://diddlefinger.com/ http://diddlefinger.com/]
|Find coordinates for places within Japan in English.
|-
|Geospatial Information Authority of Japan (GSI)
|[http://www.gsi.go.jp/ENGLISH/pape_e300284.html http://www.gsi.go.jp/ENGLISH/pape_e300284.html]
|Find coordinates for places within Japan in English and Japanese (Kanji & Hiragana) (PDF)
|-
|Géoportail
|[http://www.geoportail.fr http://www.geoportail.fr]
|Find coordinates for places within France and its territories.
|-
|NZGPD
|[http://www.linz.govt.nz/placenames/find-names/ http://www.linz.govt.nz/placenames/find-names/]
|Find coordinates for places within New Zealand. New gazetteer is in a spreadsheet but the old resource is a database that is many times more informative.
|-
|INEGI
|[http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx]
|Find coordinates for places within Mexico in Spanish.
|-
|Mapa Digital de México
|[http://gaia.inegi.org.mx/mdm6/ http://gaia.inegi.org.mx/mdm6/]
|Find locations for places and features within Mexico in Spanish.
|-
|GeoDatenZentrum
|[http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html]
|Find coordinates for places within Germany.
|-
|Lantmäteriet
|[http://kso.lantmateriet.se http://kso.lantmateriet.se]
|Find places within Sweden in Swedish but no coordinates available.
|-
|GeoArgentina
|[http://ventas.ign.gob.ar/catalog/searchadv.htm http://ventas.ign.gob.ar/catalog/searchadv.htm]
|Find coordinates for places within Argentina in Spanish.
|-
|BEV
|[http://www.austrianmap.at/amap/ http://www.austrianmap.at/amap/]
|Find coordinates for places within Austria in German.
|-
|Wikimapia
|[http://wikimapia.org/ http://wikimapia.org/]
|Find coordinates for places via user-tagged records around the world. Useful for some obscure places in particular in India.
|-
|HCSO
|[http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer]
|Find places within Hungary but no coordinates available.
|-
|PSGC
|[http://www.nscb.gov.ph/activestats/psgc/ http://www.nscb.gov.ph/activestats/psgc/]
|Find places within the Philippines but no coordinates available.
|-
|Placenames Database of Ireland
|[http://www.logainm.ie http://www.logainm.ie]
|Find coordinates for places within Ireland but coordinates need converted into WGS 84 units.
|-
|Cadastre GeoMeta
|[http://www.geometa.ch http://www.geometa.ch]
|Find coordinates for places within Switzerland but coordinates need converted into WGS 84 units.
|-
|CNIG
|[http://www.cnig.es http://www.cnig.es]
|Find coordinates for places within Spain but coordinates need converted into WGS 84 units. Click on "búsqueda avanzada (advanced search" at the top to search for a place name.
|-
|Stednavne
|[http://www.stednavne.info http://www.stednavne.info]
|Find places within Denmark in Danish but no coordinates available.
|-
|Norgeskart
|[http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1 http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1]
|Find places within Norway in Norwegian
|-
|Catalogo IGM
|[http://www.igmi.org/ware/ http://www.igmi.org/ware/]
|Find coordinates for places within Italy in Italian
|-
|National Land Survey of Finland (NLS)
|[http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en]
|Find coordinates for places within Finland
|-
|Locatienet
|[http://routenet.nl http://routenet.nl]
|Find coordinates for places within the Netherlands. First, search in Route Planner. Then after locating the locality, go back to Route Planner, select GPS above the search, then find the coordinates for the locality.
|-
|Český úřad zeměměřický a katastrální (CUZK)
|[http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx]
|Find coordinates for places within the Czech Republic in Czech
|-
|Instituto Geográfico Nacional del Perú (IGN)
|[http://www.ign.gob.pe/nomenclatorDigital/datos.php http://www.ign.gob.pe/nomenclatorDigital/datos.php]
|Find coordinates for places within Peru in Spanish
|-
|Ministry of Infrastructure and Spatial Planning (MISP)
|[http://prostor3.gov.si/iokno_ang/iokno.jsp http://prostor3.gov.si/iokno_ang/iokno.jsp]
|Find coordinates for places within Slovenia but coordinates need converted into WGS 84 units.
|-
|Mapový klient (ZBGIS)
|[https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en]
|Find coordinates for places within Slovakia
|-
|Geoportal (DGU)
|[http://geoportal.dgu.hr/viewer/ http://geoportal.dgu.hr/viewer/]
|Find coordinates for places within Croatia in Croatian. First, click on "Pretraga" in the left menu, then select the lower search type "Vrsta prostorne jedinice". The upper box "Vrsta prostorne jedinice" is the location type and the lower box "Ime prostorne jedinice" is the location name.
|}

== Geographic Tools ==
{|
!Name
!URL
!Description
|-
|Earth Point
|[http://www.earthpoint.us/TownshipsSearchByDescription.aspx http://www.earthpoint.us/TownshipsSearchByDescription.aspx]
|Convert from U.S. TRS (Township Range Section) designation to WGS coordinates
|-
|The World Coordinate Converter
|[http://twcc.free.fr/ http://twcc.free.fr/]
|Convert most coordinate system into WGS coordinates
|-
|nearby.org.uk
|[http://www.nearby.org.uk/conversions.cgi http://www.nearby.org.uk/conversions.cgi]
|Convert UK and Irish map coordinate as well as other coordinate systems into WGS coordinates
|}

[[Category:Data Entry Assistant]]
[[Category:References]]

Locality Georeferencing and Generation

2015-07-13T14:58:44Z

Matte: /* Gazetteer Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained in [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Prefecture is state level in Japan
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:58:06Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained in [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Prefecture is state level in Japan
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:57:29Z

Matte: /* Locality Comments */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality is contained in [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made:
**E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Prefecture is state level in Japan
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:57:13Z

Matte: /* Locality Comments */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has variant names, a gazetteer places coordinates over a body of water, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land; (if gazetteer puts coordinates in middle of body of water)
::*locality contained in [county] Co. rather than adjacent [county on label] Co.; if county on label differs from county containing locality

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made:
**E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Prefecture is state level in Japan
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:54:00Z

Matte: /* Locality Comments */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)
::*locality contained in [county] Co. rather than adjacent [county on label] Co.

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made:
**E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Prefecture is state level in Japan
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:52:50Z

Matte: /* Locality Comments */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, a locale is contained entirely in an adjacent county than what is on the label, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)
::*"locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made:
**E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Prefecture is state level in Japan
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:50:03Z

Matte: /* Formatting Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made:
**E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Prefecture is state level in Japan
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:49:38Z

Matte: /* Gazetteer Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made:
E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Prefecture is state level in Japan
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**Format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:49:17Z

Matte: /* Gazetteer Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made:
E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Prefecture is state level in Japan
*Using earthpoint.us for TRS coords.
**Source is label
**Enter state and TRS coords. as they are available on label
**format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"

=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:48:38Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==

=== Formatting Tips ===
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*For Brazil, Australia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made:
E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

=== Gazetteer Tips ===
*Populated places in USGS-GNIS & GEOnet are Towns
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Prefecture is state level in Japan
*Using earthpoint.us for TRS coords.
**Source is label
**enter State and TRS coords. as they are available on label
**format in coordinates section of locality name follows example: "T12N R3W S2" or "T2N R1W"
=== General Georeferencing Tips ===
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”. In this case this would be an association.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:38:36Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made: E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."
=== Formatting Tips ===
=== Gazetteer Tips ===
[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:37:29Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use forward slash (/), hyphen (-), or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made: E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-13T14:37:02Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
{|
!Resource
!URL
|-
|DEA Help Home
|[[Data Entry Assistant (DEA) Help]]
|-
|DEA (original)
|http://osuc.osu.edu/dea/
|-
|Gazetteers
|[[Geographic_Resources_/_Gazetteers]]
|-
|Statoids
|http://www.statoids.com/
|-
|State/Province Codes
|[[State_/_Province_Codes_for_Countries]]
|-
|TRS (Township-Range-Section) Conversion
|http://www.earthpoint.us/TownshipsSearchByDescription.aspx
|-
|Google Translate
|http://translate.google.com
|-
|Google Earth (download)
|http://earth.google.com
|}

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''loc_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''loc_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet. Example: [http://google.com/search?q=100ft%20to%20m 100 feet to meters]

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use forward slash (/), hyphen (-) or commas (,):
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made: E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

[[Category:Data Entry Assistant]]

Data Entry Assistant (DEA) Help

2015-07-13T13:30:08Z

Matte: /* General Help */

'''Introduction'''

This section contains information on preparing occurrence data for entry into the xBio:D database using a web application named [http://osuc.osu.edu/DEA2 Data Entry Assistant (DEA) 2.0]. Although created for use in the previous version of DEA, much of the procedures and terminology remains the same. This guide includes instructions for formatting specimen records as well as references to facilitate taxonomic name recognition, locality georeferencing, etc.

== General Help ==
* [[Data Transcription Procedures]]
* [[Data Entry Template Information]]
* [[Data Entry Assistant (DEA) 2.0 Procedures]]
* [[Locality Georeferencing and Generation]]
* [[xBio:D Controlled Vocabularies]]

== References ==
* [[Taxonomic Name / Identification Recognition Reference]]
* [[Taxonomic Resources / Catalogs]]
* [[Geographic Resources / Gazetteers]]
* [[State / Province Codes for Countries]]

== Resources ==
* Specimen Data Template: [[File:Data_Entry_Template_28-Aug-2014.xls]]
* Pub-Cited Unvouchered Specimen Data Template: [[File:Data Entry Unv Template 04-Nov-2011.xls]]
* Pre-formatted Data Entry Template: [[File:DEA_data_entry_template-full_28-Aug-2014.xls]]
* Specimen Data Database Lookup: [[File:CUID_Lookup_01-Aug-2014.xlsm]]
* Political Divisions of Countries: [http://www.statoids.com Statoids]

[[Category:Data Entry Assistant]]

Geographic Resources / Gazetteers

2015-07-09T18:57:27Z

Matte: /* Gazetteers */

'''Introduction'''

This page is designed to provide a useful list of country-level or international gazetteers as well as other geographic resources for verifying place names and/or geopolitical units.

== Gazetteers ==
{|
!Name
!URL
!Description
|-
|GEOnet
|[http://geonames.nga.mil/namesgaz/ http://geonames.nga.mil/namesgaz/]
|Find coordinates for places outside of the U.S. as well as the political division it is located within.
|-
|USGS-GNIS
|[http://geonames.usgs.gov/pls/gnispublic/ http://geonames.usgs.gov/pls/gnispublic/]
|Find coordinates for places within the U.S. and its territories as well as on Antarctica.
|-
|WDPA-UN
|[http://www.wdpa.org/ http://www.wdpa.org/]
|Find national parks, reserves & protected areas along with their respective coordinates and areas.
|-
|Fuzzy Gazetteer
|[http://dma.jrc.it/services/fuzzyg/ http://dma.jrc.it/services/fuzzyg/]
|Find places around the world mainly utilizing GEOnet data by performing fuzzy searching. Useful for place name misspellings.
|-
|CGNDB
|[http://www4.rncan.gc.ca/search-place-names/search?lang=en http://www4.rncan.gc.ca/search-place-names/search?lang=en]
|Find coordinates for places within Canada.
|-
|Geoscience Australia
|[http://www.ga.gov.au/map/names/ http://www.ga.gov.au/map/names/]
|Find coordinates for places within Australia.
|-
|Ordnance Survey
|[http://www.ordnancesurvey.co.uk/oswebsite/ http://www.ordnancesurvey.co.uk/oswebsite/]
|Find towns within the UK but no coordinates available.
|-
|streetmap
|[http://www.streetmap.co.uk/ http://www.streetmap.co.uk/]
|Find places within Great Britain but no coordinates available.
|-
|diddlefinger
|[http://diddlefinger.com/ http://diddlefinger.com/]
|Find coordinates for places within Japan in English.
|-
|Geospatial Information Authority of Japan (GSI)
|[http://www.gsi.go.jp/ENGLISH/pape_e300284.html http://www.gsi.go.jp/ENGLISH/pape_e300284.html]
|Find coordinates for places within Japan in English and Japanese (Kanji & Hiragana) (PDF)
|-
|Géoportail
|[http://www.geoportail.fr http://www.geoportail.fr]
|Find coordinates for places within France and its territories.
|-
|NZGPD
|[http://www.linz.govt.nz/placenames/find-names/ http://www.linz.govt.nz/placenames/find-names/]
|Find coordinates for places within New Zealand. New gazetteer is in a spreadsheet but the old resource is a database that is many times more informative.
|-
|INEGI
|[http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx]
|Find coordinates for places within Mexico in Spanish.
|-
|Mapa Digital de México
|[http://gaia.inegi.org.mx/mdm6/ http://gaia.inegi.org.mx/mdm6/]
|Find locations for places and features within Mexico in Spanish.
|-
|GeoDatenZentrum
|[http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html]
|Find coordinates for places within Germany.
|-
|Lantmäteriet
|[http://kso.lantmateriet.se http://kso.lantmateriet.se]
|Find places within Sweden in Swedish but no coordinates available.
|-
|GeoArgentina
|[http://ventas.ign.gob.ar/catalog/searchadv.htm http://ventas.ign.gob.ar/catalog/searchadv.htm]
|Find coordinates for places within Argentina in Spanish.
|-
|BEV
|[http://www.austrianmap.at/amap/ http://www.austrianmap.at/amap/]
|Find coordinates for places within Austria in German.
|-
|Wikimapia
|[http://wikimapia.org/ http://wikimapia.org/]
|Find coordinates for places via user-tagged records around the world. Useful for some obscure places in particular in India.
|-
|HCSO
|[http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer]
|Find places within Hungary but no coordinates available.
|-
|PSGC
|[http://www.nscb.gov.ph/activestats/psgc/ http://www.nscb.gov.ph/activestats/psgc/]
|Find places within the Philippines but no coordinates available.
|-
|Placenames Database of Ireland
|[http://www.logainm.ie http://www.logainm.ie]
|Find coordinates for places within Ireland but coordinates need converted into WGS 84 units.
|-
|Cadastre GeoMeta
|[http://www.geometa.ch http://www.geometa.ch]
|Find coordinates for places within Switzerland but coordinates need converted into WGS 84 units.
|-
|CNIG
|[http://www.cnig.es http://www.cnig.es]
|Find coordinates for places within Spain but coordinates need converted into WGS 84 units. Click on "búsqueda avanzada (advanced search" at the top to search for a place name.
|-
|Stednavne
|[http://www.stednavne.info http://www.stednavne.info]
|Find places within Denmark in Danish but no coordinates available.
|-
|Norgeskart
|[http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1 http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1]
|Find places within Norway in Norwegian
|-
|Catalogo IGM
|[http://www.igmi.org/ware/ http://www.igmi.org/ware/]
|Find coordinates for places within Italy in Italian
|-
|National Land Survey of Finland (NLS)
|[http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en]
|Find coordinates for places within Finland
|-
|Locatienet
|[http://routenet.nl http://routenet.nl]
|Find coordinates for places within the Netherlands. First, search in Route Planner. Then after locating the locality, go back to Route Planner, select GPS above the search, then find the coordinates for the locality.
|-
|Český úřad zeměměřický a katastrální (CUZK)
|[http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx]
|Find coordinates for places within the Czech Republic in Czech
|-
|Instituto Geográfico Nacional del Perú (IGN)
|[http://www.ign.gob.pe/nomenclatorDigital/datos.php http://www.ign.gob.pe/nomenclatorDigital/datos.php]
|Find coordinates for places within Peru in Spanish
|-
|Ministry of Infrastructure and Spatial Planning (MISP)
|[http://prostor3.gov.si/iokno_ang/iokno.jsp http://prostor3.gov.si/iokno_ang/iokno.jsp]
|Find coordinates for places within Slovenia but coordinates need converted into WGS 84 units.
|-
|Mapový klient (ZBGIS)
|[https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en]
|Find coordinates for places within Slovakia
|-
|Geoportal (DGU)
|[http://geoportal.dgu.hr/viewer/ http://geoportal.dgu.hr/viewer/]
|Find coordinates for places within Croatia in Croatian. First, click on "Pretraga" in the left menu, then select the lower search type "Vrsta prostorne jedinice". The upper box "Vrsta prostorne jedinice" is the location type and the lower box "Ime prostorne jedinice" is the location name.
|}

== Geographic Tools ==
{|
!Name
!URL
!Description
|-
|Earth Point
|[http://www.earthpoint.us/Townships.aspx http://www.earthpoint.us/Townships.aspx]
|Convert from U.S. TRS (Township Range Section) designation to WGS coordinates
|-
|The World Coordinate Converter
|[http://twcc.free.fr/ http://twcc.free.fr/]
|Convert most coordinate system into WGS coordinates
|-
|nearby.org.uk
|[http://www.nearby.org.uk/conversions.cgi http://www.nearby.org.uk/conversions.cgi]
|Convert UK and Irish map coordinate as well as other coordinate systems into WGS coordinates
|}

[[Category:Data Entry Assistant]]
[[Category:References]]

Geographic Resources / Gazetteers

2015-07-09T18:56:47Z

Matte: /* Gazetteers */

'''Introduction'''

This page is designed to provide a useful list of country-level or international gazetteers as well as other geographic resources for verifying place names and/or geopolitical units.

== Gazetteers ==
{|
!Name
!URL
!Description
|-
|GEOnet
|[http://geonames.nga.mil/ggmagaz/ http://geonames.nga.mil/ggmagaz/]
|Find coordinates for places outside of the U.S. as well as the political division it is located within.
|-
|USGS-GNIS
|[http://geonames.usgs.gov/pls/gnispublic/ http://geonames.usgs.gov/pls/gnispublic/]
|Find coordinates for places within the U.S. and its territories as well as on Antarctica.
|-
|WDPA-UN
|[http://www.wdpa.org/ http://www.wdpa.org/]
|Find national parks, reserves & protected areas along with their respective coordinates and areas.
|-
|Fuzzy Gazetteer
|[http://dma.jrc.it/services/fuzzyg/ http://dma.jrc.it/services/fuzzyg/]
|Find places around the world mainly utilizing GEOnet data by performing fuzzy searching. Useful for place name misspellings.
|-
|CGNDB
|[http://www4.rncan.gc.ca/search-place-names/search?lang=en http://www4.rncan.gc.ca/search-place-names/search?lang=en]
|Find coordinates for places within Canada.
|-
|Geoscience Australia
|[http://www.ga.gov.au/map/names/ http://www.ga.gov.au/map/names/]
|Find coordinates for places within Australia.
|-
|Ordnance Survey
|[http://www.ordnancesurvey.co.uk/oswebsite/ http://www.ordnancesurvey.co.uk/oswebsite/]
|Find towns within the UK but no coordinates available.
|-
|streetmap
|[http://www.streetmap.co.uk/ http://www.streetmap.co.uk/]
|Find places within Great Britain but no coordinates available.
|-
|diddlefinger
|[http://diddlefinger.com/ http://diddlefinger.com/]
|Find coordinates for places within Japan in English.
|-
|Geospatial Information Authority of Japan (GSI)
|[http://www.gsi.go.jp/ENGLISH/pape_e300284.html http://www.gsi.go.jp/ENGLISH/pape_e300284.html]
|Find coordinates for places within Japan in English and Japanese (Kanji & Hiragana) (PDF)
|-
|Géoportail
|[http://www.geoportail.fr http://www.geoportail.fr]
|Find coordinates for places within France and its territories.
|-
|NZGPD
|[http://www.linz.govt.nz/placenames/find-names/ http://www.linz.govt.nz/placenames/find-names/]
|Find coordinates for places within New Zealand. New gazetteer is in a spreadsheet but the old resource is a database that is many times more informative.
|-
|INEGI
|[http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx http://www.inegi.org.mx/geo/contenidos/geoestadistica/CatalogoClaves.aspx]
|Find coordinates for places within Mexico in Spanish.
|-
|Mapa Digital de México
|[http://gaia.inegi.org.mx/mdm6/ http://gaia.inegi.org.mx/mdm6/]
|Find locations for places and features within Mexico in Spanish.
|-
|GeoDatenZentrum
|[http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html http://sg.geodatenzentrum.de/web_bkg_webmap/applications/webatlasde/webatlasde.html]
|Find coordinates for places within Germany.
|-
|Lantmäteriet
|[http://kso.lantmateriet.se http://kso.lantmateriet.se]
|Find places within Sweden in Swedish but no coordinates available.
|-
|GeoArgentina
|[http://ventas.ign.gob.ar/catalog/searchadv.htm http://ventas.ign.gob.ar/catalog/searchadv.htm]
|Find coordinates for places within Argentina in Spanish.
|-
|BEV
|[http://www.austrianmap.at/amap/ http://www.austrianmap.at/amap/]
|Find coordinates for places within Austria in German.
|-
|Wikimapia
|[http://wikimapia.org/ http://wikimapia.org/]
|Find coordinates for places via user-tagged records around the world. Useful for some obscure places in particular in India.
|-
|HCSO
|[http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer http://portal.ksh.hu/pls/portal/CP.hnt2.gazetteer]
|Find places within Hungary but no coordinates available.
|-
|PSGC
|[http://www.nscb.gov.ph/activestats/psgc/ http://www.nscb.gov.ph/activestats/psgc/]
|Find places within the Philippines but no coordinates available.
|-
|Placenames Database of Ireland
|[http://www.logainm.ie http://www.logainm.ie]
|Find coordinates for places within Ireland but coordinates need converted into WGS 84 units.
|-
|Cadastre GeoMeta
|[http://www.geometa.ch http://www.geometa.ch]
|Find coordinates for places within Switzerland but coordinates need converted into WGS 84 units.
|-
|CNIG
|[http://www.cnig.es http://www.cnig.es]
|Find coordinates for places within Spain but coordinates need converted into WGS 84 units. Click on "búsqueda avanzada (advanced search" at the top to search for a place name.
|-
|Stednavne
|[http://www.stednavne.info http://www.stednavne.info]
|Find places within Denmark in Danish but no coordinates available.
|-
|Norgeskart
|[http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1 http://kart.statkart.no/adaptive2/default.aspx?gui=1&lang=1]
|Find places within Norway in Norwegian
|-
|Catalogo IGM
|[http://www.igmi.org/ware/ http://www.igmi.org/ware/]
|Find coordinates for places within Italy in Italian
|-
|National Land Survey of Finland (NLS)
|[http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en http://kansalaisen.karttapaikka.fi/kartanhaku/osoitehaku.html?lang=en]
|Find coordinates for places within Finland
|-
|Locatienet
|[http://routenet.nl http://routenet.nl]
|Find coordinates for places within the Netherlands. First, search in Route Planner. Then after locating the locality, go back to Route Planner, select GPS above the search, then find the coordinates for the locality.
|-
|Český úřad zeměměřický a katastrální (CUZK)
|[http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx http://nahlizenidokn.cuzk.cz/VyberKatastrMapa.aspx]
|Find coordinates for places within the Czech Republic in Czech
|-
|Instituto Geográfico Nacional del Perú (IGN)
|[http://www.ign.gob.pe/nomenclatorDigital/datos.php http://www.ign.gob.pe/nomenclatorDigital/datos.php]
|Find coordinates for places within Peru in Spanish
|-
|Ministry of Infrastructure and Spatial Planning (MISP)
|[http://prostor3.gov.si/iokno_ang/iokno.jsp http://prostor3.gov.si/iokno_ang/iokno.jsp]
|Find coordinates for places within Slovenia but coordinates need converted into WGS 84 units.
|-
|Mapový klient (ZBGIS)
|[https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en https://zbgis.skgeodesy.sk/tkgis/default.aspx?lang=en]
|Find coordinates for places within Slovakia
|-
|Geoportal (DGU)
|[http://geoportal.dgu.hr/viewer/ http://geoportal.dgu.hr/viewer/]
|Find coordinates for places within Croatia in Croatian. First, click on "Pretraga" in the left menu, then select the lower search type "Vrsta prostorne jedinice". The upper box "Vrsta prostorne jedinice" is the location type and the lower box "Ime prostorne jedinice" is the location name.
|}

== Geographic Tools ==
{|
!Name
!URL
!Description
|-
|Earth Point
|[http://www.earthpoint.us/Townships.aspx http://www.earthpoint.us/Townships.aspx]
|Convert from U.S. TRS (Township Range Section) designation to WGS coordinates
|-
|The World Coordinate Converter
|[http://twcc.free.fr/ http://twcc.free.fr/]
|Convert most coordinate system into WGS coordinates
|-
|nearby.org.uk
|[http://www.nearby.org.uk/conversions.cgi http://www.nearby.org.uk/conversions.cgi]
|Convert UK and Irish map coordinate as well as other coordinate systems into WGS coordinates
|}

[[Category:Data Entry Assistant]]
[[Category:References]]

Locality Georeferencing and Generation

2015-07-01T19:38:34Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''DEA Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 
'''Google''' http://www.google.com/ 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations (always abbreviated):
::“nr.” for near
::“Twp.” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
::"jct." for the junction of two roads
*Things that should not be abbreviated:
::Road
::Avenue
::Vicinity
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made: E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:36:42Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''DEA Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 
'''Google''' http://www.google.com/ 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations (always abbreviated):
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
::Political division types if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.)
*Things that should not be abbreviated:
::Road
::Avenue
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made: E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:34:31Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''DEA Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 
'''Google''' http://www.google.com/ 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations (always abbreviated):
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
*Things that should not be abbreviated:
::Road
::Avenue
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Political division types should be abbreviated if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.).
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*If a locale is contained entirely in an adjacent county to the one present on the label, the adjacent county should be entered in the locality name. In the locality comments a note of this should be made: E.g. "locality is in Alamosa Co. rather than adjacent Costilla Co." or for parks/mountains/ boundary related things "locality is contained in Alamosa Co. rather than adjacent Costilla Co."

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:31:23Z

Matte: /* Georeferencing Tips */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''DEA Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 
'''Google''' http://www.google.com/ 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations (always abbreviated):
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
*Things that should not be abbreviated:
::Road
::Avenue
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Political division types should be abbreviated if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.).
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*E.g. locality is in Alamosa Co. rather than adjacent Costilla Co. or for parks/mountains/ boundary related things locality is contained in Alamosa Co. rather than adjacent Costilla Co.

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:26:34Z

Matte: /* Helpful Resources */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''DEA Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 
'''Google''' http://www.google.com/ 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations:
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Political division types should be abbreviated if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.).
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*E.g. locality is in Alamosa Co. rather than adjacent Costilla Co. or for parks/mountains/ boundary related things locality is contained in Alamosa Co. rather than adjacent Costilla Co.

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:25:39Z

Matte: /* Helpful Resources */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 
'''Google''' http://www.google.com/ 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations:
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Political division types should be abbreviated if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.).
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*E.g. locality is in Alamosa Co. rather than adjacent Costilla Co. or for parks/mountains/ boundary related things locality is contained in Alamosa Co. rather than adjacent Costilla Co.

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:24:27Z

Matte: /* Locality Comments */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''Google''' http://www.google.com/ 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
::*derived from [gazetteer]/WWW
::*xxy is a variant name/alternate spelling/short name/misspelling of xxx
::*“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations:
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Political division types should be abbreviated if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.).
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*E.g. locality is in Alamosa Co. rather than adjacent Costilla Co. or for parks/mountains/ boundary related things locality is contained in Alamosa Co. rather than adjacent Costilla Co.

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:22:36Z

Matte:

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''Google''' http://www.google.com/ 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

=== Locality Comments ===
The locality comments is where any information that helps link the locality to the label is input. Record any discrepancies, concerns, and/or rationales within locality_comments column of the localities worksheet as well. For example if something on the label is spelled wrong, the locality has different names, or the coordinates are derived from a different source.
:Examples of comments:
***derived from [gazetteer]/WWW
***xxy is a variant name/alternate spelling/short name/misspelling of xxx
***“[gazetteer] coords. adjusted to place over land” (if gazetteer puts coordinates in middle of body of water)

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations:
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Political division types should be abbreviated if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.).
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*E.g. locality is in Alamosa Co. rather than adjacent Costilla Co. or for parks/mountains/ boundary related things locality is contained in Alamosa Co. rather than adjacent Costilla Co.

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:19:08Z

Matte: /* Coordinate Source (column: source) */

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''Google''' http://www.google.com/ 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, follow a major road in the specified direction for approximately the specified distance (slightly shorter due to error in exact road tracking) using the measuring tools available in ''Google Earth'' to get a more accurate coordinate. Then, in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS''). In some cases coordinates for the locality will be directly on the specimen label. In this instance, use a gazetteer to verify the locality, but use the coordinates on the label and enter ''label'' as the source.

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations:
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Political division types should be abbreviated if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.).
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*E.g. locality is in Alamosa Co. rather than adjacent Costilla Co. or for parks/mountains/ boundary related things locality is contained in Alamosa Co. rather than adjacent Costilla Co.

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:11:35Z

Matte:

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''Google''' http://www.google.com/ 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, use ''Google Earth'' to get a more accurate coordinate and in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS'').

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

== Georeferencing Tips ==
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations:
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Political division types should be abbreviated if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.).
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*E.g. locality is in Alamosa Co. rather than adjacent Costilla Co. or for parks/mountains/ boundary related things locality is contained in Alamosa Co. rather than adjacent Costilla Co.

[[Category:Data Entry Assistant]]

Locality Georeferencing and Generation

2015-07-01T19:09:26Z

Matte:

'''Introduction'''

This section contains information on the procedures used to find coordinates for collecting localities, known as georeferencing, and the manner on which to format locality names for maximal utility within DEA2 and the xBio:D system. Other locality name formatting and georeferencing methodologies may be used, but a locality name must be unique to a collecting locality, i.e., ''Columbus'' is not an acceptable locality name since it may mean Columbus, Ohio; Columbus, Georgia; or any number of separate towns. Place names are a strictly controlled vocabulary to maintain consistency, and county/municipality, state/province, and country/territory names must match the existing name within xBio:D, which may be checked from [http://hol.osu.edu HOL].

The steps below are broadly informative for producing new localities but are overly concise. Please refer to this georeferencing guide, [[File:Georef_Guid_OSUC.docx]], for more detailed information on the xBio:D preferred georeferencing protocol.

== Helpful Resources ==
'''DEA 1''' http://hymfiles.biosci.ohio-state.edu/DEA/index.html 
'''Google''' http://www.google.com/ 
'''DEA help''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Help 
'''Gazetteers''' http://osuc.osu.edu/osucWiki/Geographic_Resources_/_Gazetteers 
'''Procedures''' http://osuc.osu.edu/osucWiki/Data_Entry_Assistant_%28DEA%29_Procedures 
'''Statoids''' http://www.statoids.com/ 
'''State/Province codes''' http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries 
'''Google Translate''' http://translate.google.com 
'''Google Earth''' 
'''Township information''' http://www.earthpoint.us/TownshipsSearchByDescription.aspx 

== General Georeferencing Information ==
After [[Data Entry Assistant (DEA) 2.0 Procedures#Setting Localities|setting localities]] and [[Data Entry Assistant (DEA) 2.0 Procedures#Extracting / Saving File|extracting the processed file]], the Excel spreadsheet produced by DEA2 contains two new worksheets: ''Main'' and ''Localities''. The ''Localities'' worksheet holds all of the specimen records that were previously skipped for not having a matching locality name in DEA2. For these specimen records, new locality names must be created along with their corresponding locality information. This information includes geopolitical units that contain the collecting locality, properly formed locality name text, and [http://en.wikipedia.org/wiki/World_Geodetic_System WGS 84] coordinate information.

If more than one specimen record has the same locality name, only one record will need to contain the geopolitical hierarchy and the coordinate information but do not forget to copy the locality name for all of the records (see below).
[[File:Localities_sheet.png|none|frame|Localities worksheet]]

== Place Name Identification and Lookup ==
If the current locality is in the United States, ''USGS-GNIS'' is probably the best method for verifying the authenticity of the name, locating the county in which the locality resides, and obtaining the coordinates. Outside of the U.S., many countries have their own gazetteers (see [[Geographic Resources / Gazetteers]]), but in general, ''GEOnet'' is the best way to locate locality information. If a place name potentially is misspelled, use ''Fuzzy Gazeetter'', or simply type the place name and the country into ''Google''. Often ''Google'' will suggest the correct place name.

* '''''Note''''': If a place name on the label does not match the correct name from a gazetteer, make a note of it in the ''locality_comments'' column of the ''Localities'' worksheet. Record any discrepancies, concerns, and/or rationales within ''locality_comments'' column as well.

== Identifying the Geopolitical Hierarchy ==
When the locality information is gathered for a locality, the geopolitical hierarchy also must be obtained for the locality. The reference used for political divisions is a web site named [http://www.statoids.com Statoids] or type the parent division (i.e. country) into [http://hol.osu.edu Hymenoptera Online] and browse the subordinate divisions for the accepted spelling. Regardless of the spelling of the geographic division in ''GEOnet'' or on the label, use the spelling used in ''Statoids'' or ''Hymenoptera Online''. The political division type is the English interpretation of the type unless the division type is in a Romance (French, Spanish, etc.) language (e.g. Indonesian ''Propinsi'' -> ''Province'', Ecuadorian ''Provincia'' -> ''Provincia''). The ''Statoids'' site also provides information on the history of the divisions and alternate divisions which aids in deciphering the current political division for the locality. If a locality is not unequivocally located within a given division, do not use the uncertain division in the geopolitical hierarchy. After obtaining the locality coordinates, the coordinates may be entered into ''Google Earth'' to discover the current political division for the point (available for some countries). Only towns or equivalent can be used in the ''place'' column, thus townships and similar 3rd level divisions should not be part of the geographic hierarchy.

== Locality Name Creation ==

:''[Town / National Park / Reserve], [coordinates on label], [elevation], [field code], [habitat], [generalized locality term], [further locality information], [geopolitical hierarchy]''

The format for newly created locality names is given above, so follow this convention when creating a locality name. If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. ''Parque Nacional Henri Pittier'' -> ''Henri Pittier National Park'', ''Cerro de la Equis'' -> ''Equis Hill'', ''Wadi Saluki'' -> ''Wadi Saluki'' (no English equivalent for ''wadi'')). Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. ''Kruger National Park, South Africa''; ''Skukuza, Kruger N.P., Mpumalanga Prov., South Africa''). Also, if the 1st level geographic divisions for a country have standardized abbreviations as defined in [[State / Province Codes for Countries]], use the state-level abbreviations. In the case of United States localities, omit United States from the locality name and leave the state code at the end. Political division types should be abbreviated if an appropriate abbreviation is available (e.g. ''Province'' -> ''Prov.'', ''State'' -> ''St.'', ''Município'' -> ''Mpio.'', etc.) If the specimen data includes coordinates, include those coordinates in the locality name. As a general rule, always consult locality names that are already in DEA to use as a template for a new locality name. Many new locality names are merely slight derivations of existing localities present in DEA.

== Coordinate / Elevation Information ==
When the coordinates for a locality are found, fill in the coordinate information. This includes ''latitude'' (format: DD MM SS), ''latitude direction'' (N or S), ''longitude'' (format: DD MM SS), ''longitude direction'' (E or W), ''locality precision'' (POINT or POLYGON), ''coordinate source'' (''GEOnet'', ''USGS-GNIS'', etc.), ''elevation'' (in meters), and ''max elevation'' (in meters).

[[File:Locality_coords.png|none|frame|Coordinate information]]

=== Latitude & Longitude (columns: ''lat'', ''lat_dir'', ''long'' & ''long_dir'') ===
The latitude and longitude for the locality can come from the label, a geographic gazetteer, the internet, literature, personal communication with collector, or ''Google Earth''. A coordinate column must be in the format ''DD MM SS'' where ''DD'' are the degrees, ''MM'' are the minutes, and ''SS'' are the seconds. All of the coordinate parts must be a number which may include decimals. Thus, the coordinate, ''16°37.341'N 102°34.467'E'', would have the ''lat'' column as ''16 37.341'', the ''lat_dir'' column as ''N'', long column as ''102 34.467'', and the ''long_dir'' column as ''E''. The directional columns, ''lat_dir'' and ''long_dir'', specify the direction of the coordinates, which can only be ''N'', ''S'' or ''E'', ''W'', respectively. Negative values within a coordinate column are forbidden.

=== Locality Precision (column: ''loc_prec'') ===
There are two types of localities, points and polygons. A point, ''POINT'', is a locality that has a small margin of error for the specified coordinates, while a polygon, ''POLYGON'', is a locality that has a large margin of error. Generally, a locality is a point if the margin of error can be bound to an area smaller than a county. The quantifiable bounding area to use to determine a point is 325 sq. mi. (18 mi. by 18 mi.) Any values defining a specific amount of error for a coordinate are not stored in the database.

=== Coordinate Source (column: ''source'') ===
The resource that was used to obtain the coordinates is the coordinate source. If the coordinates used are directly from a gazetteer, then the source would be the name of the gazetteer used (i.e. ''GEOnet'', ''USGS-GNIS'', ''CGNDB'', etc.) Some localities are specified relative to a place (e.g. ''7mi NW of Columbus''). For these, use ''Google Earth'' to get a more accurate coordinate and in the locality comments specify which source the coordinates were derived from (e.g. ''derived from USGS-GNIS'').

=== Elevations (columns: ''elevation'' & ''max_elevation'') ===
The elevation for a locality is only determined by the elevation given on the specimen label(s). If a single elevation is given, enter that value in '''meters''' into the ''elevation'' column, otherwise, if given as a range, enter the lower value into the ''elevation'' column and the higher value into the ''max_elevation'' column. In order to convert the elevation from feet into meters, simply type this string into ''Google'': ''x ft to m'' where ''x'' is the elevation in feet.

=== Georeferencing Tips ===
*When to use / - or commas:
::/ used to separate habitats and field codes (if there are more than one)
::: Ex: ground litter / cloud forest
::(-) “or” something; can show a range of numbers
::: Ex: oak-pine-soybean
:::: sec. 5-7
::, separate different elements not habitats
::: Ex: Pine Creek, Knob River, etc.
::+ “and” something (not often used)
::: Ex: sec. 5+7
*Township sections should be entered as “sec. x+y” to include two separate adjacent sections, or “sec. x-y” for sections x through y (x and y not adjacent but :collecting may have occurred in intermediate sections). e.g: label: “Defiance Tp. Secs. 5 and 7 Defiance Co. O.” would yield the following locality: Defiance Township, sec. 5+7, Defiance Co., OH
*If the locality is in the USA it ends with the state abbreviation EX: NM, CA, OH
*If the locality is not in the USA, it ends with the full spelling of the country name
*Common abbreviations:
::“nr” for near
::“Twp” for township
::“km” for kilometers
::“mi” for miles
::“m” for meters
::“ft” for feet
*Place names with qualifiers that do not occur as the first element of a locality name may have their qualifier name abbreviated (e.g. Kruger National Park, South Africa; Skukuza, Kruger N.P., Mpumalanga Prov., South Africa)
**Recreational Area/Mountains/etc. is abbreviated if not at the beginning of the locality, but is spelled out if at beginning
**Roads/Avenues/Drives are part of the name of the feature, and therefore should be spelled out.
*Populated places in USGS-GNIS & GEOnet are Towns
*If a feature or place has an English equivalent, use the English equivalent as long as the qualifier is not part of the formal name (e.g. Parque Nacional Henri Pittier -> Henri Pittier National Park, Rio Pisque -> Pisque River, Cerro de la Equis -> Equis Hill, Wadi Saluki -> Wadi Saluki (no English equivalent for wadi)).
*U.S. localities should end with their appropriate state codes (CA, OH, ID, etc.) (not end with United States)
*Political division types should be abbreviated if an appropriate abbreviation is available (e.g. Province -> Prov., State -> St., Município -> Mpio., etc.).
*Brazil, Autralia, Canada, and Mexico use division abbreviations found at http://osuc.osu.edu/osucWiki/State_/_Province_Codes_for_Countries (from the wiki)
*Don’t use statoids for places in Japan – Wikipedia is usually better
*Cities in east Asia mean something very specific (we don’t treat them as towns)
*Directions from localities should be abbreviated (e.g. N of Papallacta, 4km N Sálakos)
*Prefecture is state level in Japan
*East Pakistan is Bangladesh
*W.T. is Washington Territory and should be entered as WA (Washington)
*Sylvania Cal is located in Nevada (already in DB)
*Cols. O is an old abbreviation for Columbus, OH
*Do not add a space between mile/kilometer markers on highways (e.g. mi318, km58). Nor as a direction from somewhere (e.g. 82mi E, 30km W)
*Any uncompleted locality should be highlighted, then add a row at the bottom of the file using the same color highlight to describe the problem. E.g. “can't find anything on Lebang Hara, except that it may be somewhere in West Borneo” and also cite any relevant links that may help in fully determining the locality. Uncertainties can also be pointed out using this system.
*Lowland/ mid-elevation/etc. forest is a qualifier making the term one habitat entity
*Use the “savannah” spelling of the word (vs. savanna) for localities.
*Guano, unless specified (e.g. seagull guano), is a habitat rather than association.
*“Mouse nest” is an association (specific enough, most mice are contained within one genus). “Nest” would be a habitat.
*Barrenando is formally defined as “drilling”, but can be thought of burrowing. As in “barrenando en caña de azucar” which translates to “burrowing in sugar cane”.
*Georef labels with coordinates from Chile collected by Sharkey, Argentina collected by Archangelsky or coordinates on labels collected by C. C. King as if the coordinates weren’t there. (the coordinates on the label were added after the fact and are not necessarily accurate)
*Always abbreviate township to “twp.” for every case.
*Convention for highway outside of US: for a specific name use “Hwy. xx” e.g. Highway 62/Hwy62 would become Hwy. 62. Use “hwy.” for a non-specific name, e.g. nr. hwy., side of hwy. For Highway in US use:
**State highway (white circle) Ex: OH-315
**US highway (white shield) Ex: US-650
**Interstate (blue shield) Ex: I-62
**County road (white square), different based on state Ex: Farm-to-Market Road 791 (Texas)
*“Shores” and “seeps” as in Silver Creek shore/seep should be formatted within a locality as “Shore/Seep of Silver Creek”
*Near should always be abbreviated as “nr.” no matter where it appears in the locality
*The junction of two roads are abbreviated as such: “jct.”. If “Road” appears in the name of either road, it should be not abbreviated.
*Vicinity should not be abbreviated.
*E.g. locality is in Alamosa Co. rather than adjacent Costilla Co. or for parks/mountains/ boundary related things locality is contained in Alamosa Co. rather than adjacent Costilla Co.

[[Category:Data Entry Assistant]]