4.1 Introduction to GIS Standards
4.1.1 Purpose
The GIS Data Standards provides guidance for developing geospatially-referenced data to be submitted to, maintained by, or provided by the Maryland Department of Transportation Maryland Aviation Administration (MDOT MAA). This includes geospatial vector data, related attributes, and metadata (i.e. information about the data). This standard is required so providers and receivers of MDOT MAA data have an understanding of the requirements for the GIS data they submit and use.
4.1.2 Scope
This document defines 125 of the 393 features covered by MDOT MAA’s GIS Data Standards. The remaining 268 feature classes are covered in PEGS V1, Appendix 1E.3 – Utilities Supplement.
4.1.3 Organization of this Document
This document is a reference document that defines the requirements of GIS data submitted to, maintained for, or provided by MDOT MAA. The sections that make up the body of this document define the geometry, attributes, and metadata requirements at a general level that applies to all GIS data submitted to MDOT MAA. Specific definitions and requirements for each feature class and attribute are provided in PEGS V1, Appendix 1E.1 Feature Types. In this appendix, the geometry type, required accuracy, sensitivity levels, attribute definitions and any applicable attribute domain lists are defined. A list of acceptable domain values for each attribute domain list is also provided in PEGS V1, Appendix 1E.1 Feature Types.
This document also provides a basis to convert GIS to a CAD format and vice versa. Since GIS layering and CAD layering are traditionally different, a crosswalk is necessary to identify one or more CAD layers that correlate to each GIS layer. This crosswalk is provided in PEGS V1, Appendix 1E.2 – Cross Reference of CAD and GIS.
Other topics covered in this document include a definition of the Maryland State Plane coordinate system to be used for all MDOT MAA GIS and CAD data in Section 4.5 Coordinate System. Finally, Section 4.6 MDOT MAA Data Compliance Requirements describes the GIS data delivery formats acceptable to MDOT MAA.
4.1.4 Intended Audience
This standard is intended for Geographic Information Systems (GIS) data developers, database designers, and other providers and recipients of geospatial data that depict Baltimore/Washington Thurgood Marshall International (BWI Marshall) and Martin State (MTN) airports and their surrounds, as well as other facilities owned and operated by MDOT MAA. This standard assumes basic familiarity with GIS concepts and terminology.
4.1.5 Application of this Standard
All GIS data prepared for or used, maintained, and distributed by MDOT MAA should conform to this standard. This includes Esri shapefiles and file geodatabases prepared by MDOT MAA staff, consultants, or contractors. The extent and specifications for GIS data to be delivered will be further specified in contracts with consultants and contractors.
Some of the data submitted to MDOT MAA will also be submitted to the FAA in compliance with the FAA’s Airports GIS Program requirements. This data must conform with the requirements defined by the latest versions of FAA AC 150/5300-16A, FAA AC 150/5300-17C, and FAA AC 150/5300-18B. The structure of the data required by these ACs is reflected in this document, although the FAA requirements take precedence for data that is to be submitted to the FAA.
To be in conformance with this standard, all geographic features such as runways, buildings, wetlands, obstruction and identification surfaces should be grouped into features classes (i.e. map layers) as defined in PEGS V1, Appendix 1E.1 Feature Types or in PEGS V1, Appendix 1E.3 Utilities Supplement. Features should be of the proper geometry type (i.e. point, line or polygon) as further defined in Section 4.2.1 Allowable Geometry Types, should meet or exceed the accuracy limits specified (unless otherwise stipulated in writing) and adhere to the topological constraints described in Section 4.2.2 Topology Rules. Attributes should be populated to the extent possible (or as otherwise stipulated in writing) and carry the names and be of the types specified in PEGS V1, Appendix 1E.1 Feature Types. Attributes that are bound to domains must contain values listed in PEGS V1, Appendix 1E.1 Feature Types. All data must be in the Maryland State Plane coordinate system as defined in Section 4.5 Coordinate System. This data is to be submitted along with the metadata specified in Section 4.4 Metadata in one of the formats specified.
4.1.6 Related Material
The following documents are related to this GIS Data Standard and must be followed to be compliant with this standard.
The primary normative references (i.e. references that must be complied with) are those related to the FAA’s Airports GIS Program. MDOT MAA is required to submit GIS data in a format that complies with the FAA requirements on any project funded through federal grant monies and/or changes what the FAA defines as safety critical information. As a matter of policy, MDOT MAA follows the FAA’s Airports GIS Requirements on all projects that develop GIS data regardless of whether data is to be submitted to the FAA or not. It is relevant to note that the feature class, attribute, and domain definitions in FAA AC 150/5300-18B have been incorporated into MDOT MAA’s GIS Standards. If, however, there are any differences or clarifications necessary, the FAA advisory circulars shall prevail over this document.
A. FAA AC 150/5300-16A “General Guidance and Specifications for Aeronautical Surveys: Establishment of Geodetic Control and Submission to the National Geodetic Survey”, latest edition
B. FAA AC 150/5300-17C “Standards for Using Remote Sensing Technologies in Airport Surveys”, latest edition
C. FAA AC 150/5300-18B “General Guidance and Specifications for Aeronautical Surveys: Airport Survey Data Collection and Geographic Information System Standards”, latest edition
D. Standard Provisions for Construction Contracts