Marco Hutter

Qualified names for metadata access in custom shaders

1

Right now, metadata is passed to the custom shaders via an `fsInput.metadata` structure that contains the properties. The shader code may access this data, with something like vec2 example =...

Right now, there are some links from ADOC files directly to JSON schema files in the GitHub repo, for example, ``` The common structure of metadata entities that appear in...

Requirement for alphanumeric IDs

1

The [Identifiers](https://github.com/CesiumGS/3d-tiles/tree/draft-1.1/specification/Metadata#identifiers) section currently defines the requirement that "IDs" have to match a certain regex. The specification contains documentations for these IDs in the following form: - https://github.com/CesiumGS/3d-tiles/tree/draft-1.1/specification/Metadata#id - https://github.com/CesiumGS/3d-tiles/tree/draft-1.1/specification/Metadata#id-1...

Maintaining specifications for 3D Tiles 1.0, 1.1, and beyond

2

There are efforts for the standardizing 3D Tiles version **1.1**. This version will be based on what is currently referred to as "3D Tiles Next", which currently is a set...

Consider combining `normalized/offset/scale` in `valueTransform`

2

A [class property](https://github.com/CesiumGS/3d-tiles/tree/5367720a417d7741b0f613fd29d0a584990a6548/specification/Metadata#property) can have the following properties: - name, description *(metadata)* - type, componentType, enumType, array, count *(structure)* - normalized, offset, scale *(value transform)* - required, noData, default *(usage)*...

Ideas for structuring Metadata Semantics

1

Each property of a metadata class can have a [Semantic](https://github.com/CesiumGS/3d-tiles/tree/5a4bc564360a96623315d5496c3b51c1230bcf38/specification/Metadata#semantic). This is just a string that can be used to assign an application-specific _meaning_ to these properties. A collection of...

Should tile content support multiple groups?

2

The [current `content.schema.json`](https://github.com/CesiumGS/3d-tiles/blob/5a4bc564360a96623315d5496c3b51c1230bcf38/specification/schema/content.schema.json#L29) allows assigning a `group` name to tile content. The idea is to define groups like `trees`, `buildings` and `cars` (as in the [example image in `3DTILES_multiple_contents`](https://github.com/CesiumGS/3d-tiles/tree/5a4bc564360a96623315d5496c3b51c1230bcf38/extensions/3DTILES_multiple_contents#overview)). One...

Specification of MIME Types (Media Types) in 3D Tiles

3

This is related to https://github.com/CesiumGS/3d-tiles/issues/341 . This is an attempt to collect the information about media types and file extensions for 3D Tiles, which could go into the specification at...

Definition of Feature IDs in `EXT_mesh_features`

1

Some structural changes to the `EXT_mesh_features` extension have been started recently. The largest change is that `EXT_mesh_features` will now **only** cover the definition of Feature IDs. (The remaining parts -...

Limiting the number of files in a directory for implicit tiling

6

The [3DTILES_implicit_tiling](https://github.com/CesiumGS/3d-tiles/tree/main/extensions/3DTILES_implicit_tiling) specification allows defining quadtree- or octree tilesets that only exist _implicitly_. Each of these implicit tiles may have associated `tile.content`. This tile content is stored in a file...