Page Comparison

...

• Databrowser height wasn't being overridden when height was altered.

• Databrowser resizes no longer pin the databrowser in iShareGIS.

• Fixed a memory leak with the Map Categories panel

• Fix for issue caused by IE8 caching image dimensions.
• The CSV and Excel export now works when there are multiple tables supplied

• OGC thematic layers now use the correct styling for the ranges

• Printing now uses filter(s) set for OGC layers on the map.

• The address search loading icon is no longer covered by the Go button
• The find nearest results are now cleared when you click on the Reset Layers button

• The green location arrows are now removed when the layers are reset

• The layer catalogue is now cleaning up after itself properly

• The layer catalogue no longer slows down after pressing the reset layers button

• There was duplication of code calls and web requests, getting rid of these, along with introducing of caching of legend images and loading legends after layers has sped things up a lot.

• Using find nearest on OGC layers with filters now returns only points that match the filter

• When used in an ADFS environment, the user group claims were appended to the "user@domain" string used in the iShareGIS front-end.
• iShareGIS, SoloMaps and LiteMaps as well as independent use of iShare web services should now use the workspace specified in the Application Pool name.
• Improved logging for ADFS
• Adding layers from Layer Catalogue or via other plugins should not now result in 'loading' image not being replaced by legend graphic.

Studio

• An Internal DataSource could not be created without using the "Construct" dialog. An Internal DataSource must be given a name but previously the Name field was disabled until after using the Construct dialog. The name field is now always enabled.

• Corrected "Depends on previous job" to "Depends on previous task" in Task list for Workflow Job.

• Fixed an issue where Studio would report a "502 Bad gateway" error while trying to contact

...

• MapServer

• Fixed an issue where Map Editor would raise an error if a path was wrapped in apostrophes rather than quotes

• Fixed the check to make sure that a Map Source doesn't already exist when the user tries to import a new one

• OGC and thematic layers now save the Find Nearest information correctly
• Reduced the scope for Studio Workflow to wipe stored procedure argument values.
• Resolved an issue where Studio would raise an exception about invalid characters in a map file
• Some Astun SQL functions were not communicating errors to Workflow so it would assume that they had worked successfully.
• Studio Workflow now tries to work out which one of identically named stored procedures is to be used.
• Studio now calls atversion.aspx successfully when the external site requires authentication
• Studio now no longer truncates map file layer names with spaces or special characters in them
• Studio now saves the startup values correctly when they are set to zero.
• Studio will now no longer raise an exception when you try to create a scheduled task, but ask if you have permissions to the tasks directory

Studio will now retry refreshing the external server using the user's credentials if the external server requires authentication

The SLD editor will now accept symbolizers tags that start with "ogc:"

The mapsource will no longer become corrupted after moving a layer up or down and then saving

• The Create New Mapsource functionality error messages have been improved, and the

...

• save dialog is now

...

• more intelligent on where it first opens

• The Import Existing Mapsource functionality and error messages have been improved, and the

...

• open dialog

...

• now

...

• opens in the correct directory

• The OGC layer link field names are no longer being truncated

• The OGC thematic point colour will now load correctly

• The SLD editor will now accept symbolizers tags that start with "ogc:"

• The available field list will now stay in the correct order after changing them and saving the layer

• The geometry column is no longer "forgotten" by the OGC layer after it is saved

  
  

  
  

OGC issues

OGC layers My Nearest now will return the correct nearest points

Resolved an issue where OGC layers would occasionally be rendered as either red dots or red polygons depending on the layer type. There appears to be a bug in Mapserver 6.2.0 which stops this working so we advise avoiding that version.

The OGC thematic point colour will now load correctly

The hyperlink field no longer needs to be in the field list for the hyperlinks to work

...

In situations where the same {{layerName}} had somehow been configured for more than one layer, each of those layers was written into the generated .map file a number of times equal to the number of duplicate layer names.

...