Key Dimensions and Scopes of Technology Services

The scope of technology services in the United States is defined by intersecting variables: geography, regulatory jurisdiction, operational scale, and delivery model. These dimensions determine which providers are qualified to operate, which standards govern their work, and where service boundaries begin and end. This page covers the structural framework used to assess technology service scope across the mapping systems sector, with reference to the regulatory bodies, standards organizations, and classification criteria that shape professional practice.

• Geographic and Jurisdictional Dimensions
• Scale and Operational Range
• Regulatory Dimensions
• Dimensions That Vary by Context
• Service Delivery Boundaries
• How Scope Is Determined
• Common Scope Disputes
• Scope of Coverage

Geographic and jurisdictional dimensions

Technology services, particularly those involving geospatial data and mapping systems, operate within a layered jurisdictional framework that combines federal standards, state-level licensing requirements, and local government data governance policies. The federal layer is anchored by the Federal Geographic Data Committee (FGDC), which publishes the National Spatial Data Infrastructure (NSDI) framework and enforces metadata and interoperability standards through OMB Circular A-16. At the state level, 34 states maintain GIS coordination offices with varying authority over spatial data acquisition, accuracy thresholds, and public data licensing.

International scope adds complexity for providers operating across US borders. The International Organization for Standardization (ISO) publishes ISO 19115 as the global standard for geographic information metadata, and US federal agencies are required by FGDC policy to align metadata practices with ISO 19115-1:2014. Providers delivering services under contract to federal agencies — particularly the Department of Defense, USGS, or NOAA — must meet both FGDC content standards and agency-specific data rights clauses under DFARS or FAR Part 27.

Jurisdictional boundaries for drone-based mapping add another layer. The Federal Aviation Administration (FAA) governs airspace under 14 CFR Part 107, which restricts commercial drone mapping services to operators holding a Remote Pilot Certificate. Operations in Class B, C, D, or E airspace require FAA authorization through the Low Altitude Authorization and Notification Capability (LAANC) system. State and municipal overflights may impose additional restrictions, particularly over critical infrastructure corridors.

Scale and operational range

Technology service scope scales across four primary operational ranges, each carrying distinct infrastructure, staffing, and certification requirements.

Enterprise GIS implementation projects at the national scale typically involve data volumes exceeding 1 terabyte of raster imagery, requiring distributed processing architectures and formal data governance documentation. The Open Geospatial Consortium (OGC) publishes interoperability standards — including OGC API Features and Web Map Tile Service (WMTS) — that govern how large-scale systems exchange data across organizational boundaries.

At the site level, indoor mapping technology operates within constraints defined by building information modeling (BIM) standards, including ISO 19650 for asset information management. These projects typically require sub-10-centimeter positional accuracy, which drives the choice between photogrammetry, LiDAR, or structured-light scanning methods.

Regulatory dimensions

The regulatory landscape for technology services in the mapping sector intersects federal data standards, export control law, privacy statute, and sector-specific mandates.

Federal data standards. FGDC-STD-001-1998 (Content Standard for Digital Geospatial Metadata) remains the baseline reference for federally funded geospatial projects, though agencies increasingly reference the ISO 19115 alignment published in FGDC's 2014 guidance documents.

Export controls. High-resolution satellite imagery and satellite imagery services with resolution below 0.5 meters are subject to export licensing under the Export Administration Regulations (EAR), administered by the Bureau of Industry and Security (BIS) under 15 CFR Parts 730–774. Commercial remote sensing satellites require licensing from NOAA's Commercial Remote Sensing Regulatory Affairs (CRSRA) office under 15 CFR Part 960.

Privacy law. Location data derived from mobile devices is regulated under a patchwork of state statutes. California's Consumer Privacy Act (CCPA) classifies precise geolocation data as "sensitive personal information" under Civil Code § 1798.121, requiring opt-in consent before collection. Virginia, Colorado, and Connecticut have enacted comparable statutes with similar geolocation provisions. Providers deploying geofencing technology for commercial or public-sector clients must evaluate compliance obligations state by state.

Critical infrastructure. Mapping systems serving energy, water, or transportation infrastructure are subject to CISA guidance under Presidential Policy Directive 21 (PPD-21). Utility and infrastructure mapping projects that produce pipeline centerline data or substation locations must comply with information security controls referenced in NIST SP 800-82 and, for electric utilities, NERC CIP standards.

Dimensions that vary by context

Scope parameters that remain fixed in one context become variable in another, creating classification challenges across the technology services sector.

Accuracy requirements vary by end use. The National Map Accuracy Standards (NMAS) require 90% of well-defined points tested to fall within 1/30 inch of true position at publication scale for Class 1 maps — a threshold irrelevant for real-time navigation but critical for cadastral and engineering applications.

Data licensing shifts between open, restricted, and proprietary depending on the funding source. Data produced under federal contract is typically subject to unlimited rights clauses under FAR 52.227-14. State-produced spatial data may carry Creative Commons licensing or restrictive redistribution terms depending on jurisdiction.

Temporal resolution is context-dependent. Real-time mapping systems used in emergency response require sub-second data refresh rates, while environmental monitoring mapping applications may operate adequately on weekly satellite revisit cycles.

Vertical datum selection affects elevation accuracy across applications. NOAA's National Geodetic Survey (NGS) maintains NAVD 88 as the operative vertical datum for most US applications, though the transition to NAPGD2022 (the North American-Pacific Geopotential Datum of 2022) will alter elevation values by as much as 1.5 meters in parts of the western United States when fully deployed.

Service delivery boundaries

Technology service delivery in the mapping sector is bounded by four structural categories: data acquisition, data processing, platform hosting, and professional services.

Data acquisition includes field survey, aerial and satellite remote sensing, LiDAR scanning, and crowdsourced data collection. Each acquisition method carries distinct positional accuracy characteristics and associated quality control requirements. LiDAR mapping technology achieves typical vertical accuracy of ±5–15 centimeters under optimal conditions, as documented in USGS Lidar Base Specification Version 2.1.

Data processing encompasses georeferencing, classification, feature extraction, and format conversion. ISO/TC 211 (Geographic Information/Geomatics) publishes the technical committee standards that define processing workflows for interoperability, including ISO 19157 for data quality.

Platform hosting spans on-premises server infrastructure, private cloud, and public cloud deployments. Cloud-based mapping services introduce additional scope considerations around data residency, latency, and FedRAMP authorization status for federally contracted work.

Professional services include spatial analysis techniques, system integration, training, and certification support. Providers engaged in mapping system integration must document interface specifications against the client's existing enterprise architecture, typically referencing The Open Group Architecture Framework (TOGAF) or the Federal Enterprise Architecture Framework (FEAF).

How scope is determined

Scope determination for technology service engagements follows a structured sequence of inquiry, regardless of project size.

Scope determination sequence:

1. Define the geographic extent using coordinate reference system (CRS) specification — typically a named EPSG code from the EPSG Geodetic Parameter Dataset maintained by the International Association of Oil and Gas Producers (IOGP).
2. Establish the required accuracy class using applicable standards (NMAS, ASPRS Positional Accuracy Standards for Digital Geospatial Data, or project-specific tolerances).
3. Identify regulatory obligations: federal data standards, state licensing, export controls, and sector-specific mandates.
4. Classify data sensitivity: public, controlled unclassified information (CUI), or classified — using the National Archives CUI Registry.
5. Determine delivery model: data-as-a-service, platform-as-a-service, or managed service, with associated SLA thresholds.
6. Specify integration requirements against target systems, referencing OGC API standards or proprietary API specifications for mapping APIs and SDKs.
7. Document data lifecycle terms: retention, archiving, and destruction aligned with NARA records schedules where federal contracts are involved.

Mapping data accuracy and validation forms the core quality gate in this sequence. The American Society for Photogrammetry and Remote Sensing (ASPRS) 2015 Positional Accuracy Standards define five accuracy classes (A through E) by Root Mean Square Error (RMSE) thresholds, providing the primary classification framework for data deliverable acceptance.

Common scope disputes

Scope disputes in technology services concentrate around four recurring fault lines.

Accuracy class ambiguity. Contracts that specify "survey-grade accuracy" without referencing a named standard — such as ASPRS Class 1 or NGS Third-Order — produce acceptance disputes when deliverable accuracy is tested. The ASPRS 2015 standards define RMSE thresholds precisely: RMSE ≤ 2.5 cm for Class A vertical accuracy, escalating to RMSE ≤ 20 cm for Class E.

Data rights boundaries. Federal contractors and their subcontractors frequently dispute whether derived data products (mosaicked imagery, classified point clouds, feature layers) constitute "developed exclusively at private expense" under FAR 52.227-14, which would restrict government unlimited rights claims. Geospatial data standards documentation and audit trails of processing steps are the primary evidence in these disputes.

Change in regulatory classification. A project scoped before CCPA amendments or a new FAA authorization requirement may require renegotiation when regulations change mid-contract. Mapping system compliance provisions should reference specific regulatory versions by citation date to limit retroactive application.

Integration scope creep. Web mapping application development projects frequently expand during delivery when undocumented legacy systems require custom connectors not anticipated in the original scope. Interface specification documents referencing specific OGC service types (WMS, WFS, WCS) at contract signature reduce this risk by establishing the baseline integration surface.

Scope of coverage

The scope addressed across this reference covers the full operational spectrum of technology services as applied to mapping and geospatial systems — from sub-meter site surveys to national-scale spatial data infrastructure. Coverage extends to the qualification standards governing professional practice, the regulatory bodies that enforce data and operational requirements, and the classification frameworks that define service boundaries.

Topics spanning the intersection of geospatial technology and enterprise systems — including location intelligence platforms, 3D mapping technology, routing and navigation services, and smart city mapping applications — are treated as discrete service categories with their own scope parameters, each subject to the dimensional framework described on this page. Mapping system security and mapping system costs and pricing represent cross-cutting dimensions that apply regardless of the specific technology category in scope.

The reference framework used throughout this page draws from named standards bodies — FGDC, ASPRS, OGC, ISO/TC 211, NGS, FAA, NIST, and BIS — whose published documents constitute the operative authority for professional practice in this sector.