Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OGC feedback comments #329

Merged
merged 2 commits into from
Aug 4, 2018
Merged

OGC feedback comments #329

merged 2 commits into from
Aug 4, 2018

Conversation

ggetz
Copy link
Contributor

@ggetz ggetz commented Aug 2, 2018

Edits to address feedback from OGC comment period.

Reordered the tiles section, added more explanation for geometric error and relation to SSE, and clarified tileset vs tile geometric error.

@lilleyse

@ggetz ggetz requested a review from lilleyse August 2, 2018 16:26
@ggetz ggetz mentioned this pull request Aug 3, 2018
4 tasks
* [Geometric error](#geometric-error)
* [Refinement](#refinement)
* [Additive](#additive)
* [Replacement](#replacement)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just noticed that the order of Additive and Replacement in the table of contents is different than the order in the main text.

"children": [...]
}
```
A tile's geometric error defines the selection metric for that tile. Its value is a nonnegative number specified, in meters, to be used by client implementation to calculate, along with other screen space metrics including the distance from the tile to the camera, the screen size and resolution, the SSE introduced if this tile is rendered and its children are not. If the introduced SEE exceeds the maximum allowed, the tile is refined and its children are considered for rendering.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SEE -> SSE


`root` is an object that defines the root tile using the tile JSON described in the [above section](#tiles). `root.geometricError` is not the same as the tileset's top-level `geometricError`. The tileset's `geometricError` is used to determine the maximum error when the tileset is rendered and if its tiles should be considered for rendering; `root.geometricError` is used only to determine if the root tile is rendered.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tileset's geometricError is used to determine the maximum error when the tileset is rendered and if its tiles should be considered for rendering; root.geometricError is used only to determine if the root tile is rendered.

These two descriptions almost sound like they are doing the same thing. A more accurate summary is:

The tileset's geometricError is used to determine if the tileset's root tile is rendered; root.geometricError is used to determine if the root's children are rendered.

"children": [...]
}
```
A tile's geometric error defines the selection metric for that tile. Its value is a nonnegative number specified, in meters, to be used by client implementation to calculate, along with other screen space metrics including the distance from the tile to the camera, the screen size and resolution, the SSE introduced if this tile is rendered and its children are not. If the introduced SEE exceeds the maximum allowed, the tile is refined and its children are considered for rendering.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should be a clear definition of geometric error that doesn't require defining it in context of screen space error.

Maybe something like this, which combines the implementation note:

A tile's geometric error defines the selection metric for that tile. Its value is a nonnegative number that specifies the error, in meters, of the tile's simplified representation of its source geometry. A root tile will generally have the greatest geometric error as it is generally the most simplified version of the source goemetry. Then each successive level of children has a lower geometric error than its parent, with leaf tiles generally having a geometric error of or close to 0.

Geometric error is used by client implementations to calculate, along with...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

used by client implementation to calculate, along with other screen space metrics including the distance from the tile to the camera, the screen size and resolution, the SSE introduced if this tile is rendered and its children are not

Grammatically this sentence is a little hard to follow.

`root` is an object that defines the root tile using the JSON described in the [above section](#tiles). `root.geometricError` is not the same as the tileset's top-level `geometricError`. The tileset's `geometricError` is the error when the entire tileset is not rendered; `root.geometricError` is the error when only the root tile is rendered.

`root.children` is an array of objects that define child tiles. Each child tile's content is fully enclosed by its parent tile's `boundingVolume` and, generally, a `geometricError` less than its parent tile's `geometricError`. For leaf tiles, the length of this array is zero, and `children` may not be defined.
`geometricError` is a nonnegative number that defines the error, in meters, that determines if the tileset is rendered. At runtime, the geometric error is used to compute _Screen-Space Error_ (SSE), the error measured in pixels. If the SSE does not exceed a required minimum, the tileset should not be rendered, and none of its tile should be considered for rendering, see [Geometric error](#geometric-error).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its tile -> its tiles

@ggetz
Copy link
Contributor Author

ggetz commented Aug 3, 2018

Thanks for the feedback @lilleyse, updated!

@lilleyse
Copy link
Contributor

lilleyse commented Aug 4, 2018

Looks great, thanks @ggetz.

@lilleyse lilleyse merged commit 8626009 into 1.0 Aug 4, 2018
@lilleyse lilleyse deleted the ogc-comments branch August 4, 2018 22:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants