Wednesday, December 27, 2006

GTVx Version 5.0.x.12 is Available



Version 5.0.x.12 of GTVx is available.

-----------------------
05.00.00.12 - 12/27/06
-----------------------
- FIX - The Export button on the Display Preset Dialog was always enabled even when no preset item was selected.


-----------------------
05.00.00.11 - 12/08/06
-----------------------

- FIX - QueryActivate and QueryPerform were not recognizing Query Type 13 as thematic query.



GTViewer version 5.0.x.27 is Available



Version 5.0.x.27 of GTViewer is available.

-----------------------
05.00.00.27 - 12/27/06
-----------------------
- CHG - Change to the NMEA GPS reader to better support virtual COM ports or GPS sharing devices.


- FIX - The Export button on the Display Preset Dialog was always enabled even when no preset item was selected.



Friday, December 01, 2006

GTViewer version 5.0.x.26 is Available



Version 5.0.x.26 of GTViewer is available.

-----------------------
05.00.00.26 - 11/30/06
-----------------------

- FIX - Export as Dgn was not setting the origin correctly in orphan cell headers which caused all grouped elements from the GTViewer data to scale and rotate incorrectly in Microstation.

- NEW - Export as Dgn will now export Extended Style Information as UDLS tags on the dgn elements.

- FIX - Fixes to the Style Manager's Import Map and Def funtionality.

- NEW - ExternalStyleMapFile and ExternalStyleDefinition entries can be added to the addprop.ini file or the Additional Properties section of the .GTM. If defined, these entries will import the specified .map or .def files.

- FIX - Text Elements with embedded data would lose the embedded data if edited with the Element Properties dialog.

- FIX - Reading an element would partially reset a DrawSetData. It will now fully reset the information.

- FIX - Right Mouse Menu would not activate when in Draw Dimension or Leader line modes.

- FIX - Updates to Magnify Window to provide a smoother appearance when scrolling, especially with dark or black backgrounds.


GTVx version 5.0.x.10 is Available



Version 5.0.x.10 of GTVx is available.

-----------------------
05.00.00.10 - 11/30/06
-----------------------

- FIX - Export as Dgn was not setting the origin correctly in orphan cell headers which caused all grouped elements from the GTViewer data to scale and rotate incorrectly in Microstation.

- NEW - Export as Dgn will now export Extended Style Information as UDLS tags on the dgn elements.- FIX - Text Elements with embedded data would lose the embedded data if edited with the Element Properties dialog.

- FIX - Reading an element would partially reset a DrawSetData. It will now fully reset the information.

- FIX - Right Mouse Menu would not activate when in Draw Dimension or Leader line modes.

- NEW - ExternalStyleMapFile and ExternalStyleDefinition entries can be added to the addprop.ini file or the Additional Properties section of the .GTM. If defined, these entries will import the specified .map or .def files.



Thursday, November 16, 2006

Can Pocket GTViewer be a Usable Viewing Platform?

Many people today still view Pocket PC or Windows Mobile devices as a novelty with little or limited practical use. There are generally 3 arguments against the handheld device for any application: 1) they are not powerful enough, 2) they can not hold enough data to be useful, and 3) their screens are too small to see anything (especially maps). I hope to dispel these myths and attempt to get more people looking at the handheld platform. Pocket GTViewer is an excellent application for the mobile community. If you are not utilizing this application in some way, you are missing out on a rich resource for viewing, data collection, and general accessibility to your GIS information.

Pocket GTViewer has been in existence as long as the desktop version of GTViewer, and it has progressed through several generations of Windows CE. The first version of Pocket GTViewer, introduced almost 6 years ago, supported Window CE 2.11 and the processor of the time was the Hitachi SHO running at 133 MHz. Pocket GTViewer has since supported Windows CE 3.0, Pocket PC, Handheld PC 2000, Pocket PC 2002, Windows Mobile 2003, Windows Mobile 2003 Second Edition, Windows CE.NET, and now Windows Mobile 5.0 (Window Mobile 6.0 is coming soon). I list all of the different platforms to show how quickly the handheld devices are evolving.

Let’s go through the arguments against viewing your GIS data on the handheld platform one item at a time and see how they are no longer valid excuses. The first argument is that the devices are not powerful enough. I think this argument has always been untrue. While the handheld devices are certainly not as powerful as a desktop PC, the devices of 6 years ago were more than capable of viewing complex vector map data. Pocket GTViewer was designed from the beginning to work with these slower processors and with minimal resources. On today’s handhelds, with processors 5 times faster, video hardware acceleration, and quadruple speed (or more) memory, Pocket GTViewer screams.

The second argument is not enough storage. Six years ago this might have been partially true. CF cards of that time were commonly in the range of 16M to 40M and a 100M CF card could easily cost more than the handheld device. At that time, you had to be a little more selective with what data you took with you; however, 40M of GTViewer data is a lot of information and rarely did I see a problem with not being able to take all the data along that was needed. Also, the 1G Microdrive provided some relief early on for those who needed extra storage at a premium price. These mechanical drives were very fast and usable even if they were deemed a bit fragile and consumed some precious battery power. Today, storage problems are all out the window; 4G+ memory cards (CF and SD) are common place and 2G cards very inexpensive ($70 or less). Solid state, fast, huge, and non-volatile, what more could you ask for?

The last argument is the usability of the screens which probably carries the most weight when deciding against the handheld devices as a platform. In the beginning, the standard Pocket PC and Windows Mobile screens are usually 3.5” diagonal with ¼ VGA resolution (240x320). If you leave the mainstream, there have always been a variety of screen sizes available; the only downside being that they are usually more expensive and use one of the more vanilla flavors of Windows CE (like Windows CE 3.0 and Windows CE.NET) which do not have some of the built in extras you find in Pocket PC and Windows Mobile. With the addition of Windows Mobile Second Edition, the screens are the same physical size, but they can now have full VGA (640x480) resolution and can operate in either Landscape or Portrait modes. This resolution increase is a much more profound change than it may seem at first. Going from ¼ VGA to full VGA quadruples the number of pixels in the same screen area and gives an amazing amount of clarity to graphics like the vector maps Pocket GTViewer displays. (This is one of those things you have to see to fully appreciate.) With Windows Mobile 5.0, the standard screen size is no long a standard and we see different aspect ratios. For example, the Treo 700w has a square screen.

There are really two issues when it comes to screen size. One is the hardware limitation and the other is thinking “desktop” when you have a “handheld.” The hardware limitation is really not an issue now with the full VGA screens (and really never was with ¼ VGA screens either). The screens are still small, but they are now crisper than your desktop’s screen and can still fit in your shirt pocket. The second problem has to do with doing the right job with the right tool. If you are trying to view all outages in your service area, a 3.5” screen is not the right tool. The tool for this job is GTViewer or GTVx, not Pocket GTViewer. However, the 3.5” screen with ¼ VGA or full VGA resolution is ideal for viewing a map up close. For example, you want to know if there are any underground utilities at an address, or you need to see what equipment is installed on a particular pole. A handheld device is like one of those little notepads with the wire spiraled around the top. You hold it in one hand and write on it with the other. So, what would you use a notepad for in the field? Taking notes, drawing sketches, filling out forms. Couple these tasks with an intelligent map supported by all of your GIS data and you have a very power tool in the palm of your hand.

Desktop GTViewer and Pocket GTViewer work well together. One is not a replacement for the other. GTViewer on your desktop PC can extract data for the handheld to take into the field, and receive redlines and/or collected data. GTWeb is also integrated with Pocket GTViewer allowing a web interface for selecting and loading data. Pocket GTViewer extends your GIS into places that were not always accessible before. I always carry my handheld with me, but I only lug my laptop around when I have to. Having the right information at the right time can make all the difference in the world.

The future is bright in the mobile arena. Beyond the Windows Mobile devices, we have SmartPhones and Ultra Mobile PCs. More and more devices today have built in GPS capabilities as well as cameras. Wireless connectivity is also becoming faster, more reliable, and more affordable. GTI’s product lines adapt to take advantage of the latest technologies available. You will see these new technologies leveraged in Pocket GTViewer, GTViewer, GTVx, and GTWeb.




This article was originally published in COGNET's GIS Advisor Newsletter:






Monday, November 06, 2006

Disclaimers, Messages, and Descriptions

How to inform thee, let me count the ways…

System administrators often need to provide information, in some way, to the people using GTViewer. There are three ways, and each is suited to a slightly different use. Each one is implemented as a parameter in the [General Info] section of the GTM file. Let’s take them in this order: Description, Message, then Disclaimer.

Description – This property specifies a one line description of the data. This description appears in several places:

- in the display filter
- in extract file descriptions
- in the new session dialog
- in the file > properties dialog

Here is an example of each one:

Display Filter:




Extract file description in the Tools > Extract Data by Fence



The New Session Dialog:




File > Properties Dialog:



Message – This property can be used to specify text to be displayed in the File > Properties dialog in GTViewer and the GTV > About > Open File dialog in Pocket GTViewer. The Message entry can be repeated as many times as necessary and can be used for copyright information, disclaimers, etc. The example above of the File > Properties dialog shows both Message and Description.

Disclaimer – This property can be used to specify text for a disclaimer that must be accepted before the data can be opened. The Disclaimer is limited to 255 characters per entry. It can also be set to <*blank*> to insert blank lines. The Disclaimer entry can be repeated as many times as necessary.

Here are two examples. The first shows the use originally intended, namely, to require the user to actively accept a legal notice. This is the actual disclaimer used by Jackson Electric Membership Corporation (JEMC).



The same technique can be used to present users with notices they ought to read but might skip. In this case, the administrator wants the people using GTViewer to know when their data set was exported from the GIS.



If they accept, GTViewer displays the data. If they Cancel, GTViewer exits.

I hope this blog posting has given administrators some ideas of how to inform users in the most suitable manner. And I hope at least a few readers were more amused than outraged by my distortion of Elizabeth Barrett Browning’s sonnet.

Thursday, October 26, 2006



Version 5.0.x.25 of GTViewer is available.


-----------------------
05.00.00.25 - 10/26/06
-----------------------
- NEW - The Title entry can be set to <*none*> to prevent any labels and borders from printing.


- FIX - If the session category had display thresholds, the drawing functions were disabled.

- FIX - FixedScaleFlag was not working on text elements (only symbol elements).

- NEW - Customizable support for Fixed Scale Text and Symbols. The Additional Properties section can now contain a PointFeatureThreshold entry to specify a selection tolerance based on distance from origin (instead of the text bounding box) and a FixedSymbolScale entry to the maximum zoom level to compute a symbols range for the spatial index.

- FIX - Problem with SetCurrentFilterId.

Friday, October 13, 2006

GTData version 5.0.0.4 is Available



Version 5.0.0.4 of GTData is available.


-----------
05.00.00.04 - 10/13/06
-----------

- NEW - GTStyleMgr, GTTabImport, GTMergeStyles - added to GTData.


- NEW - GTFilterImp - added to GTData.

- FIX - GTFrbConv - modified to also accept .rdl file using C(#) instead of C(Table.Attr). Non-FRB Tools .rdl files used the number of codelist tables.

- NEW - GTQuery - New silent flag will not generate the error messages, but will still provide the summary report.

- NEW - GTQuery - supports the -v1 flag to provide extra detailed information when compiling Offset Queries.

- FIX - GTQuery - If prompts were defined with a Graphic Offset Query, the query would be corrupt. Prompts are now ignored with this query type.

- FIX - GTFormatInfo - OmitFilterFlag messages in the verbose log were incorrect.

Monday, October 02, 2006

GTVx version 5.0.x.9 is Available



Version 5.0.x.9 of GTVx is available.

-----------------------
05.00.00.09 - 10/02/06
-----------------------

- NEW - Export Session Graphics as XML functionality has been added to ExportSessionGraphics and ExportSessionGraphicsEx.

- CHG - Text Drawing in UDLS lines will not turn off when the size is less than 4 pixels (like it does with regular text)

- NEW - New Method:

boolean GetElementFontId(long categoryId, long offset, long* fontId);

- NEW - The FixedTextPlacementScale property is supported with SetDataProperty to change the text placement size to not be zoom dependent. Set to the zoom level you want the text size to be based or 0 (default) to work as it has in the past.

GTViewer version 5.0.x.23 is Available



Version 5.0.x.23 of GTViewer is available.

-----------------------
05.00.00.23 - 10/02/06
-----------------------

- FIX - For the Link entries, if you specified a Link Description attribute that did not exist, the error message said the Link Attribute was not valid.


- CHG - The Measure readout has been moved from the status bar to the upper left corner of the view.

- NEW - The FixedTextPlacementScale property is supported with SetDataProperty to change the text placement size to not be zoom dependent. Set to the zoom level you want the text size to be based or 0 (default) to work as it has in the past.

Monday, September 25, 2006

GTWeb 5.0 - Use with your favorite Browser

The new version of GTWeb now provides a client-less mode of operation that makes it browser independent. Today, the three most common browsers are Internet Explorer, FireFox, and Opera. So, if you are fond of particular browser, if you are forced to use a specific browser due to corporate directives, or if your web app is for the public browser selection is out of your control, the new GTWeb client-less mode of operation addresses these needs.

Previous screenshots of GTWeb 5.0 have been with Internet Explorer 6.0, so the ones below are all using different browsers.


Internet Explorer 7.0 (Release Candidate 1)





FireFox 1.5




Opera 9.0

Thursday, September 21, 2006

Tuesday, September 19, 2006

GTViewer 5.0.x.22 is Available



Version 5.0.x.22 of GTViewer is available.

-----------------------
05.00.00.22 - 09/19/06
-----------------------

- NEW - Intersection Query now supports more than 3 prompts.

- CHG - Text Drawing in UDLS lines will not turn off when the size is less than 4 pixels (like it does with regular text)

- CHG - GPS dialog was changed to have a Track GPS in View option and a Show Indicator option as well as an Indicator Type. The Track GPS option has also been added to the toolbar.

- CHG - GPS Leave Trail is now persistent between runs.

-----------------------
05.00.00.21 - 07/18/06
-----------------------

- NEW - Shape with Holes elements now supported styled lines for their borders.

- FIX - Connectivity Query and Offset Query would not find a record if it were the first record in the file. Problem introduced with very large .gtx file support was enhanced (4.0.0.16).

Thursday, September 14, 2006

GTFilterImp Utility added to GTData

Version 5.0.0.4 of GTData will include a new utility called GTFilterImp.

This utility will import the customizable settings (including display status, minimum display threshold, maximum display threshold, and filter flags) from one Filter Definition File (.flt) into another. Since filter files have become more complex (as seen in data that is style rule based such as ESRI, Smallworld, and G/Technology), this tool can be very useful in managing the customizable settings.

Press Release: Configurable Field Application from GTI



Press Release on GT/Field:

http://www10.giscafe.com/nbc/articles/view_article.php?section=CorpNews&articleid=303473

Friday, September 08, 2006

GTWeb Version 5.0 – No Client Software Required!

For several years, GTWeb has provided an easy way for a large number of users to access your GIS data with minimal administrative effort. GTWeb has minimal client requirements, requires minimal bandwidth, and is very easy to use. GTWeb version 5.0 provides a significant amount of new features to make it even more effective at what it does best.

Client-Less Operation

Version 5.0 of GTWeb offers a new approach to viewing your GIS data while still providing all of the functionality of the previous versions. The GTWeb Server can now simultaneously support the traditional GTWeb client that has been available since the product was released as well as the GTSketch client introduced in subsequent versions. The exciting new feature offered by Version 5.0 is a new mode of operation that brings GTWeb to an even greater user base by removing the need for any client component at all other than the browser.

The new "client-less" mode uses ASP.NET 2.0 to interact with the GIS data. It allows queries, panning, zooming, and reviewing of attributes just like the original version. The GTWeb and GTSketch clients still provide a richer experience for the user (since they are very similar to GTViewer in regard to its viewing capabilities), but the gain in universality offered by the client-less version opens GTWeb (and your GIS data) up to a new, larger class of users. The client-less mode of operation grants immediate access to users without the need to install or maintain any client software other than the browser, and it provides browser independence since it can be used with IE, FireFox, Opera, etc.

Template Web Site Enhancements

The new features provided in GTWeb version 5.0 are not limited to the new client-less mode. GTWeb has always been delivered with a Template Web Site to use as a starting point for creating your own specific web application around GTWeb for your organization. The Template Site is complete and can be used as-is; generally, if any changes are needed, they are cosmetic (such as adding your company’s logo, etc.). The Template Site delivered with GTWeb version 5.0 has been rewritten to take advantage of many features found in ASP.NET 2.0, and to make the template site easier to use and customize. The new Template Site works with both the client and client-less modes of operation and can easily combine projects of both types. Some of the new Template Site features are listed below:

  • Cascading Style Sheets (CSS) are now used to give the template site both a consistent look on its different pages and provides a single place to update the styles, fonts, colors, behaviors, etc. used by the different pages in the Template Site. The Query Selection, Query Form, and Query Results pages have been combined into a single page to provide a better user experience and to eliminate the need to go through multiple pages when performing a query. The page flow has been reduced from: Project Selection -> Query Selection ->Query Form -> Query Results -> Map to a much simpler: Project Selection -> Query -> Map
  • Query results are now returned as DataSet objects which can be bound to many of the ASP.NET controls such as a DataGrid. This simple change eliminates a significant amount of web page code and complexity while also leverages the power of the ASP.NET controls. For example, a DataGrid can easily sort by column and automatically break results up into multiple pages.

GTWeb Web Service

Another significant new feature provided by GTWeb version 5.0 is that all of the server side functionality is available in the form of a Web Service. A Web Service is a self-describing software component that makes its functionality available over the internet in a platform independent way. A variety of development platforms (such as .NET and Java) can consume a web service and incorporate the web service’s functionality into a web page, a desktop application, a device application, or anything that can use web services. By providing all the functionality of the GTWeb Server component, a new approach to getting your GIS data on the web and into other applications is now available.

The screenshots below show some of the new template site pages and what the client-less maps look like:







Thursday, August 17, 2006

GTI to Exhibit at Smallworld Conference in September

Join us at the 2006 Smallworld Americas Users Conference, September 24-27. This year the conference returns to the attractive Omni Interlocken Resort near Denver, Colorado.

GTI will be showing its configurable data collection application GT/Field, the new GTWeb 5.0, and the rest of the GTViewer Family of Products that help companies gain more value from their geospatial data.

GTI will also be showing its solutions including the new Fiber OTDR Trace application that allows a field technician to find the location of breaks and splice problems. Come see Loop Makeup, Gas Valve Isolation, Outage Analysis, and more.

Tuesday, August 15, 2006

GTVx version 5.0.x.8 is Available



Version 5.0.x.8 of GTVx is available.

-----------------------
05.00.00.08 - 08/15/06
-----------------------

- NEW - Right Mouse Cancel is now supported during rendering.


- FIX - The .GTS session files did not correctly save Leader Line elements.

- NEW - Shape with Holes elements now supported styled lines for their borders.

- FIX - Connectivity Query and Offset Query would not find a record if it were the first record in the file. Problem introduced with very large .gtx file support was enhanced (4.0.0.6).

Monday, August 14, 2006

GTRead version 5.0.0.2 is Available

GTRead is a Windows ActiveX Control that reads GTViewer graphics files (.gtg) and Extract files (.gtx). GTRead is part of the GTViewer-SDK and can be used to add the cability of reading GTViewer data into any application as long as the development platform supports ActiveX controls.

Version 5.0.0.2 of GTRead uses the GTViewer 5.0 core and contains several fixes.

New GTData Tools

The next version of GTData will contain 3 new utilities: GTTabImport, GTMergeStyles, and GTStyleMgr.

GTTabImport provides a method to import custom changes from one Table Definition Files (.tab) file into another. Custom changes include alternate table names, alternate attribute names, display order of tables, and display order of attributes. The Table and/or Attribute must exist in the main .tab file before it will be imported from the import file. The GTConfig.exe utility has the capability to import custom changes from one .tab file to another, but it has a GUI and could not be run on the command-line or in scripts. The GTTabImport utility takes this feature of GTConfig.exe and makes it scriptable.

GTMergeStyles provides an easy method for merging multiple style.def and style.map files together. This task could be performed by the Style Manager in GTViewer; however, with this utility, the process can be scripted.

GTStyleMgr provides several new features for manipulating Style Rules (style.def and style map files). The features it provides are listed below:
  • The Chop option can be used to remove a string from the beginning of a style definition name (both in the .def and .map files). Some of the conversion tools (like the G/Tech converter, and the FME plug-ins) use filter id names that match style definition names. It is possible to create your filter id name/style name with a prepended string that is useful for the filter name, but not necessary for the style (since the style could be reused by several different filter ids). The chop option will simply remove this prepended string from the style definition names leaving the filter ids intact.
  • The Strip option can be used to remove a square bracket enclosed string ( […] ) at the end of a style definition name. The style definition name will be updated in both the style.def and style.map files. This option is useful in a specific case where a features state (in service, proposed, retired, etc.) is appended to the filter id and style name. It may be useful to control the display of features by state, but they may not use different style definitions. The Strip option will remove the bracketed name in the style.def and style.map.
  • The Thin option is a replacement for a previous tool called GTStyleThinner which looked at all definitions in the style.def and deleted any definitions that were not referenced in the style.map. This process of thinning the style defs can reduce the overall size of the style rules in a dataset (sometimes important on the device platforms).
  • The Fill option can be used to populate only the empty style definitions in a style.def from another style.def file.
  • The Import option can be used to import another style definition file. This option works identically to the Import Option in GTViewer when the import only if exists command it used. Therefore, only styles that already exists (empty or not) in the original style.def will be imported.