Spectrum Spatial and Routing

This section lists fixes for Spectrum Spatial, routing, and Spectrum Spatial Analyst.

(SSS-8404) MI_GridValueAt was not returning the result for some field and band combinations. This was happening for a Multi-Resolution Raster (MRR) with multiple fields and bands where each field had different extents.
(SSS-8581) The describe Named layer response would not honor list elements like showBackground, applyColor, and displayAtActualSize when used in Mapping requests.
(SSS-9558) When the Named Project contained a databind and Access Control List (ACL) permissions were assigned to the Named Project, the permissions did not propagate to tables referenced in the Named Databinds.
(SSS-9709) When a Named Project included a circular reference and permission was assigned to a resource, it would fail when fetching the reference. A circular reference is when a project has a reference to another project as parent and that project has a reference to the first project as parent.
(SSS-10302) The message, "WARN [SpatialSecurityManager] No roles found for system" was repeating in the spectrum-server.log file.

Spectrum Spatial Manager

(SSS-530) WMTS tiles did not generate when there is a Minimum Bounding Rectangle (MBR) defined within the Tile Bounds.
(SSS-5321) On the Create Tile page, the bounds values did not update for the Custom Tile Bounds radio option after changing the Coordinate system.
(SSS-5849) Spectrum Spatial Manager did not re-order reference Layers on the WMS Layers page.
(SSS-6673) After moving a TAB file to a new location in Windows Explorer, Spatial Manager would display a server error when updating the new TAB file path in the Named Table where it was used.

When there were multiple threads simultaneously creating persistent updates, the routing engine would return exceptions. Now exceptions are not returned when creating updates.
When anyone besides an administrator would access the routing examples on the Routing Services tab of the Spectrum Spatial home page (http://<server>:<port>/dcg/#spatial), an error would display. With this release of Spectrum Spatial, users who are not an administrator (admin) can now use their credentials to view the routing examples on the Routing Services tab.
The Japanese Spectrum Management Console did not list datasets when switching between driving and pedestrian filters.
The Travel Boundary stage would return an exception when opening this stage because the decimal operator was as comma (",") for numeric values for locales such as French, Spanish, German, and Japanese.

(SSS-5631) Point symbols were not round when the display size was less than 7 pixels and border is enabled.
(SSS-6675) Rendering the label source using an in-line label layer did not honor translucency.
(SSS-6677) Map failed to render when it had labels and the label expression used new line characters like Char 13 or Char 10.
(SSS-9041) The bottom portion of point symbols were not rendered when the display size was less than 7 and border was enabled.

(SSS-8700) Map Uploader would only accept a lower case user name when logging in.
You can now log into Map Uploader using a mixed case user name.

(MID-48396) Using seamless TAB files with Point in Grid on Linux now has better performance.
Using an uppercase .TAB file extension affects performance on Linux. Spectrum Spatial now checks for upper or lower case file extensions.
(MID-47439 | SSS-1137) A SQL pagination query now has better performance.

(SSS-6378) A Unable to parse Json, may be invalid or incorrect structure error message would display when using the GridStyle in a REST request.
(SSS-6579) The border was missing for polygons with border pen pattern 0 (zero) in the legend.

(SSS-5206) Spectrum Spatial documentation: "The default setting for volatility is true for all named tables." This statement is not true for named tables created via MapUploader.