Trimble
PDF Export RSS - Latest News


QuadriDCM 1.3

Released: 10.08.2015

NB: To run QuadriDCM 1.3, you need Novapoint version 19.3x or newer.

Version 1.3

Support for Windows Server 2012 R2

New installation of QuadriDCM can now be done on computers running Windows Server 2012 R2. This version does not support an upgrade of the OS from Windows Server 2008 R2 to Windows Server 2012 R2.

Novapoint QuadriDCM Client

The URI used to access a QuadriDCM has been complemented with one new element. This new element is introduced to facilitate the use of reverse proxy solutions. In such solutions, multiple QuadriDCM installations will from the client side appears as located on the same host. This will also facilitate for several QuadriDCM installation of different version installed on one host. The value for this new element is selected during the installation process of QuadriDCM. Default value is ‘quadridcm’ In the Add QuadriDCM connetion dialogue where you in previous versions only wrote the address of QuadriDCM host you must now write the full URI to the QuadriDCM-application. To access a QuadriDCM installed with default values the correct URI is ‘IP-address/quadridcm/quadri’ For description of how to migrate existing connection documents and worksets see separate migration document.

Share/Receive/Reserve/Join a Project

FIXED: In some situations message boxes with essential information appeared behind the progress bar. From now on, no message boxes will hide behind the progress bar.

Receive/Join a Project

IMPROVED: As default the system now, fetch features of different feature types from the database in parallel. In general, this gives performance improvements of both Receive and Join a project. How significant this performance improvement is depends on the composition of the requested dataset. The span of the improvement is from twice as fast as earlier to no observable improvement at all.

IMPROVED: The streaming technology used in the communication between serve side and client side is improved. In general, this gives performance improvements for datasets that contains spatial attributes with many points. Receive and Join a project for dataset with large TIN or Solid will have a significant performance improvement.

Receive

IMPROVED: First technical step when doing receive is to store a local snapshot of the workset including its current state for internal metadata. For large worksets this may take a significant amount of time. In situations where there are no changes done after opening the workset this step is unnecessary, and will not be performed with this new version. Users may utilize this by adopting a method of daily work where they perform a Receive as the very first thing they do after opening a workset.

IMPROVED: Parts of the technical solution when doing Receive is improved so that changes in the shared model is received directly into the computers memory and not via the computers disk. As the application did not have a clue about what had changed on disk, compared to what was already in memory, the whole workset was re-read from disk every time a Receive was performed. In practice, this means that there are now a better and more directly, coherence between the amount of data received, and the time spent to perform the Receive function.

Reserve/Release

Similar improvements as for Receive.

Join a Project

NEW: The Swedish Mapping Cadastral and Land Registration Authority’s (Lantmäteriet) library GTRANS is now embedded. Thanks to this library, worksets may now be defined using most of the CRSes used in Sweden independently of the CRS selected for storage of the Shared Model.

IMPROVED: The embedded library from The Norwegian Mapping Authority’s (Kartverket) to convert from NN54 to/from NN2000 is updated to the newest available version (2015A). This new updated version covers:

  1. Østfold, all
  2. Akershus all
  3. Oslo, all
  4. Hedmark: Hamar, Ringsaker, Løten, Stange, Kongsvinger, Nord-Odal, Sør-Odal, Eidskog, Grue, Åsnes, Våler, Elverum, Os, Folldal, Alvdal, Tynset, Tolga and Rendalen
  5. Oppland, all
  6. Buskerud, all
  7. Vestfold, all
  8. Telemark: Skien, Porsgrunn, Bamble, Kragerø, Drangedal and Siljan
  9. Aust-Agder: Iveland, Birkenes and Lillesand
  10. Vest-Agder, all
  11. Rogaland, all
  12. Hordaland, all (However, only preliminary for Bergen)
  13. Sogn og Fjordane, all
  14. Møre og Romsdal: Sande, Vanylven, Volda, Ørsta, Stranda, Norddal, Stordal, Sykkylven, Ulstein, Hareid, Sula, Ålesund, Skodje, Ørskog, Vestnes, Sandøy
  15. Sør-Trøndelag, all
  16. Nord-Trøndelag, all

Some modifications for Vest-Agder, Hordaland, Sogn og Fjordane and Møre og Romsdal

IMPROVED: Worksets may now be defined using most of the CRSes used in France

  • RGF93/CC42 - EPSG 3942
  • RGF93/CC43 - EPSG 3943
  • RGF93/CC44 - EPSG 3944
  • RGF93/CC45 - EPSG 3945
  • RGF93/CC46 - EPSG 3946
  • RGF93/CC47 - EPSG 3947
  • RGF93/CC48 - EPSG 3948
  • RGF93/CC49 - EPSG 3949
  • RGF93/CC50 - EPSG 3950
  • RGF93/Lambert-93 - EPSG 2154

independently of the CRS selected for storage of the Shared Model.

Manage QuadriDCM Project

FIXED: An issue where an erroneous area of interest located fare from the actual location could crash the system due to an unhandled impossible transformation. In such situations, a deadlock appeared because of the erroneous area of interest, which could not be modified because the application crashed and so on. This is fixed so that the application does not crash and erroneous area of interest can be corrected.

IMPROVED: For shared models with reference to some of the CRS used in France, it was not possible to draw an area of interest for a project. All the most used CRS for France are now supported.

Quadri Model Manager

As previously mentioned the URI used to access a QuadriDCM has been complemented with one new element. The value for this new element is selected during the installation process of QuadriDCM. Default value is ‘quadridcm’

In addition to this, the name of the QMM-application may now be specified during the installation. The default value for QMM-application name is ‘qmmweb’ This new element and the possibility to specify QMM-application name is introduced to facilitate the use of reverse proxy solutions. In such solutions, multiple QuadriDCM installations will appear as located on the same host. This will also facilitate for future solutions where several QuadriDCM installation of different version can be installed on one host.

To access QMM on a QuadriDCM installed with default values the correct URL is ‘http://IP-address/quadridcm/qmmweb’ or ‘https://IP-address/quadridcm/qmmweb’ if configured to use SSL You must modify shortcuts and bookmarks to reflect this changed URL. Alternatively delete and create new ones.

QMM – Models – Modify Model – Feature Catalogue

NEW: When doing Feature Catalogue Upgrade you may now select multiple models. To upgrade a model with new Feature Catalogue is both memory and CPU intensive operations. If situations with many models to upgrade this should be done in bulks of 10-15 models to avoid overload of the server side.

IMPROVED: Robustness of Feature Catalogue upgrade is improved and if for any reason this operation fails there is now possible to repeat the operation. If upgrade Feature Catalogue fails go to Model Information Details, press Stop Update and then you will be able to repeat upgrade Feature Catalogue.

QMM – Models – Delete Model

IMPROVED: Robustness of this function is improved. In earlier versions, it was not possible to delete the model if the database connection to the model schema was in use.

QMM – Admin - Server properties

NEW: Some new monitoring information is added to this page. Status for hot database backup can be monitored. The list of QuadriDCMRequestHandler that actually perform the QuadriDCM activities on the server side can be monitored. From this page, it is now also possible recycle both application pools that QuadriDCM use, and to free up disk space there is possible to delete log files older than 30 days.

QMM – Admin – Model Parameters IMPROVED: For easier support and error detection, a few new switches are added among the model parameters. Default values for these switches are:

  • Clean up associations: false
  • Dump all commands / results as xml: false
  • Read features in parallel: true
  • Support coordinate operations: true
  • Trace level (0-15): 8
  • Use OCILIB: true

You should not change these values unless advised so by Vianova support.

Last modified: 2015/08/10 16:07 by vn_no_lst
CC Attribution-NoDerivs 3.0 Unported License.