CONTACT MI
  Resellers
  Consultants
  MicroImages
  About MI
  Visiting
  Prices
  Send Email
  Reseller Resources

SHOWROOM
  Gallery
  Technical Guides
  New Features
  Testimonials
  Reviews
  World Languages

   View in PDF format

Database Features.

Table Setup.

Background.

A single graphical element can have many attributes accompanying it in the fields and records in a relational database structure.  Some projects require that you think out very carefully the required tables and then design their internal record structure including records, fields, and value data type.  You should also carefully structure these tables so that their relational structure simplifies them and their subsequent use.  A single flat database table can quickly grow huge to have hundreds or thousands of different fields and millions of records with a poor design and extensive duplication.  A relational structure has small compact tables with linkages to minimize this record and table duplication.  An intelligently designed structure can make your geospatial analysis much easier.  If you were trained and/or experienced with database systems, you knew all about this.  If you are a geospatial analyst, you need to learn this skill quickly.  As soon as you begin combining geometric layers, you will quickly see the impact of your skill level in this area and improve it.  TNT provides the tools you need to create your tables and structure, monitor their hierarchy, and to simplify, revise, and restructure it.

Wizard.

A simple wizard approach is now used when you set up a new table in the Spatial Data Editor or any other process and its steps are illustrated in the dialogs in the accompanying 2-sided color plate entitled Database Table Creation Wizard.  After you designate the new table’s name and description you are prompted in a dialog to select from the 6 attachment types you can use for the records in this table (for example, one element per record, one record per element, …).  If you choose any except the first option on this list, you are creating a directly related table and are next presented the Table Definition dialog to set up its contents.  If you select the first attachment type, “Relate to another table through a key field,” the next wizard dialog will prompt you to select the field and table that the new table you are creating will use as a relational link to your graphical elements.  If you have chosen a primary key in the old table as the link field for your new table, you will now be taken to the Table Definition dialog so you can continue on to design the contents of your new table.  If you choose any other field in the old table to link to, then the wizard will ask which table should contain the primary key field for their linkage.  When this selection has been made, you are given the Table Definition dialog to design the internal structure of your new table.

Virtual Tables.

Virtual fields are those whose value is defined at the time of their use, such as when they are presented in a DataTip.  Virtual fields are computed or string expressions that can be selected in the Table Definition dialog from the “Field Type” button.  Once a virtual field is set up, it is used and managed just as if it were a real field.  Virtual fields can be used to compute a DataTip’s contents (using an equation or a script) and to format the result (using string expressions and format codes).  Virtual fields can be used for many other geospatial applications, such as computing a spatially varying URL link and then starting a browser with it.  For example, selecting a zip code polygon can insert its real field zip code value into a virtual field that already contains the rest of the string expression needed to start a browser and retrieve the weather page for that zip code.

A virtual table contains only virtual fields.  This is analogous to setting up a “View” if you are familiar with relational database products. When using virtual fields, it can be convenient, even necessary, to create virtual tables in your relational table structure to contain them and support the special features they provide.  A table you set up using the wizard will automatically be virtual if it does not have any real fields and you use the Table Design dialog to create one or more virtual fields in it.  Once established in your relational structure, a virtual table looks and operates as if it were a real table.  It can be seen in your database hierarchal tree view, transferred, reused, altered, and so on.  An example using a virtual table and the sample scripts defining its virtual fields is in the accompanying 2-sided color plate entitled Database Wizard and Virtual Tables.

Database Management.

Deleting duplicate records now detects if the table attachment type would prevent a record from becoming attached to multiple elements and, if so, gives you the opportunity to change the attachment type to something less restrictive.

Current attachments are retained when changing the table attachment type from “implied one-to-one” to another direct attachment method.

Text Editor.

Tabs can now be set in text blocks using the tab key.  This is especially useful in creating vertical alignment of your text, especially in DataTips as illustrated in the multi-line DataTip on the accompanying color plate entitled Property Viewer Atlas for Lincoln, NE.  

Fonts can now be specified by their family name (“Times New Roman”) as well as by font file name (times.ttf) when using text formatting codes.

When specifying the font for a character string in a text block using {~} codes, you can now specify multiple fonts in case the preferred font can not be found.  The order in which the font names are entered will determine the order of your preference for their use.

Double-clicking on a word now selects the word instead of the whole line.  Triple clicking now selects the whole line.

Keyboard shortcuts for Cut/Copy/Paste have been changed at your request to ctrl+x, crtl+c, crtl+v to conform to common use in most other software.

A keyboard shortcut (ctrl+s) is available for Save.

Style Editor.

Styles are now sorted alphabetically.

Map Layouts.

Antialiased and Thin Line Width Hinting settings are now being controlled on an individual layer by layer basis (this effects vector, CAD, TIN, map grid, shape, and region objects).  This means layouts will render consistently from machine to machine.  In V6.9 these setting were made in user preferences and globally controlled both antialiasing and thin line width hinting.  Antialiasing and thin line width settings are now also used in 3D renderings.

Render to SVG.

Scalable Vector Graphics (SVG) is the graphics format developed and promoted by the World Wide Web Consortium (W3C) based on XML.  The optional features added to control  the rendering of a TNT map layout into SVG continues to expand: partially because SVG is an excellent layout structure for use in web applications, especially for interactive maps, and partially because it is a format for communicating graphics information between a TNTserver and the TNTclients.  You continue to expand your use of this format and request these kinds of optional control features.

A new SVG class in the geospatial scripting language (SML) permits scripts to render objects or views into SVG.  All the SVG output rendering options are available.

It is best to refer to SVG as a layout since it can carry with it linked fonts, linked style sheets and styles, linked rasters in several formats, and other files.  The graphics and their use of these the components are in a file but these other items need not be. 

SVG Control Window.

Rendering a layout to SVG is about 2 times faster in RV7.0.  The Render to SVG window has been redesigned to present the RV6.9 and many new options via tabbed panels.  These are summarized on the accompanying color plate entitled Render Complex Layouts to SVG.  More will be added as needed, particularly to control the operation of additional JavaScripts, which you can append to the SVG file.  The accompanying color plate illustrates this window and summarizes the options it provides. 

The Render to SVG window initially has two active panels:  Options and Raster Controls and the rest are inactive.  It also has toggle buttons that can be used to indicate which special feature JavaScripts to append to your SVG.  Adding these will enable the SVG viewer or other application to automatically use DataTips, Measurement tools, Layer Controls, and Coordinate Display features in your SVG.  When any of these optional tool toggles is selected, the corresponding tabbed panel is activated and can be optionally selected to change the default settings controlling how that feature will function by altering the JavaScript that is added.  The JavaScript for Coordinate Display has no options and, thus, no corresponding tabbed panel.  The reverse side of the accompanying color plate entitled Render Complex Layouts to SVG reviews the functions of these JavaScripts and their optional operations.

Options Panel.

Resolution.
The final use of your SVG can vary widely from its use as a conveyance for a subset of graphics for a limited area of a screen view, to a complete, high resolution map in a portable format.  For example, a thin network client (minimal local capability) responding to a minimum bandwidth requirement might request the SVG scale controlled coverage (thus, the portion of a vector or CAD object) that covers the current view. 

A thick client designed to do a lot of local work with the server’s data and using a broadband connection might simply get all the map layout’s contents (vectors, database, …) in an SVG layout and work with them locally off line.  In the thick client example, the precision of the coordinates and the resolution of the rasters need not exceed that for the current view.  The client will come back and request a new SVG to revise the view.  Since this is the same engine that renders to SVG in TNTserver, the options panel accepts a resolution value to control the graphics and raster precision for your targeted SVG application.  Using the value of 100 will produce an SVG layout that is minimal in size and only matches the precision of your conversion to the current view.  A value larger than 100 will increase the detail transferred from the objects in the TNT layout into the SVG layout.  This value applies to all layers and if set very high will transfer all the detail available but no more.

Toggles are available to control the following, some are new and some are not:

• render the full layout including hidden and layers currently turned off for the view scale;

• clip output to the current view;

• link to style sheets to share them and avoid duplication versus using inline or embedded style sheets to insure they are available;

• inline, or embedded, styles to insure they are available rather than linking to them for sharing with other SVG files without duplication;

• apply gzip compression to the XML file and replace extension *.svg with *.svgz (the accepted convention denoting this compression);

• use XML entities for strings if you plan to edit the XML of the SVG layout;

• embed the SVG file into an HTML framework (for use in Internet explorer only);

• embed TrueType fonts to insure they are available (for use with Adobe or Batik viewers); and

• optimize for use with Adobe Illustrator to avoid issues with scale controlled views.

Raster Controls Panel.

Toggles are available to control the following:

• embed images in the SVG file to insure they are always available rather than simply linking to them so that they can be shared with other processes;

• use only PNGs, which use lossless compression, because it may be better suited to your image data;

• set a preference to use JPEG lossy compressed rasters; and

• change the JPEG compression from approximately 35% to some other desired level.

DataTip Panel.

It is important to keep in mind that DataTips in the TNT products can make extensive use of virtual fields, which are evaluated at the time they are exposed.  For example, DataTips presenting material from several layers could change if the tables/records/field values being evaluated are changing in the tables.  This capability is not supported in SVG DataTips.  When you choose to include TNT DataTips using virtual fields in your SVG, they are all evaluated and converted to real fields as part of the rendering process. The reverse of the accompanying color plate entitled Render Complex Layouts to SVG illustrates how a multi-line DataTip defined in TNT using a virtual field is converted into SVG and then pops in using the Adobe SVG plugin for Internet Explorer.

As discussed above in the section on GraphTips, a TNT Display Control Script provides for complex mouseover events.  A simple application is to detect that the cursor is over a small symbol or label and automatically balloon it up so it can be read.  By modifying this DataTip JavaScript, this same effect can be added for your labels and pinmapped symbols showing in your SVG.  When your cursor is over one of these elements, they will automatically zoom up according to the Symbol Enlargement Ratio you set on this panel, which defaults to 2X.   Note that these are labels and symbols that are already showing in the SVG view and this effect is separate from the TNT pop-in action associated with any DataTips you have included.  The accompanying color plate entitled Render Complex Layouts to SVG shows that positioning the cursor over a symbol can enlarge it by this factor and also pop in an associated DataTip for the same feature.

This panel also programs this JavaScript to change the transparency of the frame from the default of 50%.  It also toggles the highlight for the element used for the DataTips from the default, which is your selected highlight color for the TNT products, to complementary highlighting and can be set to blink the highlight selected to draw attention to it. 

Measure Panel.

At this time this panel has only one option, which determines the drawing paradigm: click and drag (toggle on) or click for each vertex (toggle off) to add the JavaScript for the chosen paradigm.  An illustration of the use of the measurement tool is illustrated on the reverse of the color plate entitled Render Complex Layouts to SVG.

Layer Controls.

At this time this panel has two options, which are to add the Adobe Menu JavaScript for layer control in the SVG or a layer control panel.  You can choose either, neither, or both.  The Adobe Menu JavaScript will present Adobe’s layer controls via the right mouse button and only in the Adobe SVG viewer.  This Layer Control Pane now has a toggle icon and a “close” button to allow users the option of making its usage visible or hidden.  The layer controls added by TNT and Adobe JavaScripts are both illustrated on the reverse side of the accompanying color plate entitled Render Complex Layouts to SVG.

Rendering to PDF.

Print to PDF / Illustrator now renders the PDF based on the layout settings rather than requiring adjustments in the print dialog (essentially they needed to match).  This makes it easier to switch back and forth from rendering to one print destination to another by allowing you to use the same layout for printing to a printer and subsequently rendering to a PDF.  In RV6.9 you would nearly always need to make a different layout for targeting a local printer for hardcopy and for quality control and then rendering to a PDF.

Color Matching.

The release MEMO for V6.9 entitled Release of the RV6.9 Products and dated 31 December 2003 discussed color matching in detail.  It noted that ICM profiles are not provided for all large format HP color printers, especially older models.  It was subsequently found that you can download these ICM profiles for your large HP color printers from Pantone at www.pantone.com/support/support.asp?.idArticle=72.

Geospatial Scripting Language (SML).

Introduction.

The TNT scripting language used throughout the TNT products (formerly the Spatial Manipulation Language) is now referred to as the geospatial scripting language since this better reflects its current utility.  It may also be referred to as SML, geospatial scripting, TNT scripts, or simply scripts or scripting when the context is clear.

Considerable programming effort has continued to be invested in SML to provide a clean, documented, powerful scripting language aimed at those who have special geospatially oriented objectives.  SML continues new uses such as in the new Display Control Scripts and startup script applications added in RV7.0.

TNTmips is a broad-based geospatial analysis system designed to complete as many industry-common projects as possible using widely available geodata and to do them fast and efficiently.  However, it is not reasonable to expect that any such system can solve specific unique project needs and research activities.  What TNT scripting provides is a means to add, extend, supplement, prepare data, … to resolve these special but needed steps or activities. 

When a complex task is at hand, especially if it is to be repeated, time spent to automate its steps with SML can be very productive.  In the paper cited below by Wada and Ohira, its authors credit use of easily created scripts using SML macro-like geospatial functions and classes combined with the TNT processes to reduce the time to implement their complex research analysis to 10% of what was previously accomplished with some other competing product.

Yokio Wada and Wataru Ohira.  2004.  Reconstructing Cloud Free SPOT/Vegetation Using Harmonic Analysis with Local Maximum Fitting.  25^th Asian Remote Sensing Conference, Bangkok, Thailand. 5 pages.

This study was completed using TNTmips 6.9 and DV7.0 and SML scripts written by the authors.  It used 36 SPOT/VEGETATION images collected 1 January to 21 December 2002.  The PC was a Zeon 1.7 GHz with 2 GB of RAM.  This paper is not copyrighted and is published at www.microimages.com/papers/ACRS25.pdf and the authors can be contacted at yukio@jafta.or.jp.

Abstract. “The satellite data of low resolution such as SPOT/VEGETATION, NOAA/AVHRR and TERRA/MODIS etc. are very effective in vegetation analysis on global scale.  Especially, the satellite data that are observed everyday is suitable for time series analysis such as illegal logging, forest fire, seasonal vegetation change and forest change.  But, in these satellite data noises due to influence of cloud and mosaic are included, and disturb due analysis.  The result is always an image with data gaps.  This study aims to reconstruct time-series data without cloud, noise and gap.  Basic ideas used for the reconstruction are Harmonic Analysis and Local Maximum Fitting (LMF) algorithm.  We tried to reconstruct smooth and gapless data.  This Harmonic Reconstruction (HR) process was applied to 36-image series of SPOT/VEGETATION S10 product NDVI data of 1 year covering most Asian region.  S10 product is 10 days synthesis by Maximum NDVI method.  First, Local Maximum Fitting was conducted to exclude abnormal data.  Next, amplitude strength and phase parameter classified by period were calculated by Harmonic Analysis.  By fitting these in cosine equation, the data were reconstructed.  As a result, it could reproduce smooth data with which influence of cloud and noise is little.  In addition, it should be noted that specification of the used PC and the remote sensing software are not more than standard ones.  It could also save the processing time by 90% or more in comparison with the ones by other similar model fitting process.  For user’s convenience difficult programming is not necessary and this process is simple to handle.” 

SML and now TNTsdk are available for this purpose and will both automatically extend your results across all supported platforms and in your language.  There are many strategies in the TNT products for using scripts: batch run scripts, scripts for queries, Tool Scripts, Macro Scripts, Display Control Scripts for GraphTips, and other automatic activities. Scripts can be used in TNTsim3D for controlling or extending simulations.  Scripts can create display layers. Scripts can make forms, add constraints, start and communicate with other non-TNT programs in VB, C++, or Java.

Writing scripts may seem to be daunting at first for non-programmers, but MicroImages is now providing lots of good support help in this area. If you do not want to learn to script for yourself, there is always a student around who wants to earn some extra money.  Those with some programming experience will find geospatial scripting interesting because it can accomplish visually interesting results with a single page of script as shown by many of the sample scripts.  A good introductory tutorial is available entitled Writing Scripts with SML.  Hundreds of professionally written sample scripts are available at www.microimages.com/downloads/scripts.htm to be used as examples, models, and sources of code snippets for your scripts.

Sample Scripts.

Using Crystal Reports.

Periodically MicroImages is asked how to communicate with other non-geospatial commercial products such as Access, Excel, and so on.  Previous MEMOs and associated SML scripts and color plates have addressed the topic of how to communicate with these other programs. These scripts have illustrated how SML can be used to start another Visual Basic, C++, or Java program and transfer data to it.  That program in turn can use the API of other commercial products to start and use these results.  The reverse has also been demonstrated where other product’s results, such as updates to external database table(s), can use an SML or a custom program to update a table view or a pinmap in a TNT view. 

The accompanying color plate entitled Create Crystal Reports with SML illustrates the results and lists the content of a very short sample script for displaying TNT results using this commercial product.  The table used to generate this report is a simple flat table attached to a vector object.  However, much more complex results could be prepared using TNT processes and/or this script.  For example, a TNT query could be composed and interactively tuned to select the features of interest and an SML Macro Script from the TNT menu to assemble their attributes from relational tables to create this kind of report.

Computing Terrain Curvature.

This is a sample script showing how to set up and compute special raster properties yielding new raster objects.  This script computes geomorphological curvature properties of terrain.  The accompanying color plate entitled Terrain Curvature illustrates the results and lists this script, which computes profile curvature and plan curvature raster objects from an elevation raster.   Everyone has different ideas about how these kinds of properties should be computed—kernel sizes and shapes, coefficients, surface fit, and so on.  This script provides a template that can be modified to handle these different objectives and as the basis for computing other special terrain and raster properties.

Identifying Coastal Mosquito Habitat.

This Tool Script was created in close collaboration, including a visit from a long term MicroImages client, to accomplish a similar task in a TNT script as that in an  ESRI Avenue script.  Its objective is to permit this expert to statistically examine the correlations of occurrence with habitat of a specific species of mosquito restricted to coastal areas.  It uses climatic and geomorphological rasters to characterize the habitat, vector buffer zones to set test positions, relational databases of mosquito trapping results, a Tool Script approach to identify the test positions, and CartoScripts to illustrate the statistical results.  The accompanying color plate entitled Mosquito Habitat Statistics (U-Test) illustrates and explains the tool in more detail.

This Tool Script is representative of the very specialized tools that can be created to explore the spatial relationships between spatial features and massive databases.  It is typical of a design used by experts in geological, biological, and other complex analyses whose “expertise” can not be “coded.”  It is not designed to be a blind data-in and data-out geospatial analysis because there is no definitive answer.  What is required is to keep the expert’s unique knowledge of the subject tightly and interactively integrated into the tool so that generalities can be drawn to serve as the basis for the next hypotheses.  What is also required is a geospatial framework that maintains tight integration and access to all the types of geodata available, not a GIS, image processing, or CAD system.

Profiling Pipes in an Urban Infrastructure.

This Tool Script shows a sample use of interactive feature selection in a 2D view to present graphical results in an attractive custom window and is illustrated in the accompanying color plate entitled Infrastructure Graphical Profile.  The input for this sample script is a network vector object of pipelines overlaying an elevation raster.  The cursor can be used to interactively select a sequence of lines in a 2D view.  You can use it to select or deselect lines that connect to either end of the line selection you are extending in the 2D view.  Your connected line selections are highlighted in color in the 2D view.  Use this section of this script to select and connect multiple end-to-end lines in your scripts before using the line in subsequent steps.

At any time a connected line has been selected, a right click of the mouse draws a profile of the line in the profile window created by this script.  This part of this script illustrates how to draw complex graphical results in a window.  The surface of the ground is drawn from the trace of the line on the elevation raster.  The pipes are drawn at their depths below the ground profile.  Each pipe can be styled to reflect its material type and its diameter.

General Features.

Hash variables can now be used like arrays but you don’t need to specify a size in advance and the subscripts can be numeric or strings.

A “switch” statement can be used and has a syntax identical to that used in “C.”

Function “prototypes” can be used just like in “C.”

The exclusive or (XOR) operator is available.

The SML Editor now uses syntax highlighting.

Creating Manifold Objects.

New classes are available so that a script can create the 3D georeference to define a manifold surface and combine it with another object to create a manifold object.  Use these to create a script to read and use 3D control points from an external database that could change dynamically to change the surface shape when viewed in 3D.  Many data mining results are presented and viewed in this fashion.  Even more dynamic results can be achieved when manifold objects can be used in a TNTsim3D and are shaped and changed in shape from an external database.

Googling SML.

All the SML sample scripts, script names, brief descriptions, and related materials have been incorporated into the MicroImages website in such a fashion that it is now being indexed by Google.  Thus, you have one more way to find that function or script of interest.  Simply choose the Search Site tab on the MicroImages home page and let Google present you with the links to these materials using your key words.

New Functions.

Database functions. (8)

DatabaseCreate( )
     Create a “standalone” database object.

TableCopy( )
     Copy a database table from one object’s database to another.

TableDelete( )
     Drops a table from its database.

TableGetRecordElementList( )
     Get list of elements with a given record attached or related.

TableGetRecordListElementList( )
     Get list of elements to which a given list of records are attached or related.

TableRemoveDuplicateRecords( )
     Deletes duplicate records from the table.

TableRemoveUnattachedRecords( )
     Deletes unattached records from the table.

CloseDatabase( )
     Close an open database instance.

Raster Functions. (5)

ComputeMeanRaster( )
     The output raster contains the mean value (at each cell) of all the inputs.

ComputeStdDevRaster( )
     The standard deviation (at each cell) of all the inputs is assigned to the output raster.

RasterCompress( )
     Copy compressed source raster to the destination raster.

GetMaxPossibleValue ( )
     Get the maximum possible data value in the raster.

GetMinPossibleValue ( )
     Get the minimum possible data value in the raster.

Vector Functions. (3)

Vector Copy Elements( )
Returns Vector with elements from source that meet the query selection criteria.

VectorIsEquivalent( )
Determine if two Vector objects are equivalent.

VectorWarp( )
Warp the source vector from the transparm’s source to destination  projection.

Object Functions. (4)

FindInvalidObjects( )
Search the Project File (*.rvc) for invalid objects.

PackRVC( )
Eliminates unused space from the Project File (*.rvc).

RecoverProjectFile( )
Recover Project File copying to new file.

SetObjectName( )
Change the object name of an existing object.

System Functions. (1)

GetLastError( )
Get the last error encountered in the script to test if a function succeeded.

String Functions. (1)

StrToDeg( )
Convert string in degrees, minutes, seconds format to decimal degrees.

Georeference Functions. (2)

CreateSimpleGeoref( )
Create simple raster georeference.

GeorefSetCoordRefSys( )
Set the coordinate reference system for a georeference object.

Style Functions. (1)

StyleReadHatchPattern( )
Read a hatch pattern from a style object into memory.

CAD Functions. (2)

CADReadPolyLine( )
Read a CAD element into the polyline.

CADWritePolyLine( )
Write a CAD element from a given polyline.

TIN Functions. (2)

CreateTIN( )
Create a new TIN object without prompting user to select file.

OpenTIN( )
Open a TIN object without prompting user to select input file.

Resource File Functions. (1)

ResourceAugment( )
Add user-defined text resources to allow localization of dialogs created in SML.

Geodata Display View Functions. (1)

ViewRedrawLayer( )
Redraw the specified layer in the view.

Object Conversion Functions. (4)

ConvertCADToVector( )
Convert CAD object to vector object.

ConvertTINToVector( )
Convert a TIN object to a vector object.

RasterToTINIterative2( )
Converts elevation raster to TIN object as contour lines.

RasterToVectorContour2( )
Converts elevation raster to vector onject as contour lines.

Raster Global Functions. (3)

GlobalMedian( )
The median cell value in the raster object.

GlobalMode( )
The cell value occuring most often in the raster object.

GlobalMost( )
The number of times the GlobalMode value occurs in the raster.

Vector Toolkit Functions. (2)

VectorAddPolyLine( )
Add a vector line/polygon from the given polyline.

VectorChangeNode( )
Changes the location of an existing node in a vector object.

New Classes.

RVC_GEOREFERENCE
Completes all georefrence object manipulations including those for manifolds.

TRIANGUALTOR
Handles triangulation of points with break edges and clipping regions.

BOUNDARYLIST
A list of  boundary node arrays.

EDGEINFO
Information about edges in a TRIANGULATION.

TRIANGLEEDGES
Structure to hold the edge numbers of a triangle.

TRIANGLEINFO
Information about triangles in a TRIANGULATION.

TRIANGLENODES
Strucuture to hold the node numbers of a triangle.

TRIANGLETRIANGLES
Structure to hold the triangle numbers of neighboring triangles.

SVG
For writing SVG layouts.

MieARCE00RASTER
For import/export parameters.

HASH
Similar to an array (Perl programming).

ELEMENTREF
Container for spatial element specifying type and number.

GRE_LABELS
Class controlling labels and their placement.

GRE_LAYERDC
Layer drawing context containing information needed to actually draw layer on a particular view.

HATCHPATTERN
Containter class to hold hatch pattern information.

LABELATTACHMENT
Class for attaching lables to their elements.

LABELPLACE
Class for keeping track of where a label is on the screen.

LABELSTYLE
Structure for holding style information for a label.

MieCARIS
CARIS format import/export parameters.

REGION2D
An in-memory region representation.

SR_COORDOPDEF
Spatial reference coordinate operation definition.

SR_COORDOPPARM
Spatial reference coordinate operation parameter.

SR_COORDREFSYS
Coordinate Reference System.

SR_COORDSYS
Coordinate System specification.

SR_DATUM
Spatial reference coordinate datum specification.

SR_ELLIPSOID
Spatial reference ellipsoid specification.

SR_PRIMEMERIDIAN
Spatial reference prime meridian specification.

UNIT
UNIT specification for units of measure.

Upgrading TNTmips.

If you did not purchase RV7.0 of TNTmips in advance and wish to do so now, please contact MicroImages by FAX, phone, or email to arrange to purchase this version. When you have completed your purchase, you will be provided with an authorization code by FAX.  Entering this authorization code while running the installation process lets you to complete the installation of TNTmips 7.0.

The prices for upgrading from earlier versions of TNTmips are outlined below.   Please remember that new features have been added to TNTmips with each new release.  Thus, the older your version of TNTmips relative to RV7.0, the higher your upgrade cost will be.

Within the NAFTA point-of-use area (Canada, U.S, and Mexico) and with shipping by UPS ground.  (+150/each means US$150 for each additional upgrade increment.)

For a point-of-use in all other nations with shipping by air express.  (+150/each means US$150 for each additional upgrade increment.)

Internationalization and Localization

Localization Editor.

Translating the help messages is an optional requirement.  A toggle has been added to exclude these help messages if they are not to be translated.

 MicroImages Authorized Resellers

The following 5 new Resellers were authorized to sell MicroImages’ products since RV6.9 shipped.

AUSTRALIA.

BOLIVIA.

INDIA .

SOUTH AFRICA.

CHINA.

Discontinued Resellers

The following resellers are no longer authorized to sell MicroImages’ products. This list is longer than usual as some of these locations were omitted from previous MEMOs.  Please do not contact these former resellers regarding support, service, or information.  Please contact MicroImages directly or one of the other MicroImages Authorized Resellers.

MicroImages is pleased to provide new resellers the opportunity to use, learn, and resell the TNT products.  However, professional geospatial analysis is a complex undertaking.  MicroImages discontinues resellers for various reasons.  Foremost among these is that it is not in our interest, your interest, or the interest of prospective new clients to be put in contact with a reseller who makes little or no effort to use and understand the TNT products.  As a result, they can not help design or participate in projects, contribute input to MicroImages product improvement and development, or effectively promote the TNT products.      

Canada.
GlobalPoint Technologies.  [Steven Ge] located in Richmond is discontinued.

China.
Spatial Port Network Technologies (SPNT) Ltd.  [Guowei Wang] located in Beijing is discontinued.

Egypt.
iTarget.  [Sherif Khattab] located in Cairo is discontinued.

Germany.
geo-konzept GmbH.  [Thomas Muhr] located in Adelschlag is discontinued.

Ghana.
Dei Consult.  [Alfred Dei] located in Cape Coast is discontinued.

Guatemala.
SAESA.  [Eddie Alveno] located in Guatemala City is discontinued.

Mexico.
Caddland.  [Salvador Silva] located in Guanjuarto is discontinued.

Netherlands.
eXQte.  [Hans van der Maarel] located in Klundert is discontinued.

Pakistan.
Digitek.  [Hassan Mian] located in Lahore is discontinued.

Poland.
EKO-GIS Services [Marek Kamieniecki] in Szczecin is discontinued.

Russia.
RACURS Co.  [Dmitry Kochergin] located in Moscow is discontinued.
ESTI MAP Ltd.  [Alexei Prossianov] located in Moscow is discontinued.

Serbia and Montenegro.
PrimaRes d.o.o.  [Jasmin Babic] located in Belgrade is discontinued.

Spain.
URBITEC NETWORKS, S.L.  [Marina Emelianova] located in Madrid is discontinued.

Switzerland.
GeoMatics.  [Isabella Pacchiani] located in Geneva is discontinued.

USA, Florida.
Satellite Imaging Group.  [Sean Morrissey] located in Coconut Creek is discontinued.

USA, Colorado

United Arab Emirates.
Global Environmental Solutions.  [Saleh Al-Bashir] located in Abu Dhabi is discontinued.

Appendix: Abbreviations

For simplicity, the following abbreviations were used in this MEMO.

RV7.0 = the official and first release of RV7.0 of the TNT products matching the version on the CDs distributed.

PV7.0 = any version of the TNT products created subsequent to RV7.0 to which patches have been applied to update RV7.0 or a  PV7.0.

DV7.1 = The partially complete development version of the TNT products which will eventually be officially released as RV7.1 when complete.

W95 = Microsoft Windows 95.

W98 = Microsoft Windows 98.

WME = Windows Millennium Edition.

NT or NT4 = Microsoft NT 4.0 (the TNT products require the use of NT4.0 and its subsequent Service Packs).  NT4 now has a Service Pack 6a available.  Windows 2000 now has Service Pack 2, which is recommended if you are working with large files.

W2000 = Microsoft Windows 2000.

XP = Microsoft Windows XP.

Mac 10.3.5 = Apple Macintosh using Mac OS X version 10.3.2.

MI/X = MicroImages’ X Server for Mac and PC microcomputer platforms and operating systems.

GRE = MicroImages’ Geospatial Rendering Engine, that is at the heart of most MicroImages products.  The current GRE will respond and render requests from either X/LessTif or Windows.

VB = Microsoft Visual Basic

MB = megabyte (1,000,000 bytes)

GB = gigabyte (1000 megabytes) or 10⁹ bytes

TB = terabyte (1000 gigabytes) or 10¹² bytes

©MicroImages, Inc. 2010 Published in the United States of America
11th Floor - Sharp Tower, 206 South 13th Street, Lincoln NE 68508-2010   USA
Business & Sales: (402)477-9554  Support: (402)477-9562  Fax: (402)477-9559
Business info@microimages.com  Support support@microimages.com  Web webmaster@microimages.com

---