Extend and document createTilesetJson
#105
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #104
The
createTilesetJson
function was not documented in the main README.md. This is now added here.Additionally, the command is extended to receive a position for the generated tileset. The position is passed as
cartographicPositionDegrees
to the command, which can be a 2- or 3-element array that contains thelongitudeDeg, latitudeDeg, <heightMeters>
that should be used for the root transform of the generated tileset. For example:I hesitated a bit with the exact format. Passing around an
number[]
array feels a bit awkward, because you never know its length. Alternatives like--longitudeDegrees 75 --latitudeDegrees 39 --heightMeters 123
would be pretty inconvenient, and there's no way to model the constraint that the first two parameters are required (together), and the last one is optional. So I think that the current solution is a reasonable middle ground...