| - Full Metadata - | - View Attributes - | - View Sample - | - Get Data - |
This page last updated: 08/30/2000
Metadata created using Minnesota Geographic Metadata Guidelines
| Originator | Metropolitan Council and Metropolitan Airports Commission | |||
| Abstract | This dataset depicts the Noise Policy Area around the Minneapolis - St. Paul International Airport (MSP). This Noise Policy Area was adopted by the Metropolitan Council as part of the December, 1996 Aviation Chapter of the Metropolitan Development Guide. (A discussion of the Noise Policy Area is found on page 66 of the Aviation Guide Chapter.) The noise policy area lines in this layer were derived from MSP airport noise contours developed by the Metropolitan Airports Commission (MAC). The portions of the lines that correspond with the three existing runways (4/22, 11L/29R & 11R/29L) are derived from noise contours for 1996 that were modeled from 1991-92 base data (reference runway 4/22 EIS 'No-Build' option). The portions of the lines that correspond to the new north-south runway are derived from noise contours for 2005 modeled by the MAC for the EIS on MSP 2010 expansion plan. The outermost line represents a one mile buffer around the 60db noise policy contours. Notes: - The FAA integrated noise model (INM) was used to generate the noise contours. - The positional accuracy of the contours from which this dataset is derived is unknown. See the Lineage section for information. - Magnetic declination has resulted in re-numbering parallel runways to 12R/30L & 12L/30R. |
|||
| Browse Graphic | View a sample of the data. | |||
| Time Period of Content Date | 12/1996 | |||
| Currentness Reference | The MSP Noise Policy Area was adopted by the Metropolitan Council as part of the December, 1996 Aviation Chapter of the Metropolitan Development Guide. | |||
| Access Constraints | The Metropolitan Council has permission from the Metropolitan Airports Commission to distribute to 'communities surrounding Minneapolis-St. Paul International Airport,' the digital noise contour data that is included as part of the MSP Noise Policy Area data. | |||
| Use Constraints | By acceptance of this data, the user agrees not to transmit this data or provide access to it or any part of it in digital form to another party or individual. Users may make and distribute maps. | |||
| Distributor Organization | Metropolitan Council | |||
| Ordering Instructions | The Metropolitan Council has permission from the MAC to distribute this dataset to communities surrounding MSP. To request the dataset, send a letter to the distributor requesting the dataset. Include in the letter the statement that you will not hold the Metropolitan Council or the Metropolitan Airports Commission responsible for errors in the data and that you will not redistribute the data in digital form. Upon receipt of this letter, a suitable means of transfering the data will be arranged. Letters may be FAXed to the distributor provided that the original is subsequently sent in the mail. |
|||
| Distribution Liability | The Metropolitan Council and the Metropolitan Airports Commission make no representation or warranties, express or implied, with respect to the reuse of the data provided herewith, regardless of its format or the means of its transmission. Determining the appropriate applications for the use of this dataset is the responsibility of the user. The user accepts the data 'as is', and assumes all risks associated with its use. By acceptance of this data, the user agrees not to transmit this data or provide access to it or any part of it to another party or individual. The Metropolitan Council and the Metropolitan Airports Commission assume no responsibility for actual or consequential damage incurred as a result of any user's reliance on this data. | |||
| Online Linkage | none available | |||
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 and Metropolitan Airports Commission | |||
| Title | MSP Airport Noise Policy Area 1996 | |||
| Abstract | This dataset depicts the Noise Policy Area around the Minneapolis - St. Paul International Airport (MSP). This Noise Policy Area was adopted by the Metropolitan Council as part of the December, 1996 Aviation Chapter of the Metropolitan Development Guide. (A discussion of the Noise Policy Area is found on page 66 of the Aviation Guide Chapter.) The noise policy area lines in this layer were derived from MSP airport noise contours developed by the Metropolitan Airports Commission (MAC). The portions of the lines that correspond with the three existing runways (4/22, 11L/29R & 11R/29L) are derived from noise contours for 1996 that were modeled from 1991-92 base data (reference runway 4/22 EIS 'No-Build' option). The portions of the lines that correspond to the new north-south runway are derived from noise contours for 2005 modeled by the MAC for the EIS on MSP 2010 expansion plan. The outermost line represents a one mile buffer around the 60db noise policy contours. Notes: - The FAA integrated noise model (INM) was used to generate the noise contours. - The positional accuracy of the contours from which this dataset is derived is unknown. See the Lineage section for information. - Magnetic declination has resulted in re-numbering parallel runways to 12R/30L & 12L/30R. |
|||
| Purpose | The MSP Noise Policy Area is to be used in local community planning for purposes of land use compatibility with aircraft noise. The Noise Policy Area depicts the geographical area within which the compatibility guidelines apply. The digital version of the Noise Policy Area will allow communities to overlay the noise zones on local land use and other information to conduct various analysis. | |||
| Time Period of Content Date | 12/1996 | |||
| Currentness Reference | The MSP Noise Policy Area was adopted by the Metropolitan Council as part of the December, 1996 Aviation Chapter of the Metropolitan Development Guide. | |||
| Progress | Complete | |||
| Maintenance and Update Frequency | Every 5 years with Aviation Guide revisions. | |||
| Spatial Extent of Data | An area surrounding the Minneapolis-St. Paul International Airport, including portions of Hennepin, Dakota and Ramsey Counties. | |||
| Bounding Coordinates | -94.012 -92.732 45.415 44.471 |
|||
| Place Keywords | Minneapolis - St. Paul International Airport, MSP, Twin Cities, Dakota County, Hennepin County, Ramsey County, Minneapolis, St. Paul, Bloomington, Burnsville, Eagan, Edina, Inver Grove Heights, Lilydale, Mendota, Mendota Heights, Richfield, St. Louis Park, Sunfish Lake, West St. Paul | |||
| Theme Keywords | transportation, airports, airport noise, airport noise compatibility, Minneapolis - St. Paul International Airport, MSP, noise policy area, noise contour | |||
| Theme Keyword Thesaurus | None | |||
| Access Constraints | The Metropolitan Council has permission from the Metropolitan Airports Commission to distribute to 'communities surrounding Minneapolis-St. Paul International Airport,' the digital noise contour data that is included as part of the MSP Noise Policy Area data. | |||
| Use Constraints | By acceptance of this data, the user agrees not to transmit this data or provide access to it or any part of it in digital form to another party or individual. Users may make and distribute maps. | |||
| Contact Person Information | Chauncey Case,
Senior Planner Metropolitan Council 390 Robert Street North St. Paul, Minnesota 55101-1805 Phone: 651-602-1724 FAX: 651-602-1739 E-mail: chauncey.case@metc.state.mn.us | |||
| Browse Graphic | View a sample of the data. | |||
| Browse Graphic File Description | Sample map showing the mspnpa layer. | |||
| Associated Data Sets | |
|||
| Section 2 | Data Quality Information | Top of full metadata | Top of page | |
| Attribute Accuracy | This dataset contains a minimal amount of attribute data. All attributes have been verified to be accurate. | |||
| Logical Consistency | The dataset is topologically 'clean'. | |||
| Completeness | The entire MSP Noise Policy Area in included | |||
| Horizontal Positional Accuracy | The positional accuracy of the dataset has not been tested under the National Standards for Spatial Data Accuracy. The consultants that developed the noise contour data were unable to provide any information about the estimated positional accuracy of the digital data. In the process of converting the noise contour data from page units (as received by the Metropolitan Council) to real world coordinates, an estimated 10 meters of additional error was introduced into the data. See the Lineage section for more information. |
|||
| Lineage | The noise policy area lines in this layer were derived from MSP airport noise contours developed by the Metropolitan Airports Commission (MAC). The portions of the lines that correspond with the three existing runways (4/22, 11L/29R & 11R/29L) are derived from noise contours for 1996 that were modeled from 1991-92 base data (reference runway 4/22 EIS 'No-Build' option). The portions of the lines that correspond to the new north-south runway are derived from noise contours for 2005 modeled by the MAC for the EIS on MSP 2010 expansion plan. The outermost line represents a one mile buffer around the 60db noise policy contours. The outermost line represents a one mile buffer around the 60db noise policy contour. The consultants that developed the noise contour data were unable to provide any information about the estimated positional accuracy of the digital data. Several attempts were made by the consultants to provide the contour data (DXF files) in real world coordinates. Significant positional problems were observed in the data for each of these attempts. The Metropolitan Council decided to receive the data in what appeared to be page units and to convert the data in-house. To do this, the MAC provided surveyed coordinates for the centers of the ends of each runway. An Arc/Info layer was created for these points. Then the Arc/Info 'transform' command was used to convert the data to real world coordinates. Information resulting from the conversion of the MSP 2005 contours To define centers of runway ends on the msp2005 dxf input cover, the centers of runways (that appear in the dxf file) were eyeballed. This introduce an estimated +- 10 meter error on top of the unknown positional accuracy of the dxf file and potential noise model error. Transform command results: Arc: transform msp2005fix1 msp2005trans Transforming coordinates for coverage msp2005fix1 Scale (X,Y) = (1212.517,1212.785) Skew (degrees) = (-.008) Rotation (degrees) = (-.713) Translation = (475746.003,4960764.616) RMS Error (input,output) = (0.000,0.483) Affine X = Ax + By + C Y = Dx + Ey + F A = 1212.423 B = 14.915 C = 475746.003 D = -15.085 E = 1212.693 F = 4960764.616 tic id input x input y output x output y x error y error ------ ----------- ------------ -------- ------- 501 4.656 8.096 481510.861 4970511.947 0.732 0.075 502 5.506 8.576 482550.111 4971082.485 -.181 -.358 503 6.333 8.645 483553.186 4971152.625 -.509 0.356 504 7.277 7.523 484680.537 4969777.593 0.362 -.161 505 6.814 6.810 484108.579 4968920.009 -.019 0.063 507 4.396 6.671 481175.226 4968788.465 -.385 0.025 Information resulting from the conversion of the MSP 1996 contours To define centers of runway ends on the msp 1996 dxf input cover, the centers of runways (that appear in the dxf file) were eyeballed. (Runway end 22 did not appear to be in the same place on the 96nbpage cover and the control points cover, while the others did, so 22 was not used.) This introduce an estimated +- 10 meter error on top of the unknown positional accuracy of the dxf file and potential noise model error. Arc: transform 96nbpage 96nbptrans affine Transforming coordinates for coverage 96nbpage Scale (X,Y) = (1213.121,1213.555) Skew (degrees) = (0.018) Rotation (degrees) = (0.014) Translation = (853550.201,301177.230) RMS Error (input,output) = (0.000,0.506) Affine X = Ax + By + C Y = Dx + Ey + F A = 1213.121 B = 0.093 C = 853550.201 D = 0.297 E = 1213.555 F = 301177.230 tic id input x input y output x output y x error y error ------ ----------- ------------- ------ ------- 501 5.728 7.303 860499.816 310040.693 0.379 0.498 502 6.579 7.782 861532.350 310624.121 -.418 -.496 504 8.349 6.729 863679.335 309344.989 0.377 0.392 505 7.886 6.016 863117.733 308480.169 -.288 -.268 506 5.953 6.371 860772.299 308910.797 -.050 -.127 |
|||
| Source Scale Denominator | ||||
| Section 3 | Spatial Data Organization Information | Top of full metadata | Top of page | |
| Native Data Set Environment | ARC/INFO Version 7x, UNIX platform | |||
| Geographic Reference for Tabular Data | None | |||
| Spatial Object Type | Vector | |||
| Vendor Specific Object Types | arcs, nodes, polygons, label points | |||
| Tiling Scheme | One layer. | |||
| 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 | ||||
| Altitude Datum | Not applicable | |||
| Depth Datum | Not applicable | |||
| 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 | None | |||
| Section 6 | Distribution Information | Top of full metadata | Top of page | |
| Publisher | Metropolitan Council | |||
| Publication Date | Unpublished material | |||
| Contact Person Information | Mark Kotz 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 | MSPNoisePolicyArea1996 | |||
| Transfer Format Name | Arc Export files and ArcView Shape files | |||
| Transfer Format Version Number | ArcInfo: 7x, AV: 3. | |||
| Transfer Size | 0.2 Mb for zip file | |||
| Ordering Instructions | The Metropolitan Council has permission from the MAC to distribute this dataset to communities surrounding MSP. To request the dataset, send a letter to the distributor requesting the dataset. Include in the letter the statement that you will not hold the Metropolitan Council or the Metropolitan Airports Commission responsible for errors in the data and that you will not redistribute the data in digital form. Upon receipt of this letter, a suitable means of transfering the data will be arranged. Letters may be FAXed to the distributor provided that the original is subsequently sent in the mail. |
|||
| Distribution Liability | The Metropolitan Council and the Metropolitan Airports Commission make no representation or warranties, express or implied, with respect to the reuse of the data provided herewith, regardless of its format or the means of its transmission. Determining the appropriate applications for the use of this dataset is the responsibility of the user. The user accepts the data 'as is', and assumes all risks associated with its use. By acceptance of this data, the user agrees not to transmit this data or provide access to it or any part of it to another party or individual. The Metropolitan Council and the Metropolitan Airports Commission assume no responsibility for actual or consequential damage incurred as a result of any user's reliance on this data. | |||
| Online Linkage | none available | |||
| Section 7 | Metadata Reference Information | Top of full metadata | Top of page | |
| Metadata Date | 08/30/2000 | |||
| 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 |
|||
| 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: 08/30/2000
