This page shows the release notes of older versions up until the point that the new version was released. For a full list of release notes of an old version, consult the documentation of that version.
For example if you want to see what is fixed in each 2019.1.x patch release, consult the release notes in the documentation of the 2019.1 release.
2023.0
2023.0.12
Bug fixRadar Connectors
LCD-13125
The scaling factor included in ASTERIX Category 8 data was not taken into account when decoding the range, length and
coordinate parameters. This factor is now used if it is available in the data and if no external
ALcdASTERIXScalingFactorProvider is configured on the ASTERIX decoder.
In all other cases, a default value (7) is used, similar as before.
2023.0.07
ImprovementRadar Connectors
LCD-13002
Support for ASTERIX Category 34 has been added, cfr.
TLcdASTERIXCategory34. As a result,
TLcdASTERIXLiveModelDecoder and TLcdASTERIXModelDecoder
can now decode ASTERIX Category 34 datasets. The data type of the decoded objects is
TLcdASTERIXDataTypes#Category34RadarServiceMessageType.
2022.0
2022.0.03
ImprovementRadar Connectors
LCD-12240
TLcdASTERIXCategory48: now supports Asterix category 48 revision 1.21. It incorporates
cumulative changes since Asterix category 48 revision 1.15. As a result
TLcdASTERIXLiveModelDecoder
and
TLcdASTERIXModelDecoder
can now decode Asterix datasets in compliance with Asterix category 48 revision 1.21 and earlier revisions.
2022.0
ImprovementRadar Connectors
The ASTERIX API class
TLcdASTERIXTrajectory now implements ILcdCurve.
2021.1
2021.1.08
ImprovementRadar Connectors
LCD-12242
You can now configure the position field to be used for tracks within ASTERIX Category 48: by default,
the Calculated Position in Cartesian Coordinates (X / Y) field is used. This can be changed to the
Measured Position in Slant Polar Coordinates (Rho / Theta) field by setting the System property
com.luciad.format.asterix.cat48.usePolarCoordinates to true.
2021.0
2021.0.02
ImprovementRadar Connectors
LCD-11858
You can now configure the calculated altitude field to be used for tracks within the ASTERIX Categories 30 and 62:
- Category 30: By default, the Calculated Track Altitude field is used. This can be changed to the
Calculated Track Flight Level field by setting the System property
com.luciad.format.asterix.cat30.useCalculatedTrackFlightLevelto true. - Category 62: By default, the Calculated Track Geometric Altitude field is used. This can be changed to the
Calculated Track Barometric Altitude field by setting the System property
com.luciad.format.asterix.cat62.useCalculatedTrackBarometricAltitudeto true.
2020.1
2020.1.24
ImprovementRadar Connectors
LCD-11809
TLcdASTERIXLiveDecoder#decodeBlockSFCT could throw an ArrayIndexOutOfBoundsException in case of an ASTERIX
record of which the encoded record length exceeds the actual record length. Such a record is now skipped and logged.
2020.0
2020.0.16
Bug fixRadar Connectors
LCD-11490
TLcdASTERIXLiveDecoder#decodeBlockSFCT could throw an ArrayIndexOutOfBoundsException in case of an
ASTERIX data block that defines a zero length. A zero length is now interpreted as the end of the data stream.
2018.1
2018.1.14
Bug fixRadar Connectors
LCD-10619
When the records received from a radar feed (ASTERIX cat240) are not next to each other in terms of azimuth,
the visualization would show artifacts.
2018.0
2018.0.11
Bug fixRadar Connectors
LCD-10176
"Time of Day" (Data Item I021/030) octets of ASTERIX Category 21 (version 0.23) are now decoded as unsigned numbers.
2018.0.03
ImprovementRadar Connectors
LCD-9760
TLcdASTERIXCategory62: Following trajectory properties are now available on the TLcdASTERIXTrajectory and their values can be changed by calling the setValue method
in the ILcdDataObject interface:
- Callsign
- IFPSFlightId and all its subproperties
- FlightCategory and all its subproperties
- TypeOfAircraft
- WakeTurbulenceCategory
- DepartureAirport
- DestinationAirport
2018.0
ImprovementRadar Connectors
LCD-6033
TLcdASTERIXLiveDecoder: you can now pass any ILcdModelContainer to the
decode*SFCT, not only a TLcdModelList. For instance, a TLcdModelTreeNode.
This is useful if your ASTERIX data contains a mix of category 240 and other categories. For a TLcdModelList,
all models need to have the same model reference. However, category 240 models typically has a different model reference than
the
other categories. TLcdModelTreeNode does not have this restriction.
ImprovementRadar Connectors
TLcdASTERIXLiveModelDecoder: this new class is an ILcdModelDecoder implementation
which allows to decode live ASTERIX data.
Upgrade considerationRadar Connectors
TLcdASTERIXDataSource: this class is now final. This class was never designed to be extended,
and to make that clear the class has been made final.
2017.0
2017.0
ImprovementRadar Connectors
The ISO measure properties in the data model are now annotated with a
TLcdISO19103MeasureAnnotation.
2016.1
2016.1.33
ImprovementRadar Connectors
LCD-8883
When trying to visualize a high resolution radar, it can occur that the radar data is not shown in the view.
This occurs when not enough texture memory is available (e.g. not enough GPU memory or when using a 32bit JVM).
Now a
RuntimeException will be thrown in this situation, to make clear what is causing the problem.
2016.1.21
Bug fixRadar Connectors
LCD-8728
TLcdASTERIXLiveDecoder is now more robust against initial ASTERIX category 240 records which differ significantly
in azimuth resolution. Previously the radar could not initialize its parameters and as a result nothing
would be visualized.
2016.1
ImprovementRadar Connectors
The Data Model Viewer sample has a better UI now.
ImprovementRadar Connectors
TLcdASTERIXModelDecoder can now decode ASTERIX Category 10 (Transmission of Monosensor
Surface Movement Data - version 1.1). The data model can be found in the
TLcdASTERIXCategory10 class.
Bug fixRadar Connectors
LCD-8217
TLcdASTERIXModelDecoder: decodeSource now closes all created input streams, not only
the input stream to read the last source.
2016.0
2016.0.07
Bug fixRadar Connectors
LCD-7876
TLcdASTERIXDecoder.canDecode and retrieveFormat are now more correct in that they no longer accept files ending in
'asterix', but only those ending in '.asterix'. Similar for pcap, ast and astfin.
2016.0
ImprovementRadar Connectors
LCD-7613
TLcdASTERIXLiveDecoder has been improved to be more robust against out of order ASTERIX category 240 records.
The first records received are now buffered and sorted to make sure the radar visualization is initialized with the
correct parameters.
ImprovementRadar Connectors
LCD-7067
The
decode.asterix.lightspeed.trackdisplay sample was added. This sample demonstrates how a track display,
based on ASTERIX track data, can be displayed.
ImprovementRadar Connectors
TLcdASTERIXFilteredModel now implements ILcdMultiDimensionalModel, which allows it to work with
TLcdDimensionalFilter instances.
Bug fixRadar Connectors
LCD-7604
Fixed memory leak in radar layer. The memory leak occurred when the visualization of the radar was reset.
2015.1
2015.1.28
ImprovementRadar Connectors
LCD-7568
The radar visualization will now be reset when the data source identifier of the received ASTERIX category 240
record is different compared to the previously received record.
2015.1.27
Bug fixRadar Connectors
LCD-7565
TLcdASTERIXLiveDecoder is now more robust against missing ASTERIX category 240 records. If records were missing
at the start of the stream, this could result in incorrect visualization of the radar feed.
2015.0
2015.0.04
Bug fixRadar Connectors
LCD-6542
TLcdASTERIXCategory62: the "Mode 4 Age" field was decoded as 16 bits, it is now decoded as the correct 8 bits.
2015.0.01
Bug fixRadar Connectors
LCD-6322
TLcdASTERIXLiveDecoder is now more robust against ASTERIX category 240 records that arrive out of order.
2015.0
ImprovementRadar Connectors
TLcdASTERIXModelDecoder can now decode ASTERIX Category 8. The category is modelled in the
TLcdASTERIXCategory8 class. ASTERIX Category 8 concerns weather data. Weather data in ASTERIX is modeled by
TLcdASTERIXWeatherPicture and TLcdASTERIXPrecipitationZone classes. TLcdASTERIXFinalModelEncoder can encode
ASTERIX Category 8.
2014.1
2014.1.04
Bug fixRadar Connectors
TLcdASTERIXLiveDecoder has been made more robust in its handling of irregularities in
category 240 data.
Bug fixRadar Connectors
LCD-6244
TLcdASTERIXLiveDecoder did not respect the mode for firing events when decoding ASTERIX category 240 data.
2014.1.01
Bug fixRadar Connectors
Fixed the thread safety of the ASTERIX models. Some operations were not thread-safe since version 2014.1.
2014.1
ImprovementRadar Connectors
ASTERIX category 240 radar video is now supported by TLcdASTERIXLiveDecoder. More information on how to
visualize category 240 radar video can be found in the developer guide in the section 'Decoding category 240 radar
video'. The 'Visualization of ASTERIX cat 240 radar video' sample illustrates how to visualize the
radar video data.
2014.0
2014.0.13
Bug fixRadar Connectors
LCD-5909
TLcdASTERIXCategory21: the 'Track Angle' property of the 'Airborne Ground Vector' of a track is now used as the
orientation of the TLcdASTERIXTrack.
2014.0.12
Bug fixRadar Connectors
LCD-5898
TLcdASTERIXLiveDecoder no longer deadlocks if the input stream passed to decodeBlockSFCT is a
PipedInputStream with a limited buffer size.
2014.0.04
ImprovementRadar Connectors
TLcdASTERIXModelDecoder:
*.ast files are now recognized as raw ASTERIX files.
Bug fixRadar Connectors
LCD-5493
TLcdASTERIXModelDecoder: files whose extension is not recognized are now treated as raw ASTERIX files again.
This behaviour was mistakenly changed in the 2013.1 release.
Bug fixRadar Connectors
LCD-5682
TLcdASTERIXCategory21: records with the same ID were sometimes not linked to together in the same trajectory. For
model decoding, this could result in multiple trajectories for a single ID. For live decoding, this could lead to
tracks being removed from the model and then immediately added back again. This is now fixed.
Bug fixRadar Connectors
Fixed a problem with retrieving collections through the ILcdDataObject interface.
Some could have a incorrect first element.
2013.1
2013.1.06
Bug fixRadar Connectors
TLcdASTERIXCategory30: The definition of the "Reserved Expansion Field" has been fixed. Before this fix,
the presence of such an item could cause exceptions when reading the value for it.
Bug fixRadar Connectors
LCD-4675
TLcdASTERIXLiveDecoder: the methods initDecode and decodeBlockSFCT now allow you to process the live ASTERIX
data on the AWT thread. This way you can follow the threading guidelines for LuciadMap.
2013.1.05
ImprovementRadar Connectors
LCD-3781
TLcdASTERIXFinalModelEncoder: ASTERIX models can now also be saved in the plain asterix format instead of only in
the ASTERIX Final format.
Bug fixRadar Connectors
LCD-1595
TLcdASTERIXModelDecoder: the time information in raw asterix files is now interpreted correctly.
Such files containing ASTERIX records before and after midnight will now be decoded correctly.
2013.1.01
Bug fixRadar Connectors
Records that do not contain any location data are now discarded. This way, more asterix files can
be decoded without visual artifacts.
Bug fixRadar Connectors
LCD-4502
TLcdASTERIXCategory21: the target address is now used as the ID of a trajectory. This way, more
files containing category 21 data can be decoded. The TargetIdentification of a trajectory can now be
changed using the setValue method of TLcdASTERIXTrajectory.
2013.0
2013.0.14
ImprovementRadar Connectors
TLcdASTERIXAltitudeRecordFilter: this filter allows you to reject tracks and/or plots based on their altitude.
Set it on the model decoder or live decoder with the setRecordFilter method.
ImprovementRadar Connectors
The properties that can be changed for TLcdASTERIXTrack can now also be changed for TLcdASTERIXPlot.
ImprovementRadar Connectors
LCD-4090
TLcdASTERIXCategory11: all trajectory properties and related track properties for category 11 can now be changed
through the ILcdDataObject interface. More specifically, following trajectory properties can now be changed:
- Callsign
- IFPS_FLIGHT_ID and all its subproperties
- FlightCategory and all its subproperties
- TypeOfAircraft
- WakeTurbulenceCategory
- DepartureAirport
- DestinationAirport
- FlightPlanRelatedData.Callsign
- FlightPlanRelatedData.IFPS_FLIGHT_ID and all its subproperties
- FlightPlanRelatedData.FlightCategory and all its subproperties
- FlightPlanRelatedData.TypeOfAircraft
- FlightPlanRelatedData.WakeTurbulenceCategory
- FlightPlanRelatedData.DepartureAirport
- FlightPlanRelatedData.DestinationAirport
2013.0.12
Bug fixRadar Connectors
LCD-4078
TLcdASTERIXModelDecoder is now more robust when decoding multiple files containing records of multiple
categories.
2013.0.11
ImprovementRadar Connectors
LCD-4068
TLcdASDIFileReplayInputStream: the threads created by this class now get a descriptive name instead
of the default "Timer-X" names.
ImprovementRadar Connectors
LCD-4068
TLcdASTERIXFinalReplayInputStream: the threads created by this class now get a descriptive name instead
of the default "Timer-X" names.
Bug fixRadar Connectors
LCD-4070
Data fields that are optional in the ASTERIX streams are now marked as nullable in the
ILcdDataModels of the various track types.
Bug fixRadar Connectors
LCD-3925
Support property values that contain NUL characters
2013.0.07
Bug fixRadar Connectors
LCD-4008
TLcdASTERIXModelDecoder: no longer throws exceptions for some specific PCAP files that contain IP fragments
for other IP addresses.
2013.0.06
ImprovementRadar Connectors
LCD-3947
TLcdASTERIXTrajectory: the value of data properties is now the latest non-null value of the corresponding
track property instead of simply the latest value.
ImprovementRadar Connectors
LCD-3951
TLcdASTERIXModelDecoder is now able to decode multiple files in one go. A trajectory split over
two or more files can be decoded as a single trajectory with this. See the 'How to decode ASTERIX data'
section in the developer's guide and the reference documentation of
TLcdASTERIXDataSource
for more information.
Bug fixRadar Connectors
LCD-3997
TLcdASTERIXCategory11: data Item I011/170 (Track status), field "Track service end" is now
recognized as a termination message.
2013.0.02
ImprovementRadar Connectors
LCD-3911
TLcdASTERIXCategory11: trajectories of category 11 now also have properties that correspond to the
sub-properties of the FlightPlanRelatedData property of category 11 tracks.
ImprovementRadar Connectors
LCD-3910
The values for the 'TypeOfAircraft' property can now be set for tracks of categories 30 and 30 Version 2.5 Ter.
Trajectories of these categories now also have an 'TypeOfAircraft' property whose value you can change.
Bug fixRadar Connectors
TLcdASTERIXTrajectory: the values gotten through the ILcdFeatured interface now match the values
gotten through the ILcdDataObject interface.
Bug fixRadar Connectors
LCD-3936
TLcdASTERIXTrajectory: the bounds returned by getBounds now also include height information.
2013.0
ImprovementRadar Connectors
The TLcdASTERIXModelListDescriptor has been added. This model descriptor is used for model lists decoded by the
TLcdASTERIXModelDecoder. If offers functionality to edit the source and display names.
ImprovementRadar Connectors
LCD-3860
ALcdASTERIXDecoder: the measure type for all track-properties which denote a relative time is now duration instead
of absolute time.
ImprovementRadar Connectors
TLcdASTERIXModelDecoder can now decode ASTERIX Category 11 and Category 21. The data models can be found in the
TLcdASTERIXCategory11 and TLcdASTERIXCategory21 classes respectively. Also added support for a popular draft version
of ASTERIX Category 21 (version 0.23). This category can be found in the TLcdASTERIXCategory21Version0Dot23 class.
ImprovementRadar Connectors
TLcdASTERIXModelDecoder: this decoder can read ASTERIX data from PCAP files (network Packet CAPture)
where ASTERIX data are in either Ethernet (versionII, LLC or LLC+SNAP) packets directly
or in UDP datagrams ( UDP datagrams fragmented across multiple IP datagram are also supported).
ImprovementRadar Connectors
Some properties of TLcdASTERIXTrajectory and TLcdASTERIXTrack can now be changed by calling their
setValue method. Consult the developer's guide for more information.
ImprovementRadar Connectors
TLcdASTERIXTrajectory: ASTERIX trajectories now expose a subset of the underlying track properties. Specifically,
the track properties that usually remain the same in the complete trajectory are also available as trajectory
properties. Consult the developer's guide for more information.
ImprovementRadar Connectors
TLcdASTERIXFinalModelEncoder: this model encoder is able to save models and model lists decoded by
the TLcdASTERIXModelDecoder. Together with the set of properties that can now change, this allows you
to clean up your recorded ASTERIX data.
2012.1
2012.1.14
Bug fixRadar Connectors
LCD-3669
TLcdASTERIXModelDecoder: access to the decoded trajectories is again fast and thread-safe if the proper
read-locks are taken on the model.
2012.1.13
Bug fixRadar Connectors
LCD-3601
Fixed a problem with the decoding of Special Purpose Fields and Reserved Expension Fields.
2012.1.09
Bug fixRadar Connectors
TLcdASTERIXCategory1: records of the Plot UAP of category 1 are now decoded as TLcdASTERIXPlots.
Bug fixRadar Connectors
ALcdASTERIXDecoder: TLcdASTERIXPlot instances will now always get added to their own model. Sometimes they
were added to the trajectory model.
Bug fixRadar Connectors
TLcdASTERIXModelDecoder: by default, ASTERIX trajectories decoded from a raw ASTERIX file again start in the
current date instead of the first of January 1970.
Bug fixRadar Connectors
TLcdASTERIXSacSicRecordFilter will no longer throw NullPointerExceptions when reading category 244 data.
2012.1
ImprovementRadar Connectors
LCD-2805
TLcdASTERIXTrajectory now also implements ILcdPolyline, which is an ILcdShape. This improves interoperability
with the rest of LuciadLightspeed.
ImprovementRadar Connectors
Added support for plots in the ASTERIX decoder. If an ASTERIX file or live-feed contains any plot data, it
will be output in a specific model with a TLcdASTERIXPlotModelDescriptor. The model will contain
TLcdASTERIXPlot elements, which can be visualized using any painter capable of painting ILcdPoint instances.
2012.0
2012.0.06
ImprovementRadar Connectors
LCD-61, LMAP-2794
The conversion from relative time to absolute time is now more robust.
ImprovementRadar Connectors
Sample class TrackSimulatorModel now also interpolates the track altitudes, not only the 3D
location.
ImprovementRadar Connectors
The ASTERIX decoders can now filter on the record level, which allows to filter individual
tracks while decoding. One could for example filter out tracks based on their SAC/SIC code
(radar system), or ignore all coasted tracks. See also ILcdASTERIXRecordFilter,
TLcdASTERIXSacSicRecordFilter and ALcdASTERIXDecoder.setRecordFilter.
ImprovementRadar Connectors
The ASTERIX decoders now support reading a subset of network capture files (PCAP files). It
supports captures of raw Ethernet packages (LLC, IEEE 802.3), where no additional network
protocols like IP or UDP are used. Replaying PCAP files is supported as well, please refer to
TLcdASTERIXFinalReplayInputStream for more details.
ImprovementRadar Connectors
Support for version 2.5 ter of ASTERIX category 30 has been added. This is a draft version of
the specification, released in 1997. It is binary incompatible with the final release of
category 30 (v6.1 in 2000). It is therefore disabled by default. It can be enabled by setting
TLcdASTERIXCategory30Version2Dot5Ter on the ALcdASTERIXDecoder.
2012.0.05
Bug fixRadar Connectors
LCD-1560
The data models for the various categories no longer confuse the types for properties with the same
display name.
Bug fixRadar Connectors
LCD-1559
Following termination messages are now properly interpreted:
- Category 1, Track UAP: Data Item I001/170 (Track status), field TRE (Last report for track)
- Category 48: Data Item I048/170 (Track status), field TRE (Signal for End_of_Track)
- Category 62: Data Item I062/080 (Track status), field TSE (Last message transmitted)
11.0
11.0
Bug fixRadar Connectors
Fixed some wrong instance class specifications in the data model of ASDI.
Bug fixRadar Connectors
LMAP-5461
The boundary crossing information is now available through the ILcdDataObject interface on the
flight plans.
Bug fixRadar Connectors
LMAP-5241
The ILcdDataObject implementation for collection properties is now correct: the values for collection
properties are now always instances of the right collection class.
Upgrade considerationRadar Connectors
LMAP-5241, LMAP-5247
In order to fix the issues in the datamodel implementation, the datamodel itself has been changed for all data object properties that were collections.
This change will not result in compile time errors, only runtime behavior has changed.
You are only affected if you access following collection properties through the ILcdDataObject interface:
- Category 1, Plot UAP:
- RadarPlotCharacteristics
- WarningErrorConditions
- Category 1, Track UAP:
- RadarPlotCharacteristics
- TrackQuality
- WarningErrorConditions
- Category 244:
- ADSBProjectedProfile
- Category 30:
- ReservedExpansionField
- AllocatedSSRCodes
- ARTASTrackNumber
- Category 48:
- ModeSMBData
- WarningErrorConditions
- RawDopplerSpeed
- Category 62:
- TrajectoryIntentData
- ModeSMBData
- ComposedTrackNumber
- TimeOfDepartureArrival
10.1
10.1.01
Bug fixRadar Connectors
LMAP-4872
The decoder.asterix.live and decoder.asterix.file samples could throw an exception when
setting an other layer labeled.
Bug fixRadar Connectors
LMAP-4870
The decoder.asdi.live and decoder.asdi.file samples could throw an exception when setting an
other layer labeled.
10.1
ImprovementRadar Connectors
Updated ASDI classes to support ILcdDataObject interface. While ILcdFeatured is still supported,
it is recommended to use the ILcdDataObject interface instead. For more information, refer to
the developer's guide as well as the API reference of the new classes: TLcdASDIMessageDataTypes,
TLcdASDIDataTypes, TLcdASDIFlightPlanDataTypes, TLcdASDITrackTODataTypes and TLcdASDITrackTZDataTypes.
ImprovementRadar Connectors
Adjusted domain objects (tracks and trajectories) to support the unified ILcdDataObject interface. The
ILcdDataObject interface is an improvement over the ILcdFeatured interface. ILcdFeatured is still supported
for reasons of backwards compatibility.
On top of that, the ASTERIX Industry Specific Component now features a new class that can statically retrieve a data
model
for a given user application profile. The data model can also be retrieved through the ALcdASTERIXModelDescriptor,
which now implements ILcdDataModelDescriptor.
Upgrade considerationRadar Connectors
The ILcdASDIMessageFilter has been changed to accommodate the new ILcdDataObject interface. The
accept method now accepts a single ILcdDataObject instance instead of an ILcdFeatured and an
ILcdFeaturedDescriptor. The properties for this ILcdDataObject can be found in the TLcdASDIMessageDataTypes
class. The filter still offers equivalent functionality, while being easier to use in an IDE with
auto-completion.
The TLcdASDIMessageInputStream.readMessage() method now returns an ILcdDataObject representation
of a message instead of an ILcdFeatured representation. The properties for this ILcdDataObject
match the one given in ILcdASDIMessageFilter. For more information, refer to the API reference
of TLcdASDIMessageDataTypes class.
10.0
10.0.15
Bug fixRadar Connectors
The featured descriptor of trajectory models now correctly indicate that the "ID" feature
returns an Integer instead of a String.
10.0.09
Bug fixRadar Connectors
LMAP-4549
TLcdASTERIXCategory48 : the featured descriptor of the tracks now labels the 'Mission Code' as such
instead of as 'Pin Code'.
10.0.08
Bug fixRadar Connectors
Fixed exception that would occur when retrieving the orientation of a non-active TLcdASTERIXTrack.
The method now returns Double.NaN instead.
9.0
9.0.22
Bug fixRadar Connectors
Changed the unit display name of angle features to 'Degrees' to be more consistent with the rest of LuciadMap.
Upgrade considerationRadar Connectors
TLcdASTERIXCategory62 was updated for changes between edition 1.3 and edition 1.9 of the category 62 specification.
9.0
Bug fixRadar Connectors
TLcdASTERIXCategory30: decoding the same file twice now produces the same results. Because of
the bugfix for LMAP-2768, trajectories that were marked as terminated in the previous decoding
run were immediately marked as terminated in the next decoding run.
Bug fixRadar Connectors
LMAP-2795, LMAP-2796
TLcdASTERIXCategory1: trajectories of category one are no longer split up in parts of 512
seconds. This fixes a regression introduced by the fix for LMAP-2762.
8.2
8.2.24
Bug fixRadar Connectors
LMAP-3108
The constructor of TLcdASTERIXTrajectoryModelDescriptor no longer refers to a package visible
class which is not part of the API.
Bug fixRadar Connectors
Sample class 'TransformationProvider' now accept more degree formats, such as DDMMSS, in its
locations.cfg file.
8.2
Bug fixRadar Connectors
LMAP-2880
TLcdASDIFileReplayInputStream: no longer throws IOExceptions due to 'Pipe not connected' errors.
Bug fixRadar Connectors
LMAP-2881
TLcdASTERIXFinalReplayInputStream: no longer throws IOExceptions due to 'Pipe not connected'
8.1
8.1.05
Bug fixRadar Connectors
LMAP-2768
TLcdASTERIXCategory30: the terminated flag of the track status is now used to determine
which messages belong to different flights.
Bug fixRadar Connectors
LMAP-2762
TLcdASTERIXModelDecoder: the decoder now properly handles messages with information of right
before midnight, but which were received right after midnight.
8.1.03
Bug fixRadar Connectors
The "Calculated Track Velocity (Cartesian)" values of category 30 are now read as signed
numbers.
8.0
8.0.11
Bug fixRadar Connectors
Duplicate 'LayerFactory' sample class is now removed.
8.0.03
ImprovementRadar Connectors
LMAP-2532
The sample now shows an outline around the simple track-icon, making it better visible on
irregular background data.
7.2
7.2.01
ImprovementRadar Connectors
TLcdASDIFlightPlan: now has a public clone method.
7.2
ImprovementRadar Connectors
Introduced ASDI : the package com.luciad.format.asdi is the Industry Specific Component
for decoding and displaying ASDI data.
Bug fixRadar Connectors
The TLcdASTERIXFinalReplayInputStream.close did not cleanup properly the threads it started.
This is fixed now.
Upgrade considerationRadar Connectors
TLcdASTERIXLiveDecoder: To avoid threading problems between the decoder adapting the data and a user (for example) painting the data, all data modifications used to be done on the event dispatch thread (aka AWT thread). As this thread is also used for painting, there were no threading problems because all modifications and read access were queued and executed one after the other. The drawback is that this does not offer much flexibility and scalability, nor does it play well server side.
Instead, TLcdASTERIXLiveDecoder now simply adapts the data on the calling thread, but uses TLcdLockUtil to acquire a write lock whenever it does so. As a result, users of the live decoder should now protect read access by acquiring a read lock (using TLcdLockUtil). The live sample uses a an extension of EditableLabelsLockedGXYLayer to do so.
7.1
7.1.13
ImprovementRadar Connectors
Slightly simplified samples.decoder.asterix.TrackGXYPainter.
7.0
7.0.07
Bug fixRadar Connectors
Feature values (attributes) of ASTERIX domain objects that return an instance of ILcdISO19103Measure
sometimes did not use the correct SI standard units. These changes were made:
- Degrees -> Radians
- dBm -> watt
- Bar -> Pascal
- Celcius -> Kelvin
7.0.01
Bug fixRadar Connectors
Updated sample: now properly handles license errors.
7.0
ImprovementRadar Connectors
Updated sample : trajectory layers now use a TLcdGeodeticPen and simulated tracks are interpolated doing true
geodesic interpolation, all to avoid problems at the edges of the map.
ImprovementRadar Connectors
Updated sample : world data is now loaded at startup.
6.2
6.2.13
ImprovementRadar Connectors
Improved performance of updateObjectsForTime method of sample TrackSimulationModel.
6.2.01
ImprovementRadar Connectors
toString() methods of TLcdASTERIXTrajectory and TLcdASTERIXTrack now return a human readable string.