NATIONAL GEOGRAPHIC NAMES PROGRAM Phase II Compilation GNIS Workshop at COGNA July 25, 2002

1. NATIONAL GEOGRAPHIC NAMES PROGRAMPhase II CompilationGNIS Workshop at COGNAJuly 25, 2002

2. Mission: “ … provide for uniformity in geographic nomenclature and orthography throughout the Federal Government…” Public Law 80-242 U. S. Board on Geographic Names

3. U. S. Board on Geographic Names Promulgation: “…the Secretary shall promulgate in the name of the Board from time to time and in such forms as will carry out the purpose of this Act, decisions with respect to geographic names, and principles of geographic nomenclature and orthography…”

4. Federal Program for Comprehensive Geographic Names Compilation

5. All Features Great and Small! Geographic Names Information System (GNIS)

6. GNIS as a research tool • Official • Complete • Without bias • One name/one feature/one record • Regularly maintained • Dynamic

7. Electronic GNIS Maintenance Program • U.S. Geological Survey – National Mapping Program (1987) • U.S. Board on Geographic Names (1987) • U.S. Forest Service (1998) • National Park Service (1999) • Bureau of Land Management (soon)

8. Phase I • Generally – all named features on the most current, large scale USGS topographic maps were included. Some categories were omitted because more complete and digital lists were available from other sources. The following categories were not collected:

9. Phase I – not collected • Airports • Radio and television towers • Federally administered areas greater than 30 square miles • Major and minor civil divisions

10. Phase I – not collected • Major features too large to be named on 1:24,000 scale topographic maps • Regional, historical, and building names • Roads and highways

11. Phase IA • Geographic names found on the primary and secondary base maps of the U.S. Forest Service (approximately 12,000 maps) not listed on the USGS topographic maps

12. Phase IA • Geographic names found on the charts of the Office of Coast Survey (approximately 1,100 at various scales) not listed on USGS topographic maps

13. Phase II • Available information from official State and local sources, other approved sources, and historical maps and documents • Includes ALL categories except roads and highways

14. Base Map Series • USGS 1:24,000 or 1:25,000 scale topographic maps are the base map series for the United States and the National Geographic Names Project • All names and variant names collected MUST be related to either the conventional or digital version of these topographic maps

15. Base Map Series • All locative data must be measured and determined from these maps, except for some large areal features • All names on these topographic base maps may be assumed to be in GNIS

16. GNIS data requirements • Donotchange the name of a record with a BGN date or US date in Federal Status field • Record comments in the Remarks field • GNO will investigate and make changes

17. GNIS data requirements • Features under BGN purview will require a DGNR to change the feature name • Exception! Small tanks and springs may be changed as field research indicates • It may be possible to expedite the process via SPN procedures

18. GNIS data requirements • All feature names and variant names must have a bibliographic code • Bay of Chesapeack (MD-T2/p6) • Old Mitchell Mountain (US-M120) • The bibliographic code indicates the source from which that feature name or variant name was obtained

19. GNIS data requirements • Remember that the bibliographic code must remain with the name if the name is moved • From feature name to variant name • From variant name to feature name • Never change a bibliographic code • Error? Record comments in Remarks

20. GNIS data requirements • For a feature name, the bibliographic code will be listed without parentheses • Feature Name: Chesapeake Bay • Biblio code: US-M120 • For a variant name, the bibliographic code will be enclosed within parentheses • Var Name: Bay of Chesapeack • Var Biblio Code: (MD-T2/p6)

21. GNIS data requirements • One feature/one name/one record – no exceptions • One set of coordinates on the feature on each 1:24,000- or 1:25,000-scale map in which the feature exists More on what a primary point is later.

22. GNIS data requirements • The first coordinate in the record is always the primary point of the feature and, thus, determines the primary state and primary county 

23. GNIS data requirements • Minimum required data elements for all records • Feature Name • Bibliographic code • Feature type (feature class) • Primary State / County • Primary Point – coordinates in DMS or “Unknown” • Mapname (determined by the coords)

24. GNIS data requirements • Minimum required data for other conditions • If the feature type = valley, stream or arroyo, then add source coordinates • If the feature type = summit, ppl or hospital, then add elevation in feet

25. GNIS data requirements • Minimum required data for other conditions • If the feature is located on other maps, then, secondary coordinates and mapname(s) and secondary state(s)/county(ies) • Valleys, streams & arroyos – in sequence from mouth to source – (up stream) • Areal features – parks, national forests, etc. – ensure complete coverage 

26. GNIS – Primary point • The primary point is always the first coordinate in the record • For linear features, valleys, streams and arroyos: the mouth • For canals, tunnels and trails: the center • For areal features: the center 

27. GNIS – Primary point • For summits, ranges: the highest point • For lakes: the center • For reservoirs: the center of the dam • For ppls: center of original settlement or central major intersection • For “point” features: …

28. GNIS – Primary state & primary county • Primary State/County • The primary state and primary county are determined at the location of the primary point

29. GNIS – Source Coordinates • Source Coordinates – Heads • For all linear features - streams, valleys and arroyos • The longest straightest branch • May be located on the same map as the primary point

30. GNIS – Source Coordinates • Source Coordinates – Heads (cont) • Never located on the same map of any other secondary coordinate, only the primary map, if applicable • Always the last coordinate • Always the highest sequence number

31. Feature Points Cells (quadrangles) 7.5 7 6 PointFeature 7.5 1 8 5 4 7 6 3 2 2 1 5 Linear Feature Areal Feature 3 1 4 1 = Primary Point  > 1 = Secondary Points

32. GNIS – Elevation • Elevation – in feet only • Required for all summits, ppls and hospitals with known coordinates • Interpolate the value from the contours if not labeled • Elevation determined at the primary point

33. GNIS – optional data • Highly desirable • Elevation • STR • History • Description • Size 

34. GNIS – optional data • Elevation – for other feature types • Locate at the primary point • STR – section(s), township, range • sec 7,T50N,R30W,Fifth Principal Mer • secs 12&13,T36N,R15N,Fifth Principal Mer • Tps14&15S,Rgs22&23W,Fifth Principal Mer 

35. GNIS – optional data • History – chronological history or name origin • Established 1894 • ‘Aconye’ is derived from the Apache word ‘Akonye’ meaning ‘people of the canyon’ • Named for Rosse Carr, former owner of the island • Destroyed by fire in 1954 

36. GNIS – optional data • Description • Location relative to other features • Located 4 mi N of … and 10 mi E of … • Informational • Inundated by Lake Mead • Destroyed by fire • Abandoned 

37. GNIS – optional data • Description • To note some parameters of the record during data compilation, usually for incomplete records • Incomplete record • Source not determined • Secondary point(s) not complete • Elevation not determined • Primary point not determined, located in Canada 

38. GNIS – optional data • Size • Length and/or breadth • 150 feet long by 200 feet wide • 10 miles long • Acreage of feature • 4,251 acres

39. Compiling map by map vs compiling by feature • Compilation for most features can usually be completed using only one map • However, if a feature extends onto other map(s), one must determine whether a new GNIS record is required or if a current record needs coordinates and/or state(s)/ county(ies) added for the current map

40. Compiling map by map vs compiling by feature • Large areal features may be compiled more easily on small scale maps • The basic series maps will be needed to accurately locate feature boundaries near map edges • Ensure that the small scale map depicts the correct boundaries for the feature which is being compiled 

41. Compiling map by map vs compiling by feature • Once the primary point, primary state and county are determined, it may be possible to compile all the rest of the required data elements map by map, especially linear features • Use Description and carefully list applicable record parameters • Otherwise, compile the record using all maps at once

42. GNIS Web Entry and Web Edit sites • New Record Entry Form – Ver 4.1 • http://geonames.usgs.gov/pls/gnis/data_entry_form.data_entry_logon • Feature Edit Form - Ver 2.1 • http://geonames.usgs.gov/pls/gnis/v2_edit.t_forest_edit_logon

43. Determining which features require new records or editing • Obtain a listing of all features on the map being compiled or annotate the map • Using the Feature EditForm, search by cell name and state and print the list • Compare the map and listing to determine which features on the map are already in GNIS 

44. Determining which features require new records or editing • Identify the features whose records do not require editing • Optional data may be changed or added as indicated, but avoid changing optional data items for BGN records – use Remarks 

45. Determining which features require new records or editing • Identify the features whose records require editing • Name change – Edit - see Ex 1 & Ex 2 • Name error – Edit - see Ex 3 • Add coords – Edit - see Ex 4 • Delete coords – Edit - see Ex 5 • Change State/County – Edit - see Ex 6 

46. Determining which features require new records or editing • Identify the features with no records in the listing, mayormaynotrequireanewrecord_ • Feature located wholly on the map – New record - see Ex 7 • Feature crosses map boundary, search GNIS by the name and/or other criteria 

47. Determining which features require new records or editing • If the search returns no record – see Ex 8 & Ex 9 for new records • If the search returns a record for the feature, add coordinates and/or other data – Edit - see Ex 3 • We recommend, initially, that the data be recorded on a form

48. Name changes in GNIS • Records under BGN purview cannot be changed unilaterally • Exception! Small tanks and springs may be changed as field research indicates, but by SPN procedures • All new names and variant names must have a biblio code

49. Specific examples to be discussed today • Ex 1, Edit – The Name changes – the new name is not a variant • Ex 2, Edit – The Name changes, a variant name becomes the feature name • Ex 3, Edit - Name error(s) on listing

50. Specific examples to be discussed today • Ex 4, Edit - Adding secondary coordinates to a record already in GNIS • Ex 5, Edit - Deleting coordinates to a record already in GNIS • Ex 6, Edit - Adding secondary State(s) and/or County(ies) to a record already in GNIS 