ViSit Anywhere Development

Development news and release notes

ViSit Anywhere 18.2.9 Release Notes

Dashed Lines Rendering

In some specific configurations, the rendering of dashed lines in managed data was disabled.

Replace Association

So far, dropping an external row on a spatial asset was rejected for any external row already associated to a spatial asset. With this version, the application proposes to replace the existing association when it exists.

Upload Archive

Large archives are uploaded to the collaboration server in smaller pieces. These smaller files were not cleaned from the archive directory once the transfer has completed. This is now corrected.

 Add Hole

In the version, we have enhanced the Add Hole tool.It is now more robust, and accepts complex polygons as holes.

Polygon Tools

In this version, we have added in the Vigis.Kernel program an additional tool provider named 'Polygon Tools'. It currently proposes two new tools :

  • Merge : Merge two polygons ; the second polygon is deleted.
  • Split : Split a polygon into multiple parts.

Import Geometry for Network

In this version we have Added 2 graphic tools in the NETWORK ribbon page of ViSit Anywhere. They allow you to create network equipment and service pipes with a geometry imported from another site (even a static one). 

Attributes from DWG files

With this version, ViSit Anywhere GT is aware of block attributes and XData present in static CAD files. The attributes (name and value) are displayed in the tooltip of the supporting graphic element. The geometry import tools transfer these attributes values to the target table, trying to match the attribute name with the external name of the target columns.

Job Complete Message Id

When a web job is executed in the Maps application (web), the Maps SignalR hub sends a request to VQS.  VQS forwards the request to VAX.  When VAX completes, the message is returned to VQS who sends a Job Complete message to the Maps hub.  There was an error where the VQS processor created the job complete message using the Id of the response message rather than that of the request.  The Maps hub uses this id to correlate requests and the mismatched id's meant that auditing of web actions (like PDF plots) was impossible.  This problem has been corrected.

Comments are closed