Location Intelligence Module

  • (MID-37038 / SCS-5206) Spectrum™ Technology Platform servers became unresponsive when too many open files existed after repeated dataflow failures. This issue has been fixed.
  • (MID-36666) MRR files created using MapInfo Pro 16 do not work with Spectrum Spatial version 11.0 SP1. This has been fixed in this update.
  • (MID-36571) When adding a Centrus database resource in Management Console, you were limited to selecting a .gsb file as the data source. This has been changed in this update to also allow .txb files.
  • (MID-35727) When running very large batch tile jobs for MRR files, a memory leak was occurring. Memory use has now been optimized.
  • (MID-35368) Following the release of the 11.1 S12 patch an error would occur describing layers with the REST API when an "All others" bin did not exist for an individual value thematic layer. This error also affected Spectrum Spatial Analyst v8 customers using the mobile interface, causing map rendering to fail. This issue has been fixed.
  • (MID-34291) Because the Gen 4 MrSID files in multispectral color space were not supported in Spectrum Spatial, an Unknown MrSID ColorSpace error for Generation 4 MrSID raster images was occurring in Render Named Map requests and when using Spatial Manager. This issue has been fixed by converting the MrSID file in the multispectral color space to an RGBA image, similar to MapInfo Pro's raster handling. This conversion occurs at runtime and not on disk. As a result of this fix, Spectrum Spatial now supports all MrSID files, including those in multispectral color spaces.
  • (MID-34264) Sparse styles were not supported for label themes and override modifiers. The modifier had to repeat every setting from the base style for the modifier to be applied. This has now been fixed so that the modifier only has to apply the needed changes.
  • (MID-34091) A NullPointerException was occurring when rendering a named map with an individual value label theme. A named map with this type of theme now renders without an exception.
  • (MID-34014) A LabelOverrideTheme expression specified in the label source XML was not being used when the layer was rendered; instead, the base label expression was used. This has been fixed and the override expression is now applied.
  • (MID-33562) When rendering zoomed MRR tiles, rectangle pixels are sometimes rendered instead of square pixels. This is now fixed, and the rendering quality of MRR tiles has been improved.
  • (MID-33310) The MaxDistance parameter is ignored when set to zero in the Legacy Find Nearest stage and reverts to the default maximum distance. This is now fixed, and returns the desired candidates when the MaxDistance parameter is set to zero.
  • (MID-33208 / SSP-305) When two joining tables have missing join records, prior to rendering a line linkage using the Mapping service, the resulting map returns a ServiceRunTime Error. This is now fixed, and if records are not linked between the two join tables, these records are ignored.
  • (MID-32777) If you described a map or layer with labels using the SOAP Mapping Service, the returned response did not include the expression used for the label string. This resulted in an error if the describe response was then used in a map request, because there was no expression for the label string. The describe methods now include the label string expression and map requests using those responses now work correctly.
  • (MID-32633 / SCS-4395) An "unknown grid cell type" error was occurring when using a .grd file with the MI_GridValueAt function. Support has now been added for querying a cell value on high-precision Northwood Numeric Grid (.grd) files. High-precision .grd files are those which have uint32 cell data.
  • (MID-32595) The WFS GetFeature operation for multiple feature types returns the bounds of the first feature type only. This issue has been fixed in this release and the bounds for all feature types are now returned.
  • (MID-32235) When using the Map Tiling Service, a rendered image was shifted one pixel when zoomed in. This issue has been fixed in this release.
  • (MID-32099) The WFS GetFeature operation did not work against a table that contains a geometry type of GeometryCollection. This has been fixed in this release.
  • (EGMI-2321) A Geometry object from the Global Geocoding Module that was passed into Spatial Calculator in the Location Intelligence Module could not be cast as an IGeometry object and threw an exception. This has been resolved.