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

Add syntax to to delete data from properties via CZML #7818

Merged
merged 2 commits into from
May 8, 2019

Conversation

shunter
Copy link
Contributor

@shunter shunter commented May 6, 2019

Specifying delete: true for any property will delete data for that property, depending on the type of property, for the specified interval (or if no interval is specified, then for all time).

This deletes samples for sampled properties, or removes intervals for interval properties.

Example syntax:

https:/AnalyticalGraphicsInc/cesium/blob/050f448e4d6544b810f1392c2f5c8e1678abece2/Specs/DataSources/CzmlDataSourceSpec.js#L2292-L2300

@cesium-concierge
Copy link

Thanks for the pull request @shunter!

  • ✔️ Signed CLA found.
  • CHANGES.md was not updated.
    • If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

  • Cesium Viewer works.
  • Works in 2D/CV.
  • Works (or fails gracefully) in IE11.

@shunter shunter requested a review from mramato May 6, 2019 20:39
Specifying delete: true for any property will delete data for that property, depending on the type of property, for the specified interval (or if no interval is specified, then for all time).

This deletes samples for sampled properties, or removes intervals for interval properties.
@mramato
Copy link
Contributor

mramato commented May 8, 2019

Looks to be in line with what we previously discussed offline. Smokescreened some existing CZML examples and obviously everything worked. Thanks @shunter!

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.

3 participants