Vector Tiles #228

bagnell · 2017-06-05T23:17:29Z

Updated vector tiles draft. This reflects the current implementation in the vector-tiles branch of Cesium.

A few things we may want to add:

Meter width lines (like corridors on terrain/3D tiles)
Points with meter width on terrain/3D Tiles.
TOC to spec, Add TOC to all Tile Format specs #229
This is very Earth centric? Is that OK for now? What about general 3D scenes.

…tiles

…table schema.

pjcozzi · 2017-06-07T12:25:28Z

@bagnell please target this to a new branch: 3d-tiles-next

pjcozzi · 2017-06-07T12:26:32Z

Styling/README.md

@@ -1309,6 +1309,20 @@ For example:

 **TODO : add note about GLSL implementations requires strict type comparisons among other things: https://github.com/AnalyticalGraphicsInc/3d-tiles/issues/140**

+#### Vector Data


Also update the TOC at the top of this file.

pjcozzi · 2017-06-07T12:27:59Z

Styling/README.md

@@ -1309,6 +1309,20 @@ For example:

 **TODO : add note about GLSL implementations requires strict type comparisons among other things: https://github.com/AnalyticalGraphicsInc/3d-tiles/issues/140**

+#### Vector Data
+
+A [Vector Tile](../TileFormats/VectorData/README.md) is a collection of points, polygons, and polylines. All vector data can be styled similar to other features with `color` and `show`. Points have several other styling options:


is a collection of points, polygons, and polylines

Reword to something like "a collection of vector feature such as points, polygons, and polylines."

Throughout, we want our messaging to be consistent that 3D Tiles vector tiles go beyond traditional points/poylines/polygons to true 3D use cases.

pjcozzi · 2017-06-07T12:29:53Z

Styling/README.md

+| Style | Description | Default |
+| --- | --- | --- |
+| pointSize | The size of the point in pixels. | 8.0 |
+| image | A URL to an image to be displayed instead of a point. | " " |


Here and below

" "

to

''

?

Is a data URI valid?

This could go into the tasklist or a future PR, but I wonder if folks will want to this point to a subset of some payload like buffer/bufferView in glTF so they can put all their images in one atlas.

Also, explicitly say that pointSize is ignored when image is defined.

I could be a data URI.

Would another option for the future be to have an atlas as part of the payload and the image be a subregion of the atlas? That way implementations wouldn't have to rebuild an atlas.

Atlas - exactly. Can you submit an issue for this for future work?

Submitted #239

pjcozzi · 2017-06-07T12:31:06Z

Styling/README.md

+
+A [Vector Tile](../TileFormats/VectorData/README.md) is a collection of points, polygons, and polylines. All vector data can be styled similar to other features with `color` and `show`. Points have several other styling options:
+
+| Style | Description | Default |


We could improve this table with the datatype, bounds, etc. Instead, just put a TODO here to generate this table from the JSON schema.

Include an example or two of these properties being used, including some use cases like directly mapping per-feature properties to these and using per-feature properties to compute these.

pjcozzi · 2017-06-07T12:47:51Z

Styling/README.md

+| image | A URL to an image to be displayed instead of a point. | " " |
+| text | The text to display for the point | " " |
+| font | The font of the displayed text. | "30px sans-serif" |
+| labelStyle | The label style: fill(0), outline(1), or both(2). | 0 |


Can you add a table with screenshots for fill, outline, and both? Devs writing their own renderer would fine this useful.

pjcozzi · 2017-06-07T16:02:16Z

TileFormats/VectorData/README.md

+
+### Positions
+
+The positions buffer contains up to three sub-buffers for the polygons, polylines and points. The positions are encoded according to the quantized-mesh-1.0 format[1].


Use serial comma. "polylines,"

Just link to quantized-mesh-1.0 format in a Resources section. I don't think it's a good intro here.

pjcozzi · 2017-06-07T16:04:15Z

TileFormats/VectorData/README.md

+
+The positions buffer contains up to three sub-buffers for the polygons, polylines and points. The positions are encoded according to the quantized-mesh-1.0 format[1].
+
+The bounding volume for the tile must be a tile bounding region containing the north, south, east, and west bounds of the tile. The positions are represented by u, v, and height values that are quantized and delta encoded.


Throughout, order lower-left (x,y) to upper-right (x,y). west, south, east, north.

pjcozzi · 2017-06-07T16:05:28Z

TileFormats/VectorData/README.md

+
+| Field | Meaning |
+| --- | --- |
+| u | The horizontal coordinate of the vertex in the tile. When the u value is 0, the vertex is on the Western edge of the tile. Then the value is 32767, the vertex is on the Eastern edge of the tile. For other values, the vertex's longitude is a linear interpolation between the longitudes of the Western and Eastern edges of the tile. |


Throughout this table, are you sure words like Western should be capitalized? Use bold if they need focus.

Use consistent wording: vertex vs. position.

pjcozzi · 2017-06-07T16:08:22Z

TileFormats/VectorData/README.md

+
+#### Polygon positions
+
+The first section of the positions buffer, from offset 0 to `polygonPositionsByteLength`, contains the polygon positions. Polygon positions only have u and v values. The u values are from offset `0` to `polygonPositionsByteLength / 2`. The v values are from offset `polygonPositionsByteLength /2` to `polygonPositionsByteLength`. The number of positions for each polygon is determined by the value of its `POLYGON_COUNT`. 


"polygonPositionsByteLength /2" -> "polygonPositionsByteLength / 2"

pjcozzi · 2017-06-07T16:11:34Z

TileFormats/VectorData/README.md

+
+#### Polygon positions
+
+The first section of the positions buffer, from offset 0 to `polygonPositionsByteLength`, contains the polygon positions. Polygon positions only have u and v values. The u values are from offset `0` to `polygonPositionsByteLength / 2`. The v values are from offset `polygonPositionsByteLength /2` to `polygonPositionsByteLength`. The number of positions for each polygon is determined by the value of its `POLYGON_COUNT`. 


For each of these three sections, perhaps replace/augment the first sentence with a small table showing the start byte length and end byte length.

pjcozzi · 2017-06-27T12:42:19Z

Bump @bagnell

bagnell · 2017-06-28T21:32:53Z

@pjcozzi This is ready for another look.

pjcozzi · 2017-06-29T00:32:58Z

Tweaked the styling spec in 13e14ca.

pjcozzi · 2017-06-29T00:22:37Z

Styling/README.md

@@ -51,6 +51,7 @@ Contents:
   * [Notes](#notes)
 * [Batch Table Hierarchy](#batch-table-hierarchy)
 * [Point Cloud](#point-cloud)
+* [Vector Data](#vector-data)


Add yourself to the contributors list in this file.

pjcozzi · 2017-06-29T00:34:14Z

Styling/README.md

+| Style | Type | Description | Default |
+| --- | --- | --- | --- |
+| `show` | `Boolean` | Whether or not to show the feature. | `true` |
+| `color` | `vec4` | The color of the feature. | `color('#FFFFFF')` |


What does this mean? The color multiple with the image and label? How does this relate to pointColor?

pjcozzi · 2017-06-29T00:35:10Z

Styling/README.md

+| `labelStyle` | `Number` | The label style: **fill** (`0`), **outline** (`1`), or **both** (`2`). This is ignored when `labelText` is undefined. | `0` |
+| `labelOutlineColor` | `vec` | The color of the text outline. This is ignored when `labelText` is undefined. | `color('#FFFFFF')` |
+| `labelOutlineWidth` | `Number` | The width of the text outline. This is ignored when `labelText` is undefined. | `1.0` |
+| `font` | `String` | The font of the displayed text. This is ignored when `labelText` is undefined. | `"30px sans-serif"` |


I thought I mentioned this before but the format of the font string needs to be referenced, e.g., like this spec does for CSS colors.

pjcozzi · 2017-06-29T00:35:43Z

Styling/README.md

+
+For example:
+
+```json


I thought I mentioned this before, but please add more examples showing more of the vector tile-specific properties.

pjcozzi · 2017-06-29T00:47:35Z

TileFormats/VectorData/README.md

+
+If `featureTableJSONByteLength` equals zero, the tile does not need to be rendered.
+
+The body section immediately follows the header section, and is composed of four fields: `Feature Table`, `Batch Table`, `Indices`, and `Positions`.


Here - and/or maybe in the ** Positions** section below - we should explicitly state the order and how to compute the offsets for the indices and positions for each type of feature. We did to be explicit as opposed to relying on the order of the fields in the header and making an assumption.

pjcozzi · 2017-06-29T00:48:27Z

TileFormats/VectorData/README.md

+
+| Semantic | Data Type | Description | Required |
+| --- | --- | --- | --- |
+| `POLYGONS_LENGTH` | `uint32` | The number of pre-triangulated polygons in the tile. | :white_check_mark: Yes, unless one of `POLYLINES_LENGTH` or `POINTS_LENGTH` is defined. |


Sounds like we require that at least one polygon, polyline, or point is defined. Should this be required? Does this mirror b3dm, i3dm, and pnts?

pjcozzi · 2017-06-29T00:49:37Z

TileFormats/VectorData/README.md

+
+| Semantic | Data Type | Description | Required |
+| --- | --- | --- | --- |
+| `POLYGON_COUNTS` | `uint32[]` | The number of vertices that belong to each polygon. This refers to the polygon section of the positions buffer in the body. Each polygon count refers to a contiguous number of vertices in the position buffer that represents the polygon.  | :white_check_mark: Yes, unless `POLYGONS_LENGTH` is zero or not defined. |


Here and similar below, this is probably better stated as

Yes, when POLYGONS_LENGTH is greater than zero.

pjcozzi · 2017-06-29T00:51:28Z

TileFormats/VectorData/README.md

+| `POLYGON_COUNTS` | `uint32[]` | The number of vertices that belong to each polygon. This refers to the polygon section of the positions buffer in the body. Each polygon count refers to a contiguous number of vertices in the position buffer that represents the polygon.  | :white_check_mark: Yes, unless `POLYGONS_LENGTH` is zero or not defined. |
+| `POLYGON_INDEX_COUNTS` | `uint32[]` | The number of indices that belong to each polygon. This refers to the indices buffer of the body. Each index count refers to a contiguous number of indices that represent the triangulated polygon. | :white_check_mark: Yes, unless `POLYGONS_LENGTH` is zero or not defined. |
+| `POLYGON_MINIMUM_HEIGHTS` | `float32[]` | The minimum height of each polygon in meters above the WGS84 ellipsoid. | :red_circle: No. If the minimum height for each polygon is not specified, the global `MINIMUM_HEIGHT` will be used. |
+| `POLYGON_MAXIMUM_HEIGHTS` | `float32[]` | The maximum height of each polygon in meters above the WGS84 ellipsoid. | :red_cricle: No. If the maximum height for each polygon is not specified, the global `MAXIMUM_HEIGHT` will be used. |


Should be : red_circle:

pjcozzi · 2017-06-29T00:52:29Z

TileFormats/VectorData/README.md

+
+See the [Batch Table](../BatchTable/README.md) reference for more information.
+
+### Indices


Rename to Polygon Indices

pjcozzi · 2017-06-29T00:54:07Z

TileFormats/VectorData/README.md

+
+#### Polygon positions
+
+**Figure 3**: Polygon layout.


Nice diagrams!

pjcozzi · 2017-11-24T20:21:26Z

@bagnell is the tasklist at the top of this up-to-date?

pjcozzi · 2017-11-24T20:23:19Z

Update the vector tile link and description in the main README.md -

pjcozzi · 2017-11-24T20:44:20Z

@bagnell can you update the tasklist in #25?

pjcozzi

This looks good.

The two biggest areas are:

Vector vs. classification tile
Making this non-Earth centric, e.g., for BIM models in a local coordinate system

There's also some cleanup to make sure all the updates needed for classification volumes are in the text.

I added roadmap ideas to #25 - I don't think any of these need to be done as part of this PR.

pjcozzi · 2017-11-24T20:25:02Z

Styling/README.md

+
+A [Vector Tile](../TileFormats/VectorData/README.md) is a collection of vector features such as points, polygons, and polylines. Vector features can be styled similar to other features with `color` and `show`. Points have several other styling options:
+
+**TODO : generate these tables from the JSON schema**


Perhaps remove this TODO and add a note to #37?

pjcozzi · 2017-11-24T20:28:36Z

Styling/README.md

+
+| Style | Type | Description | Default |
+| --- | --- | --- | --- |
+| `show` | `Boolean` | Whether or not to show the feature. | `true` |


Can point's just use color instead of pointColor so basically point features inherit all the geometry features' style properties and add new ones - as opposed to removing some as well.

pjcozzi · 2017-11-24T20:29:18Z

Styling/README.md

+| `pointColor` | `vec4` | The color of the point. `pointColor` is ignored when `image` is defined. | `color('#FFFFFF')` |
+| `pointOutlineColor` | `vec4` | The color of the point outline. `pointOutlineColor` is ignored when `image` is defined. | `color('#000000')` |
+| `pointOutlineWidth` | `Number` | The width, in pixels, of the point outline. `pointOutlineWidth` is ignored when `image` is defined. | `0.0` |
+| `labelText` | `String` | The text to display for the point. | `undefined` |


Are \n line breaks allowed? If so, explicitly mention it.

pjcozzi · 2017-11-24T20:31:08Z

Styling/README.md

+| `pointOutlineColor` | `vec4` | The color of the point outline. `pointOutlineColor` is ignored when `image` is defined. | `color('#000000')` |
+| `pointOutlineWidth` | `Number` | The width, in pixels, of the point outline. `pointOutlineWidth` is ignored when `image` is defined. | `0.0` |
+| `labelText` | `String` | The text to display for the point. | `undefined` |
+| `labelColor` | `vec4` | The color of the label. This is ignored when `labelText` is undefined. | `color('#FFFFFF')` |


Here and throughout below probably remove:

This is ignored when labelText is undefined.

It is obvious and keeping the text makes the table more verbose.

pjcozzi · 2017-11-24T20:31:35Z

Styling/README.md

+| `labelText` | `String` | The text to display for the point. | `undefined` |
+| `labelColor` | `vec4` | The color of the label. This is ignored when `labelText` is undefined. | `color('#FFFFFF')` |
+| `labelStyle` | `Number` | The label style: **fill** (`0`), **outline** (`1`), or **both** (`2`). This is ignored when `labelText` is undefined. | `0` |
+| `labelOutlineColor` | `vec` | The color of the text outline. This is ignored when `labelText` is undefined. | `color('#FFFFFF')` |


Should this be vec4?

pjcozzi · 2017-11-24T21:34:15Z

TileFormats/VectorData/README.md

+
+### Polygon Indices
+
+TODO: `uint16` indices?


Does it have a big impact on file size? Is this consistent with b3dm?

uint32 implies using the WebGL extension (which is probably fine) or a lot of runtime slicing.

pjcozzi · 2017-11-24T21:34:56Z

TileFormats/VectorData/README.md

+
+### Polygon Indices
+
+TODO: `uint16` indices?


Does it have a big impact on file size?

After gzip...

pjcozzi · 2017-11-24T21:35:43Z

TileFormats/VectorData/README.md

+
+See the [Batch Table](../BatchTable/README.md) reference for more information.
+
+### Polygon Indices


Also for meshes?

pjcozzi · 2017-11-24T21:39:05Z

TileFormats/VectorData/README.md

+
+| Field | Meaning |
+| --- | --- |
+| u | The horizontal coordinate of the vertex in the tile. When the u value is 0, the vertex is on the western edge of the tile. Then the value is 32767, the vertex is on the eastern edge of the tile. For other values, the vertex's longitude is a linear interpolation between the longitudes of the western and eastern edges of the tile. |


With just a few wording tweaks and maybe a property tweak or two - couldn't we word this so that it is not geo specific? For example, I suspect the code doesn't care that something is "west" or "east", it is just "min" and "max."

pjcozzi · 2017-11-24T21:40:28Z

TileFormats/VectorData/README.md

+| v | The vertical coordinate of the vertex in the tile. When the v value is 0, the vertex is on the southern edge of the tile. When the value is 32767, the vertex is on the northern edge of the tile. For other values, the vertex's latitude is a linear interpolation between the latitudes of the southern and northern edges of the tile. |
+| height | The height of the vertex of the tile. When the height value is 0, the vertex's height is equal to `MINIMUM_HEIGHT` from the feature table. When the value is 32767, the vertex's height is equal to `MAXIMUM_HEIGHT` from the feature table. For other values, the vertex's height is a linear interpolation of the minimum and maximum heights. |
+
+The values are then delta and ZigZag encoded. The delta encoding ensures the values are small integers. The ZigZag encoding ensure the values are positive integers. Example encoding code is listed below:


"The ZigZag encoding ensure" -> "ensures"

bagnell · 2017-12-11T23:36:12Z

@pjcozzi @lilleyse This is ready for another look. I'll update the implementation for the few minor changes after you have another pass. The geometry and mesh were removed. Geometry tiles will be a separate PR.

bagnell · 2017-12-14T00:44:57Z

Instead of a separate PR, I added the geometry spec to this.

pjcozzi · 2017-12-14T15:58:29Z

Instead of a separate PR, I added the geometry spec to this.

Add a link to it from the main README.md.

pjcozzi · 2017-12-14T15:58:57Z

TileFormats/GeometryData/README.md

@@ -0,0 +1,108 @@
+# Geometry Data


Just call it "Geometry" - no need to have a parallel to "Vector Data."

pjcozzi · 2017-12-14T16:00:35Z

TileFormats/GeometryData/README.md

+
+The body section immediately follows the header section, and is composed, in order, of two fields: `Feature Table` and  `Batch Table`.
+
+Code for reading the header can be found in


Throughout just like to Cesium's master branch - later this can be a tag so it never breaks. The PR will be merged soon.

pjcozzi · 2017-12-14T16:02:13Z

TileFormats/GeometryData/README.md

+
+### Semantics
+
+Per-feature semantics specific to a feature type are prefixed with the name of the feature type. e.g. `BOXES` for boxes, `CYLINDERS` for cylinders and `ELLIPSOIDS` for ellipsoids.


We use the "serial comma" - put a comma after "cylinders."

pjcozzi · 2017-12-14T16:02:47Z

TileFormats/GeometryData/README.md

+Per-feature semantics specific to a feature type are prefixed with the name of the feature type. e.g. `BOXES` for boxes, `CYLINDERS` for cylinders and `ELLIPSOIDS` for ellipsoids.
+
+At least one global `LENGTH` semantic must be defined. 
+If `BOXES_LENGTH` in not defined, or zero, no boxes will be rendered.


Perhaps make each of this "If" statements, a bullet.

pjcozzi · 2017-12-14T16:04:34Z

TileFormats/GeometryData/README.md

+
+| Semantic | Data Type | Description | Required |
+| --- | --- | --- | --- |
+| `BOXES` | `float32[]` | The boxes in the tile. The length of the array will be `19 * BOXES_LENGTH`. The first three elements of each box are the x, y, and z dimensions. The following 16 elements are the 4x4 model matrix in column-major order. | :white_check_mark: Yes, when the global `BOXES_LENGTH` is greater than zero. |


Let's be super explicit - are the dimensions the full length or half length?

Do we even need this since it could just be the translation part of the 4x4 matrix? Just all boxes are unit boxes transformed by the matrix?

I'm OK with just a model matrix, that's how the implementation works.

Should it mention anything about scaling the unit geometry? The only one I thought worth mentioning was the cylinder for which axes scaled the radius and which one was the length.

+1 for the cylinder axes. I don't think anything else is needed for the box.

pjcozzi · 2017-12-14T16:06:16Z

TileFormats/GeometryData/README.md

+| --- | --- | --- | --- |
+| `BOXES` | `float32[]` | The boxes in the tile. The length of the array will be `19 * BOXES_LENGTH`. The first three elements of each box are the x, y, and z dimensions. The following 16 elements are the 4x4 model matrix in column-major order. | :white_check_mark: Yes, when the global `BOXES_LENGTH` is greater than zero. |
+| `BOX_BATCH_IDS` | `uint16[]` | The `batchId` of the box that can be used to retrieve metadata from the `Batch Table`. | :red_circle: No. |
+| `CYLINDERS` | `float32[]` | The cylinders in the tile. The length of the array will be `18 * CYLINDERS_LENGTH`. The first element is the radius of the cylinder. The second element is the length along the z axis. The following 16 elements are the 4x4 model matrix in column-major order. | :white_check_mark: Yes, when the global `CYLINDERS_LENGTH` is greater than zero. |


Similar comment for cylinders.

pjcozzi · 2017-12-14T16:06:37Z

TileFormats/GeometryData/README.md

+| `BOX_BATCH_IDS` | `uint16[]` | The `batchId` of the box that can be used to retrieve metadata from the `Batch Table`. | :red_circle: No. |
+| `CYLINDERS` | `float32[]` | The cylinders in the tile. The length of the array will be `18 * CYLINDERS_LENGTH`. The first element is the radius of the cylinder. The second element is the length along the z axis. The following 16 elements are the 4x4 model matrix in column-major order. | :white_check_mark: Yes, when the global `CYLINDERS_LENGTH` is greater than zero. |
+| `CYLINDER_BATCH_IDS` | `uint16[]` | The `batchId` of the cylinder that can be used to retrieve metadata from the `Batch Table`. | :red_circle: No. |
+| `ELLIPSOIDS` | `float32[]` | The ellipsoids in the tile. The length of the array will be `19 * ELLIPSOIDS_LENGTH`. The first three elements are the radii in the x, y, and z axes. The following 16 elements are the 4x4 model matrix in column-major order. | :white_check_mark: Yes, when the global `ELLIPSOIDS_LENGTH` is greater than zero. |


Same comment.

bagnell · 2017-12-14T22:00:31Z

@pjcozzi @lilleyse This is ready for another look.

pjcozzi · 2017-12-15T01:40:41Z

@lilleyse this is all you when you have time.

@bagnell @lilleyse

Please make sure that everything discussed here - but not currently done - is in an issue/roadmap
That we strive to make this as non-Earth centric as possible either now or in the roadmap.

lilleyse · 2017-12-22T20:26:46Z

Styling/README.md

+
+A [Vector Tile](../TileFormats/VectorData/README.md) is a collection of vector features such as points, polygons, and polylines. Vector features can be styled similar to other features with `color` and `show`. Points have several other styling options:
+
+The following style properties apply to geometry features in vector tiles:


Probably clearer to say polygons and polylines here.

lilleyse · 2017-12-22T20:27:41Z

Styling/schema/vctr.style.schema.json

+        "description" : "The size of points in pixels.",
+        "default" : 8.0
+      },
+      "pointColor" : {


This was removed.

lilleyse · 2017-12-22T20:31:30Z

Styling/README.md

+| `labelColor` | `vec4` | The color of the label's text. | `color('#FFFFFF')` |
+| `labelStyle` | `Number` | The label style: **fill** (`0`), **outline** (`1`), or **both** (`2`). See **Table1**.| `0` |
+| `labelOutlineColor` | `vec4` | The color of the text outline. | `color('#FFFFFF')` |
+| `labelOutlineWidth` | `Number` | The width of the text outline. | `1.0` |


Include in pixels here and in the schema.

lilleyse · 2017-12-22T20:32:15Z

Styling/README.md

+| `labelStyle` | `Number` | The label style: **fill** (`0`), **outline** (`1`), or **both** (`2`). See **Table1**.| `0` |
+| `labelOutlineColor` | `vec4` | The color of the text outline. | `color('#FFFFFF')` |
+| `labelOutlineWidth` | `Number` | The width of the text outline. | `1.0` |
+| `font` | `String` | The font of the displayed text. | `"30px sans-serif"` |


Mention that this is a CSS font string, here and in the schema.

This is mentioned here: https://github.com/AnalyticalGraphicsInc/3d-tiles/pull/228/files#diff-406e6affb04e8aa11fb643fb5ed2fc9fR259

lilleyse · 2017-12-22T20:33:09Z

Styling/README.md

+| `labelOutlineColor` | `vec4` | The color of the text outline. | `color('#FFFFFF')` |
+| `labelOutlineWidth` | `Number` | The width of the text outline. | `1.0` |
+| `font` | `String` | The font of the displayed text. | `"30px sans-serif"` |
+| `backgroundColor` | `vec4` | The label background color. | `rgba(42, 42, 42, 0.8)` |


All the other color defaults are specified as css color strings, this should probably as well. (Also in schema).

lilleyse · 2017-12-22T20:59:16Z

TileFormats/VectorData/README.md

+
+**Figure 4**: Polyline layout.
+
+![](figures/polyline.jpg)


In the diagram polylinePositionsByteLength / 2 should be polylinePositionsByteLength / 3

lilleyse · 2017-12-22T20:59:57Z

TileFormats/VectorData/README.md

+
+**Figure 5**: Point layout.
+
+![](figures/point.jpg)


In the diagram pointPositionsByteLength / 2 should be pointPositionsByteLength / 3

lilleyse · 2017-12-22T21:01:39Z

TileFormats/VectorData/README.md

+
+**Figure 3**: Polygon layout.
+
+![](figures/polygon.jpg)


Should this diagram also include height values?

Polygons don't have height values.The heights are either given by th epolygon minimum and maximum heightsd in the feature table or the global minimum and maximum for the tile. Only points and polylines need ber-vertex heights.

lilleyse · 2017-12-22T21:02:55Z

schema/vctr.featureTable.schema.json

+      },
+      "RECTANGLE" : {
+        "type" : "array",
+        "description" : "A floating-point 4 element array that defines a rectangle bounding all of the vector data. The elements in the array are, in order, west, south, east, and north.",


This description is out of date compared to the spec text.

lilleyse · 2017-12-22T21:03:12Z

schema/vctr.featureTable.schema.json

+      "POINTS_LENGTH" : {
+        "$ref" : "featureTable.schema.json#/definitions/globalPropertyScalar"
+      },
+      "MESHES_LENGTH" : {


Remove meshes, boxes, etc.

bagnell · 2018-01-03T20:38:27Z

@lilleyse Updated. This is ready for another look.

lilleyse · 2018-01-05T19:22:06Z

Styling/schema/vctr.style.schema.json

+        }, {
+          "$ref" : "style.condition.schema.json"
+        }],
+        "description" : "Sets near and far scaling properties of a feature based on the features's distance from the camera. A feature's scale will interpolate between the `y` and `w` values while the camera distance falls within the upper and lower bounds of the specified `x` and `z` value. Outside of these ranges, the features's scale remains clamped to the nearest bound.  If undefined, `scaleByDistance` will be disabled.",


There are minor differences between the descriptions in the schema and in the spec text, it's probably worth going through all of these to make sure they are the same.

For example this one does not include "in meters".

lilleyse · 2018-01-05T19:24:54Z

That's all my comments. This is really close now.

bagnell · 2018-01-05T19:49:56Z

@lilleyse Updated.

lilleyse · 2018-01-05T19:55:13Z

The updates look good. I'll check over the Cesium PR quickly and then this will be good to go.

lilleyse · 2018-01-08T21:16:12Z

👍

lasalvavida and others added 14 commits August 25, 2016 16:59

Saving progress

2983510

Fixed error in quantized formula

1886325

First draft of Vector tiles spec

b8f9334

Edits

990f939

More edits; added quantized-volume figure

303affa

Fixed a few paths

43b9878

Tweaks

47d6089

Tweaks

09f1222

File extension notes

79b6e8a

Merge remote-tracking branch 'rob-3d-tiles/vector-tiles' into vector-…

6b052b7

…tiles

Updates and remove unneeded figures.

842de53

Update indices and include example figure.

a976569

Update positions descriptions, update figures, create vector feature …

e88f1aa

…table schema.

Update vector styling.

e2939ce

pjcozzi added the vector data label Jun 7, 2017

pjcozzi requested changes Jun 7, 2017

View reviewed changes

Merge branch 'master' into vector-tiles

75bb1e2

bagnell mentioned this pull request Jun 27, 2017

Allow additional vector image storing options #239

Closed

bagnell added 2 commits June 27, 2017 19:37

Update vector styling.

3acd529

Updates from review.

1b45038

Tweaks

13e14ca

Tweak

bd9f198

pjcozzi requested changes Jun 29, 2017

View reviewed changes

pjcozzi mentioned this pull request Jul 7, 2017

3D Tiles Next roadmap #247

Closed

bagnell added 2 commits October 17, 2017 14:35

Merge branch 'master' into vector-tiles

a002761

Update with new types and from review comments.

2ac37bb

pjcozzi requested changes Nov 24, 2017

View reviewed changes

bagnell added 3 commits December 11, 2017 17:09

Updates from review. Remove geometry and mesh details.

0faaf50

More updates from review.

ac6c656

Update figures.

2207d1a

Add geometry tile spec.

84f3968

pjcozzi requested changes Dec 14, 2017

View reviewed changes

bagnell added 3 commits December 14, 2017 16:42

Updates from review.

ae5a7c1

Update link in main readme.

107423d

Mention classification use case.

596d30e

pjcozzi assigned lilleyse Dec 15, 2017

lilleyse reviewed Dec 22, 2017

View reviewed changes

Updates from review. Update schemas.

c57399f

Remove min/max height from schema as they are now in region.

e11fa25

lilleyse reviewed Jan 5, 2018

View reviewed changes

Updates from review.

55a582d

lilleyse merged commit 353e75f into 3d-tiles-next Jan 8, 2018

lilleyse deleted the vector-tiles branch January 8, 2018 21:16

		@@ -1309,6 +1309,20 @@ For example:

		TODO : add note about GLSL implementations requires strict type comparisons among other things: https://github.com/AnalyticalGraphicsInc/3d-tiles/issues/140

		#### Vector Data


		A [Vector Tile](../TileFormats/VectorData/README.md) is a collection of points, polygons, and polylines. All vector data can be styled similar to other features with `color` and `show`. Points have several other styling options:

		\| Style \| Description \| Default \|


		### Positions

		The positions buffer contains up to three sub-buffers for the polygons, polylines and points. The positions are encoded according to the quantized-mesh-1.0 format[1].


		The positions buffer contains up to three sub-buffers for the polygons, polylines and points. The positions are encoded according to the quantized-mesh-1.0 format[1].

		The bounding volume for the tile must be a tile bounding region containing the north, south, east, and west bounds of the tile. The positions are represented by u, v, and height values that are quantized and delta encoded.


		#### Polygon positions

		The first section of the positions buffer, from offset 0 to `polygonPositionsByteLength`, contains the polygon positions. Polygon positions only have u and v values. The u values are from offset `0` to `polygonPositionsByteLength / 2`. The v values are from offset `polygonPositionsByteLength /2` to `polygonPositionsByteLength`. The number of positions for each polygon is determined by the value of its `POLYGON_COUNT`.


		If `featureTableJSONByteLength` equals zero, the tile does not need to be rendered.

		The body section immediately follows the header section, and is composed of four fields: `Feature Table`, `Batch Table`, `Indices`, and `Positions`.


		See the [Batch Table](../BatchTable/README.md) reference for more information.

		### Indices


		A [Vector Tile](../TileFormats/VectorData/README.md) is a collection of vector features such as points, polygons, and polylines. Vector features can be styled similar to other features with `color` and `show`. Points have several other styling options:

		TODO : generate these tables from the JSON schema


		See the [Batch Table](../BatchTable/README.md) reference for more information.

		### Polygon Indices


		The body section immediately follows the header section, and is composed, in order, of two fields: `Feature Table` and `Batch Table`.

		Code for reading the header can be found in


		### Semantics

		Per-feature semantics specific to a feature type are prefixed with the name of the feature type. e.g. `BOXES` for boxes, `CYLINDERS` for cylinders and `ELLIPSOIDS` for ellipsoids.


		A [Vector Tile](../TileFormats/VectorData/README.md) is a collection of vector features such as points, polygons, and polylines. Vector features can be styled similar to other features with `color` and `show`. Points have several other styling options:

		The following style properties apply to geometry features in vector tiles:

Vector Tiles #228

Vector Tiles #228

Conversation

bagnell commented Jun 5, 2017 • edited Loading

pjcozzi commented Jun 7, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pjcozzi commented Jun 27, 2017

bagnell commented Jun 28, 2017

pjcozzi commented Jun 29, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pjcozzi commented Nov 24, 2017

pjcozzi commented Nov 24, 2017

pjcozzi commented Nov 24, 2017

pjcozzi left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bagnell commented Dec 11, 2017

bagnell commented Dec 14, 2017

pjcozzi commented Dec 14, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bagnell commented Dec 14, 2017

pjcozzi commented Dec 15, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bagnell commented Jan 3, 2018

bagnell commented Jun 5, 2017 •

edited

Loading