USGS Quadrangle Boundaries and Corner Points in Illinois in NAD83

Metadata also available as - [Outline] - [Parseable text]

Frequently-anticipated questions:


What does this data set describe?

Title:
USGS Quadrangle Boundaries and Corner Points in Illinois in NAD83
Abstract:
This feature dataset contains point, line and polygon data that describe ideal USGS quadrangle boundaries and corner points for quadrangles that intersect the state of Illinois. The attribute data include quadrangle name and index number, longitude and latitude values for quadrangle boundaries, X and Y coordinate values in decimal degrees for quadrangle corners, and boolean indicators of which lines to use to construct index maps for common map series (by scale or extent).

This feature dataset includes line and polygon feature classes for each of the following scales/extents: 3.75-minute x 3.75-minute, commonly called quarter-quadrangles, typically used for a 1:12,000-scale index, 7.5-minute x 7.5-minute, the common USGS topographic sheet extent, typically 1:24,000-scale in Illinois, 15-minute x 15-minute, typically used for 1:62,500-scale index, 30-minute x 1 degree, typically used for 1:100,000-scale index, 1-degree x 2-degree, typically used for 1:250,000-scale index.

Also included are master line, polygon, and corner point (tic) templates from which the above were generated. These are entitled Base_Template_Ln, Base_Template_Py and Corner_Tic_Pt respectively, and include of all the 3.75-minute x 3.75-minute quarter-quadrangles and corners from 36 to 43 degrees north latitude and 86 to 92 west longitude, with an indication of which are within Illinois.

Each boundary line is composed of segments that are 18 arc-seconds in length. To provide some reference, there are 25 such segments in a line 7.5 minutes long. These vertices are included so that on reprojection of the data into a different coordinate system the quadrangle boundaries will "curve" to maintain a realistic representation of quadrangle shape in relation to real world coordinates.

The data were generated as a mathematical construct, independent of ground condition. That is, they were generated from a digital file of decimal degree-minute-second locations for each quadrangle corner, using the ArcInfo Workstation GENERATE command. Tics were generated in this manner as well, one at each quarter-quad corner. Thus quadrangle corners are exact within ideal geographic decimal degree NAD83 coordinate space.

Some non-ideal quadrangle boundaries have been added to the dataset to account for quadrangle maps with irregular boundaries, for example 15-minute quadrangles in the Chicago area.

The nominal scale is as stated above for each feature class. However, these data are in fact scale-less because they are a mathematical construct independent of ground condition.

The spatial reference is the Geographic Coordinate System, decimal degrees, NAD83.

Supplemental_Information:
In July, 2003 the data set was transitioned to storage in an Oracle RDBMS using the ArcSDE geodatabase model. The result (and most current edition) is designated Edition 2.0.

Recent updates to data:

In August, 2002 the name of the Eaton 7.5-minute quadrangle was updated to Porterville, to reflect an official name change by the Geographic Names Information System (GNIS).

  1. How should this data set be cited?

    Illinois State Geological Survey, 199803, USGS Quadrangle Boundaries and Corner Points in Illinois in NAD83: ISGS GIS Database GISDB.IL_QUAD_Usgs_Quadrangle_Index_Nad83, Illinois State Geological Survey, Champaign, Illinois.

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -92.000000
    East_Bounding_Coordinate: -86.000000
    North_Bounding_Coordinate: 43.000000
    South_Bounding_Coordinate: 36.000000

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: 08-Jul-2003
    Currentness_Reference:
    n/a - These data are a mathematical construct independent of ground condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • G-polygon (51)
      • String (120)
      • G-polygon (51)
      • String (8754)
      • G-polygon (4288)
      • G-polygon (291)
      • String (632)
      • G-polygon (291)
      • G-polygon (1072)
      • String (2233)
      • G-polygon (1072)
      • G-polygon (19)
      • String (48)
      • G-polygon (19)
      • Entity point (10961)
      • String (21722)
      • G-polygon (10756)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.005. Longitudes are given to the nearest 0.005. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:

  7. How does the data set describe geographic features?

    GISDB.IL_QUAD_100K_Index_An_Nad83

    GISDB.IL_QUAD_100K_Index_Ln_Nad83

    GISDB.IL_QUAD_100K_Index_Py_Nad83

    GISDB.IL_QUAD_12K_Index_Ln_Nad83

    GISDB.IL_QUAD_12K_Index_Py_Nad83

    GISDB.IL_QUAD_15min_Index_An_Nad83

    GISDB.IL_QUAD_15min_Index_Ln_Nad83

    GISDB.IL_QUAD_15min_Index_Py_Nad83

    GISDB.IL_QUAD_24K_Index_An_Nad83

    GISDB.IL_QUAD_24K_Index_Ln_Nad83

    GISDB.IL_QUAD_24K_Index_Py_Nad83

    GISDB.IL_QUAD_250K_Index_An_Nad83

    GISDB.IL_QUAD_250K_Index_Ln_Nad83

    GISDB.IL_QUAD_250K_Index_Py_Nad83

    GISDB.IL_QUAD_Base_Corner_Pt_Nad83

    GISDB.IL_QUAD_Base_Template_Ln_Nad83

    GISDB.IL_QUAD_Base_Template_Py_Nad83


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    GIS Processing: ISGS staff and other staff of the Illinois Scientific Surveys. Documentation: ISGS and INHS staff Quality Control: INHS and ISGS staff

  3. To whom should users address questions about the data?

    Contact_Instructions: Please refer to the distribution information section.


Why was the data set created?

These data are most useful as indices and reference grids of quadrangle-based data, such as DOQs, DRGs and topographic map sheets. They have many applications in data cataloging and searching applications. These data also provide exact quadrangle corners in NAD83, which are useful for the registration of multiple quadrangle-based data layers.

These data are appropriate for use in local and regional thematic analysis. The data are not appropriate as a geodetic, legal or engineering base. The data set was not and is not intended as a substitute for surveyed locations, such as can be determined by a registered Public Land Surveyor. Although useful in a GIS as a reference base layer for maps, the data set has no legal basis in the definition of boundaries or property lines.


How was the data set created?

  1. From what previous works were the data drawn?

  2. How were the data generated, processed, and modified?

    Date: Mar-1998 (process 1 of 4)
    Boundaries were generated by version 7.1.1 of the Arc/Info software from a file of decimal degree minute second locations for each quadrangle corner (7.5-minute x 7.5-minute), using the GENERATE command. Tics were generated as well, one at each quad corner. The AML that was used is reproduced below. Latitude and longitude values were assigned to the arcs in the generation process, and the lines were DENSIFIED to have one vertex every 18 arc-seconds (25 vertices per 7.5 arc-minutes). The result was a parent coverage called QUADTILE. Two arcs for irregularly shaped 15' quadrangles in the Chicago area were added. The spatial reference was defined as Geographic, decimal degrees, NAD27, and then reprojected to the customary ISGS Lambert Conformal Conic projection. One label was added to each polygon. Internal logical consistency checks were made as described in the logical consistency report.

    This data set was used to generate updated arcs and tics for coverages QUAD75, QUAD15, QUAD100, and QUAD250. Lines in the line feature classes were UNSPLIT based on the coordinate values to create a single, complete line segment for each side of a quadrangle.

    Lines and polygons intersecting the state of Illinois were determined using a spatial join with the state boundary polygon in ArcView 3.2.

    Other attribute data were transferred using spatial joins between legacy coverage label points and newly generated coverage polygons. The source legacy coverages are from the 1996 Illinois GIS CD-ROM compilation. The source legacy coverages date back to the mid-1980s and were originally developed as a part of a project known as the Illinois Geographic Information System (IGIS).

    AML to generate tics and lines:

    &mess &off &sv ticid = 0 &sv arcid = 0

    &sv inc = 625 &sv minlat = 360000 &sv maxlat = 430000 &sv minlon = 870000 &sv maxlon = 920000

    &mess &on &type Calculating coordinates for arcs and tics... &mess &off

    &sv open1 = [open tics.txt opens -write] &sv open2 = [open arcs.txt opens -write]

    &do lat = %minlat% &to %maxlat% &by %inc% &do lon = %minlon% &to %maxlon% &by %inc%

    &sv lat1 = %lat% / 10000 &sv lon1 = %lon% / -10000

    &sv lat2 = ( %lat% + %inc% ) / 10000 &sv lon2 = ( %lon% + %inc% ) / -10000

    &sv ticid = %ticid% + 1 &sv writeline %ticid%,%lon1%,%lat1% &sv wrote [write %open1% %writeline%]

    /*&sv arcid = %arcid% + 1 &sv arcid = %lon% &sv wrote [write %open2% %arcid%] &sv writeline %lon1%,%lat1% &sv wrote [write %open2% %writeline%] &sv writeline %lon1%,%lat2% &if ^ %lat% = %maxlat% &then &sv wrote [write %open2% %writeline%] &sv writeline end &sv wrote [write %open2% %writeline%]

    /*&sv arcid = %arcid% + 1 &sv arcid = %lat% &sv wrote [write %open2% %arcid%] &sv writeline %lon1%,%lat1% &sv wrote [write %open2% %writeline%] &sv writeline %lon2%,%lat1% &if ^ %lon% = %maxlon% &then &sv wrote [write %open2% %writeline%] &sv writeline end &sv wrote [write %open2% %writeline%]

    &type %ticid%

    &end &end

    &sv writeline end &sv wrote [write %open1% %writeline%] &sv wrote [write %open2% %writeline%]

    &sv closed [close -all]

    &mess &on &ret

    -------------

    After generating the coordinate files with this AML, arc and tic coverages were manually generated with the GENERATE command and then manually combined in ArcEdit 7x.

    Person who carried out this activity:

    Date: 2002 (process 2 of 4)
    The coverages were recreated as previously described with the exception that the minimum resolution was changed to the quarter-quadrangle scale (3.75-minute x 3.75-minute), and the data were defined to have a projection of Geographic, decimal degrees, NAD83 and were not further reprojected.

    The data were then imported into an SDE feature dataset. At this point the edition number was updated to 2.0 to reflect the significant change in data storage model.

    Person who carried out this activity:

    Date: Jul-2003 (process 3 of 4)
    The data were transferred to the ISGS SDE production server and the metadata updated.

    Person who carried out this activity:

    Date: 10-Jul-2003 (process 4 of 4)
    Updated the 24K_Index_Py, Base_Template_Py and 24K_Index_An feature classes to reflect the change of the name of the Eaton 7.5-minute quadrangle to Porterville. This was in accordance with an official GNIS change. (This change was made to the source coverage in 200208 after it had been imported to the SDE development server for testing.)

    [begin excerpt from GNIS statement]

    In the case of the Porterville issue, this geographic feature (the place) was named Eaton. The name Eaton came from the establishment of the original Post Office there and it's Postmaster John Eaton in 1852. The indication of the post office Eaton is shown on the USGS map with a parenthetical under the name Porterville, though the Post Office no longer exists.

    This name case is a BGN OSN - Board on Geographic Names Official Standard Name, which means it was visited by the BGN Staff but was approved by an Administrative Authority; it did not go to a full board vote. The place was originally platted as East Berlin, but there was little growth until 1850 when Richard Porter established a Blacksmith Shop there. Porterville is the more widely accepted name for the community, though it is also known as Eaton. So this change mandated the change to the USGS quad, after it was brought forward as a possible controversy by our Mapping Center (Rolla) during a project in IL dated 07/01/83.

    [end excerpt]

    Person who carried out this activity:

    Data sources used in this process:
    • GNIS

  3. What similar or related data should the user be aware of?

    Illinois State Geological Survey, 199803, USGS Quadrangle Boundaries and Corner Points in Illinois in NAD27: ISGS GIS Database GISDB.IL_QUAD_Usgs_Quadrangle_Index_Nad27, Illinois State Geological Survey, Champaign, Illinois, USA.

    Other_Citation_Details:
    This feature dataset is identical to GISDB.IL_Usgs_Quadrangle_Index_Nad83, except the data are cast on the NAD27 datum.
    This is part of the following larger work.

    ,.


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    No formal review has been completed. Regular use of these data, however, indicate attributes are accurate.

  2. How accurate are the geographic locations?

    These data are a mathematical construct and as such should have a high degree of positional accuracy (i.e. exact, with the exception of arcs added for irregular 15-minute quadrangle boundaries). No review has been completed, however. There have been several instances where map indices generated from these boundaries have been used with other data digitized from USGS quadrangles with good results.

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    This dataset includes all of the 3.75-minute x 3.75-minute quarter-quadrangle boundaries and areas from 36 to 43 degrees north latitude and 87 to 92 west longitude, with an indication of which intersect Illinois. This includes quadrangle corner coordinates.

    Line and polygon feature classes for each of the following scales/extents can, and have been, constructed: 3.75-minute x 3.75-minute, commonly called quarter-quadrangles, typically used for a 1:12,000-scale index 7.5-minute x 7.5-minute, the common USGS topographic sheet extent, typically 1:24,000-scale in Illinois 15-minute x 15-minute, typically used for 1:62,500-scale index 30-minute x 1 degree, typically used for 1:100,000-scale index 1-degree x 2-degree, typically used for 1:250,000-scale index

    There are two additional arcs in the Chicago region form the eastern boundaries of two irregularly shaped 15' quadrangles. These have values of 999 and 0.999 in the INT_COORD and DEC_COORD fields respectively.

  5. How consistent are the relationships among the observations, including topology?

    A logical consistency review was performed in March, 1998. At that time the data were maintained in ArcInfo coverage format.

    The following checks were made:

    The data set was DESCRIBED and coverage files listed to determine the feature types present. In this data set, the following feature types were found and checked: polygons, arcs, labels, nodes, and annotation. The presence of spatial indices was also checked.

    For PAT and AAT files, each item was checked for the following: domain of allowable values, adherence of values to the domain, definition of attribute items, requirement of all unique values for an item, logic of items redefined over other items, and length of item name as regards conversion to shapefile format.

    The topology status of the data set was checked, as were LABELERRORS, NODEERRORS (if appropriate), and the PROJECTION definition.

    The presence of a BND file was verified.

    The presence and location of TICS were checked.

    Polygon and chain-node topology were present. There were no dangling arcs. There was one polygon label per polygon, except for the universe polygon. Boundary values were appropriate for the map projection and map units. COVER-ID values were recalculated to be unique. See the process step for March, 1998.

    There are two additional arcs in the Chicago region form the eastern boundaries of two irregularly shaped 15' quadrangles. These have values of 999 and 0.999 in the INT_COORD and DEC_COORD fields respectively. There are no known attribute values outside the appropriate domains.


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: none
Use_Constraints:
Reproduction or redistribution of copyrighted digital data sets or products derived therefrom outside of licensee's organization or entity is expressly forbidden. The only exception is redistribution to consultants working for the licensee, and then only for purposes, related to work for the licensee. Such consultants may not further reproduce or redistribute these data sets. None of these data shall be electronically duplicated on magnetic or optical media for use by others, in whole or in part, without permission of DNR.

Any hardcopies utilizing DNR data sets shall clearly indicate their source. If the licensee has modified the data in any way they are obligated to describe the types of modifications they have performed on the hardcopy map. Licensee specifically agrees not to misrepresent DNR data sets, nor to imply that changes they made were approved by DNR.

  1. Who distributes the data set? (Distributor 1 of 1)

    Geospatial Analysis and Modeling Section, Illinois State Geological Survey
    615 East Peabody Drive
    Champaign, Illinois 61820
    USA

    217-333-4747 (voice)
    isgs@isgs.uiuc.edu

    Hours_of_Service: 8:00 a.m. - 4:30 p.m., Monday-Friday, U.S. Central Time
  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    The Illinois Department of Natural Resources (DNR) provides these geographic data "as is." DNR makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. DNR further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although these data have been processed successfully on computers of DNR, no warranty, expressed or implied, is made by DNR regarding the use of these data on any other system, nor does the fact of distribution constitute or imply any such warranty.

    In no event shall the DNR have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the geographic data or arising out of the delivery, installation, operation, or support by DNR.

  4. How can I download or order the data?

  5. What hardware or software do I need in order to use the data set?

    The data are intended for use with GIS software. The ISGS uses ESRI ArcGIS software, however, the ESRI shapefile format can be imported into many different GIS software packages. It is expected that customers who order this data have the technical expertise to use GIS software. The ISGS does not provide software support of any kind.


Who wrote the metadata?

Dates:
Last modified: 26-Apr-2006
Metadata author:

Contact_Instructions: Please refer to the distribution information section.
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.8.11 on Tue Jul 31 15:08:27 2007