How cesiumgs/3d-tiles works
Project Type and Purpose
• This is an open‐specification repository for “3D Tiles,” an OGC-style standard defining file formats and schemas for streaming massive heterogeneous 3D geospatial content.
• It provides:
• Core specification in AsciiDoc under specification/
• Extension registry under extensions/
• Reference cards under reference-cards/
• Release PDFs and change logs.
• It’s not a runtime application but a documentation, schema, and extension management system for spec authors and implementers.
Key Components
A. Specification Sources
• specification/
• AsciiDoc files (.adoc) for chapters, figures, build instructions.
• JSON Schema under specification/schema/
B. Extension Registry
• extensions/3DTILES_* directories, each with its README, schema, and figures.
• Registry index at extensions/README.md
C. Reference Cards
• Concise PDF/ODT cheat sheets under reference-cards/1.0 and 1.1.
D. Builds & Artifacts
• Build scripts (e.g., specification/BUILDING.md)
• Published PDFs under releases/
E. Resources & Ecosystem
• RESOURCES.md links implementations, tools, and demos.
• Integration points with Cesium, glTF, OGC community.
Relationships and Data Flow
• Authors write AsciiDoc + JSON schemas → fed into build system (Antora, Asciidoctor, custom scripts) → generates HTML site, PDF spec, JSON Schema artifacts, reference cards.
• Consumers (app devs, data providers) reference generated spec and schemas to implement readers, writers, and runtime engines.
• Extension authors add new directories under extensions/; these feed into spec and registry outputs.
• Reference cards are derived from spec content to produce concise quick‐start guides.
Architectural Patterns and Principles
• Modular documentation: Core spec + plug-in extensions.
• Single source of truth: AsciiDoc + JSON Schema are authoritative; multiple output formats derive from them.
• Clear separation of concerns: specification/ vs. extensions/ vs. reference-cards/.