|
View complete document in PDF
Release of V5.80 TNT products
January 1998
Table of Contents
Color Plates
Release
Notes Index
MicroImages is pleased to
distribute V5.80 of the TNT products and the 43rd release of TNTmips.
This release has been delayed by the incorporation of three system-wide
modifications which required extensive testing, as they impacted most processes.
These overall modifications include the use of the new visualization (display)
process throughout; final adjustments to accommodate 2-byte languages such as
Japanese, Korean, and Chinese, as well as other non-romance languages; and the
addition of a floating license manager for enterprise applications of the TNT
products.
V5.80 introduces a prototype of a new GeoFormulaTM process
which you can use to directly view or save rasters from equations that you
create to define how your raster, vector, and TIN objects are to be combined.
TNTedit is being released as a product that can be purchased separately
at a lower price. TNTedit has been added to the TNT product suite
for those who need its geodata creation tools but do not need the many other
processes built into TNTmips. TNTmips will continue to provide the
full object editor process, which is functionally identical with the separate TNTedit.
The following processes have had major features added:
·
Mosaic: you can now mosaic georeferenced, non-georeferenced,
or mixes of both.
·
Styles: The interactive point style editing tool
has many new features including the import and editing of symbols and characters
from TrueType fonts.
·
SML: 158 new functions have been added to
provide access to and from vector, CAD, and TIN objects; draw into a view; and
to control styles of the elements drawn.
Twelve new Getting Started tutorial booklets are shipping
in printed format. All 33 Getting Started booklets which have been produced,
including several with revisions, are included on the V5.80 CD in PDF
format.
Over 200 new feature requests submitted by clients and MicroImages staff were
implemented in various V5.80 processes since V5.70 was shipped.
However, an even larger number of additional requests for new features was
logged from the same sources in the same period.
As usual, details on all the following and other new features
in V5.80 can be found in their expanded description in detailed sections
of this MicroImages MEMO.
Floating licenses are now available for sharing a TNT professional
product around a network. This new license allows a single TNT product to
move or "float" around a network for use on any Windows or UNIX
platform.
A new TNTeditTM professional product is available. It consists
of the following integrated processes assembled from TNTmips:
visualization (in other words, all of TNTview), object editor, import,
export, georeference, digitizer support, and some utility features.
TNTview has been expanded so that it can create and use the TNT
geospatial programming language (called SML). With the addition of tools
to create interfaces and complete applications, SML provides the means to
create and distribute advanced geospatial analysis and visualization projects
and products. TNTview can also execute new processes created entirely
with the thousands of functions in the TNTsdk (Software Development Kit).
The size of the raster objects which can be used in TNTlite has been
increased to 640 by 480 pixels to accommodate the images created by many
low-cost digital cameras.
All TNT products operate under the latest release of MacOS 8.1 and under
the latest beta release of Windows 98. When using the MacOS 7.x or 8.x, the TNT
products now dynamically manage memory. No more manual memory adjustments.
There are now a total of 33 color illustrated Getting Started tutorial booklets
of ~700 pages shipped with each TNT product, including TNTlite.
The on-line Reference Manual provided with each TNT product now totals
over 3000 pages.
The new visualization process that combines multiple 2D and 3D viewing into a
single process has been completed and is integrated into almost all TNT
processes. As a result, the advanced layer control panel is now also in use in
most processes. The first of many GPS support features now plots the position
read from an attached GPS unit into the corresponding geographic position in the
view.
Scripts prepared with the geospatial programming language (SML) available
with each TNT product, including TNTlite, can now be stored as
objects in Project Files and selected to automatically compute a display layer
in the visualization process.
TNTmips and TNTedit can now export to the following formats:
ESRI's E00 format; ESRI's coverage files; the Encapsulated PostScript (EPS) file
used in Adobe Illustrator and FreeHand; and into the world files used in the
Virtual Reality Modeling Language (VRML).
The raster profile viewing capability can now simultaneously display the
profiles from many rasters in various colors, symbolism, and scales for easy
comparison.
Templates can be created to control how database tables are imported. These same
templates can also provide the information on how a series of related tables
should be linked up within the associated TNT relational database.
Attributes linked to graphical elements in a vector object or to other tables
can now use multiple fields as key fields. For example, a FIPS code is made up
of a field combining the state and county codes. If the second table has a
separate field for the state and for the county codes, the relational linkage
can be made by simply using both fields.
Polygons selected by query or other means can be used to automatically extract
and create a series of separate raster objects containing the area of each
polygon from a large image.
Raster to vector conversion can use queries and many other new, advanced control
procedures.
The object editor has new features for improved line snapping, semiautomatic Z
value labeling of contours, and creating new elements offset from existing
elements.
A new process is available to create and use GeoFormulasTM. A
GeoFormula is an algorithm which relates raster, vector, and TIN objects in an
equation which is evaluated on demand as a visualization layer or to create a
new raster object. The objects combined by the GeoFormula need not be in the
same map projection, scale, or cover the same common extents.
An interactive procedure to allow region objects to be combined is available
wherever regions can be created or used. Using this capability in any TNT
product permits complex interactive GIS analyses to be performed between objects
with the mouse and a few keystrokes.
The mosaic process has more than doubled in capabilities and now provides
methods for fully automated mosaicking, semi-automatic bundle adjustment, and
manual mosaicking.
Symbols and characters in TrueType fonts can now be imported and edited for use
as point symbols. Important new edit tools have also been added to the symbol
editor.
Complex cartographic rendering can be accomplished by a query which also selects
the elements to be rendered using 44 CartoScriptTM functions.
Placement positions for labels and symbols can now be optimized as rendered to
avoid overlap or excessive deletions.
The geospatial programming language (SML) has been greatly expanded by
the addition of 158 new functions in several toolkits. These new toolkits or
groups of functions are now available:
·
CAD object toolkit
·
TIN object toolkit
·
drawing functions
·
serial port access functions
·
vector object toolkit
·
CartoScriptTM toolkit
·
some region analysis tools
The TNT products have been
completely internationalized for Windows and most aspects of the MacOS. All of
the user interface can now be localized into 2-byte languages such as Japanese,
Chinese, and Korean, as well as into 1-byte languages such as Greek, Turkish,
Russian, and so on. All interface components from strings in database fields to
tooltips, dialog text, and error messages can be translated.
Complex map layouts containing transparent layer features such as polygon fills
can now be printed.
First Priority.
System Level. Allow
nodes in vector objects to possess attributes and adapt other processes to
create and use such nodes. Adding attributes to nodes will allow more complex
routing and related features to be incorporated into the TNT products.
For example, an attribute of a node in a line may specify the overhead clearance
of an obstruction in a road, what kinds of turns are allowed at an intersection,
and so on.
Create a new kind of vector object which does not require that lines which cross
must intersect (as in 3D). This will be a vector object which possesses topology
but will not have any polygons. This object type will allow bridges, tunnels,
right turns only, structures, and similar features to be recorded and used in
route analysis.
There have been requests to allow an attribute table to be linked to what we
call element numbers to obtain some parallelism with this older limiting
Arc/Info concept. This is not feasible since element numbers are an internal
construct in the TNT products and change with operations on the object.
Therefore, a new element ID will be created which will be available as a hook to
which attribute tables can be linked.
Visualization. Extend the new process to provide fly-bys (any position
above terrain), drive-throughs (a track on the terrain), sail-throughs
(restricted to a plane), and other modes. Provide new tools to be used to design
the path of motion in 2D and 3D to control the 3D view. Add interactive control
of the movement for a 3D view from mouse or joystick.
Incorporate the label placement optimization algorithm illustrated via a
CartoScriptTM with V5.80 to be directly used in viewing
objects.
Add more functionality to directly attached GPS systems and as recorded
GPS-derived geodata.
Add capabilities to allow direct control of making raster layers transparent
when used as a layer (for example, use a map as a transparent overlay to an
image).
Support a view within a view concept within any 2D View window. [available now]
Styles. The improvements in designing and using Internal Styles and
CartoScripts will continue. For example, add the capability to import, improve,
and use AutoCAD points styles (in other words, blocks) and MicroStation cells as
point symbols, including their insertion into line styles.
Several weeks ago, MicroImages developed and tested a very simple and fast
method to draw hatch (line-like) pattern fills, and this function can be easily
inserted everywhere it is needed. However, before it is useful, a style editor
will have to be created or modified to enable design of such hatch fills (color,
thickness, continuity, angle, ...).
Restitution. The restitution process, or Step D in the DEM/Ortho process,
will be rewritten. The new process will allow the use of SPOT and scanned frame
satellite images to be ortho-rectified. The process will also be modified so
that it can be applied to vector, CAD, and TIN objects. Investigation will start
into the possibility of extending the process to ortho-rectify slant range RADAR
images such as RadarSAT.
Classification. A new process will be added for creating training sets
for supervised classification procedures. Continue to add new features to the
naming procedures used with unsupervised classifications and speed up its
performance.
HyperSpectral Analysis. This new image analysis process was nearing
completion with the shipment of V5.80 of the TNT products. The
prototype process should be available for download from microimages.com by the
time you read this MEMO. If you wish to experiment with this capability before V5.90
is shipped, please check its status with software support.
Import/Export. Add an import for the MapInfo internal format (TAB).
SML. Significantly expand the suite of user interface
functions. Some of this will be available by the time you receive this MEMO. Add
a suite of functions to create, read, write, and maintain relational database
tables when used as attributes or as separate tabular geodata objects. Supply
additional missing functions as identified by clients who are experienced and
active SML script writers. Those particularly interested in experimenting
with this expanded functionality can periodically download the SML
process during the next quarter. [many functions available now]
Printing. Add improved, easier, and expanded legend generation in both
the screen and print layouts. For example, provide a hierarchical-type legend
display window to TNTmips, and thus TNTview, providing similar
functionality to that found in ArcView and MapInfo displays.
Vector Extract. Modify the vector extraction process to use regions and
the region generation tools.
TNTedit. The interface will be added into TNTedit to
allow it to directly load and save E00 and coverage files (and potentially
others).
TNTatlas. Produce written instructions and any needed
software to assist in the assembly of TNTatlas CDs.
Tutorials. At least six new Ptolemy Getting Started booklets will be
prepared on such topics as:
·
Constructing HyperIndexes®
·
TNT Technical Characteristics
·
Understanding Map Projections
·
Managing Geoattributes
·
Changing Languages (localization)
·
Using the Software Development Kit
·
Introduction to Hazard Modeling
·
Introduction to DOQs from 35mm Slides
This will increase the total
number of Getting Started booklets and their sample geodata available to about
38 to 40. As usual, all these new booklets will be posted on microimages.com
during the quarter in Adobe Acrobat PDF and PageMaker files as soon as they are
available in draft form. Use your Internet access to download these new booklets
and sample geodata, and view them on your system or print them in color.
Second Priority.
Allow cut, copy, and paste between objects of different
types (for example, vector to raster and raster to vector).
Extend theme mapping to raster layers.
Populate tables by copying fields from other tables. Example use would be to
copy geocoordinate fields from one table and paste into another.
Add capability to save graphic views (histogram, X-Y plot, ...) as CAD objects
so that they can be used as a component in a map layout.
Add capability to save tabular views so that they can be used as a component in
a map layout.
Allow theme profiles (queries and display settings) to be saved and reused.
Support the inclusion of "hard edges" in TIN objects (for example,
fixed ridges, drainage, coast lines, ...) and modify the necessary processes to
use them.
Allow cut, copy, and paste between objects of different types (for example,
vector to CAD, CAD to TIN, ...).
Modifications.
Transparent changes have been
made in the MicroImages MI/X server in the past quarter to correct minor
problems. These alterations resulted in somewhat faster response in the PMac
version of MI/X. MI/X was checked out in a beta release of W98 and
runs without modification. However, MI/X was modified to allow the X
window it generates to span several screens to accommodate this important new
feature being introduced in W98. The MI/X server for dual screen W98
operation is not on the V5.80 CD and can be requested when needed via
software support. No significant future changes are anticipated in the operation
of MI/X.
Public Release.
Downloads of the MI/X
server by non-clients from microimages.com now average approximately 1300 per
week (100 for 68xxx Macs, 200 for PMacs, and 1000 for Windows products). A total
of 50,000 direct downloads have been performed since it was made available
without cost for use by others.
There are also 60 different registered international mirror sites from which MI/X
can be downloaded (see below). MicroImages projects from this information that
hundreds of thousands have downloaded and tried these MI/X products. The
minor flaws these users have found and reported have helped MicroImages further
perfect the MI/X server. Several of these users communicate with
MicroImages each day requesting changes or assistance. Most are referred to the
Frequently Asked Questions (FAQ) section which they have obviously not read, but
some get direct responses when new questions are raised.
Universidad
Autonoma de Madrid, SPAIN joao.damas@uam.es
Grand Valley State University, USA behresm@river.it.gvsu.edu
Graduate School of Information Sciences, Tokoku University, JAPAN harada@cc.tohoku.ac.jp
Technical University of Lodz, POLAND pczyryca@itr2.p.lodz.pl
Columbia Union College, USA sopwith@cuc.edu
unknown (University of Michigan), USA scittven@umich.edu
University of California at San Diego, USA mstark@ucsd.edu
ICL, JAPAN hayase@po.jah.or.jp
Embrapa - CNPGC, BRAZIL carlo@cnpgc.embrapa.br
Somerset Schools, USA matt@musictown.mec.edu
Oracle Corporation Japan, JAPAN mkanda@jp.oracle.com
The University of Aizu, JAPAN takafumi@u-aizu.ac.jp
Pacific Link Communications Ltd., HONG KONG edmund@hkabc.net
Student at Cambridge University, GREAT BRITAIN mb245@cam.ac.uk
Netmar, Inc., USA cengiz@netmar.com
TU Bergakademie Frieberg, Institute for Geology, GERMANY fuerst@geo-tu-freiburg.de
Gesellschaft fuer wissenschaftliche Datenverarbeitung mbH, GERMANY emoenke@gwdg.de
GeoQuest, USA eragan@houston.geoquest.slb.com
Graduate School of Mathematical Sciences, University of Tokyo, JAPAN jzh@ms326kaz.ms.u-tokyo.ac.jp
University of Hamburg, GERMANY larsson@infomatik.uni-hamburg.de
Carnegie Mellon University, USA nosinut@cmu.edu
Uniformed Services University bob@bob.usuf2.usuhs.mil
Science University of Tokyo, JAPAN narayan@sut.ac.jp
EfesNet (Yesil Ege Internet & Communication Services Inc.), TURKEY hamarat@efes.net.tr
University of California at Santa Cruz, USA stmc@cats.usc.edu
Zentralbereich Elektronenmikroskopie Technische Universitat Hamburg Hamburg,
GERMANY priese@tu-hamburg.d400.de
Instituto de Quimica da UFRJ, BRAZIL jomal@ig.ufri.br
Netlight GmbH, GERMANY rbear@netlight.de
Nagova Municipal Industrial Research Inst., JAPAN ogawa.kiyoshi@nmiri.city.nagova.jp
?, GREAT BRITAIN andrwe@hougie.co.uk
Kagoshima University, JAPAN tetsu@eee.kagoshima-u.ac.jp
University of Witwatersrand, SOUTH AFRICA jon@cs.wits.ac.za
PVT.NET, CZECH REPUBLIC zdenekh@pvt.net
Lakehead University, CANADA apcarr@flash.lakeheadu.ca
Mediasoft a.s., CZECH REPUBLIC noas@mediasoft.cz
United Network Technologies Inc., REPUBLIC OF CHINA james@mail.unt.com.tw
Seagate Technology, USA tim_t_walker@notes.seagate.com
Megamac, BRAZIL webmaster@megamac.com
Ryukoku University, Faculty of Science and Technology, JAPAN kjm@rins.ryukoku.ac.jp
DLR, GERMANY jens.schleusener@dlr.de
Shijiahuang Postal College, CHINA xzh@sjzpc.edu.cn
Sunsite at the University of Tennessee, USA uther@utk.edu
James Cook University, AUSTRALIA kilroy@mail.zce.jcu.edu.au
Independent Computer Retailers, AUSTRALIA helpdesk@icr.com.au
Universidad de los Andes, COLUMBIA erojas@euclides.uniandes.edu.co
Sizzling Platter, Inc., USA
john_hardin@rubyriver.com
Brunel University, GREAT BRITAIN tony@belle.nd.rl.ac.uk
University of Girona, SPAIN rocher@gnomics.udg.es
VP.pl Internet Services, POLAND msz@vr.pl
Supelec, FRANCE claude.bocage@supelec.fr
WINS, USA andrew@netcasting.net
ASM Software, GREAT BRITAIN andrewbetts@programmer.net
INPE - Instituto Nacional de Pesquisas Espaciais ulisses@dem.inpe.br
Johns Hopkins University, Homewood Academic Computing, USA sujal@jhu.edu
Osaka University, JAPAN kitagawa@ee.es.osaka-u.ac.jp
Trinity College, GREAT BRITAIN acn1@cam.ac.uk
net CCI, USA colin@net-cci.com
MI/X Feedback.
The following is typical of the feedback from the FREE MI/X
products and provides insight into how they are being used around the world.
email from Ola Persson smurfen@ludd.huth.se
on 4 September 1997
"Your X Server for
Windows 95 is the best thing I have seen for a LONG time. I have been forced to
have a UNIX partition at home, in order to do cad/cam in Xwindows at home. I am
on a LAN in my dorm, so I usually go home when the computer labs are
full...."
email from Paul Whittington
paul@sage.inel.gov on 11 September 1997
"I think MI/X is
wonderful, and thanks for making it freely available."
email from Stuart Siegel
ssiegel@cmu.edu
"Thanks for making an
excellent product available free!"
email from Gurpratap Virdi
virdigur@ee.mcgill.ca
"Hi! I am a Computer
Engineering student at McGill University, Montreal. I wanted to thank you for
making available the MicroImages X server as freeware. This has enabled me to do
all my assignments at home without spending a penny, opposed to all those
expensive shareware x-servers. Thank you again."
email from Jeff Sheremata <jshereme@maildrop.srv.ualberta.ca
"Over the past two weeks
I have been using MI/X for my engineering graphical analysis and I am
very impressed with it's performance. Using Matlab on my host's server, my plots
essentially appear instantaneously on my home computer screen once the command
to plot them is entered. I have not yet used Matlab sitting in front of an UNIX
box or through ethernet connection. Once again thanks for your technical
support." [This student user of MI/X is using a cable modem to
connect from his home to the university host. From what we can determine to
date, a cable modem is at least as fast as a T1 line when using MI/X as
an interface.]
email from Brian Ruppert
brianr@nightstar.ml.org
"This is not a request
for support. Trust me. :)"
"Without going into a long story about myself, my life, my computer, and
the benefits of managed sheep herding, I would just like to let your corporation
know that the MI/X server has finally provided me with an easy-to-use,
free solution to my previous inability to access X apps from my Linux box on
Win95 computers."
"My sincerest regards go out to the developers of this product. Thank
you."
email from Thomas Cameron
tcameron@three-sixteen.com.
"Two Words: Holy [expletive]
!!!!"
"I am completely stoked that there is a free X server that runs under NT
that works at all, much less one that works so well!!!"
"Thanks a million times, you have made my life much, much easier with this
product!"
email from John jsillers@austin.ibm.com
"Well, I had my Mac long
before I joined IBM. It turns out that having a Mac at IBM is not that unusual.
I am very impressed. I spent ~$200 of my own money for eXodus. After about 9
months Apple changes OpenTransport and eXodus no longer worked. There was no
upgrade path and basically I would have to spend another ~$200. Since I don't
use X THAT much from home I went without... So I REALLY appreciate MI/X
!!!! It works great and I think is quite a bit faster than eXodus."
"It seems like there should be a middle ground. $200 was far more than
X-at-home was worth to me. But I have to say that having MI/X free makes
me feel guilty (especially when I had to send a note for support). If you are
every in Austin I'll buy you dinner!"
Introduction.
A
new category of license can now be purchased for all the TNT products. It
is a floating license used in enterprise-oriented network situations. No license
previously purchased by any client to use a single-user/single-processor or a
multiple-user/single-processor setup with your V5.70 or earlier TNT
product will be changed by the addition of this new license category.
A floating license still requires the physical authorization key but allows a
single TNT product to be "checked out" or shared via the
network and executed wherever it is needed. With a floating license, the
physical authorization key is not moved between platforms! The check-out,
check-in authorization scheme used with this floating license is a commercial
license manager called FLEXlm, which is in turn controlled by the TNT
physical authorization key. FLEXlm is very commonly used to manage the floating
licenses of other products such as Arc/Info and ERDAS.
A floating license allows an organization to get more use from a single TNT
product. For example, installation of three floating licenses might satisfy a
network of users with 20 computers who do not use TNTmips full-time but
only as the need arises. Without employing floating licenses, this organization
might require at least five or six conventional single-user licenses to
accomplish the same access to TNTmips. And even with a larger number of
single-user licenses, they would still be constantly manually swapping the
physical authorization keys among the 20 computers. As a result of the
significantly expanded flexibility of a floating single-user license, its price
will be 20% higher than the equivalent single-user fixed license.
The following paragraphs explain the various types of licenses which are now
available for the use of the TNT products.
Introductory Information.
These
general conditions apply regardless of the type of TNT product purchased.
TNT software can be installed from the official TNT CD anywhere on
the network--local machine, remote machine, and on several machines of differing
types. Placing, installing, and keeping the TNT executables on many
different computers of different types is not controlled by your license to the TNT
product. It is the actual startup and continued operation of the product that
will be permitted or prevented by the MicroImages hardware key and/or the FLEXlm
license manager, according to the type of license (in other words, type of
operation) you have purchased.
The TNT product can be operated via X windows from a remote X terminal or
a Mac or Windows-based computer using the MI/X or some other X server.
Some or all of the TNT Project Files can be kept and used on the local
computer with the physical authorization key or on a file server without a key
anywhere on the network. In other words, project materials can be stored
anywhere that file storage resources are provided by the network.
Single User License.
(Single-User/Single Processor)
This
license is widely used on stand-alone, local computers which may or may not be
part of a network. It permits the TNT product it controls to be easily
moved around by manually moving the license's physical authorization key from
computer to computer.
The physical authorization key must be installed on the computer which will then
be permitted to execute one, and only one, copy of the TNT product. A
second copy of a TNT product cannot be started. However, many
different TNT processes can be started simultaneously within the single TNT
product as well as simultaneous use of other non-TNT products.
The TNT software (executables) can be installed on as many computers of
varying types as desired, but will execute only if the physical authorization
key is attached.
The key can be physically moved from computer to computer by simply unplugging
it and replugging it into the same kind of port (parallel or serial) or the
Apple Developer Bus (ADB).
For example, this license permits the installation of the TNT product
software on an office computer and a home computer of a different type. The TNT
product is then used exclusively at each location by moving the physical
authorization key between the two computers.
This license only requires the FLEXlm license manager to be installed on the
UNIX or NT computer with the key attached if the single operation of the TNT
product is going to be from a remote X terminal or remote computer using the MI/X
server.
Multiple User License.
(Multi-User/Single Processor)
It
is most common for this license to be used by remote access via X terminals or
other computers on the network which are using the MI/X or some other X
server. It can also be used on a stand-alone machine to start several copies of
the TNT product.
The physical authorization key must be installed on the computer which will
execute all copies of the TNT product. A two-user license allows two
separate copies of a TNT product to be started, each of which can
simultaneously use the multiple TNT processes within that product.
Similarly, a three-user license allows three copies, and so on.
The TNT software executables can be installed on as many computers of
varying types as desired, but all of the authorized multiple copies must be
executed on the computer which has the physical authorization key attached.
The key can be physically moved from computer to computer by simply unplugging
it and replugging it into the same kind of port (parallel or serial) or the ADB.
This is not common with this license type, as several other users may be
remotely using the license.
This license always requires the FLEXlm license manager to be installed on the
computer with the physical authorization key attached. It is the FLEXlm license
which, together with the physical authorization key, allows the authorized
multiple copies of the TNT product to be operated simultaneously.
Before it is shipped, MicroImages encodes the physical authorization key to run
the number of simultaneous copies purchased. Thus, it is not necessary to obtain
any kind of authorization code from MicroImages to use this license. It is also
not necessary to obtain any authorization code when changing computers, changing
operating systems, or even moving between computers. Simply attach the key and
reinstall the FLEXlm license manager. This can easily be done as part of the
reinstallation of the TNT product.
Floating License. (Single User/Floating
Processor)
This license is for institutional
networked situations where TNTmips will be shared on a network among
multiple users who will use it only part-time. This kind of license creates a
"virtual" authorization key which "floats" from computer to
computer under the control of the physical authorization key and the FLEXlm
license manager. It allows any computer on the network which has the exclusive
use of the virtual key to check out the virtual authorization and use the TNT
product. The network can be in a single office, between buildings, or any other
structure which will support access to the FLEXlm license manager.
Each floating license allows a single use of a TNT product at a given
time. If a second attempt is made anywhere on the network to start a second copy
of the TNT product, that location will be notified that the product is
being used until its current user exits the entire TNT product. However,
more than one floating license can be operated on a network so that two or more
simultaneous floating operations of TNT products can be authorized by
purchasing additional single-user floating licenses.
The physical authorization key of the proper type (serial or parallel) must be
attached to an operating computer on the network. The FLEXlm license manager
must be installed on this computer to create and serve up the virtual
authorization key(s) to any other computer on the network. The computer using
the license manager can be any UNIX or NT platform supported by the TNT
products. The floating license can float to and be used on any UNIX, NT, or W95
platform, depending upon the license level purchased. MicroImages and the TNT
products do not need to know anything about the computer where the license
manager is to be installed. Similarly, MicroImages and the TNT products
do not need to know anything about the remote computers which might use the
floating license.
A floating license purchased at a UNIX level must be installed (key and license
manager) on a UNIX computer. However, it can float with all authorized features
to any UNIX or Windows computer on the network for which TNT products are
shipped.
A floating license purchased at a Windows level may be installed (key and
license manager) on a Windows or UNIX computer but cannot float to a UNIX
platform. It can float to a Windows or Linux computer. The display level (D40,
D50, D60) will control the size of the display window on that
remote computer using the virtual key. Mac and PMac computers can only be used
as remote X terminals with a floating license.
More than one license manager with a physical license key can be set up on a
single network. One physical key can be used to control one or more floating
licenses of a given type (in other words, UNIX level or Windows level).
The TNT software can be installed all over the network on as many
computers of varying types as desired, ready to run the floating license as soon
as a virtual authorization key is available and secured. This results in a lot
of software duplication and complicates the management of the TNT
products. As a result, floating license installations may maintain the actual
executables on a single file server. A TNT product using a floating
license can be set up to automatically load and execute as needed each processor
module from this remote file server for the specific computer type using the
virtual authorization key.
Before it is shipped, MicroImages encodes the physical authorization key to run
one or more floating licenses purchased, as well as any extended features. It is
not necessary to supply any kind of information about your PC or a workstation
I.D. code to obtain an authorization code from MicroImages to install the FLEXlm
license. The physical authorization key can be manually moved from computer to
computer by simply unplugging and replugging it in to the same kind of port
(parallel or serial) or the ADB. The FLEXlm license manager can then be
reinstalled at the new location. This may be periodically required if the
license server fails or computer resources are being reallocated or rearranged.
TNTedit is being released
as a new product for the first time as part of V5.80. All clients who can
install TNTmips 5.8 can also install TNTedit 5.8 at no additional
cost. However, it is not necessary to do this except as an experiment, since the
object editor and other processes provided in TNTedit are identical to
those provided in TNTmips.
What is it? TNTedit is a product which fits into an intermediate
position between TNTview and TNTmips at an intermediate price. It
consists of the following integrated processes assembled from TNTmips:
visualization (for example, all of TNTview), object editor, import,
export, georeference, digitizer support (optional product X3 is included
as standard), and some utility features. Since SML is now a part of TNTview,
it is also a part of TNTedit. All the powerful features in TNTview
are provided, including 2D and 3D visualization, interactive GIS, GeoFormulas,
limited size layout and printing, and so on.
Why have it? This new product fits into two niches. First, it allows TNT
clients who create original vector or CAD geodata to operate more stations at a
lower cost. The object editor used in TNTmips and TNTedit is
filled with labor saving concepts; however, creating, editing, or upgrading
vector and CAD geodata from scanning and conversion, tracing, digitizing, heads
up digitizing, photointerpretation, and so on, is still time consuming. This
creative activity requires a lot of dedicated "console" time using the
object editor, which can now be purchased via TNTedit.
It has also been made very clear from many GIS and remote sensing sites which
are locked into other competing products by years of investment and experience,
that a good, interactive object editor is needed to create or update their
project materials. TNTedit 5.8 provides MicroImages' powerful object
editor for use with Arc/Info and ArcView; can run concurrent with these products
on the same computer; and easily exchanges vector data with them via the import
and export of their native coverage, E00, or shapefiles. During the next
quarter, TNTedit will be modified to directly use these ESRI formats
without the need for their import or export into a TNT Project File. This
will allow these ESRI files to be directly edited and modified in TNTedit
with both the TNTedit and ESRI products running concurrently on the same
machine.
Similarly, the powerful image, vector, CAD, and TIN features of TNTedit
can be applied by those who use MapInfo, ERDAS, ER Mapper, PCI, ENVI, and other
commercial products, since their geodata formats are also supported. They can
now interactively create or edit any TNT objects and convert them into a
form suitable for use in the analytical process in these products (for example,
convert a raster to a vector object, a database table(s) into a vector object,
...).
Options? No options are available for purchase with TNTedit except
annual maintenance. In contrast to TNTmips, you can use TNTedit
at any screen resolution you choose as is also the case with TNTview.
This makes TNTedit particularly powerful if run on a platform with dual
monitors (common with MacOS and to become more common with the release of W98). You
cannot purchase large format printing, scanning, or TNTlink as part
of TNTedit or TNTview.
Prices? TNTedit is priced intermediately between TNTview
and TNTmips as follows. Please take special note that no optional or
other special features (except product X3 = digitizer support) are
bundled with TNTedit for any platform. TNTview can be upgraded at
any time to TNTedit for full credit. Similarly, TNTedit can be
upgraded to TNTmips at any time to obtain access to its processes such as
mosaicking, image classification, large format color printing, and so on.
Shipping is not included in the prices shown below for TNTedit. However,
shipping is included in the annual maintenance cost by UPS in the NAFTA nations
and air express to all other nations. Those Getting Started booklets applicable
will be included with each TNTedit product as well as the on-line version
of the complete reference manual for all the TNT products.
for NAFTA sites.
·
$3000 for Intel and Mac platforms: MacOS, Windows,
and LINUX [product E30].
(annual maintenance will be $500 [product A5/E])
·
$4000 for the DEC Alpha platform when used with
Windows NT [product E40].
(annual maintenance will be $600 [product A6/E])
·
$5000 for the various workstations using variants
of UNIX [product E50].
(annual maintenance will be $900 [product A9/E])
for International sites.
·
$3600 for Intel and Mac platforms: MacOS, Windows,
and LINUX [product E30].
(annual maintenance will be $600 [product A5/E])
·
$4800 for the DEC Alpha platform when used with
Windows NT [product E40].
(annual maintenance will be $700 [product A6/E])
·
$6000 for the various workstations using variants
of UNIX [product E50].
(annual maintenance will be $1000 [product A9/E])
Installed Sizes.
Loading the TNTedit 5.8 processes onto your hard drive
(exclusive of any other products, data sets, illustrations, Word files, ...)
requires the following storage space in megabytes.
·
PC using W31 34 MB
·
PC using W95 42 MB
·
PC using NT (Intel) 42 MB
·
PC using LINUX (Intel) 27 MB
·
DEC using NT (Alpha) 46 MB
·
Mac using MacOS 7.6 (680xx) 44 MB
·
Power Mac using MacOS 7.6 and 8.0 (PPC) 48 MB
·
Hewlett Packard workstation using HPUX 37 MB
·
SGI workstation via IRIX 44 MB
·
Sun workstation via Solaris 1.x 33 MB
·
Sun workstation via Solaris 2.x 33 MB
·
IBM workstation via AIX 4.x (PPC) 42 MB
·
DEC workstation via UNIX=OSF/1 (Alpha) 49 MB
New Features.
The
following is a summary of the new features added to V5.80 of the TNT
products which are now available in TNTview 5.8. Detailed descriptions of
these and many other new features can be found in the appropriate section below
entitled New TNT Features.
·
TNTview can run executable programs
compiled in C using the TNTsdk on a TNTmips platform.
·
SML, the geospatial programming language,
is now provided as an integral procedure to create or run SML scripts
(more details are provided immediately below).
·
The new Visualization process incorporating
integrated 2D, 3D, and stereo is now fully functional and integrated.
·
GeoFormulas can be made and used.
·
Regions can be interactively combined to support
more complex interactive GIS functionality.
SML Added.
Gradually, SML in V5.70,
5.80, and 5.90 is being repositioned as the basis for the creation
and distribution of special purpose geospatial products with targeted or private
markets. Its incorporation and use in the inexpensive TNTview is part of
this evolution. As a result, TNTview and TNTlite are moving into
competition with widely distributed commercial products such as ArcView and
MapInfo. However, SML is expanding to provide many more functions than
either of these, since the TNT products already manage more integrated
objects and datatypes (for example, rasters and TIN objects, all platforms, 1 to
128 bit rasters of many types, ...) and provide a broader range of analysis
functions. For example, as many already know, ArcView and MapInfo are not
advanced in their use of raster datasets. Similarly, they have no features for
the analysis of images, the creation and use of surfaces from TINs, directly
using topological objects, and so on. However, as an integrated geospatial
programming language, SML will differ from these in a number of other
unique ways.
The most important distinction is that the development of SML features is
not focused upon the creation of public and widely distributed products. SML
is being focused upon the creation of products for direct use by professionals
within limited professional interest groups. Thus, MicroImages envisions the end
users of your scripts as a group of clients or professionals already working
with you, the creator of the script. These might be other members of your
organization; your professional peers; your consulting customers; those who
subscribe to your image, mapping, GPS, database, or other geodata collection and
preparation services; a cooperative; members of a professional association; and
so on.
TNTview on any supported platform can create and use scripts prepared
with TNTview or TNTmips on any other platform without
modifications. Let's make this clearer as it is unique to the TNT
products--a single SML script will now run without modification or change
on any platform with any TNT product except the FREE TNTatlas
product. Yes, all these same TNT products provided within TNTlite
can also run the SML script(s) as long as the sizes of the objects
created conform to the limits imposed by TNTlite. Project Files are also
transparent across all operations, so your project materials can also be
immediately used in these scripts wherever they roam. Can any of this be
accomplished within ArcView or MapInfo at approximately the same price?
|
REMEMBER: The
scripts and products you prepare with SML are automatically cross
platform. Any script can be immediately used without alteration by any TNTmips
or TNTview on any computer platform for which they are available.
|
SML Modifications since V5.80 CDs.
Advances
in SML are pressing forward at a rapid pace. In preparation for a
demonstration to a group of agricultural managers for various corporations, a
simple prototype of a sample of a self-contained SML agricultural field
image application will be available for your testing and modification by 10
February. The creation of this prototype product has required that all the
additions and modifications to SML and TNTview outlined in this
section will be completed by the time you read this MEMO. Please contact
software support to obtain and experiment with the prototypes of all these new
modifications. The sample script(s) involved will, as usual, be posted on the SML
script exchange at microimages.com, but you will need a new display process to
use these post V5.80 scripts.
Interface Tools.
The
TNT drawing tools controlled by the mouse (draw lines, circles, ...) can
be used in your scripts. A series of other initial modifications have been made
to allow you to use the View window and other interface components in a script.
For example, you can now add your own 16 by 16 bit icons into the toolbar at the
top of the View window to control a jump to, and use of a subsection of your
script. To avoid confusion with your icons and processes, most of the icons
placed by TNTview in the View window toolbar can be suppressed by your
script which presents a View window as part of its interface.
The sample agriculturally-oriented SML application uses the new interface
features. After the SML application is started from its icon on a toolbar
menu, it presents a simple dialog box asking for the composite colorinfrared
image to be displayed and subsequently used to compute relative canopy biomass.
Once these inputs are made for the images of a farm, a View window is shown
containing the reference image. The cursor in the View window is automatically
placed in the polygon drawing mode. After a polygon is drawn around a crop
field, the script continues on to compute and display the biomass within this
field using the following steps:
·
create a temporary region object from this
polygon,
·
use the region to compute the canopy biomass for
the cells it inscribes in the color infrared image in the view,
·
scale the biomass range in these cells into 10
intervals to be portrayed in 10 bright colors,
·
assign each biomass cell to interval and assign
its color,
·
replace the cells in the original image inside the
polygon with these new color cells representing 10 possible levels of canopy
biomass.
Helptips.
In
the above sample biomass application, the beginning user may not know what to do
if the cursor is in the view waiting for the polygon to be drawn. A new variant
on the datatips interface component is used to provide simple instructions
called "helptips" right at the point of the cursor. If the cursor is
in the view and stationary long enough (say two seconds), a helptip will be
displayed such as "Depress the left mouse button and draw a polygon".
After drawing part of a polygon and waiting, the following helptip appears at
the point of the cursor: "Depress the right button to close this
polygon". The message strings in these helptips and their associated time
delays are imbedded directly in the SML script. Any drawing tool is
available in the script and can have such helptips inserted into it.
Binding Scripts and
Data.
Scripts
can now be stored as an object in any Project File. Thus, the SML script
to process and display the geodata in a Project File can be placed into and
moved around freely with it. Scripts and Project Files are operating system
transparent, so anything you create can be immediately moved between Windows,
UNIX, and Mac platforms by network or CD, 'no java'! If you create a standard
geodata Project File, add to it your SML script(s). You can transfer and
use this application on any platform equipped with TNTview, TNTedit,
TNTmips and their equivalents in TNTlite. This script plus geodata
binding, coupled with the unique startup features outlined below, make your SML
product very easy to use, flexible, available on many platforms, Internet
transportable, and unique.
A simple example of this binding would be to put commercial image sets into a TNTmips
Project File for a fixed area being ordered (for example, a quadrangle or farm).
Then copy your SML agricultural analysis script, similar to that
described above, into the Project File. Your analysis application can then be
run automatically accessing the proper images using the new startup features
introduced below. When perfected, this approach is similar to clicking on a
document on the desktop and starting the application with the document inserted.
It improves on this theme by providing various levels of protection to your
document = Project File and your application = SML script and by
automatically operating on any popular platform and operating system.
Starting Script from
Icons.
Directly.
The script stored in a subobject of a Project File or elsewhere can be
automatically started from an icon you create and place on the desktop of your
Windows, UNIX, or Mac platform. When you click on your icon, it will then run
your own autostart SML process as follows:
·
MI/X will be automatically started in the
background,
·
TNTview will be started in the background,
·
your SML script will be automatically
started using the geodata in the project file,
·
the interface created by your script will be
exposed in the MI/X window, and
·
depending on your script design, the geodata in
the attached Project File will be automatically analyzed, displayed, or
otherwise processed.
Via
a Toolbar Menu. An alternate startup procedure is available if several
scripts are to be provided so that your user can select from a series of your SML
procedures or products. When they click on your icon on their desktop, they will
run your menued SML process as follows:
·
MI/X will be automatically started in the
background,
·
TNTview will be started in the background,
·
your toolbar menu will appear containing 32 by 32
bit TNT icons/tooltips, and
·
selecting an icon will run that SML script
and so on as outlined above.
For
example, one icon on the desktop of any TNTview-equipped platform could
run a standard script to provide for locating and choosing the geodata object
needed, the script could analyze it, and finally one could print it with a
prepared layout. Obviously, you can also build a single autostart script to do
all of these steps in sequence, but often the beginning user of your products
might have less difficulty using a sequence of simpler, semi-isolated steps.
Setting up a Start-up. A toolbar menu of your icons for your SML
scripts and product can be created by placing all your SML scripts into a
directory. This is the directory to which you assign the startup icon you create
on the desktop. In each of these scripts, you will have imbedded your own 32 by
32 bit TNT icon. All icons used within the TNT products have been
created in a TNT icon editor. It will now be provided for your use in
creating TNT icons.
Accessing TNTview. When you create any toolbar menu, it will
automatically contain, at the extreme right, a TNT icon to exit from TNTview.
Also, since you do not see TNTview when your icons and scripts are being
used, an icon to provide access to TNTview will automatically appear just
to the right of the exit icon in your toolbar menu. The user of your product
need not be concerned about the use of the advanced features provided by TNTview
unless you or they are interested in learning more.
More SML Changes for V5.90.
Introduction.
V5.90
of SML will provide even more tools to create complex interfaces for your
SML scripts such as dialog boxes, legends, and other user interface
design and operation tools. You will also be able to encrypt your scripts so
that their logic and algorithms cannot be read by others.
A number of you are already at work developing commercial products using SML.
Some will be privately distributed for sensitive activities confined within a
corporation. Some are being created to sell independently with a TNTview
product. Still others will become available for general use and will be promoted
by MicroImages on behalf of their creators. MicroImages will also distribute
with V5.90 more sample product SML scripts with their own user
interfaces to demonstrate simple products and to serve as models to help you
create your own products and interfaces.
Gradually, SML in V5.70, 5.80, and 5.90 is being
repositioned as the basis for the creation and distribution of special purpose
geospatial products with targeted or private markets. It is thus moving in the
direction of competing with ArcView and MapInfo. However, as an integrated
geospatial programming language, it will differ from these other commercial
products in a number of ways.
First of all, we envision the end user of these scripts as a group of clients
already working with you, the creator of the script. These might be other
members of your organization; your consulting customers; those who subscribe to
your image, mapping, GPS, database, or other geodata collection and preparation
services; a cooperative; members of a professional association; and so on.
Second, it will be possible, by the use of an encryption process introduced
below, to protect the intellectual ideas incorporated into your scripts and to
control exactly who has access to use them. This will be accomplished by tying
all scripts to the hardware authorization keys used with TNTmips, TNTedit,
and TNTview. In other words, the protection of the TNT keys will
be extended to protect your SML products.
More Sales
Pitch.
At
a minimum, all the powerful features of TNTview will be available with
the SML based products you distribute. Does ArcView or MapInfo have the
powerful 2D and 3D visualization tools, interactive regional analysis,
import/export, and other advanced tools built into the base TNTview
product or even available from the myriad of add-ons which must be bought?
However, your SML applications can still look simple and easy to operate
to the new or inexperienced user. For example, the availability of TNTview
can be hidden as an icon on the toolbar containing icons to start your SML
products until it is needed by a more experienced user.
V5.80 SML scripts can now contain powerful functions for reading,
displaying, analyzing, and writing raster, vector, CAD, TIN, and region objects.
Thus, SML products can already produce more advanced applications than
MapBasic and Avenue. These other programming products hardly know what a raster
is let alone what to do with it; they cannot deal with TINs and their
application; CAD objects are converted into intermediate forms; and so on. Also,
products created with these other products widely circulate at low cost or free
without protection from unauthorized use. Do you want to work to create advanced
products which circulate in such a fashion?
Let's compare the SML cross-platform strategy to other procedures used to
customize GIS and desktop mapping products. When using Avenue and MapBasic, you
must create separate programs or scripts for each operating system. This
increases the difficulty, resulting in limiting the availability of extensions
and add-on products to only the most popular platforms. For example, MapInfo has
ceased releasing products for the Mac or UNIX platforms, and their partners
releasing add-ons or companion products never provided their products for these
platforms. This "code for each platform" strategy has also limited
these kinds of products to the most popular platforms. It also means that
support for your platform will be dropped much sooner when it is no longer
marketed. It means that support for new operating systems gaining in popularity
will be delayed (for example, the switch from Solaris 1.x to 2.x, support for
Rhapsody or Linux, 64-bit NT--there is already a 64-bit version of the TNT
products).
All the V5.70 and V5.80 changes in SML, coupled with the
ability to choose SML scripts as a layer in the new visualization
process, already allow you to create powerful custom geospatial analysis
processes. With V5.80, your scripts can be distributed free or for sale
for use with pow |
