2018.2.0 Updates

Apply all the Platform updates in addition to updates for the modules you have installed.

Important: You must install updates in order. For example you must install S01 before S02, and S02 before S03, and so on.

Platform

Update Number Description Download Software/Release Notes Bundles Download Release Notes Only
2018.2 S10 This product update fixes multiple issues and provides some security enhancements.

Server error

Received error “java.lang.NumberFormatException: null” when running a dataflow in Distributed mode

Enterprise Designer fixes
  • Display help in French, according to locale
  • Some subflows are missing for users with non-administrator rights

Security enhancements

  • Provide a way to export security overrides through Admin Utility
  • Add logout events to the audit log
  • Allow LDAP/AD connection with multiple domains

This product update is optional and applies to all supported platforms.

  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S15 This software update resolves two issues and provides two security enhancements.
  • The security enhancements:
    • Direct Spectrum™ Technology Platform to encrypt all resource passwords and to either remove or mask passwords in log files.
    • Provide default support for external requests to the Spectrum Technology Platform server via proxy.
  • We have resolved an issue that caused scheduled jobs running according to control file triggers to end with errors.
  • We have added Japanese language support to Management Console.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S19 This product update resolves two customer-reported issues and provides a new Command Line Interface (CLI) command.
  • Exported JSON file does not list multiple admin roles.
  • Management Console is unresponsive when multiple secured entities exist.
  • Added a new CLI command to export audit log events.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S20 This product update provides two customer-requested enhancements:
  • Change persistence layer to always check indexes and recreate indexes if not found.
  • Improve the process that Spectrum follows to shut down Neo4j.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S25 This product update resolves an issue that occurred when backing up the Spectrum repository. This product update also provides a utility to perform index consistency checks and a store copy utility.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S28 This product update includes the following:
  • Resolution of a DistributedObjectDestroyed exception occurring in a microflow
  • Improved performance of service dataflows that use the Group Statistics stage
  • A utility that generates encryption strings
  • Requested security enhancements
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:

Advanced Matching Module

Update Number Description Download Download Release Notes Only
2018.2 S30 This product update fixes the functioning of system security role in the Data Normalization Module and Advanced Matching Module.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S06 This product update improves the system generated tags and provides a better user experience.

Data Hub Module

Update Number Description Download Release Notes
2018.2 S13 This product update resolves an issue in which the Write to Hub initial load is failing for large model (Garbage Collection overhead memory issue). This is an optional product update.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:

Enterprise Geocoding Module

Update Number Description Download Release Notes
2018.2 S23 This product update includes:

Canada (CAN) dataset: Added a new field CPC_RECORD_TYPE to return a two-character alphanumeric code to identify details on the type (for example, high-rise buildings, or a government street address) of the postal record it was matched against. This information is only returned when a match contains a full FSA (Forward Sortation Area)-LDU (Location Delivery Unit).

Czech Republic (CZE) dataset: Matching improvements include a more accurate and precise location returned because it will now match both house and plot numbers.

New custom fields: For 17 countries, new geographic and postal geocoding custom fields provide additional metadata including primary postcode, multiple area postcodes, and the number of postcodes for each town.
  • MULTIPLE_AREAS_FOR_POSTCODE: Postal centroid candidates return true if more than one town is contained within the postcode.
  • PRIMARY_AREA_FOR_POSTCODE: Postal centroid candidates return true if the current town is the primary town for this postcode.
  • POSTCODE_COUNT_IN_AREA: Geographic centroid candidates return the number of postcodes found in that town when available.

These features are available with the JULY 2019 datasets. For more detail, refer to the Geocoding International Data v2019.07 Release Notes.

  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S26 This EGM-USA product update includes:
  • Updated GeoStan libraries: The libraries have been updated to version 32.00. This includes improvements to alias address details and singleline matching enhancements
  • Address variations are easier to identify: In the Reverse pbKey stage, the standardized address elements remain identical, but the parsed, alias address information (the variations) are returned as additional output fields.
  • Added the User Dictionary Writer: Enables you to map fields from your source data to required and optional Spectrum fields, creating a custom dictionary. For example, a local government might create a custom dictionary based on parcel maps for an emergency response or tax assessment application. Note: User Dictionaries are not for use with CASS geocoding.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:

Enterprise Routing Module

Update Number Description Download Software/Release Notes Bundles Download Release Notes Only
2018.2 S07 This mandatory product update applies to all platforms and fixes an issue where in the Settings tab of the GetRoute stage when the user clicked OK and then reopened the Settings tab, the OptimizeBy setting would change from Time to Distance.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S21 This product update is for both the Enterprise Routing Module (ERM) and Location Intelligence Module (LIM). It fixes:
  • Some routing web services were reading and writing numeric data in the wrong format because comma decimal points (“,”) used in some countries were not handled in a locale-independent way.

  • For the Travel Boundary stage, when adding a new parameter with String (or list type of string) in the input stage, the same was not listed in Values Field Name in the stage. When modifying the default TravelCost parameter on the Input tab from Double to String (or list type of string) in the input stage, the parameter was listed in the Travel Boundary stage but was not working as expected.

  • An error was occurring while applying persistent updates. It was corrupting the update file which in turn would throw an error at the time of server start.

  • The persistent update request for non-English locales was throwing an error before the completion of the operation.

  • In Enterprise Designer, placing a Spectrum platform stage after a Travel Boundary stage would hide the Cost and CostUnit fields from the output. These fields were in the inspection window but unavailable to downstream stages.

  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S22 This product update is for both the Enterprise Routing Module (ERM) and Location Intelligence Module (LIM). It fixes:
  • Enterprise Routing Module stages were reading numeric data in text box fields in the wrong format because comma decimal points (“,”) used in some countries were not handled in a locale-independent way.

  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:

Global Addressing Module

Update Number Description Download Software/Release Notes Bundles Download Release Notes Only
2018.2 S04 This product update includes Global Addressing Module support for the Q3 2018 data refresh. You must apply the 2018.2 S04 product update to use the most current version of global data with the Global Addressing Module. n/a
2018.2 S18 This product update includes:
  • Global Addressing Module support for distribution of dynamic libraries
  • Support for the Global Addressing Module Q1 2019 Data Refresh
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:

Global Geocoding Module

Update Number Description Download Software/Release Notes Bundles Download Release Notes Only
2018.2 S14 This product update includes the following enhancements:
  • PBLocator REST API

    Additional fields exposed - The geocoding candidate output now includes PBKey™ and Census information where available.

    Note: The PBLocator feature in the Global Geocoding Module is a licensed feature. Please contact your sales representative to obtain a license.

  • MatchScore & Confidence (USA) returned for Forward Geocode Stage

    The EGM confidence values for USA addresses is now available in the Global Geocoding Module.

  • MatchScore – all countries: (Global Feature)

    This is a new custom field that represents a score (0-100) of how well the input compares to the candidate values for certain fields. It is used to better indicate what parts of input address were changed to make the match. Fields checked include street name, house number, directional, street type, unit number, place name, postal code, and area names 1, 3, and 4. A lower match score indicates many input fields were changed.

  • Confidence

    This indicates the confidence in the output provided, from 0 to 100. The higher the score, the higher the probability that the match is correct. If the match is exact, the confidence score is 100. For all other matches, the confidence score is calculated based on which portions of the input address had to be changed to obtain a match.

    If you have enabled the option to return centroids, the confidencevalue indicates the type of centroid returned:
    • 60 for a street centroid
    • 50 for a postal code centroid
    • 35 for a city centroid
    • 30 for a county centroid
    • 25 for a state centroid
2018.2 S24 This product update includes the following enhancements:
  • Canada (CAN) dataset: Added a new output field, CPC_RECORD_TYPE.
  • Czech Republic (CZE) dataset: Matching improvements include a more accurate and precise location returned because it will now match both house and plot numbers.
  • New custom fields: For 17 countries, new geographic and postal geocoding custom fields provide additional metadata including: MULTIPLE_AREAS_FOR_POSTCODE, PRIMARY_AREA_FOR_POSTCODE, and POSTCODE_COUNT_IN_AREA.
  • Updated GeoStan libraries: The libraries have been updated to version 32.00. This includes improvements to singleline matching enhancements.

Location Intelligence Module

Update Number Description Download Software/Release Notes Bundles Download Release Notes Only
2018.2 S01 This product update addresses these issues:
  • From version 2018.2, custom image symbols created by the user can be placed in a folder called SpatialSymbols on the Spectrum server in a location referenced in the classpath.ext properties file. However, when accessing symbols from this location, Spectrum Spatial was pre-fixing the symbol name with the folder name (for example SpatialSymbols/MyCustomSymbol.png). When the Map Uploader creates layers, it references only the symbol names without a path. This behavior meant that custom symbols referenced in layers created by the Map Uploader were not getting matched to the one copied into Spectrum. This has now been fixed so that symbols added to the root of the SpatialSymbols folder will not have the path pre-fixed onto their name.
  • When setting enableAlpha as false in a grid style for an MRR image (which was using classified and image palette component type), the setting was getting ignored and a previously cached value was used. Now any updates made to the GridStyle are being reflected in map rendering and in Spatial Manager.
  • There was an entry in the app switcher called "Spectrum Single Sign-on Integration". This was not relevant for administrators, so it has been removed now.
  • The default settings for the Apache Jackrabbit Janitor was set to 24 seconds instead of 86400 seconds (24 hours). The janitor cleans up the repository journal in which cluster nodes write their changes. It is only relevant for customers who are using a common repository database (LIM cluster) and who have manually set janitorEnabled to true (since by default it is false). If you have enabled the janitor, then please review its settings after the patch is deployed.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S05 This software update includes the following updates:

Enhancement:

Support of query-param in the POST body along with bound parameters has been provided for the Feature service REST API. This improvement enhances the user experience where the user needed to pass a long SQL query in the query parameter (q) in the POST body, which would otherwise be too long to specify as part of a GET request.

Bugs Fixed:

  • The email and phone icons were missing in the Help menu in Spatial Manager. The missing icons have been restored now.
  • MapInfo Brush values that are used for filling polygons are documented as 1-8, 12-186 according to the MapBasic documentation. Values 9-11 are not supported. However, MapInfo Pro handles value 11 as solid fill whereas Spectrum Spatial did not. In addition, a long-standing black and white thematic template for individual value themes used value 11. This meant that any themes created with this template could not be rendered after uploading. The issue has been fixed as Value 11 is now supported.
  • After upgrade to the Spectrum 2018.2, the validationQuery= "SELECT 1" was returning an error when the query was enclosed with quotes. This property is located in the file pooling-datasource-factory.properties located under \server\modules\spatial. This has been fixed now.

Known Issue:

In the Find Nearest Stage, a maximum distance must be set when using a SQL Server-based named table that uses the SQL Server geography data type (i.e. the database table is in a projection such as EPSG 4326 with longitude and latitude co-ordinates).

2018.2 S17 This product update resolves an issue in which Spatial Manager displays a "LIM license has expired" message after installing a perpetual license key.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S21 This product update is for both the Enterprise Routing Module (ERM) and Location Intelligence Module (LIM).

This update adds two new properties for controlling ACL related behavior and fixes:

  • Combining native and custom handlers for data source definitions was generating an error: “MissingDataProviderReader: Unable to find a data provider reader for this element.”

  • After applying the 2018.2 S05 patch the POST Feature Service request was returning a “Bad Request” error. The same service was returning the expected output in the GET request.

  • The Output field defined for some spatial calculator operations such as Within and Intersects was not part of the stage output.

  • A Describe Table request was not returning the correct EPSG code (such as EPSG 3301) for a native TAB file that uses a specific Estonian Coordinate System.

  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S22 This product update is for both the Enterprise Routing Module (ERM) and Location Intelligence Module (LIM). It fixes:
  • In Internet Explorer 11, options on the Spatial Manager Settings tab were grayed out and unavailable. The Apply button, Restart button, and the Propagate checkbox are now enabled.

  • The geodetic coordinate system for Japan (JGD2000) was not accurately represented.

  • Using MI_GridValueAt and MI_GridValueAtPixel to query the value stored in a classified field generated an error. These Grid functions were returning the class name by doing an additional lookup in the classified table structure, and an error would result when the classified table structure did not have a “Class” field type. They now return the class index itself when the band stores class index. A second MI_GridValueAt and MI_GridValueAtPixel function can be used to specify the band containing the class label to get the class name.

  • When a MI_GridValueAt function was used to query a grid table and field=0 and band=0 was specified, the result was returning the data from the field and band present in the GHX file instead of field 0 and band 0.

  • The MappingService was re-initializing when the mapping configuration in the repository cache was refreshed. This could affect performance when loading many resources to the repository cache.

  • Spatial Manager was not reverting back to English or the default language selected in the Management Console when the browser was set to an unsupported language. It was showing internal variable names for the text. It now works as expected.

  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S27 This product update fixes:
  • Rendering BMP (Bitmap) raster data results in misplaced tiles (at raster edges). BMP raster images now tile correctly.

  • Performance using SHP files is slow due to a failure to create a spatial index.

  • Count aggregation query on Oracle native query table had poor performance with large tables. This performance issue has been resolved.

  • Spatial Manager does not have a volatile setting when creating tables with a Database query. It now has a Volatile flag that can be set to true or false, and the default value is set to true.

  • The feature count request made when viewing sample rows in Spatial Manager is slow for large tables. This performance issue has been resolved.

  • A "maximum open cursors exceeded" message displays when querying a database. This has been fixed so that queries do not leave a database cursor open (unclosed) when working with a database query table. This is a named table that contains a database-specific query rather than a reference to an existing database table or database view.

  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:

Screener Module

Update Number Description Download Software/Release Notes Bundles Download Release Notes Only
2018.2 S02 This product update fixes the issue where the List Ingestion Utility was not initializing on Spectrum™ Technology Platform version 2018.2. n/a
2018.2 S12 This product update enables interactive processing of batches of data. Windows software and Release Notes:

Spatial Analyst Application

Update Number Description Download Software/Release Notes Bundles Download Release Notes Only
2018.2 S01 Spectrum Spatial Analyst is a standalone application that installs and updates separately from the Spectrum Technology Platform.

This product update:

  • Lets you specify a friendly name for map layers so that after saving a map project users see the customized layer names.
  • Lets administrators add various routing options by manually editing the routing config XML.

See the Release Notes for a complete list of fixes.

2018.2 S02 Spectrum Spatial Analyst is a standalone application that installs and updates separately from the Spectrum Technology Platform.

This product update gives Extensibility Developers a new Spectrum Spatial Analyst API action called RemoveLegendByNameAction to delete a legend entry for a layer that was dynamically added using the Spectrum Spatial Analyst extensibility.

This product update fixes:
  • Thematic and Query options are visible when unavailable.
  • Legends created using Spectrum Spatial Analyst extensibility cannot be deleted.
  • Template Designer shows duplicate table entries when creating a custom template.
  • Administrators can now manually update the ˂˂print_template.xml˃˃ file to control the callout and FMN results from showing up in the printed PDF documents. This can be done by setting the following flags to false:
    • ˂show-callout-info˃false˂show-callout-info˃
    • ˂show-fmn-results˃false˂show-fmn-results˃

    Note: If you save this print template from Admin Console, these changes will be overwritten.

2018.2 S03 Spectrum Spatial Analyst is a standalone application that installs and updates separately from the Spectrum Technology Platform.

This product update fixes:

  • When creating components for Spectrum Spatial Analyst using extensibility it is now possible to reference and load external JavaScript libraries in cases where Analyst is accessed securely. Previously these would only work if accessing Analyst as a guest user.

  • The performance of the project settings dialog has been improved. Previously for very large projects comprising 100 to 300 layers the project settings would take time to populate and be sluggish to use. This has been fixed and now the page loads quickly and is responsive.

  • We have added the version number of Spectrum Spatial Analyst into the help side panel on the SSA home page. Admins can use this to determine the exact patched version of Spectrum Spatial Analyst.

    Note: The main Spectrum version is still available from the Spectrum landing page under System Information.

  • When creating components for Spectrum Spatial Analyst using extensibility it is now possible to set the visibility of annotations added in extensibility code to be initially hidden.

  • You can now add custom fonts to the customer configurations directory and reference them when creating components for SSA using extensibility. The supported font extensions are .ttf, .woff, and .woff2.

  • When setting the units in a Spectrum Spatial Analyst project between imperial (miles) and metric (meters/kilometres) on the project settings page, the settings did not always apply in all places where measurement units are shown. Previously for example Spectrum Spatial Analyst would show yards as the default unit if imperial was set. Measurements are now shown by default in either miles or feet (if under 1 mile) or kilometres and meters (if under 1 kilometre). Users can still change between all of the supported units.

  • When creating components for Spectrum Spatial Analyst using extensibility it is now possible to get table and layer level information at both group and individual record level for map information. This is available as part of the context data in the call out container. This information can be used for customizing existing map information behaviour.

2018.2 S04 Spectrum Spatial Analyst is a standalone application that installs and updates separately from the Spectrum Technology Platform.

This product update fixes:

  • Previously, an admin query was only visible to the user if it had been configured on the first layer of the named map. This has been fixed now.

  • Previously, users were unable to set the center of map when using the URL XY parameters for EPSG 27700. This has been fixed now.

  • In the Address Search box, clicking on "Enter coordinates" now defaults to “Longitude-Latitude” coordinates if the map projection is either EPSG:3857 or EPSG:4326 and to “X-Y” for any other map projection. Previously, it always defaulted to “Longitude-Latitude” for any map projection.

  • For map projects migrated from version 12.2, Map Information was shown as "enabled" in Project Settings whereas it had previously been "disabled". This has been fixed now.

  • Previously, a named map was always shown unchecked on the legend and its visibility is also turned off when user saved a map project that was migrated from the 12.2 SSA release. This has been fixed now.

  • Previously, when using map information in an annotation, incorrect results were returned. This has been fixed now.

    This was happening because in SSA we were converting the geometry to EPSG:4326 before sending it to Spectrum. This conversion resulted in a minor offset of the annotation in the case of EPSG:27700 and EPSG:29902 relative to the layer being searched.

  • Previously, the global copyright statement was not displayed for Spectrum Spatial Tiles when used as a base map. This has been fixed now.

  • Previously, admin created queries assigned in a project against a named layer did not show up in Spectrum Spatial Analyst. This has been fixed now.

  • Previously, the ViaEuropa tile layer was not being displayed beyond zoom levels 16 and was showing a watermark. This has been fixed now.

Universal Addressing Module

Update Number Description Download Software/Release Notes Bundles Download Release Notes Only
2018.2 S08 This product update fixes an issue where users were unable to configure UAM International database on Spectrum Technology Platform 2018.2 windows server. Windows software and Release Notes:
2018.2 S09 This product update fixes the issue where the Validate Address stage of UAM module throws a pb.service.options.optionNotFound error in Management Console while saving any changes after upgrading from 11.1 S39 to 2018.2 version.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:
2018.2 S16 This product update adds a tr​ansaction tracker for Universal Addressing Module Loqate, which lets you record the number of valid records processed.
  • Linux/Unix software and Release Notes:
  • Windows software and Release Notes:

Visual Insights Module

Update Number Description Download
2018.2 S03 This product update releases SVI installer with enhanced security.