LP360 Data Handling, Cloud Services, and Network Communication Overview

Applies to: LP360 2026.x and later
Last Reviewed: 18Jun2026

Overview

LP360 is a local-first geospatial processing platform with optional cloud-enabled capabilities through LP360 Online services.

• Core processing of LiDAR, imagery, and derived datasets occurs locally on the user’s workstation or network
• Additional capabilities, including:
  • automated diagnostics
  • cloud-based processing workflows
  • advanced analytics
    are delivered through LP360 Online (cloud) services

This article describes:

• what data is generated and stored
• when data may be transmitted outside the local environment
• how cloud services are used
• where data is hosted

Data Types in LP360

1. Project Data

• LiDAR point clouds
• imagery (camera data)
• derived outputs (surfaces, classifications, etc.)

2. Cycle Data

• Raw datasets collected by TrueView sensors
• Includes:
  • flight data
  • configuration files
  • ancillary files

3. System / Diagnostic Data

• Cycle logs (e.g., CycleLog.csv, system.log)
• Contains:
  • system status
  • warnings and errors
  • operational diagnostics

4. Licensing Metadata

• License activation and validation information
• Limited to system/license-related identifiers

Default Data Behavior (Local Operation)

By default:

• All project data and Cycle datasets are:
  • stored locally
  • processed locally
• LP360:
  • does not require internet connectivity for standard workflows
  • can operate in a fully offline (isolated) environment

Data Transmission Scenarios

Data transmission from LP360 occurs only under specific conditions.

1. Automatic Diagnostic Log Transmission (During Cycle Import)

When importing a Cycle:

✅ If LP360 is connected to the internet:

• Cycle/System log data may be automatically transmitted
• Purpose:
  • automated diagnostic analysis
  • system health evaluation
  • issue detection and troubleshooting support
• Processing is performed by:
  • LP360 Online backend services (e.g., Reckon analysis systems)
• Users may request to optout of this service.

✅ If LP360 is offline:

• No data is transmitted
• All logs remain fully local

2. LP360 Online Services (Cloud Features / Add-Ons)

LP360 Online provides optional cloud-enabled capabilities, including:

• automated diagnostic analysis
• cloud processing workflows
• data management and sharing features
• advanced analytics and automation services

When these services are used:

• Relevant data required for the selected workflow may be transmitted
• This may include:
  • selected dataset components
  • associated system/log data

✅ Important:

• These services are:
  • optional
  • user-driven
• They are not active unless:
  • the system is online, and
  • a cloud-enabled workflow or feature is used

3. Manual Data Sharing (Support and Collaboration)

Users may explicitly upload data:

• Cycle datasets
• logs
• project files

Typical use cases:

• technical support
• collaboration or data sharing

✅ All such transfers are:

initiated and controlled by the user

4. Licensing Communication

LP360 communicates with licensing systems for:

• product activation
• license validation

Characteristics:

• Transmitted data:
  • minimal licensing-related metadata only
• Not transmitted:
  • project data
  • imagery
  • Cycle/System logs

Cloud Architecture and Hosting

LP360 Online Services

• Hosted on Amazon Web Services (AWS)
• Region: United States (US East)

This includes:

• backend processing systems (e.g., automated diagnostics / Reckon services)
• cloud-enabled LP360 Online features

Cloud Processing Data Flow and Third-Party Services

As part of LP360’s expanded cloud-enabled capabilities—such as DJI L2 Cloud Batch Processing and AI Ground Classification—the following describes how data is transferred, processed, and retained, including involvement of third-party service providers.

Processing models used by LP360 cloud workflows may be hosted either within LP360-managed infrastructure or within third-party environments, depending on the specific workflow and service being used.

Processing Model Hosting Comparison

Data Transferred to the Cloud

When cloud processing workflows are used, the following data types may be uploaded:

• Raw LiDAR flight data (e.g., LAS, SBET files)
• Trajectory and positioning data (e.g., RTK/PPK base station data, antenna height)
• Project metadata (e.g., coordinate system, flight line definitions)
• User-defined processing parameters
• Derived outputs (e.g., point cloud classifications such as ground, vegetation, structures)

All cloud transfers are explicitly initiated by the user through LP360.

Security and Access Control

• All data transfers occur over secure HTTPS/TLS-encrypted connections
• No data is transmitted without explicit job submission
• LP360 and processing partners do not perform background synchronization or archiving
• Access to results is controlled through the LP360 cloud portal and tied to licensing

Hosting Infrastructure

LP360 cloud services operate using a combination of GeoCue-managed infrastructure and third-party processing environments:

• Primary Platform: Amazon Web Services (AWS), United States
• Job Management: Handles job submission, queuing, and execution
• Cloud Portal: Manages user access and licensing

Third-party processing services are used only during active job execution:

• DJI Processing: AWS infrastructure located in the United States
• The Cross Product (TCP): servers located in France
• FLAI (Enhanced AI Tools): AI models hosted within LP360 Online infrastructure (AWS, United States)

Data Retention Model

• Temporary Processing Storage: Third-party providers retain data only during job execution
• User Responsibility: Users are responsible for downloading and archiving results
• License Dependency: Continued access to results may require an active LP360 Cloud license

DJI L2 Cloud Batch Processing

• Primary Storage: Data remains on LP360 AWS infrastructure (U.S.) until user deletion
• Processing Transfer: Temporarily transferred to DJI-hosted AWS infrastructure (U.S.)
• Retention:
  • Deleted after successful processing
  • May be temporarily retained for debugging if processing fails

AI Ground Only Classification (The Cross Product)

• Primary Storage: Hosted on LP360 AWS infrastructure (U.S.)
• Processing Transfer: Temporarily transferred to TCP servers in France
• Return Path: Results are returned to LP360 cloud storage after processing
• Retention:
  • No long-term retention by TCP
  • Temporary retention may occur only for failure diagnostics

Enhanced AI Tools (FLAI)

• Applicable Tools: AI Ground+, AI Forestry, AI Utilities
• Model Hosting: AI models are deployed and executed within LP360 Online infrastructure (AWS, United States)
• Data Transfer:
  • No transfer to external third-party processing environments
  • All processing occurs within the LP360-managed cloud environment
• Data Residency: Data remains within U.S.-hosted AWS infrastructure
• Retention:
  • Consistent with LP360 cloud storage model
  • No independent retention by FLAI outside LP360 infrastructure

✅ Key Takeaway: All cloud processing in LP360 is user-initiated and purpose-limited. Data may be temporarily transferred to third-party providers only where required for specific workflows (e.g., DJI, TCP). Enhanced AI tools powered by FLAI operate entirely within LP360’s managed AWS environment.

Licensing Infrastructure

• Hosted on U.S.-based infrastructure
• Separate from AWS-hosted LP360 Online services

Offline and Restricted Environments

LP360 supports operation in secure environments:

• Offline / Air-Gapped Mode
  • No data is transmitted externally
  • All processing remains local
• Restricted Network Environments
  • External communication can be controlled through:
    • network policies
    • firewall rules

What Does NOT Occur

Unless explicitly triggered by one of the scenarios above:

• ❌ No automatic upload of full project datasets
• ❌ No continuous or background synchronization of all data
• ❌ No transmission of imagery or LiDAR data by default
• ❌ No data transfer when operating offline

Summary

LP360 follows a local-first architecture with controlled cloud interaction:

• Project data remains local by default
• Diagnostic log data may be transmitted:
  • during Cycle Import when online
• Additional data transmission occurs only when:
  • LP360 Online (cloud) services are used, or
  • the user explicitly uploads data

All external services:

• operate within U.S.-based infrastructure
• are limited in scope to the functionality being used

Related Topics

• LP360 Cloud Services Overview
• LP360 Licensing and Activation
• TrueView Cycle Data Structure
• Archiving Cycles to LP360 Cloud

📬 Need More Information?

If your organization requires:

• formal security documentation
• data residency confirmation
• cloud architecture details

please Contact Support or your GeoCue representative for additional materials.