Code of Maine Rules › 18 - DEPARTMENT OF ADMINISTRATIVE AND FINANCIAL SERVICES › 127 - MAINE LIBRARY OF GEOGRAPHIC INFORMATION BOARD › Chapter 158 - STANDARDS FOR DIGITAL PARCEL MAPS › Appendix 127-158-A

Current through 2024-29, July 17, 2024
DATA STANDARDS FOR
MAINE GEOGRAPHIC INFORMATION SYSTEMS
Presented to the Information Services Policy
				  Board
by
GIS Executive Committee Chair, Richard Dressler
June 27, 2002
Approved by the ISPB
June 27, 2002
1.
INTRODUCTION
This document provides guidelines covering the digital
				  conversion of geospatial data into geographic information system (GIS) format.
				  The overall goal is to ensure that a high quality, well-documented GIS database
				  is built for the State of Maine. The document objectives are three-fold:
1. Set technical specifications for geospatial data
				  automation and development;
2. Provide basic guidance in map compilation/recompilation;
				  and
3. Provide standard procedures for documenting the history of
				  each geospatial data layer and source map to aid users of the Maine GIS
				  database in determining the viability of those data for specific applications.
All proposals, agreements, contracts and grants for GIS data
				  automation should require that these standards be met or exceeded.
If agencies are planning projects that will generate large
				  amounts of digital data, it is recommended that a pilot project be performed on
				  a small area covering all aspects of the process from map compilation to the
				  actual application. A pilot project insures that all systems and procedures
				  used do in fact generate adequate data. The project should cover at least two
				  study area modules (e.g. quad sheets) so that edge matching capabilities can be
				  assessed. GIS personnel should participate in all aspects of the pilot
				  project.
2.
MAP COMPILATION/RECOMPILATION
The ultimate quality of a GIS database is as dependent on the
				  quality of the source map as it is on the care used in the digital automation
				  process. Whether new map data are being compiled onto a basemap or old maps are
				  being recompiled onto a new base, certain basics need to be addressed. Precise
				  automation procedures, although very important, will not improve an inferior
				  source map. Georeferenced, rectified photographs and images, as well as vector
				  basemaps may serve as source maps. Important considerations are:
2.1 Map Scale
o Varies with intended use and companion data layers
o Data submitted for inclusion in the Maine GIS database will
				  conform to National Map Accuracy Standards (NMAS) for scale.
The choice of a basemap is the first step in the map
				  compilation/recompilation process. Mapped data at any scale may be input to the
				  system, but digital maps retain the accuracy of their original source map
				  regardless of the scale at which they are plotted. Thus, a 1:100,000 map
				  retains its original accuracy even when plotted at a 1:24,000 scale. The map
				  scale also determines the best use of the final data. The following table
				  illustrates how applications vary depending on the scale of the original
				  map.
TABLE 1: Relationship among scale, use, and number of
				  maps
MAP SCALE
MAP UTILITY
# MAP SHEETS
							 TO COVER MAINE
Small scale
1:500,000
Statewide studies, planning
1
1:250,000
Statewide studies, planning
13
1:100,000
Regional studies,
							 planning
35
1:62,500
Detailed studies, local planning
appx. 200
1:24,000
Detailed studies, local planning
appx. 800
1:12,000
Parcel level studies, detailed
							 local planning
appx. 3,200
1:5,000
Parcel level studies
appx.
							 18,400
Large scale
USGS 7.5 minute quadrangle series have served as the standard
				  digital basemap for agency data development since 1990. The 1:24,000 scale
				  properly balances the economic and accuracy considerations of data development
				  for most planning and natural resource activities. Basemaps of larger scales or
				  different sources may be considered, but the decision must be carefully judged
				  relative to the intended use, the scale of currently available digital data and
				  the proposed basemap's quality.
Data submitted for inclusion in the Maine GIS database will
				  conform to National Map Accuracy Standards (NMAS). For maps on publication
				  scales larger than 1:20,000, not more than 10% of the points tested will be in
				  error by more than 1/30 inch, measured on the publication scale; for maps on
				  publication scales of 1:20,000 or smaller, 1/50 inch. The following table shows
				  the NMAS for some common map the scales:
TABLE 2: Common Scales and NMAS horizontal accuracy
				  requirements
Scale
Engineering
							 Scale
NMAS
Feet
Meters
1:500,000
1" = 7.89 miles
+/-
							 833.33
appx. 254
1:250,000
+/- 416.66
appx.
							 127
1:100,000
+/- 166.67
appx. 51
1:63,360
1" = one mile
+/- 105.60
appx. 32
1:24,000
1" = 2000'
+/- 40.00
appx. 12
1:12,000
1" = 1000'
+/- 33.33
appx. 10
1:4,800
1" = 400'
+/- 13.33
1:1,200
1" = 100'
+/- 3.33
appx. 1
A map resulting from the combination of two or more maps,
				  photographs, or images of differing scale retains the accuracy of the least
				  accurate source map. It is, therefore, important to consider the scales of data
				  layers you expect will be most commonly used with the maps being prepared when
				  choosing a scale for your data. This will have a bearing on both the technical
				  and economic aspects of a project.
2.2 Map Media
o Stable-base mylar
Whenever possible, the mapped data should be drafted on the
				  most scale-stable medium available. Shrinking and swelling in non-stable base
				  media due to changes in atmospheric conditions can have a profound effect on
				  the spatial accuracy of the final digital product. The following represents,
				  from most to least desirable, the media to be used as the mapped data source
				  for automation:
1. Mylar original
2. Mylar contact reproduction from mylar original
3. Non-stable base paper from mylar original
4. Non-stable base paper
Manuscript maps should not be folded. They should be stored
				  in flat files or rolled up in map tubes.
2.3 Coordinate Reference
o Minimum of four reference points
Each map, photograph or image included in the Maine GIS
				  database through digitizing or other means must have a minimum of four
				  reference points (tics) for which the geographic coordinates are known and are
				  printed on the map. Coordinates may be latitude/longitude pairs, or other units
				  consistent with the projection of the map. If no coordinate reference is
				  provided on the map, reference points must be calculated. Increasing the number
				  of "quality" reference points will increase the accuracy of the
				  registration.
2.4 Projection
o Projection of a map must be known and defined.
Prior to digitizing, and for later digital manipulation of
				  map information, the projection of a map must be known. Maps are printed in
				  many different projection systems. For example, most U.S. Geological Survey
				  maps at 1:24,000 and 1:62,500 scales are in the Transverse Mercator or
				  polyconic projection, although many other projection systems can be handled by
				  current GIS technologies. Once in digital form, a map can be transformed from
				  one projection to any other. The current standard projection for data in the
				  Maine GIS database is Universal Transverse Mercator (UTM), North American Datum
				  1983 (NAD83), Zone 19, Meters. To facilitate inclusion in the Maine GIS
				  database, data should be submitted in this standard projection and projection
				  should be defined.
2.5 Line Work
o Maximum line width of 0.013 inch
Lines to be digitized will be drafted with a standard 00
				  technical drafting pen producing a line width of no more than 0.013 inch Lines
				  that are too thick introduce subjectivity on the part of the digitizer
				  operator.
2.6 Coincident Features
o Compile/recompile coincident features to avoid topological
				  error.
Coincident features are those that are common to two or more
				  data layers. For example, the mean high water mark of a pond may serve as a
				  boundary for a residential zone, a soil type, and a wildlife management area;
				  the mean high water mark, soil boundary and management area boundary are
				  coincident features; therefore, coincident features should be digitized only
				  once. Regardless of the care taken in digitizing, slight differences may lead
				  to problems with small "slivers" if the layers are topologically joined. To
				  avoid this phenomenon, use and reuse coincident features in new data layer
				  development.
Coincident features should be clearly symbolized and labeled.
				  During manual map compilation or recompilation a coincident feature should be
				  symbolized in drafting and labeled by source. A standard method is to draft
				  coincident features with a dashed line. If a coincident feature is to be
				  extracted from an existing digital map and added to a new digital data layer,
				  it should be attributed with information on the source from which it is
				  extracted. Dashed line symbology may also be incorporated as an attribute value
				  to allow the feature to be displayed and/or selected as a coincident
				  feature.
2.7 Data not Recompiled on Standard
				  Basemaps
In some cases it may not be feasible to recompile existing
				  data on a standard basemap. The preparation of these data for entry into the
				  Maine GIS database must be considered on a case-by-case basis with GIS
				  personnel. The issues of media, coordinate reference, projection, and line work
				  are particularly important under those circumstances.
3.
DATA AUTOMATION SPECIFICATIONS
3.1 Automation Technique
o Features automated by heads up digitizing will be
				  attributed with information on the source, and the process, used to add the
				  feature to the data set and will equal or exceed NMAS standards for scale, of
				  the original map, photograph, or image.
Tablet digitizing and scanning are currently the most
				  commonly used techniques for automating maps. The selection of an automation
				  technique depends on issues such as the complexity and quality of the source
				  map, type of scanner, and the number of maps.
Data automation by heads-up digitizing has become more common
				  with the increased availability of online scanned high resolution imagery. This
				  is an interactive process in which data is created using previously scanned and
				  georeferenced images such as scanned topographic sheets or photography. The
				  process is similar to conventional tablet digitizing, but rather than using a
				  digitizing tablet and a cursor, the user creates the data layer on the screen
				  with the mouse and typically with referenced imagery as a background. The
				  attention of the user is focused up on the screen, and not on a digitizing
				  tablet. The accuracy of heads-up digitizing as a method of data automation
				  depends on the type of image being used and the experience of the operator. For
				  example, drafting features from a scanned topo sheet is easier to do with
				  precision because the features have already been cartographically interpreted
				  and drawn. By contrast, accurate drafting of features from a photograph
				  requires the use of more photo-interpretation skill.
3.2 Compatibility
o Final format will be compatible with this standard.
As Maine's state government GIS network evolves, emerging
				  systems will use ARC/INFO or will be fully compatible with ARC/INFO through a
				  common data interchange format so existing digital spatial data can be
				  shared.
Therefore, all data developed for the Maine GIS database must
				  be in a format that is easily converted to an interchange format compatible
				  with other components of the statewide GIS.
3.3 Digitizer Tolerances
o Strictly follow software and hardware vendor guidelines for
				  digitizing
There are several digital tolerances which affect the
				  accuracy and resolution of a digital map that can be explicitly defined during
				  the map automation process. The tolerances recommended by the vendor should be
				  strictly adhered to when digitizing or editing data on a particular
				  system.
o RMS error not to exceed 0.005
The Root Mean Square Tolerance (RMS) defines the error
				  incurred when predefined tics are used to register a map on the digitizing
				  board for automation. In order to maintain the spatial relationship of map
				  features during digitizing, the RMS error must be kept as low as possible when
				  a map is registered on the digitizing table. The recommended maximum RMS error
				  is 0.005.
o Tolerance equivalent to 0.005 digitizer units
The tolerance defines the minimum distance separating line
				  coordinates, and the tolerance set corresponds to the resolution of the
				  digitizer.
3.4 Cartographic Accuracy
o Digitize map features to within the equivalent of 0.01
				  inches of the original manuscript.
Digitizing spatial data involves taking a hard copy map and
				  tracing it with a cursor to produce a digital file. Errors and distortions can
				  easily occur in the tracing process. These errors are often small or
				  negligible, but this may not always be the case. Careful, consistent and
				  systematic digitizing, plus thorough verification are essential to adequately
				  retain the quality of the source maps.
o Scanned data will be georeferenced and vectorized to within
				  the equivalent of 0.01 inch of the original manuscript
o Data collected with Global Positioning System (GPS)
				  equipment will have an accuracy equal to or greater than the base data to which
				  it will be added.
Base stations and differential correction should be used to
				  maximize the accuracy of GPS data collection. An accuracy assessment and
				  documentation of method, collection parameters, and technology that affect data
				  accuracy should be provided with the data.
Required standards for feature accuracy are:
o 90 percent of the planimetric features on the digital map
				  will be within 0.01 inch of the centerline of that feature on the manuscript
				  map when plotted at the original scale.
o 100 percent of all features will be within 0.02
				  inch.
The 0.01 inch interval is equivalent to a standard 0.01
				  plotter pen width. When a proof hardcopy plot of the digital map is overlaid on
				  the original basemap, discrepancies in line work will be seen as an open space
				  between the plotted feature and the original manuscript. Discrepancies in point
				  data are more difficult to judge.
It should not be assumed in conversion between data formats,
				  i.e. shapefile to coverage or coverage to SDE layer, that cartographic accuracy
				  will be preserved. Careful management of tolerances and precision of the work
				  environment will greatly improve the results of such a conversion and the
				  conversion process should be documented.
3.5 Data Capture
o Use a minimum number of coordinates to define a
				  line.
Storing many layers of statewide digital data requires
				  efficient use of available computer storage, so digitize the minimum number of
				  vertices needed to accurately represent the cartographic feature within the
				  0.01 inch accuracy limit.
o Digitize the exact center of a point map symbol
If possible, point locations should be entered directly into
				  the system for exact known coordinates such as latitude and longitude rather
				  than by digitizing. When digitizing points from a source map, digitize the
				  exact center of the point map symbol.
3.6 Spatial Topology
o No overshoots
o No slivers
o No open polygons (e.g. undershoots)
o No label errors
o No unresolved node errors
o No unresolved line segment intersections
Digital data submitted for inclusion in the Maine GIS
				  database will be topologically clean and free of errors. All points, lines, and
				  polygons will have a single unique user-id number. Figure 1 shows graphic
				  examples of acceptable and unacceptable topological conditions.
FIGURE 1: Graphic examples of unacceptable and
				  acceptable topological data conditions for digital data
Topologically Topologically
Unacceptable
Acceptable
Click here
				  to view Image
Click here
				  to view Image
3.7 Edge Matching
o Contiguous features should be edge matched or
				  closed.
Line segments (arcs) that intersect the boundaries of a
				  coverage must be accurately edge matched with the corresponding arcs in the
				  adjacent coverages. Computer edge matching techniques ensure an exact match. In
				  lieu of an exact match, arcs must be matched to within 0.01 inch, centerline to
				  centerline.
o Closure lines should be attributed as "closure".
In the absence of more accurate data, where edgematching line
				  segments from adjacent coverages would move a feature or features a distance
				  that exceeds NMAS standards for scale, the addition of a closure line is the
				  preferred. A closure line is an arbitrary feature drawn to close a polygon or
				  arc. Features that represent closure lines should be attributed
				  accordingly.
o Map features should not to extend beyond prescribed dataset
				  boundaries.
Arcs must not extend beyond (overshoot) nor fall short of
				  (undershoot) the dataset boundary.
3.8 Coding Accuracy
o 99.5 percent of all attributes will be coded
				  correctly.
The most serious problem is miscoding a feature. Coding an
				  area of glacial till as a sand and gravel deposit is an example of this type of
				  error. Other errors in attribute coding include any occurrence of misspelling
				  or omissions. All attributes will be coded correctly.
3.9 Accuracy Assessment
The following assessments will measure data accuracy:
o 90 percent of all features within 0.01 inches when
				  reproduced at the scale of original manuscript map
o 100 percent of all features within 0.02 inches when
				  reproduced at the scale of original manuscript map
o Topology complete and accurate
o 100 percent of all attributes coded correctly
It is the responsibility of the producing agency to verify
				  that the original data have been encoded within the accuracy limits set by
				  these standards. Ninety percent of the cartographic features on a map will be
				  digitized within 0.01 inches measured from the centerline or center point of a
				  feature. One hundred percent of all cartographic features will be digitized
				  within 0.02 inches.
There are many ways to formulate a scheme to assess data
				  accuracy. Methodology to assess data accuracy should be developed with the
				  automation contractor or within the producing agency if data are automated in
				  house.
If all criteria are met, then note in the documentation (next
				  section) that the digital map meets these standards.
3.10 Proof Plots
o Mylar proof plots
o Pen width - 0.01 inch
For each digital map created, a mylar proof plot of that map
				  should be made to verify that the original data have been digitized within the
				  accuracy requirements of these standards. The proof plot should be plotted on
				  mylar at the same scale as the manuscript. All lines on the proof should use a
				  linewidth of 0.01 inch or less and be drawn with liquid ink pens. Point data
				  should be represented with the "+" symbol.
3.11 Attribute Coding
o Choose attribute coding schemes that are well defined and
				  in common use.
o Names of new datasets should not be the names of existing
				  datasets in the Maine GIS database.
o Begin all dataset names, item names, and attribute codes
				  with a letter.
o Eliminate punctuation, i.e. hyphens, pound signs, periods
				  from dataset names, item names and attribute codes.
o Limit the length of dataset names and item names to 8
				  characters or digits.
o Define items according to intended use, i.e. numeric data
				  types for statistical data or for data that will be used for calculation,
				  characters data types where these functions are not anticipated.
o Limit the length of attribute codes to 12 characters or
				  digits.
o Eliminate the use of the Boolean values 0 and 1 as
				  attribute codes.
o Wherever practicable utilize character attribute codes,
				  i.e. previously defined acronyms or abbreviations in common use.
Naming conventions, item length, and punctuation
				  recommendations are based on format conversion and compatibility requirements.
				  For example, conversion to shapefile format changes some characters ( # - .) to
				  underscores; item names over 8 places are truncated; the Boolean values 0 and 1
				  impact the results of geographic analysis. An effort will be made over time to
				  consider these limitations in item names and to eliminate the use of these
				  characters in data included in the Maine GIS database.
o Use Standard Geocodes for Maine.
As an information service to state agencies and the public,
				  Standard Geographic Codes for Maine, are available for download through the
				  Maine Office of Geographic Information Systems (MEGIS) Data Catalog. The
				  published table contains the first official Standard Geographic Code endorsed
				  and adopted by the Governor of Maine, on July 1, 1971. Geocodes have undergone
				  subsequent revisions, all of which were "officially" rolled back to this 1971
				  list by Maine's Information Services Policy Board (ISPB), as of January 2000.
				  In 1971, all Maine state agencies were requested to implement these five digit
				  geocodes, in agency information systems, to build a base of data for Maine's
				  Minor Civil Divisions (MCDs) and to promote data sharing. Data coded by MCD may
				  subsequently be summarized by any other type of region, administrative
				  district, natural area, etc. The first two digits of the geocode represent the
				  federal code (FIPS) for Maine counties, the remaining three digits uniquely
				  identify each of Maine's MCDs and Reservations.
Prior to the development of important new data sets, a
				  detailed series of data layer specific content standards that expand on
				  existing standards should be completed. Attribute coding and content for all
				  new data sets will expand on adopted standards and reflect coordination with
				  federal and regional content standards. For example, coding of a soils database
				  will follow the conventions of the USDA Soil Conservation Service. Nationally
				  recognized formats also exist for coding of data layers such as wetlands and
				  land use. When devising a new scheme, it is important to allow for as many
				  different foreseeable uses of the data as possible. For example, in a land use
				  coding scheme, it is preferable to have individual codes for different types of
				  agricultural use (e.g. cropland and pasture) than a single code specifying
				  agricultural use. The individual codes may be aggregated, but the single code
				  cannot be broken into its components.
3.12 Database Attributes
o Add and properly define a database field to store a
				  standard geographic reference.
Standard geographic reference exist at all levels of
				  government and in the private sector, for example the U.S. Board of Geographic
				  Names responsible for the Geographic Names Information System(GNIS), the
				  National Bureau of Standards, Federal Information Processing Codes (FIPS). Many
				  Maine state agencies maintain standard geographic reference information
				  relating to their programs. Examples include the Maine State Planning Office,
				  Standard Geographic Codes for Maine Minor Civil Divisions (GEOCODES), Maine
				  Bureau of Parks and Lands, Coastal Island Registry (CIREG), Maine Inland
				  Fisheries and Wildlife Maine Information Display and Analysis System (MIDAS).
				  An effort is ongoing to promote the standardization of database attributes by
				  working with agencies who serve as primary sources for geographic references.
				  To take full advantage of Maine's growing capability to process, analyze and
				  display geographic information, databases developed within state government,
				  whose records relate to a geographic feature, should include a minimum of one
				  field that stores a related standardized geographic reference from a primary
				  source, such as:
o Standard Geocode for Maine Minor Civil Divisions
o Federal Information Processing Standard or FIPS Code
o Latitude and longitude to the nearest second
o Universal Transverse Mercator Eastings and Northings to 6
				  and 7 digits, respectively.
o Coastal Island Registry Number
o MIDAS Number
o Tax Map Identifier and Lot Identifier
o Street Address
Georeferenced databases can be linked in the GIS environment
				  for analysis and display with the spatial data that makes up the Maine GIS
				  database. Georeferences can be very specific, for example: latitude and
				  longitude locations for storage tanks and hospitals. Some data, for example
				  disease occurrences or demographic data, can be assigned a less specific
				  georeference like a geocode or a census geographic unit. Many phenomena can be
				  mapped including: bus routes and school bus stops, chemical and oil spills,
				  contamination, hazardous material locations, storage tanks, administrative
				  districts, emergency service locations, disease occurrences, demographic
				  characteristics, clients, services, natural and biological resources.
4.
FGDC DOCUMENTATION
o Federal Geographic Data Committee (FGDC) compliant
				  documentation is required for all data to be included in the Maine GIS
				  database
.
The FGDC Content Standard for Digital Geospatial Metadata
				  (CSDGM) has been adopted by the GIS EC as the documentation or "metadata"
				  format for all data included in the Maine GIS database. Participating agencies
				  are responsible for providing documentation in FGDC compliant metadata format
				  for geospatial data products. The metadata must be stored and maintained by the
				  agency developing and maintaining the geospatial data.
FGDC metadata is the required documentation of all geospatial
				  data productsproduced through partnerships, grants or contracts with federal
				  agencies. Federal agencies collecting or producing geospatial data, either
				  directly or indirectly (e.g. through grants, partnerships, or contracts with
				  other entities), are required to ensure, prior to obligating funds for such
				  activities, that data will be collected in a manner that meets all relevant
				  standards adopted through the FGDC process. (Executive Order 12906, published
				  in the April 13, 1994, edition of the Federal Register, Volume 59, Number 71,
				  pp. 17671-17674. COORDINATING GEOGRAPHIC DATA ACQUISITION AND ACCESS: THE
				  NATIONAL SPATIAL DATA INFRASTRUCTURE)
Metadata is "data about data". Like a style guide, the FGDC
				  CSDGM defines what information belongs in a metadata record and the order in
				  which it is presented. The goals and objectives of Maine's FGDC compliant
				  documentation can be summarized as follows:
1. to provide a history of each geospatial data set included
				  in Maine's GIS database with standardized information on content, location,
				  purpose, accuracy, condition, quality, collection and development processes,
				  scale, projection, feature attribution, and other characteristics of geospatial
				  data necessary to determine the utility of a map for a specific purpose;
2. to protect Maine's investment in geospatial data by
				  minimizing the risk of data loss, and minimizing the recreation of existing
				  data, through systematized documentation of geospatial information; and
3. to promote data sharing by providing information about
				  Maine geospatial data holdings to external catalogues, clearinghouses, and
				  brokerages and by providing information on the processing and interpretation of
				  spatial data received through a transfer from an external source.
4.1 Basics of FGDC
FGDC compliant documentation or metadata tells you the who,
				  what, why, how, when and where of geospatial data. The standard organizes a
				  metadata record into seven main sections.
o Identification Information
o Data Quality Information
o Spatial Data Organization Information
o Spatial Reference Information
o Entity and Attribute Information
o Distribution Information
o Metadata Reference Information
4.2 Technical Support for FGDC
Technical support for content development of FGDC metadata
				  and information on FGDC compliant software for metadata development is
				  available through the MEGIS, Data Center, Technical Support phone line at (207)
				  287-6144. A link to additional FGDC resources is available under "Standards and
				  Guidelines", MEGIS homepage,
http://apollo.ogis.state.me.us
.
4.3 More About FGDC
Maine FGDC compliant metadata is published through the MEGIS
				  internet Data Catalog. FGDC metadata documents are also the basic components of
				  the National Geospatial Data Clearinghouse, and FGDC compliant metadata for
				  Maine's geospatial data can be made available to clearinghouse nodes
				  nationwide. The National Geospatial Data Clearinghouse is a distributed online
				  catalog of digital spatial data, part of the National Spatial Data
				  Infrastructure (NSDI) (Executive Order 12906). NSDI goals are to reduce
				  duplication of effort among agencies, improve quality and reduce costs related
				  to geographic information, to make geographic data more accessible to the
				  public, to increase the benefits of using available data, and to establish key
				  partnerships with states, counties, cities, tribal nations, academia and the
				  private sector to increase data availability.
REFERENCES
Arkansas State Land Information Board, 2001. Standards for
				  Collecting Mapping Grade Global Positioning System Positions. Arkansas
				  Legislative Subcommittee on Rules & Regulations, Arkansas State Land
				  Information Board. Little Rock, Arkansas. More information on this document is
				  available at
http://www.gis.state.ar.us/LIB/GPS.htm
.
Department of Conservation, 1989. Interim Geographic
				  Information System Policies and Quality Standards. Department of Conservation,
				  Augusta, Maine.
Environmental Data Center, 1988. Digital Database Standards
				  for the Rhode Island Geographic Information System. Department of Natural
				  Resources Science, The University of Rhode Island, Kingston, Rhode
				  Island.
EOEA Data Center, 1987. Draft Data Standards for the
				  Massachusetts Executive Office of Environmental Affairs Geographic Information
				  System. EOEA, Boston, Massachusetts.
Federal Geographic Data Committee. Content Standard for
				  Digital Geospatial Metadata Workbook Version 2.0. Federal Geographic Data
				  Committee. Washington, D.C.
Federal Geographic Data Committee. FGDC-STD-001-1998. Content
				  Standard for Digital Geospatial Metadata (revised June 1998). Federal
				  Geographic Data Committee. Washington, D.C.
Maine Geographic Information System, 1990. Data Standards for
				  Maine Geographic Information Systems. Maine Department of Conservation,
				  Augusta, Maine.
Maine Office of Geographic Information Systems, 2000. Maine
				  Geographic Codes for Minor Civil Divisions (GEOCODES). Maine GIS Technical
				  Group subcommittee report, additional information on this initiative and other
				  Maine GIS recommendations is available at
http://apollo.ogis.state.me.us/standards/standards.asp
,
				  Augusta, Maine.
Maine Office of Geographic Information Systems, 2000. Maine
				  GIS Feature Metadata Recommendation 2000. Executive Council for Geographic
				  Information Systems (GIS EC), additional information on this initiative and
				  other Maine GIS recommendations is available at
http://apollo.ogis.state.me.us/standards/standards.asp
, Augusta, Maine.
Maine Office of Geographic Information Systems, 2001. Maine
				  GIS Remote Sensing Final Report, Draft Land Cover Classification. Maine GIS
				  Technical Group subcommittee report, additional information on this initiative
				  and other Maine GIS recommendations is available at
http://apollo.ogis.state.me.us/standards/standards.asp
, Augusta, Maine.
Maine Office of Geographic Information Systems, 2002. GIS
				  Recommendations for ARC/INFO Work Environments. Augusta, Maine.
Office of Geographic Information Services, 1989. Proposed
				  Digital Data Standards for the Vermont Geographic Information System (VGIS).
				  School of Natural Resources, The University of Vermont, Burlington,
				  Vermont.
RTSe, 2000. Spatial GIS Metadata/Data Manager, User Guide,
				  Version 3.1 for Oracle 8. RTSe USA, Redmond, Washington.
University of Texas at Austin School of Architecture, 1999.
				  National Map Accuracy Standards (NMAS) Horizontal Accuracy Examples. Community
				  and Regional Planning Program, University of Texas at Austin, Austin,
				  Texas.