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

Long Trail Time Reduces Performance #5015

Closed
mmcgarity opened this issue Feb 20, 2017 · 3 comments
Closed

Long Trail Time Reduces Performance #5015

mmcgarity opened this issue Feb 20, 2017 · 3 comments

Comments

@mmcgarity
Copy link

mmcgarity commented Feb 20, 2017

I'm trying to playback 3-6 month tracks durations, with a trail time of about a week, and I'm finding the performance of Cesium be reduced substantially. The entire UI just slows down, and you can barely use it.

This is with a small amount of track data, the duration just happens to be a long period and that destroys Cesium.

Here's some example code which is basically the same as the CZML Path example:

var czml = [{
    "id" : "document",
    "name" : "CZML Path",
    "version" : "1.0",
    "clock": {
        "interval": "2012-08-04T10:00:00Z/2013-08-04T15:00:00Z",
        "currentTime": "2012-08-04T10:00:00Z",
        "multiplier": 10
    }
}, {
    "id" : "path",
    "name" : "path with GPS flight data",
    "description" : "<p>Hang gliding flight log data from Daniel H. Friedman.<br>Icon created by Larisa Skosyrska from the Noun Project</p>",
    "availability" : "2012-08-04T10:00:00Z/2013-08-04T15:00:00Z",
    "path" : {
        "material" : {
            "polylineOutline" : {
                "color" : {
                    "rgba" : [255, 0, 255, 255]
                },
                "outlineColor" : {
                    "rgba" : [0, 255, 255, 255]
                },
                "outlineWidth" : 5
            }
        },
        "width" : 8,
        "leadTime" : 10,
        "trailTime" : 1000,
        "resolution" : 5
    },
    "billboard" : {
        "image" : "http://maps.google.com/mapfiles/kml/pushpin/blue-pushpin.png",
        "scale" : 1.5,
        "eyeOffset": {
            "cartesian": [ 0.0, 0.0, -10.0 ]
        }
    },
    "position" : {
        "epoch" : "2012-08-04T10:00:00Z",
        "cartographicDegrees" : [
            0,-122.93797,39.50935,1776,
            31575490,-122.94563,39.44125,566
        ]
    }
}];


var viewer = new Cesium.Viewer('cesiumContainer', {
baseLayerPicker : false
});

viewer.dataSources.add(Cesium.CzmlDataSource.load(czml)).then(function(ds) {
viewer.trackedEntity = ds.entities.getById('path');
});
@denverpierce
Copy link
Contributor

Try adjusting the resolution as a workaround. 1 week * 7 days * 24 hrs * 60 minutes/hr at a 5 second resolution makes a lot of extraneous data points, slowing things down.

@pjcozzi
Copy link
Contributor

pjcozzi commented Jun 14, 2017

Thanks for the idea @denverpierce. @mmcgarity any luck with this?

Perhaps it would be best to discuss on the Cesium forum first, and then submit an issue if there is a specific feature request or bug.

@pjcozzi pjcozzi closed this as completed Jun 14, 2017
@emackey
Copy link
Contributor

emackey commented Jun 15, 2017

This may be a dup of #2310.

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

No branches or pull requests

4 participants