Geospatial Data Act federal agency compliance
Geospatial Data Act compliance: manage federal location data from acquisition to public release
A working guide for the federal team responsible for geographic information. Use it to identify the agency’s legal scope, inventory location-based datasets, document quality and metadata, protect personal and licensed information, coordinate data themes, plan budgets, and prepare for the recurring Inspector General audit. The GDA is a stewardship and governance obligation across a data lifecycle, not a badge an agency or vendor earns.
- Issuing authority
- Federal Geographic Data Committee (FGDC), Office of Management and Budget, covered-agency Inspectors General
- Timing
- Operate continuously. The Act requires an annual agency report to the FGDC on strategy implementation and other responsibilities, an inventory of geospatial data assets for budget submissions, and an Inspector General audit at least once every two years. Set the exact annual reporting and budget dates from the agency’s current FGDC, OMB and budget instructions; the statute does not create one universal calendar date for every artifact. Run metadata and inventory quality checks monthly and complete a management evidence freeze well before each IG audit.
- Reviewed
- Inside this guide
- 7 steps · 7 templates
Who it applies to
The Geospatial Data Act applies to covered agencies that collect, produce, acquire, maintain, distribute, use or preserve geospatial data for their missions, including work performed through state, local, tribal, academic, business-partner or contractor relationships. The statutory definition includes executive departments, NASA and GSA, while excluding specified Department of Defense and intelligence-community activities. Counsel should confirm component-level scope and any national-security exclusions. Contractors and grantees may have assigned duties through award terms, but the covered agency remains responsible for its statutory program.
What you’ll produce
A current agency geospatial strategy and owner map; complete inventory of data assets and NGDA theme relationships; standards-based metadata records; documented search-before-buy decisions; privacy, confidentiality and license reviews; auditable acquisition and funding evidence; annual report inputs; and a two-year audit evidence room.
The Act contains 13 covered-agency responsibilities, and the IG review is broader than a catalog check: it examines collection, production, acquisition, maintenance, distribution, use and preservation, standards and metadata, and restrictions on Federal funding. Auditors describe the program’s status against the current implementation framework, so do not turn one agency’s audit language into a universal certification or pass rate. HUD’s September 2026 OIG report said it met all 13 duties during implementation but still identified improvements in four areas and made five recommendations. GSA’s October 2026 report listed five open recommendations on property-location accuracy, strategy, reuse searches and agency governance. Commerce’s October 2026 fourth biennial audit found full compliance with 11 of 13 responsibilities and partial compliance with two. Its gaps involved an expired strategy that was updated but lacked an implementation performance framework, and metadata that was incomplete, lower quality or unavailable. These are three agency-specific snapshots with different scopes and conclusions, not a government-wide rate. The most common trap is to publish a dataset while its metadata, licensing, privacy and re-identification review, retention schedule or upstream partner evidence remains unresolved. Funding restrictions are theme-specific: § 2809 generally bars Federal funds for nonconforming collection, production, acquisition, maintenance or dissemination starting five years after standards for each NGDA theme are established, subject to statutory exceptions. A waiver request has to be submitted at least 30 days before that theme’s implementation date and include a compliance plan and target date. Do not apply one blanket deadline across all themes.
Run the project
Go to the roadmapDecisions for leadership
- What applies to each entity, product and activity?
- Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
- Who will do the work and who can sign?
- Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
- Which deadlines can we promise?
- Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
- Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
- Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
- Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
Geospatial Data Act federal agency compliance kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Determine statutory scope and assign accountable owners · Agency counsel + Senior Agency Official for Geospatial Information + Chief Data Officer [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
- Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
- Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
- Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
- Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
How this works in practice
Two questions to check scope
- Does the activity create, maintain, buy, use or share information tied to a location?
- Which agency component owns the asset and which NGDA theme or lead agency applies?
- Has the team checked privacy, re-identification, confidentiality, licensing and retention before sharing?
- Can the metadata and source inventory be exported, validated and traced back to the authoritative dataset?
Worked scenario
A contractor is collecting street-level imagery and parcel attributes for a federal resilience program. The program manager first searches GeoPlatform, agency catalogs and partner sources, then records why existing data does not meet the mission need. The data steward assigns the dataset to an owner and theme, checks whether imagery reveals people or sensitive facilities, confirms the license permits the planned public use, and selects an FGDC-endorsed metadata profile. Engineering records collection date, lineage, coordinate reference system, accuracy and known gaps. Records management confirms the retention schedule. The acquisition office puts metadata, delivery, correction, accessibility and reuse rights into the contract. Before publication, Privacy and Security approve a release copy, the steward validates required metadata fields and services, and an independent reviewer samples records against the source files. The team saves the decision, metadata validation output, contract acceptance and publication receipt for the annual report and next IG audit.
What to read next
- Federal FISMA audit readiness
Use the audit evidence method for owner assignments, sampling, management response and corrective-action retesting.
- CCPA / CPRA
Use when location data is also personal information about California residents.
Official milestones
See the deadline calendar- Before Federal funds are committed to new geospatial collection
Document search for existing data sources
43 U.S.C. § 2808(a)(11) requires covered agencies to search available sources, including GeoPlatform, before spending for collection.
Official reference (opens in a new tab) - Annually
Submit strategy and compliance achievement report to FGDC
Use the reporting format and deadline in current FGDC and agency instructions.
Official reference (opens in a new tab) - At each agency budget submission
Include geospatial data in budget planning and maintain asset inventory
Use current OMB instructions and retain traceability from requested investment to data assets.
Official reference (opens in a new tab) - At least once every two years
Prepare for the IG audit of geospatial data lifecycle and compliance
Audit covers collection through preservation, standards and metadata, agency duties and Federal funding limits.
Official reference (opens in a new tab) - Five years after standards are established for each NGDA theme
Check that newly funded geospatial data work complies with applicable theme standards
43 U.S.C. § 2809 applies a theme-specific funding limitation, subject to exceptions for some pre-existing data.
Official reference (opens in a new tab) - At least 30 days before a theme-specific implementation date
Submit any § 2809 waiver request
Include reasons, a detailed standards-compliance plan and the date compliance will be achieved.
Official reference (opens in a new tab)
- 01Determine statutory scope and assign accountable owners, Agency counsel + Senior Agency Official for Geospatial Information + Chief Data Officer, about 14 days
- 02Build a complete, source-reconciled data asset inventory, Chief Data Officer + Geospatial data steward + System owners + Acquisition data lead, about 30 days
- 03Map each dataset to themes, strategy goals and lead-agency coordination, Geospatial program office + NGDA theme contact + Mission owner, about 21 days
- 04Write, approve and fund the agency geospatial strategy, Senior Agency Official for Geospatial Information + Chief Data Officer + CFO + Mission executives, about 45 days
- 05Acquire or collect data only after reuse and rights checks, Program manager + Geospatial data steward + Acquisition + Counsel + Privacy, about 14 days
- 06Validate metadata, privacy, confidentiality and records treatment, Data steward + Privacy officer + Records officer + Security + Subject-matter reviewer, about 30 days
- 07Publish, report and prepare the biennial audit evidence, Agency geospatial contact + CDO + IG liaison + Data owners, about 30 days
Step by step
Checklist, instructions and 7 templates.
View plan as a table
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Determine statutory scope and assign accountable owners | Agency counsel + Senior Agency Official for Geospatial Information + Chief Data Officer | At program intake; recheck after mission, component or data-sharing changes | Set a start date | Signed applicability memo and named responsibility matrix | Open |
| Build a complete, source-reconciled data asset inventory | Chief Data Officer + Geospatial data steward + System owners + Acquisition data lead | Initial baseline within 30 days; reconcile quarterly and before annual reporting | Set a start date | Versioned geospatial data inventory with reconciled source totals and an exception register | Open |
| Map each dataset to themes, strategy goals and lead-agency coordination | Geospatial program office + NGDA theme contact + Mission owner | Before collection or acquisition; refresh for each annual strategy review | Set a start date | Theme mapping and strategy-to-asset crosswalk | Open |
| Write, approve and fund the agency geospatial strategy | Senior Agency Official for Geospatial Information + Chief Data Officer + CFO + Mission executives | Maintain continuously; refresh on the agency’s approved strategic-planning cycle and before the annual FGDC report | Set a start date | Approved strategy, funded roadmap and measurable performance framework | Open |
| Acquire or collect data only after reuse and rights checks | Program manager + Geospatial data steward + Acquisition + Counsel + Privacy | Before committing Federal funds or issuing a collection task order | Set a start date | Reuse-first decision memo, acquisition clauses and acceptance criteria | Open |
| Validate metadata, privacy, confidentiality and records treatment | Data steward + Privacy officer + Records officer + Security + Subject-matter reviewer | At creation and every material update; before external disclosure | Set a start date | Validated metadata record, disclosure decision, license and privacy review, approved records schedule | Open |
| Publish, report and prepare the biennial audit evidence | Agency geospatial contact + CDO + IG liaison + Data owners | Annual FGDC and budget-report cycle; IG audit at least once every two years | Set a start date | Publication receipts, annual report evidence pack and audit-ready control/evidence index | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
- 01
Determine statutory scope and assign accountable owners
Map every component and funded activity that collects, produces, acquires, maintains, distributes, uses or preserves location-tied data. Record agency and contractor roles, data flows, national-security exclusions and statutory rationale. Identify the agency geospatial contact, NGDA theme leads, Privacy, Security, Records, Acquisition, budget and data owners. Counsel signs off on disputed scope; an exclusion is not inferred from a dataset label.
What to produce
Signed applicability memo and named responsibility matrixApplicability and RACI memo
Gather first
- Agency component list
- Mission descriptions
- GIS and imagery catalog
- Contracts and grants
- Data-flow diagrams
- Current 43 U.S.C. Chapter 46
- National-security exclusions
How to prepare it
- Create one row per agency component and activity. Mark collect, produce, acquire, maintain, distribute, use or preserve, including contractor and partner activity.
- For each row record the legal entity, mission, data type, responsible official, funding source, partners, proposed exclusion, supporting authority and counsel decision. Do not presume every activity of a covered agency is in scope or excluded.
- Assign one accountable owner for each requirement: strategy, inventory, standards, privacy, records, acquisition, budget, theme coordination, annual reporting and IG evidence. Record delegates and escalation route.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional scope row
- A federally funded resilience grant produces parcel-level flood layers at a state university. The agency records its covered-agency role, grant terms, data owner, intended disclosure, privacy and licensing reviews, and the reason the data is included in its stewardship inventory.
- Exclusion review
- A component proposes an exclusion for a sensitive facility layer. Counsel records the exact statutory basis, approving official, affected files and whether a releasable generalized product can still support the mission.
Check before handing it over
Each scope call is tied to an activity and a documented authority, with owners assigned to the actual work.
Have agency counsel approve scope before the inventory baseline and audit population are frozen.
- 02
Build a complete, source-reconciled data asset inventory
Collect asset rows from GIS catalogs, cloud storage, data warehouses, contracts, grants, field programs, partner agreements and published services. Assign a stable asset ID. Capture title, description, geographic extent, collection vintage, responsible owner, source, scale or resolution, coordinate reference system, accuracy, update cadence, sensitivity, license, retention schedule, theme, metadata profile, access URL and lifecycle state. Reconcile duplicate, unknown and orphan records instead of deleting them. Preserve the query, count, unmatched items and disposition.
What to produce
Versioned geospatial data inventory with reconciled source totals and an exception registerAsset inventory
Gather first
- GIS catalog
- GeoPlatform exports
- Cloud and data-lake catalogs
- Program lists
- Contracts and grants
- Records schedules
- Published service endpoints
How to prepare it
- Define the inventory population and preserve dated extracts from every source. Create a stable asset identifier and retain source identifiers for traceability.
- Capture title, owner, mission, geographic extent, collection vintage, coordinate reference, scale or resolution, accuracy, source lineage, theme, metadata profile, sensitivity, license, retention, update cycle, access URL and status.
- Reconcile totals by source and classify every row as matched, duplicate, orphaned, retired, new or out of scope. Assign an accountable owner and dated decision to each exception; obtain a second-person review of completeness.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional exception
- The program catalog lists a wildfire perimeter service absent from GeoPlatform. Preserve the catalog row, identify the service owner, test whether it is already represented under another ID, and either link the authoritative record or log a scope decision and remediation date.
- Quality metric
- Report both reconciled assets divided by the known in-scope union and the raw unresolved item count. Do not exclude unmatched assets from the denominator to improve the percentage.
Check before handing it over
An auditor can reproduce the source union, trace every inventory asset to an authoritative system and inspect unresolved gaps.
Use the frozen inventory to support strategy, annual reporting, budget planning and audit sampling.
- 03
Map each dataset to themes, strategy goals and lead-agency coordination
For each asset, identify whether it is a National Geospatial Data Asset or supports a designated theme. Record the lead agency, theme plan, authoritative source, dependencies, standards and sharing service. Link the asset to an agency strategy goal, mission need, expected user and outcome measure. If no theme applies, document why and identify the applicable catalog and coordination path. Assign a named contact for lead-agency collaboration.
What to produce
Theme mapping and strategy-to-asset crosswalkTheme and strategy register
Gather first
- Asset inventory
- NGDA theme list
- Lead-agency plans
- Agency strategy
- Mission measures
- Partner agreements
How to prepare it
- Map each asset to the relevant NGDA theme and theme lead where applicable. Record lead contact, theme-plan version, standards, authoritative data source and planned contribution.
- Link the asset to a strategy goal, mission owner, users, expected outcome, data-quality objective and delivery channel. Flag assets supporting multiple themes or agency missions.
- Record the annual review date, partner input, decision, dependencies and an explanation for assets with no applicable theme. Reconcile the map to the asset inventory and strategy milestones.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional crosswalk
- A coastal inundation layer supports emergency management and a national elevation theme. The row names both mission owners, identifies NOAA as the relevant theme lead where applicable, and links accuracy and update targets to the agency strategy.
Check before handing it over
Every theme and strategy claim has an owner, authoritative source and measurable relationship to real assets.
Give the crosswalk to the Senior Agency Official for Geospatial Information and annual-report owner.
- 04
Write, approve and fund the agency geospatial strategy
Set mission outcomes, priority datasets, standards, shared services, partner roles, staffing, acquisition needs, privacy safeguards and milestones. Include a performance framework with baseline, target, owner, source and review cadence. Reconcile strategy commitments to budget requests and the asset inventory. Obtain approval from the authorized executive and publish the approved version where required. Record version, superseded strategy and implementation status.
What to produce
Approved strategy, funded roadmap and measurable performance frameworkStrategy and operating plan
Gather first
- Prior strategy
- Current NSDI strategic plan
- Asset inventory
- Mission plans
- Budget submissions
- Staff and contract forecasts
- IG recommendations
How to prepare it
- Set a baseline and measurable target for each goal. Name the accountable official, source system, review cadence, funding and dependencies.
- Cover data acquisition and reuse, standards, metadata, privacy, partner coordination, shared services, preservation and workforce. Map commitments to responsible units and the statute’s covered-agency duties.
- Reconcile each milestone to budget and procurement evidence. Obtain executive approval, publish the approved version where required and retain the superseded strategy and implementation review.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional measure
- Goal: improve discovery of agency geospatial assets. Baseline is the number of in-scope assets with complete required metadata at the first validated inventory freeze; the quarterly target, data source, accountable office and funding are recorded separately.
- Governance check
- A published strategy without an owner, implementation measures or resources is not proof that the agency has implemented it.
Check before handing it over
The strategy is approved, funded, linked to assets and measurable during the next annual report and audit.
Submit milestones and resource needs into agency budget and performance planning.
- 05
Acquire or collect data only after reuse and rights checks
Search GeoPlatform and other Federal, state, local, tribal, academic and private sources to determine if existing data meets the need. Compare fitness for purpose: geography, vintage, completeness, accuracy, license, restrictions, resolution, service availability and total lifecycle cost. Document why reuse is adequate or why new collection is necessary. Put standards, metadata, lineage, quality acceptance, correction, privacy, security, accessibility, retention, machine-readable formats, reuse rights and export obligations in the contract or grant. Check statutory and acquisition-specific funding conditions separately.
What to produce
Reuse-first decision memo, acquisition clauses and acceptance criteriaAcquisition decision and contract schedule
Gather first
- Mission requirement
- GeoPlatform search
- Agency catalogs
- Partner sources
- License terms
- Cost estimates
- Privacy and security requirements
How to prepare it
- Search GeoPlatform and relevant Federal, state, local, tribal, academic and private sources before paying to collect new data. Record search terms, date, datasets considered and source owners.
- Compare fitness for purpose: geography, vintage, accuracy, completeness, latency, access, licensing, restrictions, lifecycle cost and privacy or security constraints. Explain the decision and approvals.
- Put required metadata profile, lineage, coordinate reference, accuracy, delivery schema, validation rules, correction turnaround, change notice, public release rights, accessibility, retention, security and exit/export duties into the award.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional reuse decision
- An existing county parcel layer is current enough for planning but lacks emergency access attributes and has a license limiting redistribution. The memo records the gap and uses a bounded acquisition for the missing attribute, with a written rights plan.
- Acceptance example
- Reject a delivery if a required coordinate reference, accuracy statement or lineage field is absent; log defect, responsible vendor, correction deadline, retest and acceptance approval.
Check before handing it over
The agency can show it considered existing data before spending and purchased data it can validate, preserve and lawfully use.
Route the memo through Acquisition, Counsel, Privacy, Security and the program official before award.
- 06
Validate metadata, privacy, confidentiality and records treatment
Select the currently applicable FGDC-endorsed or agency-required metadata standard. Do not assume the legacy CSDGM is always the required profile; confirm the current standard and service schema. Validate title, abstract, owner, lineage, source, vintage, geographic extent, coordinate reference, accuracy, limitations, access conditions, update frequency and contact. Review Privacy Act and re-identification risk, sensitive-location harm, confidential or licensed inputs, security controls and approved records schedule. Keep sensitive review notes separate from public metadata.
What to produce
Validated metadata record, disclosure decision, license and privacy review, approved records scheduleMetadata and disclosure review
Gather first
- Dataset and lineage
- Selected FGDC or agency profile
- Privacy analysis
- License and partner terms
- Security classification
- NARA-approved schedule
How to prepare it
- Select the current required metadata standard and target profile. Follow the agency’s GeoPlatform/Data.gov schema and FGDC-endorsed standards; verify whether ISO 19115, a profile or a transition exception applies. Do not assume the older CSDGM is the sole current standard.
- Validate title, abstract, publisher, owner, source, lineage, vintage, geographic extent, coordinate reference, accuracy, limitations, update cadence, access constraints, contact and distribution link. Preserve validation output and fix failed mandatory fields.
- Before disclosure, assess Privacy Act implications and re-identification risk, including small-area combinations and sensitive locations. Check confidentiality, security, partner rights, license conditions, records schedule and any permitted redaction or aggregation. Approve the public metadata and dataset as separate release objects.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional metadata check
- A census-block layer has complete provenance but no documented coordinate reference or limitations. The validator blocks release, assigns the GIS lead to correct both fields, and reruns schema validation after the owner signs off.
- Privacy decision
- A point layer could identify a person’s home and a protected service location. The privacy reviewer compares aggregation and masking options, records residual re-identification risk and approves only the release version with controlled precision.
Check before handing it over
The public record accurately describes the dataset, passes the applicable schema and has a documented disclosure decision.
Keep the signed review with the release version, not only in the project’s email thread.
View template for Validated metadata record, disclosure decision, license and privacy review, approved records scheduleView example for Validated metadata record, disclosure decision, license and privacy review, approved records scheduleFGDC endorsed metadata standards and guidance (opens in a new tab) - 07
Publish, report and prepare the biennial audit evidence
Publish approved, non-sensitive metadata through GeoPlatform and required agency catalogs. Verify machine readability, service availability, accessibility and the actual dataset-to-metadata link. Assemble the annual report from the inventory, strategy measures, coordination, investment and disclosure records. For the IG audit, provide a complete population, current source exports, tested metadata samples, funding and acquisition decisions, privacy and records decisions, prior findings and owner attestations. Track questions and corrective actions without altering historic evidence.
What to produce
Publication receipts, annual report evidence pack and audit-ready control/evidence indexAnnual report and audit evidence room
Gather first
- Approved strategy
- Current asset inventory
- Metadata validation
- Acquisition search decisions
- Privacy and records decisions
- Budget records
- Prior recommendations
How to prepare it
- Publish approved metadata to GeoPlatform and required catalogs. Test that records are discoverable, machine-readable and linked to the intended dataset or service. Save timestamp, record ID and service response.
- Build annual report inputs from the same frozen inventory and strategy measures. Reconcile counts, explain changes, identify incomplete assets and document coordination, budget and stewardship work.
- For the at-least-biennial IG audit, map each statutory responsibility to the policy, owner, data population, evidence, test, exception and corrective action. Include collection through preservation and the Federal funding restriction review.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional audit sample
- The auditor selects a funded imagery contract. The index links the pre-award reuse memo, contract metadata clause, delivery validation, license, privacy review, approved release record, retention schedule and annual-report asset row.
- Metric example
- Track required-metadata completeness with numerator, denominator, dataset population, schema version and snapshot date, then separately report how many incomplete records block user needs.
Check before handing it over
The annual assertions can be traced to source systems and the audit team can sample one asset end to end without recreating history.
Deliver the evidence index through the agency-approved secure channel and retain access and version logs.
Official sources
- 43 U.S.C. § 2801 · Definitions and covered-agency scope (opens in a new tab)
- 43 U.S.C. § 2804 · National Spatial Data Infrastructure and privacy goals (opens in a new tab)
- 43 U.S.C. § 2806 · Geospatial standards (opens in a new tab)
- 43 U.S.C. § 2808 · Agency duties, reporting and biennial audits (opens in a new tab)
- 43 U.S.C. § 2809 · Restrictions on Federal funds (opens in a new tab)
- FGDC · Current metadata standards and transition guidance (opens in a new tab)
- FGDC · Federal roles and responsibilities (opens in a new tab)
- Commerce OIG · FY 2026 GDA audit, OIG-27-003-A (opens in a new tab)
- Commerce OIG · Final audit report PDF (opens in a new tab)
- HUD OIG · FY 2026 GDA implementation-stage review, 2026-FO-0005 (opens in a new tab)
- GSA OIG · FY 2026 GDA audit, A260022ITF27001 (opens in a new tab)
- FGDC · Geospatial Data Act program and agency resources (opens in a new tab)