One capture.
Digital
intelligence.

Inside the P3D package

P3D is a packaged digital asset: captured appearance, media and machine-readable context stay together. The archive-style structure uses a manifest to describe the product and link its visual, textual and optional spatial layers. A consumer opens one asset and extracts the information needed for its task.

What is included

A concrete package example

The supplied image-stack export contains manifest.json and 360 PNG files under images/. Richer exports add the applicable media and spatial payloads. A package’s manifest is the guide to its actual content.

Use cases: one asset, multiple possibilities

These uses share a common requirement: preserve appearance and meaning together. Free navigation, relighting, physics and geometric interaction are separate rendering or modeling requirements; a view-based asset supplies captured viewpoints and can feed a richer reconstruction workflow when required.

File compression and AI-ready delivery

The product family offers four size profiles: Ultra 200 MB, High 80 MB, Medium 40 MB and Lite 4 MB. They provide a 50-fold range in delivered file size, allowing a rich source asset and compact distribution copies to serve different deployment needs.

Where the efficiency comes from

Image-led assets avoid making dense geometry part of every distribution copy. Resolution, frame count, encoding and included data layers determine the payload. The media is already encoded before archive packaging, so most of the space saving comes from the representation and profile choices rather than repeatedly ZIP-compressing an image.

¹ Decimal units. Storage totals equal nominal file size × 10,000 and exclude replicas, backups and indexes. Lower-resolution profiles do not imply unchanged pixel detail or identical spatial payloads. The reported 4K capability belongs to high-definition capture and appropriate exports, not automatically to every 4 MB file.

Why compact, structured assets help AI workflows

Compact deployment copies reduce the bytes moved and stored for those copies. The manifest keeps the product identity connected to extracted views and textual attributes. AI pipelines can ingest the relevant images and fields rather than first generating and rendering a dense model for an image-based task.

Turnaround time and output options

The automated scanning workflow captures a product with repeatable viewpoints and a controlled sequence. Capture runs from as low as 1 minute to about 7 minutes for a detailed scan, with an average of approximately 6 minutes. Processing takes 7 minutes. These timings replace the earlier 10-minute processing figure.

A shorter capture cycle

Against the 10–20-minute conventional capture reference used by the product team, the 6-minute average is 40–70% shorter, or 1.67–3.33× the capture throughput before processing and handling. This comparison describes that capture reference; it is not a universal timing claim for every scanning system.

Why the processing path is shorter

P3D’s core delivery asset is an indexed image and media representation. Preparing it does not require a complete dense point cloud, watertight mesh, retopology or baked texture atlas. The processing effort is directed toward usable visual frames, indexing, associated information and packaging. Optional depth and sparse spatial data enrich the asset without making dense reconstruction mandatory.

Resolution, profiles and file types

P3D supports 4K high-definition capture for detailed appearance. The distribution profile selects an appropriate payload footprint. The reference export supplied for this paper contains 1080 × 608 PNG frames, and its resolution metadata records 1080; the embedded pixels establish the actual resolution of that sample.

Container versus extracted outputs

The P3D file is the source package. A consuming tool may extract images, transcode sequences to a video, build a dataset record or pass optional spatial information to another application. JPEG/WebP previews, rendered video and reconstructed 3D derivatives are downstream outputs; their availability depends on the exporter or application, not solely on the .p3d extension.

From visual files to digital training records

P3D’s contribution to digital training is the association of evidence: what an object looks like, what it is, what is written on it and how its views relate. A dataset pipeline can extract imagery and structured fields from one object-level record instead of reconciling independently named files and spreadsheets.

Why the architecture changes dataset production

The reusable unit becomes an object with its evidence, rather than a single anonymous image. Additional tasks start from the same captured record: extraction, indexing, annotation and augmentation can preserve the product identity throughout. This reduces repeated source-data assembly and makes provenance easier to carry into downstream datasets.

Multiple views remain observations of the same object. Dataset splits must preserve object identity to avoid training/test leakage. Model accuracy, convergence time and the number of training examples required are properties of a specific experiment, not automatic consequences of the container.

One source for GenAI and content production

P3D turns a scan into a reusable content source. High-definition product views preserve real details; metadata and text provide factual context; optional masks and spatial fields provide additional conditioning. Marketing and creative teams can start successive outputs from the same asset instead of arranging a new shoot for each format.

Capture once; distribute the work

The production gain is the reuse of captured evidence, not a claim that every generated result is automatically correct. Product identity, geometry, branding and visible text still require output review. Photographed reference views improve the input supplied to a generation system; they do not by themselves guarantee a physically accurate generated scene.

Compute the representation the task needs

For product presentation and image-based AI, a dense 3D reconstruction is often an intermediate expense rather than the required output. P3D preserves the captured surface appearance and associated context in 2.5D. It moves dense geometric work off the critical path for tasks that consume images, sequences and product information.

4K appearance and spatial detail are different properties

4K capture preserves fine visual details such as print, finish, color boundaries, texture appearance and visible surface relief. In an image-led asset, this appearance is already photographed rather than recreated by material authoring. A 4K image is not itself a 4K depth map or a measured topographic model. Metric size, depth precision and surface accuracy depend on the optional spatial layer, camera calibration and capture geometry.

Sparse spatial data gives selected geometric anchors while keeping the mandatory asset lightweight. Full model training, reconstruction or complex inference still has its own compute requirements; the efficiency benefit is avoiding that work for every basic viewing or content task.

A product digital twin with visual and factual context

For catalog and product-information workflows, P3D serves as the visual and contextual digital counterpart of a physical item. It links the product’s appearance to identity, descriptions, specifications and capture information. Optional sparse geometry adds a spatial layer for future enrichment.

A catalog digital twin is an appearance-and-information record. Engineering simulation, live operational synchronization and certified measurement need additional validated models, measurements or system connections.

Keep a lightweight spatial foundation

P3D supports an optional sparse point-cloud layer and associated camera-angle information. This retains selected information about shape, scale, surface structure and depth for later spatial processing. The core 2.5D viewing workflow stays usable without reconstructing every surface into a dense 3D model.

The lightweight benefit comes from carrying a selective spatial representation and invoking further processing only when needed. Rich images remain available for future algorithms while the asset avoids the mandatory storage and preparation of a complete dense model.

A capture architecture beyond the dedicated scanner

The automated scanner provides repeatable capture and reduces the amount of manual viewpoint planning required from an operator. A technician follows the capture workflow rather than building a 3D model, repairing topology or authoring materials. Product placement, lighting and visual quality checks remain practical operator responsibilities.

The image-based architecture also extends to sources such as mobile phones, conventional cameras, video cameras and extracted video feeds. A dedicated station emphasizes consistency and automation; field sources emphasize availability and coverage. They feed the same general pattern: prepare usable imagery, associate context and package a reusable record.

The 1–7-minute scan range and 7-minute processing figure describe the product scanning workflow. Capture conditions, missing viewpoints and sensor-specific preparation determine the workflow for other sources.

Earth observation: a spatial intelligence extension

The P3D concept extends naturally from an object record to a geospatial observation package: imagery, sensor context, derived spatial information and related datasets travel as one interpretable unit. The opportunity is to preserve relationships among observations and analysis products while distributing only the data needed for a task.

Retain the sensor context

An Earth-observation extension would carry geolocation, timestamps, coordinate reference systems, sensor/lens model and calibration, viewing geometry, platform position and orientation, processing lineage, uncertainty and derived depth or sparse points. For optical imagery, lens and exposure fields describe acquisition. SAR requires radar-specific information such as wavelength, polarization, incidence angle and processing level; an optical lens description cannot substitute for it.

Normalize and fuse without losing scientific meaning

RGB, hyperspectral and SAR sources observe different physical properties. A common package can associate them, but useful fusion requires co-registration, coordinate and timing alignment, sensor calibration and task-specific normalization. Native precision, spectral bands, units and complex SAR values must be retained where the analysis depends on them. A display image is a derivative, not a substitute for the scientific measurements.

Process near the sensor; downlink the useful result

An onboard pipeline can select regions, extract features or generate compact derived products before transmission. P3D’s proposed role is the delivery envelope that preserves their metadata and relationships. Downlink savings come from the processing and selection policy; packaging alone does not shrink every scientific dataset to 4 MB. Satellite deployment requires suitable flight hardware, software validation, power and thermal budgeting, and a policy for retaining or retrieving the original measurements.

Build on existing geospatial standards

GeoTIFF already embeds georeferencing metadata, Cloud Optimized GeoTIFF supports efficient partial web access, and STAC structures searchable metadata across geospatial assets. P3D’s opportunity is complementary: bind related media, context and optional spatial derivatives into an application-facing package while preserving standard scientific assets and identifiers.^{4, 5, 6}

Viewing options and deployment

Interaction follows the captured view envelope. Horizontal and vertical view coverage determines available angles; frame interpolation is a viewer/processing capability, not a substitute for observing missing surfaces. The supplied comparison sample has 36 horizontal indices and 10 vertical indices. Its preview supports selection across the full 360-view grid; these are indexed views, not a claim of calibrated camera poses.

Separate portable data from the rendering layer

P3D stores the representation and relationships. A viewer decides how to decode, cache and present those views; an AI pipeline decides how to extract and transform them. This lets the same source asset support different applications without requiring every consumer to render a full 3D model.

More catalog value.
Less reconstruction work.

P3D is designed around what a catalog team needs next: product views, interactive presentation, factual context and reusable content inputs. Its advantage is a shorter path from capture to those outputs, while a geometric model remains useful when the brief needs free viewpoints, relighting, AR or measurement.

Reading the numbers: Measured = inspected supplied file. Specification = owner-reported workflow. Published benchmark = another dataset and system. Calculated scenario = explicit inputs, not a measured speedup. File formats do not prescribe scanning times or production prices.

01 / What each route produces

02 / Capture time and processing are separate budgets

The specified 6-minute capture is 40–70% shorter than the owner’s conventional 10–20-minute capture reference. This is a capture-only comparison. Setup, handling, content generation, review and publication sit outside the 13-minute source cycle.

These published results show where reconstruction compute is spent. They use different datasets, outputs and hardware from P3D; no cross-method speedup percentage is inferred from them.

03 / What is actually in the supplied file?

The manifest is 14,088 raw bytes → 2,212 stored bytes (84.30% smaller through ZIP compression). Most product attributes are empty in this sample; the non-empty text-dump field also holds links and placeholder values, which are not embedded media or validated measurements. There are 361 archive entries in total.

3D file-size budgets: geometry, textures and primitives

A 3D file has no single “resolution.” Count geometry and texture budgets separately. These calculated payload examples describe the inputs below; they are not exports of the supplied tea product.

A compact, optimized GLB can be smaller than this P3D source. A rich reconstructed scene can be larger. Compare the actual exported bytes at a common visual target and required camera freedom.

04 / Retain the master. Deliver the right derivative.

At a modeled 20 Mbps connection, payload-only transfer is 21.77 s for the original or 1.67 s for the preview (bytes × 8 / bitrate). Requests, latency, decoding and cache behavior add time. Preserve RAW masters separately if future color grading, sensor-level editing or a higher-resolution export requires them.

05 / Zoom quality is a sampling budget

Older, simplified 3D exports may blur on zoom because of low-resolution textures, sparse geometry, poor UV allocation or incomplete capture. Age or file extension alone does not determine detail. A 2048² texture has 4.19 million texels shared over the mapped surface; a 4096² texture has 16.78 million. Neither number is directly equivalent to a photographed view’s pixel count.

Modern glTF supports detailed PBR assets and compressed KTX2 textures; compression can reduce transfer size and GPU memory. P3D retains the photographed finish at captured viewpoints, but zoom cannot recover pixels absent from its embedded images. Its 4K capability is separate from this 1080 × 608 sample.^[10]

06 / Rendering libraries and compute requirements

07 / Quantify your own time and cost

Use your current workflow as the baseline. The defaults below are a planning scenario, not research measurements, service prices or a guaranteed saving. Both routes charge the same hourly rates; every capture/processing minute is assumed attended. Processing compute is billed as one machine at the entered hourly rate, not as measured GPU utilization.

08 / Where P3D makes the strongest case

A matched comparison should scan the same products, hold visible detail and output requirements constant, log active operator time and wall time separately, and record machine model, peak RAM/VRAM, GPU time, kWh, retained bytes and quality. No such cross-format trial was supplied; universal cost, compute or quality superiority is not asserted.

Closing: capture once, build digital intelligence

P3D’s efficiency comes from choosing an image-led representation for the many tasks that need appearance and context, then retaining optional spatial information for tasks that need more. The product is captured once, its evidence stays connected to its identity, and downstream workflows extract the information they use.

For commerce, the same record supplies catalog and interactive product content. For AI, it organizes visual and textual inputs around an object. For inspection, archives and immersive media, it preserves an inspectable source. The proposed Earth-observation extension applies that packaging principle to related sensor data and spatial derivatives.

Evidence, calculations and references

This edition presents HyperD / Perfit / Is Going Online product specifications and architecture as supplied by the product owner on 21 October 2026: 1–7-minute capture range, approximately 6-minute average capture, 7-minute processing, 4K capture capability, four nominal MB profiles, metadata/text/media packaging and optional sparse spatial data. It is a technical product white paper, not an independent certification or a controlled cross-vendor benchmark.

Arithmetic in the graphics: average sequential source TAT = 6 + 7 = 13 minutes; detailed TAT = 7 + 7 = 14 minutes; Lite size reduction = (200 − 4) / 200 = 98%; Ultra-to-Lite size ratio = 200 / 4 = 50:1. Capture comparison = (reference − 6) / reference for the owner’s 10–20-minute reference. No measured AI accuracy gain, GPU-energy saving, sales uplift or universal end-to-end content speedup is claimed.

The satellite section describes a proposed extension and its technical requirements. The comparison source IGO_2026_0675_017_P3D_001.p3d was inspected directly and remains unchanged. It is a 54,436,585-byte high-size example with 360 PNGs at 1080 × 608 and a 14,088-byte manifest (2,212 bytes stored). The 4,164,696-byte web preview is a resized, lossy derivative, not an official size profile or equal-quality benchmark. Product-size profiles are nominal values, not maximum-size guarantees. Pixel resolution, geometry accuracy and scientific measurement fidelity are separate properties.

Comparison research · checked 22 October 2026

The comparison keeps independent file measurements, owner timings, historical published benchmarks and editable cost assumptions separate. P3D sample metadata audit: 67 top-level product-attribute keys, 4 non-empty values; text-dump links do not count as embedded media. Pixel-memory calculations use RGBA8 and exclude runtime overhead. Storage uses decimal GB; decoded memory uses binary MiB/GiB. No cross-format product quality score or GPU energy measurement is available.