# PointCloud Document

## Purpose
3D point cloud datasets from LiDAR or photogrammetry.

## GeoJSON (DB metadata)
```json
{
  "type": "Feature",
  "geometry": {"type": "Polygon", "coordinates": [[[
    30.10, 59.90
  ], [
    30.20, 59.90
  ], [
    30.20, 60.00
  ], [
    30.10, 60.00
  ], [
    30.10, 59.90
  ]]]},
  "properties": {
    "type": "PointCloud",
    "title": "Urban LiDAR",
    "created_at": "2025-06-01T09:00:00Z",
    "updated_at": "2025-06-01T09:00:00Z",
    "source": {
      "url": "/s3/<bucket>/<ResultKey>/<filename>",
      "type": "PointCloud"
    },
    "metadata": {"point_density": 12.5, "crs": "EPSG:4978"}
  }
}
```

## Required properties
- `properties.type` = `PointCloud`
- Footprint geometry for the point cloud AOI
- Link to a web-accessible tileset (EPT) or file archive

## Publishing workflow
1. Convert point cloud to EPT tileset for scalable rendering.
2. Host on static HTTP or S3.
3. Publish Feature referencing the tileset root.

## Validation checklist
- Tileset responds and viewer can load sample tiles.
- CRS documented in `metadata`.

See [Common properties](../common.md) for shared fields like legend, metadata, and classification.
See also: [GeoJSON Strategy](../../Geojson_strategy.md) and [Upload Strategy](../../Upload_strategy.md).