GVH 2.6 to 2.7 viewer upgrade cooridnateSystem / customCoordinateSystems issue

Tyson Schoepflin

28. September 2016 17:06

Our 2.6 viewer uses some custom coordinates.  These are defined in the Coordinates module under the CoordinatesViewModel.

 

Coordinates Module > CoordinatesViewModel > coordinateSystems

 

The 2.7 viewer appears to use a different location for custom coordinates.  2.7 uses the Map module and MapCoordinatesModel.  They are defined in customCoordinateSystem.

 

Map Module > MapCoordinatesModel > customCoordinateSystems

 

Our 2.7 template works fine if you add it as a new viewer.  However, when upgrading a viewer from 2.6 to 2.7 the upgrade process does pull over customCoordinateSystems in the viewer config file.

 

Is this something we will have to change manually for all our viewers after updating them?

0

• 

  Tyson Schoepflin

  28. September 2016 17:07

  My kingdom for an edit button.

   

  "the upgrade process does NOT pull over"

  0
• 

  Permanently deleted user

  28. September 2016 20:16

  Hi Tyson -

   

  First some explanatory background.  The configuration change that you mention in your post was actually made between GVH 2.5 and GVH 2.6.  I reviewed the upgrader that we use to allow users to upgrade between these two versions.  That upgrader was coded to respect user changes to the Coordinates Module > CoordinatesViewModel > coordinateSystems property and to port those changes to Map Module > MapCoordinatesModel > customCoordinateSystems.  So when a user upgrades from 2.5 to 2.6, these changes should happen automatically.  They should also happen automatically if a user upgrades from 2.5 to 2.7.  Here, the upgrader from 2.5 to 2.6 would be applied first and the upgrader from 2.6 to 2.7 would be applied subsequently.

   

  It appears that your situation is a little bit different.  It appears that your configuration for GVH 2.5 was transferred directly to GVH 2.6 without any changes to the relevant configuration.  That is, your configuration files for GVH 2.6 include the coordinateSystems information in the Coordinates module rather than in the Map module.  Assuming that to be true, the upgrader from 2.6 to 2.7 does not include the rule that would move this configuration to the proper module.  That rule is found in the upgrader fro 2.5 to 2.6, which appears not to have been applied.

   

  Here are the practical implications for your sites:

  • If you have any remaining 2.5 sites and you upgrade them to 2.7, the coordinate systems should be ported to the Map module; and
  • If you have any remaining 2.6 sites, you should first check their configuration.  If the coordinate systems configuration is located in the Coordinates module, the upgrader will not move it to the Map module.  Therefore, you will have to manually change these sites following the upgrade. 

  I hope that helps, and I hope you don't have too many sites to manually upgrade.  If my assumptions were incorrect or you need more assistance, please let me know.

  0
• 

  Tyson Schoepflin

  29. September 2016 16:09

  Thanks for the reply and great detail!

  0
• 

  Permanently deleted user

  29. September 2016 16:27

  No problem - hope it helps you resolve your issues!

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.