Route related files rendering on WWK

[GeorgePapageorgakis]

For routing, we usually need .shp, .shx, .dbf, .prj. files and some optional, maybe for styling, .sbx .sbn .avl .cpg.

Any ideas/suggestions how can I render the route/roads/land coverage view data on WWK? Do you plan to support these files?

[EMaksymenko]

External data formats are not a part of the engine. We have some of these formats in our navigation software, but we do not plan to add them to the engine itself. You can take any opensouece library and implement the convertation of these files i to Path renderables.

[EMaksymenko]

Surface path by default has isDynamic = false property and makes textures under the hood.
If you will not edit the path, iy will act as surface texture.

[GeorgePapageorgakis]

For surface images I mean the shape files that may include roads, land coverage etc. For the calculated route, we can use a Path Renderable.

[EMaksymenko]

You can use Surface Image and preprocess vector data into raster on the server side if you wish.

I do not understand what are you asking for.

[GeorgePapageorgakis]

There are 2 use cases for all the Route related files:

1. Visualize the imported data, meaning the roads, land coverage etc, on the map.
2. Visualize a calculated/generated Path based on the imported data.

For the second use case I know that we can somehow calculate/generate with an external lib a path/route and render it on the WW engine as a Path Renderable.

I am asking for the first use case. What do you think would be the optimal way to view this data? As a Surface layer as in the example of "Surface Image"? GeoJson? Or maybe convert it to geopackage and then import it?

[EMaksymenko]

One surface image instead of 100 paths will be faster, even including the fact that it internally caches into texture, af it makes frustum calling anyway 100 times for each path.

[EMaksymenko]

You can also make PR with these mappings in the earth.worldwind.formats package, and we can review them to be in luded in the delivery.