Browser support

This version of iShare officially supports Internet Explorer 11, Microsoft Edge, Chrome, and Firefox.

Pre-requisites

This release of iShare requires the following to be installed:

• Windows Server 2012 R2, 2012, 2008 R2 or 2008
• Internet Information Services (IIS) Versions 8.5, 8.0, 7.5 or 7.0
• Microsoft .NET Framework V3.5 Service Pack 1 (installed and enabled)

Installers

• Corrected the default My Alerts DSN parameters.
• Astun 3rd Party Installer now installs the SUDS library when you install Python - required for Python to communicate with SOAP Web Services.

iShare GIS

• New Web Processing Service (WPS) added to iShare GIS. This is used by the new Feature Builder plugin and is configured under the External Services iShare Settings.
• In the Feature Editor:
  • the Create Feature and Select Feature buttons are now Create and Modify respectively.
  • when editing a polygon feature, the map will always continue to create polygons after the initial creation/selection of a geometry. This is a change from previous versions where it would continue to select features when in 'Modify' mode.

  • when adding or editing a polygon layer, iShareGIS is now able to make use of a WPS Union Process to merge overlapping polygons in a feature. This requires that a WPS server is setup in External Services and has a geo:union Process available. No other configuration is needed.

  • there is a new Feature Builder plugin to allow you to create polygons based on the underlying OS MasterMap data.
  • Feature editing no longer loses edits to the feature when saving of feature fails.
  • The Modify button is now activated after choosing a feature from a list of those that overlap at a selected point.
• New HiDPI Printing function. 
  • If templates are present in the WebApps\WebService\custom\print\templates then they will be used by the new HiDPI print plugin instead of the default Print Templates supplied by Astun (found in the WebApps\WebService\print\templates folder). See Creating your own HiDPI Print Template for details.
• iShare GIS will no longer show an exception if the Metadata server returns an error.
• Classic Layers now will correctly show the extents of features when you hover over them in the Information Browser.
• Switching BaseMaps will now no longer remove drawn geometries from the map (e.g. when using Annotations or Feature Editing).
• Fix for issue where the attribute panel would remain blank if layer description request hadn't completed by the time a feature had been created. It will now show a 'loading' spinner and fill in the panel once the request has finished.
• Improve detection of map selections on mobile devices (especially Samsung).

• Info-clicks now return fields with spaces in their name correctly.

• Fixed a Feature Server configuration file issue regarding the schema not being set correctly.

iShare Studio

• There is a new DeleteFiles script which can be used through a Workflow Program Task to clear out directories that can fill up with temporary files over time. 
• Fast-clicking between Layers in the tree view should no longer cause Layers to be overwritten.
• Correctly disable all the My Alerts Field Settings on Classic Layers if My Alerts is not enabled.
• Correctly set type of Layer's SQL after editing data definition.
• Changing the display name of a Datasource field should no longer cause the layer to stop working in My House.
• Removed the Save button from the Map Source save dialog (that appears if you change any Map Source Options and close Studio without saving your changes) as there is a Save All button that does the job.
• Can no longer create Workflow Tasks with duplicate names.
• Removed the MULTILINE option from Force Geometry in the Spatial Data Transformation Workflow.
• Studio now should no longer throw an unhandled exception if the Data Share database connection string is in the wrong format.
• New Info click movement ignore entry in the Master Settings under the Web section to control the number of pixels of movement allowed when clicking before Info-clicks are disabled. This is primarily used for mobile devices and too low a value can make it very difficult to perform info-clicks.
• The SLD Style Editor:
  • should no longer include commented-out includes in the map file.
  • now caches and uses symbols which are situated directly in the map file.
  • now handles multi-geometries correctly.
  • is now being correctly updated on first load and after the Advanced editor is changed.
  • should no longer incorrectly switch the order of the symbolizers.

iShare Core

• iShare now handles large Metadata record sets correctly.
• The VIEWPARAMS parameter for GetOWS requests has added new capabilities (and altered the way it works).

iShare Maps

• The Map Categories panel should no longer obstruct the Address Search when going back from the last page of results.
• Saving a Layer with an unknown Geometry Type should no longer cause all layers in the Map Source to stop working.
• Improve detection of map selections on mobile devices (especially Samsung).
• Ensure the Clear search, Previous & Next buttons remain in the same place on the Search Results to prevent clicking Clear search by mistake.
• The generic alert title and OK button text are now correctly drawn from the languages file

My House / My Nearest

• My House will no longer fail to render dynamic panels if a Layer does not have a Display Name set.
• iShare Maps tabs not having a Display Name will now render correctly.
• The My Nearest Layer Custom Output Footer text now appears in the correct location.
• The My Nearest Layer Group Headers and Footers no longer show when the panel is collapsed.
• Accessibility improved in several places.
• The My Nearest Layer Groups are now keyboard navigable.

My Alerts

• The My Alerts Console will now attempt to convert the Fields XML depending on the URL type.

Web Services

• Option to enable the new HiDPI printing to avoid having to give iShare Web Service higher permissions for printing under Windows 2012 or above. See Enabling the HiDPI Print Plugin for iShare GIS for details.
• Specifying a PropertyName parameter on a GetFeature request no longer causes an error if the field(s) listed are not the first in the field list.