LuciadRIA Release notes

`FeatureLayer` now processes a limited amount of model updates before the next frame, rather that after. This reduces visual jitter when you adjust camera based on a changing `Feature`, for example when following a moving airplane.

If you do more changes than can be processed before the next frame, the rest will be done asynchronously and be visible in later frames only. The amount that can be processed is dependent on the changes and your browser performance.

LuciadRIA is now shipped as a set of ES6 modules, packaged as npm packages. You can find the npm packages in the packages/es6 directory of the release.

Once you've installed the packages into an npm registry, you can use install and use them like any other npm package:

Use npm install to install LuciadRIA packages

The packages include Typescript definition files with documentation for all the public API.

• The LuciadRIA API is now distributed as ES6 modules. For backward compatibility, the AMD version of the API is still included. In order to run LuciadRIA on a browser that does not support ES6 module loading, the code has to be bundled. For the LuciadRIA samples this is done using webpack, as demonstrated in samples/common/webpack.config.
• LuciadRIA folder structure has been changed to match npm style. LuciadRIA classes are located under the packages folder. AMD classes can be found in the packages/amd folder and ES6 classes can be found in the packages/es6 folder. LuciadRIA, Defense Symbology and Advanced GIS Engine modules are stored in their own directories separetely.
• The samples have also been converted to the ES6 module structure. A ready-to-run version is already included in the release and can be accessed by running the startSampleServer.[sh|bat] script. If you want to make changes to the samples, you can modify the source code and run the webpack dev server to inspect your changes. See the developer guide for more information the samples.

• Mode OcclusionMode.VISIBLE_ONLY shows only the part of a shape that is not obscured by other 3D data. This is the default.
• Mode OcclusionMode.ALWAYS_VISIBLE shows the entire shape even if behind by other 3D data. The shape will appear in front of other objects.
• Mode OcclusionMode.OCCLUDED_ONLY shows only the part of the shape that is behind other 3D data. You typically use this to display obscured shapes in combination with another style that uses "VISIBLE" mode.

• Namespaces are no longer used to differentiate our modules. To handle this change you will need to update your type imports.
• Names of several interfaces have changed to have a more consistent naming across the LuciadRIA API. Interfaces for option objects used in constructors have the following naming scheme: {ClassName}ConstructorOptions, for example FeatureModelConstructorOptions. For other option objects, the interface name will always end with 'Options'.
• Some class and interface properties are now optional. This is because the old 'luciad.d.ts' file contained some bugs, causing it to be out of sync with the actual API. This implies that you might need to add an undefined check before using these properties.
• Our definition files are generated with non-nullable types, as a result of this our typing now explicitly contains null and undefined.

• The Evented class has been renamed EventedSupport and the Evented class has been changed to an interface. Custom classes that extend the old Evented class must now implement the Evented interface. Classes that implement the Evented interface can delegate requests to the EventedSupport class. We recommend using the delegate pattern for this.
• The emit function has been deleted from the Evented interface. As such, users will not be able to emit any events in one of the LuciadRIA classes anymore; For example, the 'ModelChanged' event in the FeatureModel cannot be triggered by users, but is automatically triggered by LuciadRIA when an object is added to the model.
• The static functions on and once are also no longer available on Evented since this is now an interface. These functions are however available on the new EventedSupport

• Draped content will not show up properly when underground.
• Some imagery tiles can be missing underground, near the "horizon".
• When disabling or re-enabling the above terrain constraint, the bottom-most layer will reload its data.

• When zoomed out, the back of the globe may be visible through the front.
• When switching the fully opaque to transparent or back, the layer will reload its data.

• The painter supports the following elements for TextSymbolizer: IsAligned, IsRepeated, Gap, InitialGap, PerpendicularOffset.
• It now supports Rotation, AnchorPoint and Opacity for Graphic elements.
• Support for GraphicStroke elements has been added.
• The painter can handle the uom attribute from LineSymbolizer and PolygonSymbolizer elements to draw lines in world size units.
• It now supports Mark, Size, Rotation and Opacity for Graphic elements used in a GraphicFill element.
• Added support for the SVG format, SVG images can now be used with both InlineContent and OnlineResource elements.

• A createFromCapabilities method accepting the capabilities and the name of the desired data set
• A createFromURL method accepting the service URL and the name of the desired data set

• Loading times have been improved by using tight-fitting oriented bounds for tile selection. This means less tiles will be downloaded.
• Framerate while loading has been improved by removing and optimizing some cpu-intensive operations. This also improves loading latencies.
• Overall memory consumption was significantly reduced.
• TileSet3DLayer follows the map's allowed memory usage (see WebGLMap.maxMemoryUsageHint, and other release note below), resulting in caching that adapts to the dataset, as well as avoiding crashes.

      OGC3DTilesModel
      .create("dataset.json")
      .then(function(model, { label: "My dataset" }) { return new TileSet3DLayer(model); })
      .then(function(layer) { map.layerTree.addChild(layer); });
    

• The object body
• The object label. This option is inactive by default.

• A navigation restriction is set on the Map (with Map#restrictNavigationToBounds)
• Axes are configured on the Map
• There is a GoogleLayer present on the Map

• By decoding a glTF file. LuciadRIA includes support for single-texture based glTF files (Note that custom shaders, animations and skins are not supported). You can decode a glTF file by specifying its path in the Icon3DStyle class.
• By creating a custom 3D Mesh using the MeshFactory class.

• a light based on your camera (this is the default)
• a sun light based on a specific time
• no lighting

• Shape:
  • contains2D(x, y) in favor of contains2DCoordinates(x, y)
  • contains2D(point) in favor of contains2DPoint(point)
• Bounds:
  • contains2D(bounds) in favor of contains2DBounds(bounds)
  • contains3D(point) in favor of contains3DPoint(point)
  • contains3D(bounds) in favor of contains3DBounds(bounds)

It is now possible to introduce clustering to help reduce the clutter when there are many objects in a LuciadRIA view. You can configure a FeatureLayer to use a ClusteringTransformer, which will aggregate model elements that are close together into a cluster.

For more information, please refer to the LuciadRIA Developer's Guide chapter "Clustering".

• When a FeatureModel is constructed without explicitly setting the reference, it will borrow the reference from the WFSFeatureStore.
• When the reference of the FeatureModel is not identical to the reference of its WFSFeatureStore, a warning will be logged to the console explaining this discrepancy. It is a restriction of the WFSFeatureStore that its reference is identical to the reference of the FeatureModel it is added to.

• Albers Equal Area Conic
• Azimuthal Equidistant
• Cassini
• Dutch Stereographic
• Eckert IV and VI
• Lambert Azimuthal Equal Area
• Lambert Conformal
• Mollweide
• Oblique Mercator
• Orthographic
• Polyconic
• Spherical Oblique Mercator
• Stereographic
• Swiss Oblique Mercator
• Transverse Mercator

• Circles: see luciad.shape.Circle. Circles are defined by center point and radius (luciad.shape.CircleByCenterPoint) or by three points on the circumference (luciad.shape.CircleBy3Points).
• Ellipses: see luciad.shape.Ellipse. Ellipses are defined by center point, major axis length, minor axis length and major axis rotation azimuthal angle.
• Circular arcs: see luciad.shape.CircularArc. Circular Arcs are defined by center point and radius (luciad.shape.CircularArcByCenterPoint), by start, intermediate and end points (luciad.shape.CircularArcBy3Points), or by two points and bulge (luciad.shape.CircularArcByBulge).
• Elliptical arcs: see luciad.shape.Arc. Elliptical arcs are defined by an ellipse, a start azimuthal angle and an arc azimuthal angle.
• Arc bands: see luciad.shape.ArcBand. Arc bands are sectors, defined by a center point, a minimum and maximum range, a start azimuthal angle and an arc azimuthal angle.
• GeoBuffers: see luciad.shape.GeoBuffer. They are defined by a base shape, which can be a polyline or polygon, and a width.

• To avoid long running scripts and improve responsiveness of the application, the FeatureLayer will process the results of a model query in small batches.
• Developers can now also enable incremental rendering by setting the FeatureLayer.options.incrementalRenderering flag to true. This way the visual representations of Features is processed in small batches, and drawn to the screen in small increments.
• The Developer's Guide now includes a chapter on how to create applications when dealing with large datasets. This includes information on web caching strategies, as well as Javascript and LuciadRIA tips and tricks to improve performance.

LuciadRIA now has support for performing boolean operations on shapes. In order to do so, you can use a ConstructiveGeometry object. ConstructiveGeometryFactory allows you to create ConstructiveGeometry objects performing boolean operations using a cartesian, spherical or ellipsoidal topology.

The following operations are supported:

• Union
• Intersection
• Difference

It is now possible to load a luciad/symbology/Symbology without using the AMD-plugin method. Instead, you can now just call luciad/symbology/Symbology#getSymbology to retrieve a Symbology for a given code.

The advantage of loading symbologies with this approach is that it does not rely on the AMD-plugin API. This API is generally well supported when using build-tools from the AMD ecosystem, but may not be well supported with other toolchains or JS module systems.

Military symbols now show movement direction arrows.

The following modifiers affect the arrows:

• "movementDirection": a number indicating the heading of the object. Must be an azimuth: degrees, clock-wise, 0 is north.
• "speedLabel": a string expressing the movement speed, for example "17 km/h" or "11 kn". Affects the length of the arrow. Only relevant for APP-6C and MIL-STD-2525C.

Ground units will have an arrow starting from a vertical stem.

The length of the arrow is determined by the existing style property "iconSize" in combination with the "speedLabel" modifier if available. The line-width of the arrow is determined by the existing style properties "lineWidth".

There is now visualization support for all APP-6 (A/B) and MIL-STD-2525 (B/C) objects, including tactical line-based symbols. In addition, interactive creation and editing is also supported for all symbols.

Relevant components are located in the luciad.symbology namespace. Important modules are:

• luciad.symbology.SymbologyProvider: an AMD plugin which allows you to load a particular symbology standard
• luciad.symbology.military.MilitarySymbologyPainter: a configurable painter for military symbols.

• it goes outside the beginning or the end of the line (unless the decoration is placed at the beginning or at the end of the line)
• it overlaps with a previous decoration

• widths for TextStyle & PinStyle are now defined as number instead of string in docs & Typescript def, in correspondence with other numeric widths in LuciadRIA
• Typescript def now requires position property to be a valid PointLabelPosition or array of PointLabelPositions
• docs not also mention position property should be a valid PointLabelPosition or array of PointLabelPositions
• docs now correctly mention PointLabelPosition.NORTH & PointLabelPosition.SOUTH instead of PointLabelPosition.ABOVE & PointLabelPosition.BELOW

• Data loading (tiles, features) caused by navigation etc.
• Feature processing caused by painter invalidations etc.

      map.mapNavigator.fit({bounds: somewhere});
      map.layerTree.whenReady().then(makeScreenshot);
    

• Features that aren't submitted to the geoCanvas in your FeaturePainter.paintBody will not be labeled
• In 3D, the submitted shape has to be either a point or one of the shapes submitted in the paintBody for the corresponding feature

• EPSG:23035
• EPSG:23036
• EPSG:23037
• EPSG:23038
• EPSG:2206
• EPSG:2207
• EPSG:2208
• EPSG:2209
• EPSG:2210
• EPSG:2211
• EPSG:2212

• Terrain: if enabled, the camera will stay above the data in elevation layers. On by default.
• Mesh: if enabled, the camera will stay above the data loaded in 3D tiles layers. Off by default.
• None: the camera is not restricted, and can go under or inside the terrain and mesh data.

• OGC services (WMS and WFS)
• GML decoding
• OGC BBox filters