2018.2.0 Updates

Server error

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

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.

• 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.

• 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.

• Change persistence layer to always check indexes and recreate indexes if not found.
• Improve the process that Spectrum follows to shut down Neo4j.

• 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

• A job located under the Job folder moves to the root folder unexpectedly.
• The jobexecutor -w option does not work as expected when running multiple (10 or more) concurrent jobs.
• The account ID needs to be exposed in the Transformer stage.
• Settings for string conversion format defaults were lost after restarting the server.
• Previously exposed multi-level Spectrum parent services do not return updated results when a child subflow is updated and exposed.
• Previously exposed Spectrum parent services do not return updated results when a child subflow is updated and exposed.
• Spectrum is returning a java.lang.NullPointerException: null INFO | jvm 1 | datetime| at com.pb.spectrum.platform.server.common. audit.core.aspect.AuditAspect.evaluateExpression
• Processing returned a null pointer exception during a scheduled purge task. The Spectrum 2018.2 remote server is not connecting.

• Fixed incorrect next run date in scheduled flow.
• Fixed issue that job for checking the certificate expiration does not use the encrypted password.
• Fixed issue that Spectrum performance degraded over time.

User can create a service in Spectrum Enterprise Designer which has a Lookup Key field for searching the PBKEY in data.

• This Lookup Key field can now named as any valid string, which was earlier named as "lookupKey" only.
• Now user can search the PBKEY in Spectrum Management Console with the same name as configured in service.
• Message for PBKEY not available in data is now logged as info instead of error in the Spectrum wrapper log file.
• The error messaging is improved for the Geoenrichment service.

This patch updates the deprecated Geocoding service for Data Hub Visualization.​ The service is updated to use the Map Tile Layer on Precisely servers.

This product update resolves the following issues:

• Fixes TrasientTransactionFailureException error when running multiple query/write stages in parallel.
• Fixes TrasientTransactionFailureException error when while performing a HUB model backup.
• Fixes a ConstraintViolationException error.
• Fixes various transaction termination errors in a cluster.

This product update fixes issues with locks in the Delete from Model stage, adds retry logic to Merge Entities and Split Entity stages, and fixes update issues in the Write to Model stage.

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.

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

• 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.

This optional EGM-USA update provides access to MLD Extended Attributes such as Assessor's Parcel Number (APN), Elevation, Address Type, and many more output fields.

SHA-256 hashes (What's this?)

cdq20182s31_Linux_Unix.zip:
213F550D5A0F0108E54F2A11A61A29BF194408AE5F621E311999794275176D79
cdq20182s31_Windows.zip:
176D222DC994B79BAF2A24010B5BFDCD58BE72CC207518D2661D03927FEFB627

This product update provides access to new fields in Master Location Data (MLD) Extended Attributes.

SHA-256 hashes (What's this?)

cdq20182s50_Linux.zip:
3E52CCFFBE85E9A8AF2A20800A7CD2E4680373FB813C70C8CC9981B173982B57
cdq20182s50_Windows.zip:
BF131193BFBB109EAAA936D7DE2C7DD0518D5CB0771BC444A850E35E7BE87A27

This patch fixes Java Runtime Environment fatal error when accessing MLD Extended Attribute data.

SHA-256 hashes (What's this?)

cdq20182s52_Linux.zip:
27FCC03EAF342DAB49A749ABC092D699BF0E5D42D8F4DF92848F7E7519CD3105
cdq20182s52_Windows.zip:
763E568B5CCCCA39118EDCFD2840E31BF214F63311333C82075B238C4DA7C15C

• 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.

• 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.

This product update includes the following:

• While replacing an old H2DB data with a new one or on creating a new Spectrum database using the latest H2DB data, the product expiration information was not getting updated, as the internal cache memory within the module is not getting refreshed.
• This patch will resolve the issue by refreshing the cache and completely deregistering the previous database.

• While updating the H2DB data using the same Spectrum resource connection, a Spectrum restart was required to put the new data into effect.
• With this patch, a Spectrum restart will not be necessary for Database Resource update.

• Global Addressing Module support for distribution of dynamic libraries
• Support for the Global Addressing Module Q1 2019 Data Refresh

SHA-256 hashes (What's this?)

cdq20182s18_Linux_Unix.zip:
51D572C7B24864A07A145205B2D07AE75997C4FECDF56F7838AED59E7BBAD9C2
cdq20182s18_Windows.zip:
420E82C63787DF16663C3149005E622B49299D1F46EBAE6229741A5896B07F68

• 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

• 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 prefixing 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 prefixed 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.

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 (that is, the database table is in a projection such as EPSG 4326 with longitude and latitude co-ordinates).

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.

• 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.

• 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.

This software update addresses the Spectrum 2018.2 Java client jar integration issues.

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.

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:

• 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.

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.

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

• 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".

• 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.

• Previously, when using map information in an annotation, incorrect results were returned.

  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.

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

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

This product updates:

• Exporting data in CSV format with semicolon (";") as a field separator, and comma (",") as a decimal separator in French OS.
• A Spectrum Spatial Analyst user can now configure a multi-select feature count to customize a number of features selected on the map using multi-select functionality.
• The Spectrum Spatial Analyst API now includes parameter validation to ensure that it cannot be used to read files outside of the configuration directory. The file name validation ensures that only alphanumeric, dash ("-") and underscore ("_") characters are allowed in filenames for search nearest and print template-icon names.
• The line feature now highlights on the map using the multi-select tool when fill-opacity is set to "0" for the multi-select class in the corresponding brand.css.

This product updates:

• The HTTP session ID for a guest user, which was reused when they logged into Spectrum Spatial Analyst after browsing to the application as a guest. Now, the existing HTTP session is destroyed when the user is successfully authenticated, and a new session ID is created. This fixes a potential security vulnerability.
• The Spectrum Spatial Analyst usage logs. The user's IP address will now use the IP address present in the "X-Forwarded-For" header if that header is included in requests. This is useful in cases where a proxy server sits between the user and Spectrum Spatial Analyst, for example, in a DMZ.

• Good addresses failing validation due to incomplete reference data.

• Validate Mailing Address Premium multi-match returned where V4 is achievable (France).

SHA-256 hashes (What's this?)

cdq20182s46_Linux.zip:
3F74757EB9449AAA8A6F66A11E0DC1A13593327A81F66DC24748D0DEEE419AE8
cdq20182s46_Windows.zip:
9EDBC43626E565A429FE072C0379C4ED7F0E69F27C842862E9E79BACCFFEBDEF

SHA-256 hashes (What's this?)

cdq20182s51_Linux_Unix.zip:
9F55058A912A08332C0DECF32E587BE53A43D5609BFB3DD5CFB13B24517DCDFF
cdq20182s51_Windows.zip:
104D065F1A47B79FBE59F73985BA58211DCFA0C1E61EFEEDA59B0C056D718B94
              

SHA-256 hashes (What's this?)

cdq20182o20_Linux.zip
0C3688562C971D9846D74C34BFEADCE418611F146D7ABD6553D04E2134100D6E