| - Full Metadata - | - View Attributes - | - View Sample - | - Get Data - |
This page last updated: 07/18/2006
Metadata created using Minnesota Geographic Metadata Guidelines
| Originator | Metropolitan Council |
| Abstract | The 2005 Generalized Land Use dataset encompasses the seven county Twin Cities (Minneapolis and St. Paul) Metropolitan Area in Minnesota. The dataset was developed by the Metropolitan Council, a regional governmental organization that deals, in part, with regional issues and long range planning for the Twin Cities area. The data were interpreted from 2005 air photos, with additional assistance from county parcel data and assessor's information, reverse directories, and Internet information. The land use classification scheme has been expanded somewhat from that used in previous versions of the generalized land use data. The following generalized land use classes are used (some of which have subclasses): Single Family Residential Multifamily Residential Office Retail and Other Commercial Mixed Use Industrial and Utility Extractive Institutional Park, Recreational, or Preserve Golf Course Major Highway Railway Airport Agriculture Undeveloped Water See Section 5 of the metadata for a detailed description of each of these land use categories and available subcategories. Note: This dataset does not attempt to delineate what lands might be considered developable. This dataset does contain an 'Undeveloped' land category. The definition of that category can be found in Section 5 of this metadata. More information about the Metropolitan Council's generalized land use data can be found here http://gis.metc.state.mn.us/landuse/landuse_notes.pdf |
| Browse Graphic | View a sample of the data. |
| Time Period of Content Date | 04/14/2005 |
| Currentness Reference | The dates of the original aerial photography were April 8, 13 and 14, 2005. County parcel and assessors data was from varying dates in the spring of 2005. |
| Access Constraints | None |
| Use Constraints | By acceptance of this data, the user agrees to include a copy of this metadata record, including the liability disclaimer, whenever the user transmits or provides the GIS Data (or any portion of it) to another user. We recommend that other interested parties download this dataset from the Data Finder web site (www.datafinder.org) to ensure that the most current data is obtained. |
| Distributor Organization | Metropolitan Council |
| Ordering Instructions | This dataset is distributed on the internet by clicking below after 'Online Linkage'. Doing so will tell your browser to download a 'ZIP' file which will contain the following: - ArcView shape files - metadata for the dataset (.htm) - NOTICE.RTF, an important notice about this dataset that can be read by any word processing software. This dataset can also be viewed and downloaded from the MetroGIS DataFinder Cafe at http://www.datafinder.org/cafe/ . The Cafe allows users to subset or clip datasets using an existing feature, such as a city or school district boundary or an ad-hoc, user defined area. Additionally, this dataset is available for direct use via one or more map services. More information about what a web mapping service is can be found at http://www.datafinder.org/services/ . The specific map service and layer name for this dataset can be found by clicking the blue or green boxes under the map service column of the DataFinder Catalog at http://www.datafinder.org/catalog/ . |
| Online Linkage | Click here to download data. (See Ordering Instructions above for details.) By clicking here, you agree to the notice in "Distribution Liability" in Section 6 of this metadata. |
Go to Section:
1. Identification Information
2. Data Quality Information
3. Spatial Data Organization Information
4. Spatial Reference Information
5. Entity and Attribute Information
6. Distribution Information
7. Metadata Reference Information
| Section 1 | Identification Information | Top of page | ||
| Originator | Metropolitan Council | |||
| Title | Generalized Land Use 2005 for the Twin Cities Metropolitan Area | |||
| Abstract | The 2005 Generalized Land Use dataset encompasses the seven county Twin Cities (Minneapolis and St. Paul) Metropolitan Area in Minnesota. The dataset was developed by the Metropolitan Council, a regional governmental organization that deals, in part, with regional issues and long range planning for the Twin Cities area. The data were interpreted from 2005 air photos, with additional assistance from county parcel data and assessor's information, reverse directories, and Internet information. The land use classification scheme has been expanded somewhat from that used in previous versions of the generalized land use data. The following generalized land use classes are used (some of which have subclasses): Single Family Residential Multifamily Residential Office Retail and Other Commercial Mixed Use Industrial and Utility Extractive Institutional Park, Recreational, or Preserve Golf Course Major Highway Railway Airport Agriculture Undeveloped Water See Section 5 of the metadata for a detailed description of each of these land use categories and available subcategories. Note: This dataset does not attempt to delineate what lands might be considered developable. This dataset does contain an 'Undeveloped' land category. The definition of that category can be found in Section 5 of this metadata. More information about the Metropolitan Council's generalized land use data can be found here http://gis.metc.state.mn.us/landuse/landuse_notes.pdf |
|||
| Purpose | To aid in forecasting region-wide land supply and demand and to be used as a general regional planning tool. This data does not indicate developability of land, but does show the location of 'Undeveloped' land based on the definition described in Section 5 of this metadata. | |||
| Time Period of Content Date | 04/14/2005 | |||
| Currentness Reference | The dates of the original aerial photography were April 8, 13 and 14, 2005. County parcel and assessors data was from varying dates in the spring of 2005. | |||
| Progress | Complete | |||
| Maintenance and Update Frequency | Approximately every 5 years. | |||
| Spatial Extent of Data | Twin Cities 7 County Metropolitan Area. This includes the counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington in Minnesota. | |||
| Bounding Coordinates | -94.012 -92.732 45.415 44.471 |
|||
| Place Keywords | Twin Cities, Anoka County, Carver County, Dakota County, Hennepin County, Ramsey County, Scott County, Washington County | |||
| Theme Keywords | Land Use, planning and development Land Type, Single Family Residential, Multifamily Residential, Office, Retail and Other Commercial, Mixed Use, Industrial and Utility, Extractive, Institutional, Park, Recreational, or Preserve, Golf Course, Major Highway, Railway, Airport, Agriculture, Undeveloped, Water |
|||
| Theme Keyword Thesaurus | None | |||
| Access Constraints | None | |||
| Use Constraints | By acceptance of this data, the user agrees to include a copy of this metadata record, including the liability disclaimer, whenever the user transmits or provides the GIS Data (or any portion of it) to another user. We recommend that other interested parties download this dataset from the Data Finder web site (www.datafinder.org) to ensure that the most current data is obtained. |
|||
| Contact Person Information | Paul E. Hanson,
GIS Specialist Metropolitan Council 390 Robert Street North St. Paul, Minnesota 55101-1634 Phone: 651.602.1642 FAX: 651.602.1674 E-mail: paul.hanson@metc.state.mn.us | |||
| Browse Graphic | View a sample of the data. | |||
| Browse Graphic File Description | Sample map showing the landuse_2005 layer. | |||
| Associated Data Sets | Historical Generalized Land Use (1984, 1990, 1997, 2000 & 2005 combined): http://www.datafinder.org/metadata/landuse_hist.htm 2005 Digital Orthophotos: http://www.datafinder.org/metadata/orthos2005_markhurd.htm |
|||
| Section 2 | Data Quality Information | Top of full metadata | Top of page | |
| Attribute Accuracy | During the land use interpretation, digital orthophotos and county parcel data with assessor's land use/type attributes were used. Reverse directories, Internet information, and field checks were used to augment this interpretation. Also, comments and corrections for the 2005 data from the cities and townships (each of which was given a map with the preliminary 2005 data) were used to update the 2005 layer. Known deficiencies in the dataset include: - The only delineated roads are those with at least 4 lanes, controlled access and a 200 ft. right-of-way, and all 4-lane roads with a Metropolitan Council functional class designation of 'Principal Arterial.' All other roads are incorporated into the adjacent land use category. - The only delineated railroads are those with at least 2 tracks side-by-side and they are classified as 'Railway'. All single track railroads are incorporated into the adjacent land use category. - The interpretation of the 'Institutional' and 'Park, Recreational or Preserve' classes can be fuzzy. For example, ball fields adjacent to a school are classed as Institutional if owned by the school district, while ball fields adjacent to a school that are not owned by the school district are classified as 'Park, Recreational or Preserve'. - Some Horticultural specialty land uses (the growing of nursery stock, flowers, seeds, sod, and food crops grown indoors) are included in the 'Industrial' category where they could be delineated (e.g. large greenhouses that do not sell to the public). However, most of these facilities that are out of doors are included in the 'Agricultural' class. - The interpretation of a discernable shoreline for a body of open water or flowing waterway may vary. In many cases, the shoreline was taken to the treeline. |
|||
| Logical Consistency | The dataset is topologically 'clean'. | |||
| Completeness | Entire seven county geographic area is covered. Incompleteness in attribute information is discussed under 'Attribute Accuracy' above. | |||
| Horizontal Positional Accuracy | Estimating the horizontal positional accuracy of this layer is somewhat complicated, because a number of factors must be considered. For this reason, a description of some of these factors seems instructive. Many of the boundaries defining land uses in urban areas were drawn along parcel lines based on parcel data from the metro counties. Metro county parcel datasets vary greatly in positional accuracy as well as in the documentation of that accuracy. Furthermore, positional accuracy may vary for different features within the same parcel dataset. An additional factor is the degree to which Metropolitan Council staff matched the parcel boundaries in heads-up digitizing within ArcGIS. The scale at which lines were digitized varied as staff zoomed in and out while heads-up digitizing within ArcGIS, however most lines were digitized at an on-screen scale of no higher than 1:3000. In highly urbanized areas, 1:1500 was more common. In rural areas, parcel boundaries were often not used. Rural residential land use boundaries were defined by the mowed lawns or used areas around the dwellings as viewed on the 2005 MARKHURD Digital Orthophotos, Twin Cities Metropolitan Area. For this reason a positional accuracy estimate would have to describe the accuracy with which the interpreted boundary of this area was defined as well as whether the interpretation of the boundary was correct or inaccurate (causing a positional error). A variety of other factors play a role in the positional accuracy of this layer. The information in the Entity and Attribute Detailed Citation (Section 5 of the metadata) may shed light on some positional issues with respect to this dataset. As a general rule when developing this dataset it was the Metropolitan Council's intention to meet the National Mapping Accuracy Standards at 1:24,000 (within approximately 40 feet of actual location). No testing has been conducted to verify this. |
|||
| Lineage | DATA SOURCES: - 2005 MARKHURD Digital Orthophoto quarter quads (0.6 meter resolution) - 2000 land use delineations - parcel data from all seven counties - The Lawrence Group's road centerline layer - reverse directories, Internet resources, and field checks - community feedback from preliminary maps sent out to them HISTORY OF THE LAND USE DATA: The Metropolitan Council has conducted analyses of land use for the years 1966, '70, '74/'75, '78, '80, '84, '90, '97, 2000 and 2005. Each project included analysis of aerial photography as well as field checks and the use of other sources to delineate land use and land use change. Land use maps were developed from these data for the years 1966, '75, '84, '90, '97 and 2000. In addition, reports on land use change were prepared for the periods of 1960-1975, 1970-1978, 1970-1980, 1980-1990, 1990-1997, 1997-2000, and 2000-2005. PROCESSING STEPS FOR THE 2005 LAND USE LAYER: The 2005 land use layer was developed on the base of the 2000 land use dataset. The primary tools used for the 2005 land use interpretation were the 2005 MARKHURD digital orthophotos and county parcel data with assessor's attributes indicating various land use type information. It is important to note that the assessor's attributes varied greatly from county to county. In many cases the land type or use categories used by the county for assessment purposes did not match the categories used in this dataset. The assessors attributes were matched as closely as possible to Council land use categories. Additionally, the property owner name from the parcel data and entries in reverse directories were used as aides in the land use interpretation. Address matching and owner name from the parcel data was at time used to search Internet resources for clarification. Where these sources were insufficient to determine the land use category, field checks were performed. Once the preliminary 2005 land use dataset was completed, each of the approximately 200 cities and townships within the metro area was sent a map of the preliminary data and asked to provide comments and corrections. 79% of the the cities and townships responded and their comments were used to enhance the accuracy of the 2000 land use data. The original categories used for land use breakdowns were established in 1962 and were modified only slightly through the preceding years of generating the Twin Cities generalized land use maps (1966, 1975, 1984, 1990, 1997). For 2000, the categories changed significantly. These changes were maintained in the 2005 Generalized Land Use data set. The classes for 2005 are described in the Entity and Attribute Overview section. Included in the class descriptions are various decisions that were made related to delineating each land use class. The interpretation was conducted on 7.5 minute quadrangles (USGS quads). The editing was done using ArcInfo 9.1 desktop software. Once completed, the geodatabase tiles were converted to polygon ArcInfo coverages and then the tiles were combined into one metro wide layer, where small sliver polygons were removed and other miscellaneous editing was done. More information about the Metropolitan Council's generalized land use data can be found here http://gis.metc.state.mn.us/landuse/landuse_notes.pdf |
|||
| Source Scale Denominator | ||||
| Section 3 | Spatial Data Organization Information | Top of full metadata | Top of page | |
| Native Data Set Environment | ArcGIS Version 9x | |||
| Geographic Reference for Tabular Data | None | |||
| Spatial Object Type | Vector | |||
| Vendor Specific Object Types | polygon shapes | |||
| Tiling Scheme | One layer for entire seven county region. | |||
| Section 4 | Spatial Reference Information | Top of full metadata | Top of page | |
| Horizontal Coordinate Scheme | UTM | |||
| Ellipsoid | GRS80 | |||
| Horizontal Datum | NAD83 | |||
| Horizontal Units | Meters | |||
| Distance Resolution | ||||
| UTM Zone Number | 15 | |||
| Section 5 | Entity and Attribute Information | Top of full metadata | Top of page | |
| Entity and Attribute Overview | Polygon Attributes: |
| Entity and Attribute Detailed Citation | The original categories used for land use breakdowns were established in 1962 and were modified only slightly prior to 2000. For 2000, the categories were expanded significantly and although the descriptions changed slightly, the classifications were maintained for the 2005 land use dataset. The 2005 land use dataset are as follows: RESIDENTIAL - SINGLE-FAMILY, DETACHED; SINGLE-FAMILY, ATTACHED; AND MULTIFAMILY Beginning in 1997, the Council has been able to incorporate county assessor information in their land use project which, among other things, has allowed them to, in a dramatic fashion, more accurately distinguish between the different residential housing types - Single-Family, Detached, Single-Family, Attached, and Multifamily housing. However, some recent housing development trends have made the Council's ability to distinguish housing types more difficult. One prominent trend includes the construction of large, multi-unit buildings (8 units or more) that provide private entrances rather than a common building entrance. From a county assessor's perspective, these are Multifamily housing; from a traditional real-estate/housing perspective, these units more closely meet the definition for Single-Family, Attached housing - a definition the Council has adopted in distinguishing housing units within the region. As a result, using the assessor's code as a indication of the land use, can, to the casual viewer be misleading and result in a incorrect residential land use designation. To compound matters, visually, because of the shear size of these buildings, visually these buildings look like apartments and unless a discerning eye notices multiple 'drive-ways' or individual unit walkways. The other prominent trend is the construction of detached 'townhouses.' Historically, a town home or townhouse is defined as a form of ownership in real estate that, in general, consist of a series of low-rise, single-family residential units, attached to one or more similar dwellings by common walls, but have separate entrances and stand on individual lots - Single-Family, Attached. The owners have title to the unit and lot they occupy, however, the common areas and the building exteriors are owned jointly with adjacent owners. More recently, the term Townhouse has been expanded to include residential units that DO NOT share a common wall with a similar and neighboring dwelling. In other words, the residential units are by definition Single-Family, Detached Residential units. Therefore, although the ownership patterns between Attached and Detached Townhouses are similar, the construction should dictates how the land use is classified. SINGLE FAMILY RESIDENTIAL Land used exclusively for residential purposes and containing a single dwelling unit. Includes the following four codes: 111 - FARMSTEAD Land that encompasses the single family residential dwelling and associated buildings of a farm. Associated buildings of a farm may include buildings used for animal husbandry (barns, chicken coops, grain solos, etc.) along with accessory uses, provided that such accessory uses are incidental to the agricultural activities. 112 - SEASONAL/VACATION Land meeting the general definition of single-family residential containing a dwelling unit occupied seasonally or used as vacation property. 113 - SINGLE FAMILY DETACHED Land meeting the general definition of single-family residential and detached from any other residential dwelling unit (i.e., with open space on all four sides). Includes detached townhomes. 116 - MANUFACTURED HOUSING PARK Land meeting the general definition of Single-Family, Detached dwelling and designated for the placement of multiple manufactured housing structures. Note: this classification IS NOT used for an individual manufactured home. MULTIFAMILY RESIDENTIAL Land used exclusively for residential multiple-family dwellings containing a building or multiple buildings. Includes the following two codes: 114 - SINGLE FAMILY ATTACHED Land meeting the general definition of multifamily residential containing two or more attached dwelling units (share a common wall, each with primary ground floor access to the outside. Examples: attached townhome, double bungalow, triplex, large multi-unit structures with each unit having its own external entrance, etc. 115 - MULTIFAMILY Land meeting the general definition of residential containing two or more attached dwelling units, one or more of which does not have primary ground floor access to the outside. Examples: Apartment building, condominium with a main entrance for all residents. Note: Where it was not possible to differentiate between these two categories based on aerial photography and assessors data, the next criteria for differentiation was the number of units. If an indistinguishable parcel contained two to four units, it was coded Single Family Attached. If it had 5 or more units, it was coded Multifamily. If the number of units also was not available, then the final distinction was made using the house like test. If it looked like a house from the photo (e.g. large house split into apartments), it was classified as Single Family Attached, otherwise it became Multifamily. 120 - RETAIL AND OTHER COMMERCIAL Land used for the provision of goods or services. This category is for general sales and services that comprise the vast majority of establishments typically associated with commercial land use. This category is used as the default for commercial/retail land uses. Examples: store, restaurant, hotel, bank, daycare facility, mini-storage facility, Metrodome, Excel Center, Canterbury Downs, YMCA, American Legion, skeet club/outdoor gun range (large game/gun clubs - 80 acres or more - will be coded as Park and Rec.). 130 - OFFICE Land used predominantly for administrative, professional, or clerical services. Examples: law offices, accounting firms, clinics (but not hospitals), and veterinary clinics. Government office buildings are generally categories as Institutional. However, where government offices are housed on a privately owned parcel (e.g. leased office space), they may be included in the Office category. MIXED USE Land containing a building with mixed uses. Includes the following three codes: 141 - MIXED USE RESIDENTIAL Land containing a building with multiple uses in combination with at least a residential unit(s). Examples include: Galtier Plaza in St. Paul, a mom & pop bakery with living space above it. 142 - MIXED USE INDUSTRIAL Land containing a building with multiple uses in combination with industrial uses and NO residential units. An example would be a building containing a warehouse, offices, and stores. 143 - MIXED USE COMMERCIAL AND OTHER Land containing a building with multiple uses but with NO residential units or industrial uses. An example would be a building containing commercial shops, childcare facility, offices, and/or restaurants. Downtown areas usually have buildings where the first and/or second floor is commercial and the rest is office (e.g. Lawson Software Building), these types of buildings would be coded under this category. 151 - INDUSTRIAL AND UTILITY Land containing manufacturing, transportation, construction companies, communications, utilities or wholesale trade. This category includes publicly owned industrial lands (e.g., wastewater treatment plants, water towers, large transit garages, DOT road sanding stockpiles or maintenance staging areas). Industrial also includes: warehouses, some special horticultural uses (e.g. large greenhouses that do not sell to the public), landfills, and automotive junk yards (even if they sell retail, SIC 5015). Radio and TV stations were also included in this category. 153 - EXTRACTIVE Land containing extractive industry (Ex: Gravel Pits and Quarries). 160 - INSTITUTIONAL Land used primarily for religious, governmental, educational, social, cultural or major health care facilities (where they have beds for overnight stay). Examples: schools, synagogues, cemeteries, hospitals, nursing homes, city halls, county and state fairgrounds, and museums. This category includes all publicly owned land that is not clearly in any other category (e.g. not in Office, Parks, or Industrial, etc.). Clinics and health care facilities with only outpatient procedures will be classified as Office, NOT Institutional. Government office buildings are generally categories as institutional. However, where government offices are housed on a privately owned parcel (e.g. leased office space), they may be included in the Office category. NOTE: All land should be classified based on use NOT Ownership! If land is owned by a church but appears to be Single-Family, Detached housing, say for the minister, or clergy, then the land use should be Single-Family, Detached residential NOT Institutional. 170 - PARK, RECREATIONAL OR PRESERVE Land used for park and recreational sport assembly or passive open space. This may occur at community level fields, regional parks, public parks, private parks, campgrounds, small urban parks, playgrounds, rest areas, and other venues used for indoor and outdoor sporting events or like purposes. This category also includes passive recreational activities or land use areas, such as park preserves, wildlife refuges, habitat areas, public plazas, river walks, DNR or US Fish and Wildlife owned land, greenways and residential common areas with distinguishable walk or bike paths. The category also includes a small number of 'non-developable' areas based on local ordinances or Planned Unit Developments (PUD). Areas designated as PUD represent open areas within or adjacent to urban development (i.e. housing) which together fulfill or meet overall density guidelines for such urban developments as outlined by the city. In addition, some lands within park boundaries are discernibly farmed (i.e., possibly leased lands or granted uses for future protection) and therefore are classified as Agricultural use rather than Park. 173 - GOLF COURSE Land used for golfing, including driving range and practice areas. 201 - MAJOR HIGHWAY Major roadway strips of land or area, on which a vehicular rights-of-passage exists under the following conditions: all interstate highways; all 4-lane divided highways with rights-of-way of 200 feet or greater in width; or all 4-lane roads with a Metropolitan Council functional class designation of 'Principal Arterial'. NOTE: Where closely aligned frontage roads exist along vehicular rights-of-way which meet the preceding criteria, these frontage roads will be included in the total rights-of-way. Additionally, land uses occurring within a Major Highway rights-of-way, as specified above, but clearly has a different use (i.e., agriculture - row crops) are to be classified by its actual use. In addition, for consistency, if some major roadways that don't meet the above criteria yet have been classified as a Major Highway in past land use dataset, will remain Major Highway. Includes Park-n-Rides lots adjacent to Major Highways 202 - RAILWAY Land used and occupied or intended to be occupied by multiple railroad track lines or similar uses. This includes railroad classification, storage and repair yards; intermodal containerized freight and transload facilities; railroad depots, etc. that might otherwise be classified under as industrial Note: Single-track railroads are not delineated. 203 - AIRPORT Land used for the operation of aircraft and any related uses that are on the airport property (Ex: parking lot or car rental) Uses such as ball fields on the airport property would not be included in this category. 100 - AGRICULTURAL Land used for agricultural purposes. Includes discernable cultivation (Ex: ground tillage or crop rows) horticulture, floriculture (exotic flowers), viticulture (grapes) activities, pasture, and a broad range of other agricultural activities such as horse boarding and training, kennels, sod farms, tree farms, fish production and processing, storage areas or buildings). Agricultural buildings (including feedlots) that are not surrounding a farmstead (see definition above) are included in this category. NOTE: Not all agricultural lands are discernable based on available data (aerial photography and assessors data). Thus, a significant amount of agricultural land may be placed in the Undeveloped category. 210 - UNDEVELOPED Land not currently used for any defined purpose that may or may not contain buildings or other structures or has no discernable use based on the aerial photos or available data. Undeveloped may include non-protected wetlands or lands currently under development. 220 - WATER A body of open water or flowing waterway inclusive within a discernable shoreline. This typically does not include wetlands or periodically flooded areas. Generally only features three acres or greater in size were delineated. Areas definable as another land use type will not be depicted as in the Water category (e.g. major highway bridge over a river and marina). |
|||
| Section 6 | Distribution Information | Top of full metadata | Top of page | |
| Publisher | Metropolitan Council | |||
| Publication Date | 07/10/2006 | |||
| Contact Person Information | Mark Kotz GIS Database Administrator Metropolitan Council 390 Robert Street North St. Paul, Minnesota 55101-1805 Phone: 651-602-1644 FAX: 651-602-1674 E-mail: mark.kotz@metc.state.mn.us |
|||
| Distributor's Data Set Identifier | landuse_2005 | |||
| Distribution Liability | NOTICE: The Geographic Information System (GIS) Data to which this notice is attached are made available pursuant to the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). THE GIS DATA ARE PROVIDED TO YOU AS IS AND WITHOUT ANY WARRANTY AS TO THEIR PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The GIS Data were developed by the Metropolitan Council for its own internal business purposes. The Metropolitan Council does not represent or warrant that the GIS Data or the data documentation are error-free, complete, current, or accurate. You are responsible for any consequences resulting from your use of the GIS Data or your reliance on the GIS Data. You should consult the data documentation for this particular GIS Data to determine the limitations of the GIS Data and the precision with which the GIS Data may depict distance, direction, location, or other geographic features. If you transmit or provide the GIS Data (or any portion of it) to another user, the GIS Data must include a copy of this disclaimer. | |||
| Transfer Format Name | ArcView Shape File | |||
| Transfer Format Version Number | ArcGIS 9x | |||
| Transfer Size | 50 MB for zip file. | |||
| Ordering Instructions | This dataset is distributed on the internet by clicking below after 'Online Linkage'. Doing so will tell your browser to download a 'ZIP' file which will contain the following: - ArcView shape files - metadata for the dataset (.htm) - NOTICE.RTF, an important notice about this dataset that can be read by any word processing software. This dataset can also be viewed and downloaded from the MetroGIS DataFinder Cafe at http://www.datafinder.org/cafe/ . The Cafe allows users to subset or clip datasets using an existing feature, such as a city or school district boundary or an ad-hoc, user defined area. Additionally, this dataset is available for direct use via one or more map services. More information about what a web mapping service is can be found at http://www.datafinder.org/services/ . The specific map service and layer name for this dataset can be found by clicking the blue or green boxes under the map service column of the DataFinder Catalog at http://www.datafinder.org/catalog/ . |
|||
| Online Linkage | Click here to download data. (See Ordering Instructions above for details.) By clicking here, you agree to the notice in "Distribution Liability" above. | |||
| Section 7 | Metadata Reference Information | Top of full metadata | Top of page | |
| Metadata Date | 07/18/2006 | |||
| Contact Person Information | Paul E. Hanson,
GIS Specialist Metropolitan Council 390 Robert Street North St. Paul, Minnesota 55101-1805 Phone: 651-602-1642 FAX: 651-602-1674 E-mail: paul.hanson@metc.state.mn.us |
|||
| Metadata Standard Name | Minnesota Geographic Metadata Guidelines | |||
| Metadata Standard Version | 1.2 | |||
| Metadata Standard Online Linkage | http://www.gis.state.mn.us/stds/metadata.htm | |||
This page last updated: 07/18/2006
