Contact
Mapping Systems Authority serves professionals, researchers, and organizations engaged with geospatial technology, GIS platforms, spatial data infrastructure, and location-based services across the United States. This page describes how to structure an inquiry, what general timeframes apply to different request categories, and the full range of channels through which the office can be reached. Specific guidance on editorial, technical, licensing, and partnership communications is organized by request type below.
What to include in your message
The quality and completeness of an inquiry determines how quickly it can be routed to the correct editorial or technical reviewer. The following breakdown covers the information required for each major request category.
Editorial and content accuracy requests concern factual claims, source attribution, or missing coverage across pages such as Geospatial Data Standards, Mapping Data Accuracy and Validation, or GIS Platforms Comparison. For these requests, include:
Technical integration and API coverage inquiries relating to pages such as Mapping APIs and SDKs, Real-Time Mapping Systems, or Mapping System Integration require the following:
Vendor provider and provider network inquiries applicable to the Mapping System Vendors US section should identify the organization's full legal name, primary service classification (hardware, software, data services, or integration consulting), and the geographic scope of operations. Unverified or anonymous vendor submissions are not processed.
Regulatory and compliance questions related to coverage on Mapping System Compliance US, Mapping System Security, or Geofencing Technology must reference the applicable regulatory framework — such as the National Spatial Data Infrastructure (NSDI) framework administered under Executive Order 12906, state-level surveying licensure boards, or Federal Aviation Administration (FAA) Part 107 rules governing drone-derived spatial data.
Research and data partnership inquiries should describe the project scope, the affiliated institution or agency, and the specific data category or reference content required. Academic partnerships with university geography and remote sensing programs are evaluated on a rolling basis.
Response expectations
general timeframes vary by request category and complexity. Editorial corrections referencing a verifiable named source — such as an OGC Implementation Standard or a FGDC Content Standard for Digital Geospatial Metadata — are reviewed promptly. Requests that require cross-referencing against USGS, National Oceanic and Atmospheric Administration (NOAA), or Census Bureau TIGER/Line datasets may take longer due to the complexity of the data involved.
Technical accuracy disputes involving third-party platform documentation, such as discrepancies between published content and the current Esri ArcGIS documentation or the OpenStreetMap Foundation's published contributor guidelines, are escalated to a subject-matter reviewer and carry a 10-business-day standard.
Vendor and partnership inquiries receive an initial acknowledgment promptly. A substantive response follows after the necessary data is compiled and reviewed, which typically concludes for first-time submissions after a thorough review process.
Priority routing applies to inquiries from federal or state agencies, including the Department of Transportation (DOT), Department of Homeland Security (DHS), or any state 911 authority referencing emergency response mapping covered under Emergency Response Mapping Systems. Government-origin inquiries are flagged and escalated promptly.
Additional contact options
Beyond direct messaging, the following structured channels address specific professional and institutional needs.
Standards body coordination: Inquiries referencing OGC standards, ISO/TC 211 geographic information standards, or FGDC metadata profiles should cite the specific standard number and version in the subject line. This accelerates routing to reviewers with standards-body familiarity.
Academic and research inquiries: Researchers affiliated with university GIS programs, federal research agencies such as the USGS National Geospatial Program, or the National Aeronautics and Space Administration (NASA) Earth Science Division should identify their institutional affiliation and whether data access or citation support is the primary need. Coverage of Satellite Imagery Services, LiDAR Mapping Technology, and Terrain and Elevation Data Services is regularly updated based on agency-published releases.
Press and professional publication requests: Journalists or publication editors requesting reference material on geospatial technology topics should specify their publication, the relevant deadline, and the subject area. Content covering Location Intelligence Platforms, Smart City Mapping Applications, and Transportation Mapping Technology is available for factual reference under standard attribution terms.
How to access this platform
The primary contact channel is the submission form available on this page. All submissions are logged and assigned a reference number at the time of receipt. Submissions that do not include a contact email address cannot receive a response.
Postal correspondence is accepted for formal legal, regulatory, or institutional communications. Physical mail should be addressed to the editorial office and marked with the relevant subject category — editorial, technical, compliance, or partnership — on the outer envelope to ensure proper routing.
No telephone support line is maintained for general public inquiries. Requests submitted through unofficial channels, including social media platforms, are not monitored and will not receive responses.
For inquiries specific to coverage gaps in Enterprise GIS Implementation, Drone Mapping Services, Indoor Mapping Technology, or 3D Mapping Technology, the submission form is the only intake channel that guarantees review by a qualified subject editor with domain-specific expertise in geospatial systems.
Report a Data Error or Correction
Found incorrect information, an outdated fact, or a broken link? Use the form below.
To report a correction or suggest an update:
Please include the page URL and a description of the issue.
For general questions: