Thursday, September 30, 2021

GTViewer for iOS/Android Update

 


GTViewer for iOS (version 5.47.6) and GTViewer for Android (version 5.32) have several new features:

  • The Data Collection functionality now supports customizable symbology for its markers.    Previously, the only markers were an Arrowhead, Circle, or Square.  You can now specify a Symbol of your choosing as well as its size, color, and justification using the Data Collection State Definitions.   
  • The Data Collection State Definitions have been expanded to allow a different set of definitions per Data Collection form.  You can still use a default set of state definitions for all forms that do not have a specific set defined.
  • The ability to associate Data Collection information with Session Graphics (redlines) is now available.  The original Data Collection functionality uses its own point (selected by the user or derived from a selected Feature) to position a dynamic marker on the map.  The new Session Graphics Data Collection uses a redline as the marker and provides two new workflow options for capturing data:
    1. Attach a Data Collection record to an existing redline (using the same style of forms used with the original Data Collection to enter the information).

    2. Start from a feature in the map and fill in the data collection form. A new redline copy of the selected feature is generated with the captured data attached.  The redline can be moved and edited just like any other redline.


Session Graphics Data Collection Example:

- Draw any Redline (freehand circle below):




- Select the Redline:


- Press the Data Collection button to activate the Data Collection form.  Forms can be associated with one or more redlines types (line, shape, circle, text, dimension, leader line, symbol, or a specific symbol). You can also have more than one form to choose from.



- Once the collected data is saved, the Data Collection State rules apply to the redline for Color and style.  It can be synced with the GTViewer Data Server, and reviewed like any other feature:


Wednesday, September 29, 2021

GTWeb for iOS is 10 Years Old!

    



GTWeb for iOS was released in September 2011, a few months after GTWeb for Android.  So GTI's first products on iOS and Android are both 10 years.

GTWeb has changed more than any other GTI product over its lifetime. The rapidly evolving nature of the internet (since the early 2000s) has driven GTWeb to reinvent itself several times.  Starting with an ActiveX client (closely related to GTVx), the GTWeb Server cut out elements for the user's view and let the client do all the rendering. When ActiveX controls were no longer allowed in browsers, the Server rendered raster tiles for the client to display in an HTML wrapper.  Then the rise of Apple and Android made Apps the way to provide the best client experience on phones and tablets. Ten years later, this is still true.   

In memoriam, GTWeb for BlackBerry and GTWeb for Windows Phone were discontinued when their platforms ceased to exist.

Tuesday, September 28, 2021

GTStyleDiff Utility added to GTData

A new utility called GTStyleDiff has been added to GTData.  

This new tool allows you to take a Style Definition File (style.def), compare it to another Style Definition File, and then produce a list of styles added and any property changes made to existing styles.  This list of changes is usually saved in a file called style_update.def and is used with the GTStyleMgr tool to integrate any custom changes into a style.def.

Why is something like this needed?  The GTech Loader produces a fresh set of styles from the database for each export. If you kept track of all custom changes to the Style.def and maintained your own style_update.def file, then GTStyleDiff may not be of use to you.  If you use the Style Manager in GTViewer to interactively set the styles like you want and then export a new style.def, then it becomes tricky knowing what changed.  That is there the GTStyleDiff tool comes in handy.   It can create the style_update.def file for you and can be automatically applied to the style.def created by the GTech Loader exporter each time.