Displaying a huge number of polylines

[BrunoSpy]

Hi,

I try to display a huge number of polylines, but I've a big performance issue : WWJ is nearly unusable...

I don't need to pick, rollover, hover or whatever.

For example, this is what I do, it works but so slooowwwlyy :



Do you have an idea ?

[what_nick]

They look like airport approach/exit paths. You may be creating separate polyline Java objects. Will it be possible to push them all together into a display list ?

Cheers,

what_nick.

[nlneilson]

Originally Posted by what_nick

You may be creating separate polyline Java objects. Will it be possible to push them all together into a display list ?

I would like to know what you mean by the "display list" also.

BrunoSpy: The number of red and the few blue lines seems like it should be manageable without too much of a performance hit.

A few thing which you have probably done but will mention.
Each track should be one polyline with many points rather than a bunch of polylines.
pathType = LINEAR;
.setNumSubsegments(1);
Do not call redraw() until they are all drawn.

If each new point has been added every second of the flight path then for a full day you may need to cull that to 10 sec or more at that view altitude and when zoomed in then each second but cull outside the view.

Are you getting the data from an ADS-B receiver?

Does France have charts in digital format similar to the U.S. FAA charts?
http://aeronav.faa.gov/index.asp?xml...v/applications
http://www.nlneilson.com/sectionals.html

[BrunoSpy]

Originally Posted by nlneilson

Does France have charts in digital format similar to the U.S. FAA charts?
http://aeronav.faa.gov/index.asp?xml...v/applications
http://www.nlneilson.com/sectionals.html

Most of aeronautic information is published in XML, but it's not available for people outside of DSNA (french air navigation service provider).

[BrunoSpy]

Yes that is. Paris arrivals during two hours. But we need to display a whole day.

Your idea sounds interesting, can you explain it a bit more ?

[BrunoSpy]

It's offline data, they are not updated once they are displayed.

We want to see the traffic of a whole day to study new airspace designs.

What you see on the screenshot is only 2 hours of traffic and it is already very slow to move the globe.

I have one polyline for each aircraft

I did not try pathType = LINEAR, but numSubSegments is already set to 1.

[nlneilson]

I think pathType = LINEAR; is the default so unless you specify something like
pathType = GREAT_CIRCLE; there will be no extra CPU time for calculations.

"It's offline data, they are not updated once they are displayed."
I wasn't as clear as I should have.
Add only one point and skip the next 9. You will have only 1/10th the number points in each polyline at the eye distance you have. It could be the number of pixels your display has you will see no difference. Or at least a negligible difference and acceptable to get performance.

[BrunoSpy]

Ok, I'm doing something like that (dropping points that are too close of the previous point).

But it only allows me to get 4 hours of traffic and keeping the app usable ...

[nlneilson]

Also if points are less than a certain lat and lon from the center of the airport cull those.
Seems like seeing the runways rather than painting each pixel 50 times would a benefit.
Look at the Grid layers to see how Pat Murris did the culling.

I did a proof of concept to show every runway/airstrip in the CON U.S.. There are just under 20,000. I got the approx. latlonalt at LAX and several others then offset those to get about 25,000. First above a certain altitude they would not show. That list was then run through and if was within a certain latlon of the center of view it was drawn.
Performance was very acceptable in Java. I do all of that stuff with C++ now and feed it in with a socket. I basically just use WWJ as the display.

[nlneilson]

Just try an if statement and drop all but every 5th, 10th, 20th or whatever to see where performance v a smooth track is acceptable.

You could also consider breaking it into one of every 20 tracks. Each loop would show 1/20th of all the tracks.
Even at a redraw of 50/sec it may acceptable rather than draw all the tracks every redraw.