Erdas Imagine
Erdas Imagine
Erdas Imagine
ERDAS IMAGINE
Convert .............................................................................................................. 20
Metadata Input................................................................................................... 43
Orthogonalize Geometry.................................................................................... 44
Update Statistics................................................................................................ 51
GDA2020 ........................................................................................................... 61
Planet imagery................................................................................................... 69
WorldView-4 ...................................................................................................... 69
This release includes both enhancements and fixes. For information on fixes that were made to ERDAS IMAGINE
for this release, see the Issues Resolved section.
This document is only an overview and does not provide all of the details about the product's capabilities. See the
online help and other documents provided with ERDAS IMAGINE for more information.
IMAGINE Essentials® is the entry-level image processing product for map creation and simple feature collection
tools. IMAGINE Essentials enables serial batch processing.
IMAGINE Advantage® enables advanced spectral processing, image registration, mosaicking and image analysis,
and change detection capabilities. IMAGINE Advantage enables parallel batch processing for accelerated output.
IMAGINE Professional® includes a production toolset for advanced spectral, hyperspectral, and radar processing,
and spatial modeling. Includes ERDAS ER Mapper.
NEW PLATFORMS
64-BIT
As imagery gets larger and larger (for example, a single Sentinel-2 image can be over 8 GB in size, even when
JPEG 2000 compressed) it becomes increasingly urgent to be able to make fuller use of the resources provided by
modern computer systems, especially the additional memory that is usually installed. In prior versions of ERDAS
IMAGINE we have made extensive progress in providing background processing (such as from Spatial Modeler)
and specific applications (such as Semi Global Matching) that run in 64-bit. However the Ribbon interface itself
(ewkspace.exe) was always launched as a 32-bit application - it was only select applications that could be
launched from, but run independently of, the Ribbon that would execute in 64-bit. This meant that the applications
embedded within the Ribbon, such as the 2D View and the Spatial Model Editor, also ran as 32-bit and
consequently were limited to utilizing, at best, 4GB of memory each.
One of the main reasons why the Ribbon remained 32-bit was that some functionality that could be run from it
(especially functionality depending on third-party libraries) could not be modified to run 64-bit and so everything
needed to run 32-bit.
With ERDAS IMAGINE 2018 it has consequently been decided to offer two distinct versions of the ERDAS
IMAGINE Ribbon interface that the user can opt to launch and utilize:
Another advantage is that Spatial Models will be able to process large datasets more efficiently even when
executed within the Spatial Model Editor interface. Previously, Models might have to be executed in Background
mode to take advantage of 64-bit execution, which meant that the progress of the model was more difficult to
monitor and, if a problem occurred, address by modifications of the Model. Now the Model can be executed
efficiently within the Editor and modifications to the Model made directly if required.
But why launch the ribbon in 32-bit mode if there's a 64-bit version available? As mentioned earlier, there are some
very limited capabilities that run from the Ribbon which remain unable to be updated to run in 64-bit. Consequently
these capabilities are absent from ERDAS IMAGINE 2018 (64-bit). If you need to routinely use these features, we
are providing ERDAS IMAGINE 2018 (32-bit) so that all functionality that was provided in ERDAS IMAGINE 2016
is still available to the user. Functionality that is only available in ERDAS IMAGINE 2018 (32-bit) includes:
1. Raster formats
a. ER Mapper Algorithm
b. GRID
c. GRID Stack
d. ORACLE Georaster
e. SDE Raster
g. VisionMap .sup
2. Vector formats
a. Arc Coverage
b. ArcGIS Geodatabase
If you routinely use any of these in your work then you might want to consider running ERDAS IMAGINE 2018 (32-
bit) rather than ERDAS IMAGINE 2018 (64-bit).
ARCGIS 10.5.1
ERDAS IMAGINE 2018 has been tested and declared Supported when using an installed and licensed version of
ArcGIS 10.1 through 10.5.1 in order to provide Geodatabase support libraries. Alternatively, the IMAGINE
Geodatabase Support component (based on ArcGIS Engine 10.5) can be installed to provide Geodatabase
support.
NEW LICENSING
With the Power Portfolio 2018 release, licenses will no longer be based on Certificate-file based technology;
instead, licenses will be based on Activation IDs so that customers are able to activate their products without
having to provide Host IDs or other hardware-related parameters.
Customers will also be able to re-host without emailing the licensing team to assist.
The Power Portfolio 2018 release will also include improved tools to make it easier to install licenses, set up
license servers, and provide more professional error handling.
Finally, the Power Portfolio 2018 release will have improved customer notification in the products, such as an “end
of subscription” message in the Start-up screen.
These more secure and automated processes, along with a new licensing portal, will provide a better customer
experience.
NEW TECHNOLOGY
MACHINE LEARNING CLASSIFICATION OPERATORS
Machine learning is the science of getting computers to act without being explicitly programmed. Stated in another
way, it is a way of programming where computers are programmed to learn from data.
• Problems for which existing solutions require a lot of hand-tuning or long lists of rules: one Machine
Learning algorithm can often simplify code and perform better.
• Complex problems for which there is no good solution at all using a traditional approach: the best Machine
Learning techniques can find a solution.
• Fluctuating environments: a Machine Learning system can adapt to new data.
• Data mining - getting insights about complex problems and large amounts of data
Geospatial phenomena are non-linear, spatially and temporally variable and have multi-scale variability which
creates challenges in geospatial analysis. With the proliferation of sensors around us, from micro satellites to
UAVs, the volume of data has greatly increased. The complexity of geospatial phenomena and the deluge of data
has made geospatial analysis using machine learning methods a natural fit.
We have introduced several machine learning algorithms based classification operators in Spatial Modeler which
can be used to perform supervised and unsupervised raster and vector classification. The supervised
classification operators need training data and attributes of the training data to be used in performing the
classification, while the unsupervised classification operators only need attribute of the data to be used to separate
the data into clusters.
Another set of classification operators based on deep learning algorithms are also introduced. These are a class of
Machine learning algorithm that use deep neural networks to decide the attributes of the data that need to be used
to perform classification.
A classification operator based on Inception, which is an award winning deep learning classification algorithm
introduced by Google, is also introduced. The operator can be re-trained using user’s data to perform
classification.
The example below shows how the NNDiffuse sharpened image, shown on the right, retains the spectral fidelity of
the input, lower resolution multispectral image, shown on the left, while increasing the spatial resolution four-fold
(from 2m pixels to 0.5m pixels):
ANALYZE RADIANCE
Given time of day and calendar date, the operator provides output in radiance units (Watt per meter squared) for
each elevation pixel using its local slope and aspect, computing either insolation (incident solar/lunar irradiance) or
terrestrial radiation (reflected radiance from a surface with known dominant reflectance coefficient), with or without
including light viewshed that blocks direct beam irradiance.
Insolation is computed using medium fidelity models of radiative energy transfer through the atmosphere and
ground radiation. Algorithm considers atmosphere (based on standard pressure of average DEM elevation) for
both light refraction and light scatter (Rayleigh and Mie). Algorithm considers ground as a secondary source of
illumination from terrestrial radiation such that total energy incident on any surface (defined by its local normal) is
composed from 3 parts - direct beam irradiance, diffuse radiation (skylight), and ground albedo (neighborhood
terrain illuminates any non-horizontal surface).
The algorithm employs efficient polynomial models for earth curvature when elevation grid footprint exceeds
certain limits, which allows producing realistic illumination over very large geographic areas.
The image below left shows Insolation calculated from a LiDAR dataset, while the one on the right shows
Insolation with Shadowing derived from the same dataset and the same time of day parameters:
K-Means is an unsupervised machine learning algorithm that classifies data into a specified number of classes
while minimizing the sum of squares of distances between the data points and their corresponding class centroids.
Classifies raster zones as defined by the geometry of input features. The classification is performed using a trained
machine intellect specified on the MachineIntellect port. Results are added as attributes to the output feature
stream.
Performs classification on the input data using the trained classifier specified on the MachineIntellect port.
This operator computes the lengths of the primary and secondary axis of the primary geometry of features; the
ratio of the two axes is also computed.
The lengths of the primary and secondary axis are represented in the units of the horizontal coordinate system of
the primary geometry field (it is a 2D measurement). See Compute Primary Axis Skewness for more information on
the computation of the primary and secondary axis.
COMPUTE CIRCULARITY
The operator measures how close a geometry is to a true circle. Circularity is computed as follows:
A center point is computed by averaging the coordinates of all points in the geometry.
The distances from each point on the geometry to the center point is calculated.
The standard deviation is subtracted from 1.0. If the result is less than zero, it is set to 0.0
Consequently, a value of 1 represents a geometry which is more likely to be circular than one with a value of 0.1.
COMPUTE COMPACTNESS
The operator measures the compactness of a feature. Compactness is defined as the ratio of the perimeter of a
circle, whose area is equal to that of the feature, to the perimeter of the feature. The value ranges between 0 and
1, where a circular geometry will have a value of 1.
COMPUTE CONCAVITY
The value ranges between 0 and 1, where a geometry with no concavity will have a value of 0. A concave
geometry will always have at least one reflex interior angle—that is, an angle that is between 180 degrees and 360
degrees
COMPUTE CONVEXITY
The operator measures how convex a geometry is. Convexity is defined as the ratio of the geometry's convex hull
perimeter to the geometry's perimeter. The value ranges between 0 and 1, where a geometry with no concavity will
have a value of 1.
This operator counts the numbers of corners of the primary geometry of the feature stream.
A corner is defined as vertex whose angle (θ) is between the MinAngle and MaxAngle specified (inclusive). The
smaller of the absolute value of the interior or exterior angle is used to determine if a corner fits within the specified
constraints. The operator by default looks for corners with angle θ ∈ [79°,101°], indicative of corners that are close
to being orthogonal.
COMPUTE ECCENTRICITY
The operator measures how much a geometry deviates from a square. Eccentricity is defined as the ratio of the
primary axes length to the secondary axes length.
Horizontal skewness measures how asymmetric an object is in the horizontal direction (i.e., about the vertical
axis). It is computed based on the vertices of the object.
Skewness is computed as the ratio of the third moment about the mean and the standard deviation cubed.
COMPUTE ORIENTATION
Computes the angle between the primary axis of the geometry and the vertical axis
This metric computes the angle between the primary axis of a feature and the vertical axis (north), indicating how
the object is aligned with respect to the vertical axis. Orientation value ranges from 0 to 180 degrees, starting at
zero from the vertical axis (north) and increases clockwise.
COMPUTE ORTHOGONALITY
This operator measures how close a geometry resembles an orthogonal feature (a feature with all right angles).
This metric measures how skewed an object is along its primary axis (i.e., about its secondary axis). The minimum
value is 0 for an object that is symmetric along its primary axis. A positive value indicates that the object is skewed
in the positive primary axis direction, while a negative value indicates that the object is skewed in the negative
primary axis direction.
COMPUTE RECTANGULARITY
The operator measures how rectangular a geometry is. Rectangularity is defined as the ratio of the area of the
object to the area of its oriented bounding rectangle. The value ranges between 0 and 1, where a rectangle
geometry will have a value of 1.
This metric measures how skewed an object is in the direction of its secondary axis (i.e., about its primary axis).
The minimum value is zero for an object that is symmetric about its primary axis. A positive value indicates that the
object is skewed to the positive secondary axis direction, while a negative value indicates that the object is skewed
to the negative secondary axis direction.
Vertical skewness measures how asymmetric an object is in the vertical direction (i.e., about the object's horizontal
axis). A positive skewness indicates the object has a longer tail to its top side, while a negative skewness indicates
it has a longer tail to its bottom side. A zero value means the object is symmetrical in the vertical direction.
CONVERT
The Convert Operator has been enhanced to support conversion from a List datatype to a Table datatype
(assuming that the List contains appropriate Data). This is particularly useful when dealing with the output from
an Iterator, which will be produced as a List.
CONVERT TO SURFACE
Creates a raster surface by interpolation through a TIN over the specified or implied output extent. Areas outside
the convex hull of the TIN will be NODATA. The area within the convex hull will not contain holes.
Create the coordinate-system-axis-aligned bounding box of the primary geometry of the input features. This
geometry is added as the primary geometry and the original geometry is retained in the output features.
CREATE CENTERLINE
This operator creates a single center line from the primary geometry of the input features. The center line is added
as the primary geometry and the original geometry is retained in the output features.
CREATE CENTERPOINT
The Create Centerpoint operator creates a center point within a geometry. A centerpoint differs from a centroid in
that it is guaranteed to fall in the interior of the geometry, however there is no one correct centerpoint location. If
the need is for a true centroid (center of gravity), use the Create Centroid operator.
CREATE CENTROID
The Create Centroid operator creates a point at the centroid (center of gravity or center of mass) of a geometry.
The centroid of a convex area geometry lies always inside the area boundary. A non-convex geometry might have
a centroid that lies outside it (the centroid of a ring, for example, lies within the area's hole).
CREATE CONVEXHULL
The operator removes all concave areas of a geometry by connecting the two vertices adjacent to the concave
area. This geometry is added as the primary geometry and the original geometry is retained in the output features.
Outputs a filename that can be used to access a raster image, given either a filename or a URI input. When
working with datasets containing multiple images, this is a useful way of obtaining a file reference to a subimage.
When DatasetReference is a URI referencing a subimage, an .sbi proxy file will be created in the same directory
as the dataset according to the following scheme: <FullDatasetFilename>_<ImageName>.sbi (eg Image1 in
c:\work\some.ntf would generate c:\work\some.ntf_Image1.sbi). If the .sbi file exists already, it will be reused if it
refers to the referenced subimage, and overwritten if it does not. The CreatedProxyFile output is set to true if a
proxy file was created or overwritten (but not if an existing proxy file was reused without modification).
If DatasetReference is a filename or a URI referencing the primary image in a dataset, the filename of the dataset
will be returned.
For example, this model shows how to create a proxy file for the third subimage of a Sentinel 2 dataset:
This operator creates the fitted bounding box of the primary geometry of the input features. This geometry is added
as the primary geometry and all original fields are retained in the output features.
The fitted bounding box is determined by generating the convex hull geometry of the primary geometry of the input
feature and then finding the minimum area rectangle that fits the convex hull.
This operator creates the oriented bounding box of the primary geometry of the input features such that it has the
same primary and secondary axes as the primary geometry. The oriented bounding box geometry is added as the
primary geometry and the original geometry is retained in the output features.
CREATE SKELETON
This operator creates skeleton from features. A skeleton is a polyline representation of a polygon shape that
approximates the centerline of the shape. For polygons that have tentacle-shaped boundary, the skeleton will be a
collection of polylines with each tentacle-shaped part of the shape represented by a polyline.
DATA INFORMATION
Defines a deep learning convolution layer which can be used as an input to the Initialize Deep Intellect operator to
create a machine intellect.
A convolution layer applies spatial filters to an input image to identify features such as edges, curves, colors and
other distinctive features to create a feature map. A feature map is an image that indicates the presence or
absence of a feature the filter is designed to identify in the input image.
Defines a deep learning pooling layer which can be used as an input for creating a machine intellect using the
Initialize Deep Learning operator.
Pooling down-samples the size of the feature map while retaining the most important information in the map. It
operates by moving a filter across the feature map and taking a representative value within the region defined by
the filter.
Defines a deep learning activation layer which can be used as an input for creating a machine intellect using the
Initialize Deep Learning operator.
An activation layer introduces non-linearity to the network. Non-linearity is introduced so that the network can
understand and model complex relationships.
Defines a deep learning dense layer which can be used as an input to the Initialize Deep Learning operator to
create a machine intellect.
The nodes in a dense layer are fully connected, which means all of the nodes in the dense layer are connected to
all nodes in the previous layer.
Defines a deep learning flatten layer which can be used as an input for creating a machine intellect using the
Initialize Deep Learning operator.
The Define Functional Attribute operator receives as input a Field Name and an Expression, and produces as
output a FunctionalAttribute data type. The functional attribute can be input to the Generate Functional Attributes
operator as well as other operators which use functional attributes.
The Define Processing Area operator has been enhanced to recognise “dd” (decimal degrees) as a valid input
option for Units. It previously recognised “degrees”, but this made it difficult to automatically derive from the Cell
Units operator, which output the string “dd”.
This operator removes holes and/or Islands from geometry collection in a feature by the specified thresholds. The
main/largest area (not considering holes within it) will always be kept regardless of the thresholds.
Extracts the specified shapefile if it is present. ShapeToExtract is normally a string indicating the kind of shapefile
to look for: "IMAGE_SHAPE", "CLOUD_SHAPES", or "CLOUD_SHAPES_LineSample" (corresponding to typical
values of the CSSHPA DES field). Alternatively, ShapeToExtract may be set to the numeric index (1-based) of a
DES containing a shapefile.
An error is raised if a DES segment index is specified that does not exist or does not contain a shapefile. If a
shapefile type ("IMAGE_SHAPE") is specified that does not exist in the .ntf, no output will be produced
(ShapeFilenameOut is null) but no error is raised.
FIND ITEM
The operator compares the item to the content of the list and returns the indices of all the occurrences. The type of
the comparison item must match the type of the elements in the list. An empty list is returned if no matches are
found.
Building on the algorithms implemented in the Rapid Atmospheric Correction spatial operator, we have added a
new spatial operator which enables any 16-bit imagery with at least four bands in the wavelength range from
Coastal Blue to NIR2 to be atmospherically corrected to ground reflectance based on parameters that can be
derived from the image header. Correcting to ground reflectance has the advantage of normalizing scene-to-scene
variations, which in turn makes tasks such as change detection, standardized classification, and other feature
extraction tasks more straightforward.
Below is an example showing how to correct a Landsat 8 scene:
Downloads the relevant Landsat 8 scenes for the given input parameters from the public AWS S3 Bucket
(https://aws.amazon.com/public-datasets/landsat/). SaveToDirectory specifies a download directory for scenes;
previously downloaded scenes in that directory will be reused. (Scene directories that exist are assumed to contain
usable Landsat 8 scene data.) Scenes sufficient to completely cover RegionOfInterest will be downloaded or
reused. QueryMethod and CollectionModeFilter further specify which scenes should be considered.
Please note that this operator relies on an external service not owned or controlled by Hexagon Geospatial. The
bucket is provided by Amazon Web Services, Inc. and the data by USGS. If the service is discontinued or the site
moved, the operator may cease to function. It is highly recommended that you review the web page at the above
address prior to using this operator.
In the example below, the downloaded data (which consists of individual TIFF files, one per band of the Landsat 8
scene) is selectively stacked into a 7 band multispectral image. A Boundary Input is used to define the scenes to
download. The Get AWS Landsat 8 operator outputs a List of Directories that were downloaded. The first (0th)
item on this List is extracted using the Nth Item operator. That Directory is then scanned using the Multi Filename
Input operator to build a List of Filenames of those files which match the search criteria (LC8*_B?.tif). That criteria
would include bands 8 (the high resolution Pan) and 9 (Cirrus), which we don't want to include in the multispectral
image stack. So Remove Items is used to remove two entries from the List of Filenames. The thinned List of
Filenames is then passed into an Iterator which simply wraps a Raster Input operator such that the List of
Filenames is transformed into a List of Rasters. The Iterator also deconstructs each input filename and turns them
into a List of Strings which is used later in the model in the Set Band Names operator. The List of Rasters is
passed into the Stack Layers operator to create a single 7 band raster. Since Landsat 8 usually uses DN 0 to
denote NoData, it is set that way using a Set to NoData operator. The Set Band Names then assigns appropriate
band names on each of the bands derived from the input filenames (thereby retaining the original band/wavelength
information). Finally the Raster Output creates a 7-band MSI image file on disk.
Iterator 2 sub-model:
Get band identifiers from the specified dataset reference. Supplying a band identifier to the Raster Input operator
instead of a filename will cause only the specified band to be opened. In a Spatial Model that performs quick
calculations on a single band of a raster with many bands, this can give a substantial performance benefit.
The Spatial Model shown below uses the Get Band IDs operator to compute statistics for a single raster band
without opening other raster bands:
Use the Get DRA Params operator to acquire the necessary inputs to use with the DRA Stretch operator.
Dynamic Range Adjustment (DRA) is a technique used to perform tonal processing of raw image data, mapping it
from the dynamic range of the sensor to that of a well-defined metric. Once mapped, standardized enhancement
processing can then be applied. The DRA algorithm permits the adjustment and optimization of an image’s
dynamic range so that the maximum amount of information can be obtained from all portions of the tonal range.
The algorithm will clip information beyond the desired range.
Below is an example of how this operator might be used in a larger model intended to compute statistics for an
input image, determine default DRA parameters, and apply a stretch using the DRA parameters:
Creates the format-specific output-option dictionary for Enhanced Compressed Wavelet (ECW) format.
Below is an example of how this operator might be used to convert an input raster to ECW:
Below is an example of how this operator might be used in conjunction with other Get Options operators to create
a model that can convert an input raster to any supported raster format, depending on the extension of the output
filename provided:
Creates the format specific output option dictionary for JPEG File Interchange Format (JFIF).
Creates the format specific output option dictionary for JPEG 2000 format.
Computes color-preserving parameters for the DRA Stretch operator. For single-band images, use the Get DRA
Params operator. Use caution when supplying data for more than the three image bands intended for stretch and
display, as the results may not be meaningful.
This model shows how to perform a color-preserving DRA stretch of a multispectral image. In the Raster Input,
metadata reading has been enabled (ReadMetadata=true); this increases the accuracy of bits-per-pixel
determination for NITF images. The Statistics operator provides raster statistics, plus Dark Point and Bright Point
(these ports are normally hidden). PMinIn and PMaxIn have been set to 0.1 and 0.95; they could be made model
inputs for easy run-time adjustment. (Good default PMin and PMax values for a particular image can be found by
running Get Multispectral DRA Params with no PMinIn and PMaxIn inputs and using the resulting PMinOut and
PMaxOut values.)
Creates the format specific output option dictionary for National Imagery Transmission Format (NITF).
See Get ECW Options for an example of using this Operator in a model.
Gets a value from the preference database. The result is a String, Bool, Double, or Color. An error is raised if the
preference specified does not exist.
Valid preferences are defined by text files with the .pdf extension in $IMAGINE_HOME/defaults. These files should
not be modified.
The Category port specifies the preference category. This corresponds to a filename (minus the .pdf extension) in
$IMAGINE_HOME/defaults; for instance, "rasterprocess" or "spatial_modeler".
The Name port specifies the preference name within the category. Preference names can be found by opening
one of the .pdf preference files in a text editor.
An easy way to find the category and name of a specific preference in ERDAS IMAGINE is to locate it in the
Preference Editor (File / Preferences), modify its value, and Save. This will cause a line to be added to the text file
$PERSONAL/v8preference of the form: category.name : value.
Returns the lowest pixel value that is greater than or equal to a requested percentage of pixels in each band
(subject to histogram binning limitations).
A cumulative image histogram for each band is computed from Statistics. Values is a table containing the lower
limit of the bin for each band corresponding to Percentage, first skipping over any bins with zero counts.
The model shown below calculates the mean values of pixels that are in the top 0.1% of brightness in all bands
simultaneously. Statistics are calculated for the raster (using a limiting image boundary, if one is provided), and the
Full Stats output is connected to Get Raster Values By Percentage. A single-band image is generated whose
values are the number of bands with 0.1% pixels (Gt, Integer, Stack Total), and the input image is set to NoData
at all other pixels (Ge, Set To NoData, Either/Or). Finally statistics are calculated again on the mostly-NoData
image (Statistics 2), and the Mean of the non-NoData pixels--the pixels that are simultaneously bright in all bands-
-is connected to the BrightMean output port.
Checks whether a raster dataset is a proxy file of the specified type(s). If so, outputs the filename pointed to by the
proxy; otherwise, outputs the original filename.
This Spatial Model shows the use of Get Referenced Dataset to determine the underlying dataset referred to when
creating RSETs. Sub-band image proxy files (.sbi) are commonly used to access subimages in multi-image
datasets. Using Get Referenced Dataset with sbi specified as the only allowed proxy type, we will get either the
underlying multi-image file if an .sbi file was specified, and the user-specified file for all other cases.
The Generate Functional Attributes operator receives as input a Features data type, and produces as output a
Features data type. The schema in the output Features may have one or more additional attributes with values
computed from expressions. Because these are computed, they are called functional attributes.
INITIALIZE CART
Defines and trains a CART classifier which is used as an input for classifying data using Classify Using Machine
Intellect operator.
CART (Classification and Regression Tree) is a decision tree based supervised classification algorithm.
Defines and trains a deep neural network to generate a Machine Intellect that can be used for classifying images
using the Classify Using Deep Learning and/or Classify Images Using Deep Learning operators.
INITIALIZE INCEPTION
Re-trains the trained Inception model based on new training images. Inception is a 22 layer deep convolutional
neural network developed by Google.
Defines and trains a K-Nearest Neighbors classifier which is used as an input for classifying data using the Classify
Using Machine Intellect operator.
Defines and trains a Naive Bayes classifier which is used as an input for classifying data using the Classify Using
Machine Intellect operator.
Naive Bayes classifiers are part of family of simple probabilistic classifiers based on Bayes theorem.
Defines and trains a Random Forest classifier which is used as an input for classifying data using the Classify
Using Machine Intellect operator.
Random Forest is an ensemble of decision trees and one of the most popular machine learning algorithms.
INITIALIZE SVM
Defines and trains a Support Vector Machine (SVM) classifier which is used as an input for classifying data using
the Classify Using Machine Intellect operator.
Support Vector Machine (SVM) is a supervised machine learning algorithm that performs classification by finding
optimal hyperplanes that separates the classes.
INTERSECT FEATURES
This operator constructs topology from the two sets of features and computes the topological intersection of those
two sets based on the given spatial relationship.
The operator applies the Kurtosis Texture operator on pixels of the input raster that are inside a feature and then
computes mean, median and standard deviation of the kurtosis texture values. The computed statistical values are
added as attributes to the feature stream.
When computing texture for a feature, only pixels that are inside the feature are considered. If some cells of the
moving neighboring window fall outside the feature, as happens when computing texture near the boundary of the
feature, these cells are treated as NoData cells during the computation. This ensures pixels in a feature do not
affect the texture of adjoining features.
MASK FEATURES
This operator constructs topology from the two sets of features and masks the geometries of the FeaturesIn port
by subtracting the geometries from the Mask port.
MERGE FEATURES
This operator merges groups of features together based on attribute matches and/or spatial relationships,
summarizing data for the groups via functional attributes. It is a two-step operation, involving first the grouping of
input features, then second the creation of output features from those groups.
The operator applies the Mean Euclidean Distance Texture operator on pixels of the input raster that are inside a
feature and then computes mean, median and standard deviation of the mean euclidean distance texture values.
The computed statistical values are added as attributes to the feature stream.
When computing texture for a feature, only pixels that are inside the feature are considered. If some cells of the
moving neighbouring window fall outside the feature, as happens when computing texture near the boundary of the
feature, these cells are treated as NoData cells during the computation. This ensures pixels in a feature do not
affect the texture of adjoining features.
The attribute names for the output feature stream are constructed based on AttributeNamePrefix,
AttributeBasename for the statistics being computed and the number of bands of the raster. If the constructed
attribute name matches with the name of an existing field and the field type is appropriate, the existing field will be
overwritten. otherwise, the operation will fail.
METADATA INPUT
The MetadataInput operator reads the metadata from a Raster, and the output is a Dictionary object.
NORMALIZE HEIGHT
This operator computes the height above the ground for the selected points and replaces their Z value with the
computed value.
For example, this model identifies tall vegetation which may be encroaching on powerlines:
ORTHOGONALIZE GEOMETRY
The operator creates orthogonalized geometry of the primary geometry of the input features. This geometry is
added as the primary geometry and the original geometry is retained in the output features. No densification or
simplification operation is applied in the process. The operator uses the existing vertices of the geometry
The algorithm analyzes the segment length and orientation to figure out the best orthogonal polygon for the input
polygon. The Orthogonality Factor is a relative term used to decide how detailed the orthogonalized polygon will be
created. The bigger this number, fewer right angle corners will be created
RANGE STRETCH
Linearly stretches the input raster between start, end values to 0-255 (8-bit).
RASTER CACHE
Caches blocks of the requested raster planes at distinct pyramid levels. Allows downstream operators to use
smaller block sizes without the duplicate I/O overhead.
This operator computes statistics on pixels of the input raster that are inside a feature. The computed statistical
values are added as attributes to the feature stream. By default, mean is computed. Other statistical values
(Standard Deviation, Minimum, Maximum, etc) can be calculated by turning on their appropriate ports.
This is a particularly useful Operator for creating information for Machine Learning models.
Reads vendor-supplied metadata files associated with a raster dataset. If a metadata file is found, its full contents
are added to the Metadata object in the Format Specific region; additionally, common schema fields in the
Metadata object may be updated.
In the Spatial Model Editor, double-clicking on the SensorIn port will show a list of available metadata parsers.
Setting SensorIn to one of these values will cause only the corresponding parser to be used. If no sensor is
specified, available parsers will be tried until one succeeds.
Below is an example of a portion of a model that uses the Read Sensor Metadata operator to get read information
from the vendor-supplied metadata files associated with the input raster dataset to compute the parameters to be
used in the Generic Atmospheric operator.
REMOVE ATTRIBUTES
RENAME ATTRIBUTES
The operator renames attributes in features. The operator will fail if the attribute to be renamed does not exist.
SELECT ATTRIBUTES
Below is an example of how this operator might be used to set the names of the output bands to a specific list of
names. It uses the Custom Table Input operator to create a Table of Strings. A Table of Strings can automatically
be converted to a StringList.
Another way of creating the StringList of BandNames is using an Iterator operator. Below is an example of using
an Iterator Operator to create the BandNames dynamically.
This operator designates the primary geometry for the feature stream. The attributes of the feature stream are
otherwise unchanged. If there are existing attributes representing measurements on the geometry, they may not
be valid for the newly designated primary geometry.
Designation of the primary geometry field is useful for working with features operators that only operate on the
primary geometry field.
SIMPLIFY GEOMETRY
This operator uses Douglas-Peucker algorithm to simplify the primary geometry of the features. The new geometry
is added as the primary geometry and the original geometry is retained in the output features.
The operator applies the Skew Texture operator on pixels of the input raster that are inside a feature and then
computes mean, median and standard deviation of the skew texture values. The computed statistical values are
added as attributes to the feature stream.
When computing texture for a feature, only pixels that are inside the feature are considered. If some cells of the
moving neighboring window fall outside the feature, as happens when computing texture near the boundary of the
feature, these cells are treated as NoData cells during the computation. This ensures pixels in a feature do not
affect the texture of adjoining features.
The attribute names for the output feature stream are constructed based on AttributeNamePrefix,
AttributeBasename for the statistics being computed and the number of bands of the raster. If the constructed
attribute name matches with the name of an existing field and the field type is appropriate, the existing field will be
overwritten. otherwise, the operation will fail.
SPLIT BY SKELETON
The operator converts a polygon into a collection of smaller parts if its skeleton is composed of multiple polylines.
It does this by internally creating a skeleton for the input geometry and using each polyline from the skeleton to
extract the part of the polygon it represents.
STACK COUNT
Returns a single layer whose pixels contain the number of occurrences of the requested value at that pixel among
the layers of RasterIn.
Below is an example of how this operator might be used to determine the number of occurrences in a layer stack
of the Stack Majority pixel value.
Below is an example of how this operator might be used to determine the number of occurrences of a particular
value in a layer stack.
TASSELED CAP
UPDATE STATISTICS
The operator applies the Variance Texture operator on pixels of the input raster that are inside a feature and then
computes mean, median and standard deviation of the variance texture values. The computed statistical values
are added as attributes to the feature stream.
When computing texture for a feature, only pixels that are inside the feature are considered. If some cells of the
moving neighboring window fall outside the feature, as happens when computing texture near the boundary of the
feature, these cells are treated as NoData cells during the computation. This ensures pixels in a feature do not
affect the texture of adjoining features.
The attribute names for the output feature stream are constructed based on AttributeNamePrefix,
AttributeBasename for the statistics being computed and the number of bands of the raster. If the constructed
attribute name matches with the name of an existing field and the field type is appropriate, the existing field will be
overwritten. otherwise, the operation will fail.
In the example below the Spatial Model has a Port Input which the user can set to define the sensor being
processed by the model. The model only knows how to interpret six specific values (integer values 1 through 6)
which represent the sensor. However, by default the user could enter any integer value in the Port Input prompt
and if that value were not recognised by the model (a value of 7, for example) the model would fail to run.
Using the new capability, the Port Input can be constrained to only accept the valid integer values of 1 through 6,
as shown in the screenshot. This makes it much more straightforward to create Spatial Models which can be
distributed for use by other users by providing a user interface to the Model which only allows valid values to be
entered.
Similarly, valid input strings can be defined to produce pop-up lists for the user to choose from when executing a
model, such as this list of sensor types:
At the same time options have been added to exclude NoData from the analysis. Consider a single pixel location in
a stack of 100 DEM layers. If this column of pixels included any NoData value in a layer, a Stack <Statistics>
analysis in the past would have returned NoData at that location. With this release, the NoData values are
excluded from the analysis. So, for example, a pixel location with 97 NoData values, but three values of 300, 400
and 500, will now return 400 if analysed through the Stack Median operator.
This also provides the capability to ignore specific values in the Stack <Statistics> operators. Simply use one or
more Set to NoData operators to set any values you wish excluded from the analysis prior to feeding the raster
stream to the appropriate Stack <Statistics> operator.
Once the scripts are detected by ERDAS IMAGINE, they will be listed in the SME operator tree list and can be
used in combinations with other operators to leverage the strengths of both ERDAS IMAGINE and GeoMedia in a
spatial model.
For details on how to get your ArcPy scripts recognized by ERDAS IMAGINE, refer to the white paper “Leverage
ArcPy scripts in Spatial Modeler” on our website.
Using the Add to User Operators option the model currently open in the Spatial Model Editor will be saved to
$PERSONAL/etc/UserOperators. It will then be shown in the Operators panel and can be used in other models.
…then select the Add to User Operators option and I would subsequently have a new, custom Operator which I
can re-use in other Spatial Models:
Dockable Panel
Rather than an independent dialog, the new Inquire Cursor is a dockable panel to display the attribute
information at the cursor location, along with associated ribbon tab and tool groups.
If there are multiple data layers displayed in the View (as indicated in the Table of Contents on the left of
the ERDAS IMAGIGNE window), then information from all displayed images at the location can be
optionally displayed in the CellArray.
A common request when performing a Preview in the Spatial Model Editor (or displaying imagery using he
Image Chain option) was to be able to use the Inquire Cursor to see the values being produced by the
model on the fly. This is now possible using the new Inquire Cursor:
When using the Preview option in the Spatial Model Editor the new Inquire Cursor can also show
information for Feature (vector) layers that are being produced.
Neighbor Values
The new Inquire Cursor can also now show a view of the pixels which neighbour the location being
targeted:
This includes the ability to display string field values such as Class Names:
A custom change detection algorithm will be automatically picked by IMAGINE once it is built in the Spatial
Modeler Editor and saved to a specific location. For details on how to build a custom change detection algorithm,
refer to the white paper “Building a custom change detection algorithm for Zonal change detection in ERDAS
IMAGINE” on our website.
GDA2020
Australia is in the process of changing to a new official geodetic datum called the Geocentric Datum of Australia
2020 (GDA2020) which is replacing the current Geocentric Datum of Australia 1994 (GDA94). This datum has
been implemented in ERDAS IMAGINE 2018.
SUBSET IN BATCH
The Batch dialog has had an option added to send the command to the Batch Editor in a similar form to the way it
was populated in ERDAS IMAGINE 2016 and prior. This alleviates the complication, that had been created by
using the newer Spatial Modeler, of exposing more variables than the user generally wished to set, to perform the
batch process.
Default result of using Batch (original), showing that there are no Variables added to the command:
This was because when the Map Info Options dialog was used to set the desired Projection, the dialog also
passed in the Upper Left X and Upper Left Y map coordinate of the first image. Unless you noticed this (and
manually set up variables to replace the fixed values), that single map extent would then be applied by the Batch
process to all the input images, along with the desired Projection.
In ERDAS IMAGINE 2018, Edit Image Metadata has been enhanced so that the Upper Left X, Upper Left Y, Pixel
Size X and Pixel Size Y parameters are automatically passed to Batch as variables that pull their information from
each input image being processed. Only Projection and Units are passed as fixed values.
However, if the user manually sets one (or more) of the values in the Map Info Options dialog then those values
will be assumed to be the desired values and will be passed to the Batch Editor as fixed values as well.
The importer will also now handle Landsat-8 CDR reflectance data.
SECURITY INDICATORS
To support use of the software in classified environments, the title bar of the 2D View can be set to display differing
colors based on the security classification of the imagery being displayed.
PLANET IMAGERY
Planet changed formatting on RapidEye and PlanetScope imagery in late 2016. The new data can now be directly
read in ERDAS IMAGINE.
WORLDVIEW-4
Directly read the latest offering from DigitalGlobe, including the ability to orthorectify the imagery.
EXTERNAL PYRAMIDS
Reading external TIFF-formatted pyramid layers generated by SOCET is now directly supported.
PeruSAT-1
VNREDSat-1
GEOSPATIAL PDF
Creation of multi-layer Geospatial PDF documents from input imagery and overlay layers, or single layer
documents from map compositions is now provided using GDAL’s Geospatial PDF engine.
Geospatial PDF documents can also be generated in the Spatial Modeler Environment using the Create
Geospatial PDF operator.
SYSTEM REQUIREMENTS
ERDAS IMAGINE
64-bit: Intel 64 (EM64T), AMD 64, or equivalent
Computer/ Processor
(Multi-core processors are strongly recommended)
4 GB for software
OpenGL 2.1 or higher (this typically comes with supported graphics cards5)
Internet Explorer® 9 and higher with JavaScript enabled, or Firefox® 32 and higher with
JavaScript enabled
Java Runtime 1.7.0.80 or higher - IMAGINE Objective requires JRE and can utilize any
installed and configured JRE of version 1.7.0.80 or higher.
Software
Python 3.4 (Python is optionally usable with Spatial Modeler. In most cases 64-bit Python
is required; however, if you run 32-bit ERDAS IMAGINE / Spatial Model Editor, or
configure smprocess to not run 64-bit, 32-bit Python is also required)
MSXML 6.0
Software security (Hexagon Geospatial Licensing 2018) requires one of the following:
Ethernet card, or
MOUSE-TRAK
Z/I Mouse
ERDAS IMAGINE can be safely installed on a computer that has GeoMedia 2014,
GeoMedia 2015, GeoMedia 2016 or GeoMedia 2018 installed. However for greatest
compatibility, it is highly recommended to install matching versions.
ERDAS IMAGINE 2018 requires GeoMedia 2018 for live linking. Order of installation does
not matter.
ERDAS IMAGINE can interact with both types of personal Geodatabases (*.mdb and
*.gdb).
ArcGIS and GeoMedia
Interoperability
ERDAS IMAGINE can be safely installed on a computer that has ArcGIS® versions 10
through 10.5.1.
ERDAS IMAGINE and IMAGINE Photogrammetry can interact with ArcGIS Server 10
Geodatabase servers (ArcSDE). To read or interact with an Enterprise Geodatabase, you
must either:
o Install and license the appropriate version of ArcGIS for Desktop versions 10
through 10.4.1, OR
Oracle Server 12c 12.1.0.2.4 64-bit : Oracle Server 12c can be used to store Oracle
GeoRaster (.ogr) (requires Oracle Spatial), SDE Raster (.sdi) (requires ArcGIS for Server)
Database Engines and Oracle Spatial Features (.ogv) (requires Oracle Spatial), as well as GeoMedia
Features (.ofp).
Microsoft SQL Server 2014 : Microsoft SQL Server 2014 can be used to store GeoMedia
Features (.sfp)
PRO600
64-bit: Intel 64 (EM64T), AMD 64, or equivalent
Computer/ Processor
(Multi-core processors are strongly recommended)
1 GB for software
Disk Space
Data storage requirements vary by mapping project11
Recommended Stereo
120 Hz (or above) LCD Monitors with NVIDIA 3D Vision™ Kit 14
Display Monitors
Ethernet card, or
Peripherals Advanced data collection requires one of the following hand controllers: 16
Immersion 3D Mouse
MOUSE-TRAK
Z/I Mouse
ISSUES RESOLVED
IMAGINE ESSENTIALS
Summary – ERDAS Description / How to Reproduce
Issue ID
IMAGINE Essentials
Image Chains cause Using ERDAS IMAGINE 2016 v16.1:
crash within 5 minutes of 1. Start ERDAS IMAGINE and maximise it to your screen
starting using them (2D
View) 2. Click the Open Raster as Image Chain icon ( I have it saved to my Quick
Access Toolbar)
3. Select and open a multispectral NITF image
4. On the Multispectral tab turn on Discrete Update
5. On the SIPS tab drag the TTC slider to around 30
IM-39913
6. Pan the image a bit using the middle mouse button
7. Change Method: to Percentage DRA
8. Pan the image a bit using the middle mouse button
9. Change Method: to Multispectral DRA
10. Pan the image a bit using the middle mouse button
11. Clear the View
Choose another multispectral NITF image and open as Image ChainWhen I was
recording these steps ERDAS IMAGINE crashed at this point.
Error in displayed values Error in displayed values. The display options were set identically and the
cursor report (2D View) preferences are the same (default) in both cases. The file for which values were
IM-38946 compared is an unsigned 8 bit continuous image with 72 layers, pyramid layers
had been created in the model. When the error occurs, the histogram falsely
shows no occurrences.
Ambient Light setting on If you display a DEM as a Relief image chain the Ambient Light slider on the Relief
Relief tab only has two tab can only be set to 0 or 1. You cannot select any values between 0 and 1, the
values: 0 and 1. slider only moves to the + and – ends of the bar. ERDAS IMAGINE 2015 allowed
the user to adjust the ambient light slider to anything from 0.0 to 1.0.
IM-40539 1. Add the attached DEM “30meter.img” as image chain (File > Open >
Raster as Image Chain).
2. Change the image chain to Relief.
3. Select the Relief tab and try to change the ambient light value to
something in-between the – and + ends.
Missing the first row and Customer reported that the data of the first row and column are missing when
IM-40345 column data when reading using Gokturk-1 XML format (checked against TIFF format for the same dataset
Gokturk-1 XML format using Image Info's pixel data tab).
Help of Image Compare 1. Launch ERDAS IMAGINE 2016 v16.1
dialog to be updated with 2. Launch Compare Images from Manage Data tab > Image group
IM-37992 compare nonstandard
objects 3. Image Compare dialog opens, click on Help button
4. Observe “ Compare Nonstandard Objects” option is not in Help
Help page should be 1. Launch ERDAS IMAGINE 2016 v16.1
modified for Upload to 2. Launch Upload to Database command from Manage Data > Conversion group >
IM-37416 Database command Feature Database tools.
3. Click Help button on the Upload to Feature Database dialog.
MGRS Grid Zone Element Open an image in a Map View. From the Layout tab click the Map Grid drop-down
IM-40097 Tool does nothing menu and choose MGRS Grid Zone Element. With the other grid tools you will get
a crosshair when you hover over the image, but this tool does nothing.
Chipping: Incorrect Chips have incorrect Display Flag of blank for some specific SAR data. Since no
IM-35756 HISTOA display flag in image enhancements have been applied, the display flag of 0 should be carried
Chips forward from the previous event.
ERDAS IMAGINE 1) Open WGS84_Coords.shp in ERDAS IMAGINE.
reprojects NZTM to EPSG 2) Run Vector> Reproject Shapefile to create two derived shapefiles
4326 incorrectly
- Target projection: named ‘NZTM’ in standard list of projections
- Target projection: EPSG 2193
IM-41014
3) Overlay the output shapefiles with the original WGS84 in GeoMedia
- The file named ‘EPSG’ 2193 aligns correctly.
- The file named ‘NZTM’ not.
NAD83 (2011) projection Lidar data in NAD83 (2011) projection is recognized in ERDAS IMAGINE 2015 as
recognition GRS 1980 NAD83 (26918)
IM-38975 ERDAS IMAGINE should be able to resolve the NAD83 (2011) datum usage by
identifying the datum references that are found in the ProjectionX tab of an IMG
file produced by a third party GIS package.
Enable Editing mode When you have a Shapefile displayed in two separate 2D Views and you click the
cannot be deactivated Enable Editing button under the Drawing tab to make edits to the vector layer you
when Shapefile is cannot deactivate the editing mode by clicking the Enable Editing button again.
displayed in two different When you click the Enable Editing button to stop making edits to the vector layer
2D Views the Verify Save on Close dialog pops up asking if you want to save the changes
IM-41064 before closing. If you click Yes it saves the vector file, but it is still in editing mode.
If you click No it remains in editing mode. Sometimes ERDAS IMAGINE will crash
if you click Yes to save the vector file, click the Enable Editing button again (trying
to turn it off) and chose Yes to save the changes again.
1. Start ERDAS IMAGINE and add two 2D Views.
2. Display the Shapefile germtm_poly.shp in both 2D Views.
3. Enable editing mode by going to Drawing tab > Modify group > Enable
Editing button.
4. Select the polygon and move it to a new position.
5. Try to disable editing mode by click the Enable Editing button again.
6. The Verify Save on Close dialog pops up asking if you want to save the
changes before closing.
7. Click Yes.
8. If ERDAS IMAGINE does not crash, the editing mode is still activated.
OLH-Help of WMS tab to 1.
IM-41089 be updated The Help page for WMS support has not been updated with the *Projection* drop
down information
Discrete Update, Stretch In ERDAS IMAGINE 2016 v16.1
Panel and panning cause 1. Open a Multispectral NITF as Image Chain.
crash with Image Chains
display 2. On the Multispectral tab turn on Stretch Panel and Discrete Update.
3. In the Stretch Panel change the Left Percentage to 0.5%.
IM-36657 4. Start panning around the image using the middle mouse button for a few
seconds (15 - 30s).
5. Clear the View
6. Load a different Multispectral NITF.
7. ERDAS IMAGINE crashes.
Preference settings for Customer reported that the Precinct size settings for the JPEG2000 files in the
Precinct size for Preference are not honored by JPEG2000 DirectWrite tool.
JPEG2000 files are not The customer changed the Precinct Settings for JPEG2000 in the Preference , but
honored by JP2 found that in the output JP2 file those settings were not honored.
DirectWrite tool
Replicated in the JPEG2000 DirectWrite tool with the following settings for
JPEG2000 file in the Preference:
Tile Size: 1024
IM-36423 Precinct size: 512
Packet Progression order: LRCP
Found that in the output JPEG 2000 file the following parameters were written:
Tile Size: 1024
Precinct size: 1024
Packet Progression order: LRCP
Therefore the Precinct settings in the Preference were not honored in the above
test.
Landsat 7 or 8 USGS 1. The “Landsat-7 or Landsat-8 USGS” importer should work with IMAGINE
importer requires Essentials, but it actually requires an IMAGINE Advantage license prior to
IM-35897 IMAGINE Advantage the release of ERDAS IMAGINE 2018.
license – should only need
IMAGINE Essentials.
After assigning the CRS The customer is using an IMG file in the Lambert Azimuthal Equal Area (LAEA)
EPSG:2163 to an IMG file, CRS, which is widely uses in eMODIS Data sets by EROS in USGS. The datum
you can not open the file used in the LAEA is undefined and the Spheroid is "Sphere of Radius 6370997.
IM-36067 in a 2D View The parameters are given below:
Map Projection Parameters
Projection: LAEA
Spheriod: Sphere of Radius 6370997
Datum: Undefined
Long of projection center: 100 W
Lat of projection center: 45 N
False easting 0
False northing 0
The above particular CRS is very similar to the EPSG:2163, the US National Atlas
Equal Area, which ERDAS IMAGINE already supports. The CRS is widely used in
US National Atlas (http://georepository.com/crs_2163/US-National-Atlas-Equal-
Area.html.)
By using the Edit Image Metadata/ View Metadata If we assign a CRS
EPSG:2163, to an IMG file, which is in the CRS LAEA CRS and then open the
modified file in a 2D View, ERDAS IMAGINE crashes. The same file can be
opened in the Image Metadata (ImageInfo), but cannot be opened in the 2D View.
JPEG 2000 exporter If you create a JPEG2000 image from signed 16-bit data the resulting JP2 file is
writes empty file when empty, it only contains zeroes. The input file could be a signed 16-bit TIFF or IMG
exporting signed 16-bit raster image with a range of values (positive and negative) greater than 256.
image. Writing an unsigned 16-bit JPEG2000 file works correctly with unsigned 16-bit
input data. The help documentation for Export JPEG2000 Data states that it
supports compression of images up to unsigned and signed 28-bit depth in export.
To replicate:
1. Open the Export Data tool and set the format to JPEG 2000. (Manage
Data tab > Conversion group > Export Data)
IM-36134
2. Select “test_s16.img” as the input file.
3. Enter a name for the output JP2 file and click OK.
4. Leave the default settings in the Export to JPEG 2000 dialog and click
OK.
5. Display the JP2 output file in a 2D View and open the Image Metadata
tool to observe that the file only contains zeroes.
6. The same problem occurs when writing to JPEG 2000 format in a spatial
model using the Raster Output operator.
Problem with EPSG 6543 ERDAS IMAGINE 2016 doesn't recognize NAD83 (2011) CRS State Plane North
NAD83 2011 North Carolina ft. Assigning the CRS using Edit Image Metadata corrupts / deletes the
Carolina Ft CRS histogram of the image.
Customer reported that ERDAS IMAGINE 2016 doesn’t recognize the Datum and
IM-36078 Projection of their TIFF file. They are using image data in “ NAD_1983_2011 State
Plane North Carolina ft”. According to the customer if they do any process with
their data, the output shows the CRS in NAD83 datum , not the NAD83 (2011)
datum.
Upload and download files Upload and download files to Smart M.App option does not intimate the user
to Smart M.App option needs to login to Smart M.App
does not intimate the user Steps to replicate:
to login to Smart M.App
Without logging in to Smart M.App from ERDAS IMAGINE, go to Manage Data
IM-35900
Tab > click on Upload files to Smart M.App. A dialog opens up, with which user
cannot perform the uploading of the files.
Same case with Download files from Smart M.App.
Help also does not give info on usage of Login to Smart M.App
Proxy files aren't being If a directory containing a (multi-segment) NITF is read-only and is opened in
created in the correct ERDAS IMAGINE the SBI (sub image proxy) isn't being created in the regular
IM-36824 proxy file location proxy file location
CGCF-JP2 not creating In ERDAS IMAGINE 2016 v16.1 there are problems creating Signed 16-bit JPEG
Signed 16bit JP2 correctly 2000 images
1. JP2 is created with NoData as layer 1, and DATA as layer 2. The correct
order is DATA as layer 1, and NoData as layer 2.
IM-34601 2. Likely related to the above... The stats are correct in the JP2, but when
recalculated, all values are Zero.
3. The elevation reference system is stored in the AUX, but Image Info does
not present it.
ERDAS IMAGINE 2016 Customer reported that ERDAS IMAGINE 2016 crashes while opening Sentinel-2
crashes while opening Level 2A atmospheric corrected data in *.SAFE format.
IM-35107 Sentinel-2 Level 2A
atmospheric corrected
data
ERDAS IMAGINE 2016 Customer reported that the ERDAS IMAGINE 2016 ECW Export tool with non-
ECW Export tool creates square pixel size input data will deliver incorrectly geo-located output file. The
wrongly geo-located geolocation failure will increase from UL to LR corner.
output with non-square Transformation of pixel seems to be not exact. The output ECW image gets
IM-34969 pixel size input distorted also in shape
However if we look at the Output image metadata, it shows the exact same pixel
dimension and resolution as that of the input image, but the Active Area pixels are
moved
ERDAS IMAGINE crashes Drag and drop the KAZEOSat .dim file from Windows Explorer to a 2DView.
IM-34175 dragging KazEOSat ERDAS IMAGINE crashes.
image into 2DView
Image Chains don't When you display a NITF (and some other formats) image in a 2D View as a
display the NITF metadata Raster, parts of the NITF metadata tags are displayed in the 2D Views title bar.
banners in the title bar of Classification, GSD, WAC, etc.
IM-33848 the 2D View However if you display the same image as an Image Chain, only the image file
name is shown in the title bar.
dialog, ERDAS IMAGINE crashes. The partner also reported that they had older
data from previous deliveries from ESA and they do not cause any problems.
ERDAS IMAGINE crashes 1. Launch ERDAS IMAGINE 2016 v16.1
with Stretch panel type as 2. Load SAR image as Raster as Image chain from File > Open > Raster as
Two Point Linear (or SD) Image chain.
in the case of the Radar
Image Chain. 3. Now Click on Panchromatic tab and Launch stretch panel
IM-39300
4. Select Radar from Image Chain drop down
5. Now select Stretch panel type as Two point Linear and observe ERDAS
IMAGINE crashes.
Editing with Breakpoint Editing with the Breakpoint Editor can cause ERDAS IMAGINE to crash when
Editor will cause ERDAS clearing the display. External report cites a crash, but internal test results in
IMAGINE to crash ERDAS IMAGINE hanging until the process is terminated.
To replicate:
1. Open the oranien_save.img (without No Stretch Option)
2. Open the Breakpoint Editor
3. Add 2 points and modify the LUT
IM-38972 4. Select Apply To: Image File
5. Press 'Apply' button
6. press "OK" to confirm Warning dialogue
7. Close the Breakpoint Editor
8. Clear the Display
At this point, ERDAS IMAGINE is reported to crash. In internal tests, ERDAS
IMAGINE hangs until the ERDAS IMAGINE process is terminated.
Cannot open Sentinel-2 Customer reported that ERDAS IMAGINE 2016 v16.1 + the initial Sentinel-2 Hotfix
IM-39297 data from USGS Earth cannot open the Sentinel-2 data from the USGS Earth Explorer.
Explorer
Batch Command Editor In the Batch Command Editor:
isn't selecting Variable 1. Select the output variable (Output1).
column in CellArray,
giving the user zero 2. Close the Variable Editor.
feedback of how to enable 3. Go to add more input files.
the Add Files button or to 4. The Add Files... button is disabled
specify files for a specific
5. How do I enable it?
variable
6. Select the Input1 column in the CellArray.
IM-38759 7. OK, now the Add Files... button is enabled.
8. Select the Ouput1 column in the CellArray.
9. Now the Add Files... button is disabled again.
10. Select the Input1 column again.
11. Bring up the Variable Editor again.
12. Select the Output1 variable.
13. The Input1 column in the CellArray gets unselected, but the Output1
column does not show that it's selected (although it is, according to the
Batch Command Editor).
IM-38394 Need new proxy Need new proxy setting/preference for the ERDAS IMAGINE 2016 WMS service.
preference for ERDAS
Coregistration with Stripping observed when processing a single burst. We believe that is it being
IM-37729 Sentinel-1 can have caused by the Doppler parameters being incorrect.
Stripping
Filename length error in When trying to open Sentinel-2 data in SAFE format, you may get a filename
ERDAS IMAGINE when length error in ERDAS IMAGINE.
reading from *.SAFE
How to resolve (for both formats):
1. Try to reduce the number of characters (together with .*SAFE filename)
IM-37668 to less than or equal to 100. Counting to the .jp2 files location (together
with filename itself) it appeared to be that appropriate maximal filename
length for reading from SAFE is 184 characters for new format and 244
for old.
2. New format has shorter filenames than old, but acceptable deepest
filename length is less. The only what is in common here is 100
characters counting together with *.SAFE filename.
Saving Zonal Change 1. Launch ERDAS IMAGINE 2016 v16.1
project crashes ERDAS 2. Launch Zonal change layout from File> Layout > Zonal change layout.
IMAGINE
3. Create a New project and load images
4. Now select Auto-grid and provide Rows and Columns as 4,4 Click OK.
5. Now Run region and Load Results.
IM-37618 6. Now from the process tab select Save As and browse to the project name
which is created in second step (i.e. initially created new project
name)and Click Ok
7. Click Yes for attention dialog and Click OK on File chooser.
8. Now Click Yes for overwrite attention dialog and observe ERDAS
IMAGINE crashes.
Printing a Map with 1. The image had been displayed using LaGrange resampling.
LaGrange resampling 2. Display the .map in a Map View
causes a memory error
IM-37634 3. Select File / Print and send to our network printer
4. Error: No memory.
Pixel Blocks are missing 1. In a 2D View, open both an img and a jp2. make sure that img is on
IM-37922
in the 2D View while the bottom in the TOC.
transition of overlapped 2. Zoom in to an area where there is overlap so that you can see all of
images. the jp2
3. In Home tab turn on swipe and the transition tab appears.
4. Place the swipe line in an observable location
5. Zoom in to 1:204 on the location and note there are not pixel blocks
missing from the image.
6. Zoom in/out and move the Transition Extent.
7. Observe pixel blocks missing.
RadarSAT II images When opening RadarSat 2 greater than 4Gb the display is incorrect (SLC data
IM-37743 greater the 4gb fail to be format)
read correctly
"Thematic" NITF as This behavior was noticed in ERDAS IMAGINE 2016 v16.1
ImageChain ends up with 1. Open the NITF as ImageChain.
a blank TTC Family menu
2. Click the SIPS tab.
IM-37542
3. Note that the TTC Family pull down is blank - there's no options to
choose from.
ERDAS IMAGINE 2016 Customer reported that ERDAS IMAGINE 2016 v16.1 does not subset ECW
v16.1 subset dialog images to a ECW subset image. The customer is using the IMAGINE subset tool.
IM-37320
crashes while subsetting a The status dialog either crashes or disappears. No file is written to disk in the
6GB or more ECW file. designated folder. The issue appears to be with files around 6GBs.
All File-based Raster 1. Make sure your Preferences are set so you are using the "All File-based
Formats filter does not Raster Formats" file filter.
see *.nitf files 2. Bring up the File Chooser by clicking the "Open" icon on the Quick
Access Toolbar (top left)
IM-37602 3. Note that none of the SICD NITF files show up.
4. If you change the filter to "NITF 2.x" they show up.
5. Also if you change the extension from .nitf to .ntf they show up.
6. "All File-based Raster Formats" should be capable of showing *.nitf files.
I got a similar error when attempting to use the File Chooser / Sub-images tab and
selecting the "Unknown" Mosaic segment.
Reprojected output from Customer reported that when they reproject from Sinusoidal CRS to Lambert
Sinusoidal CRS to LAEA Azimuthal Equal Area (LAEA) CRS , the output file gets shifted as compared to the
CRS in IMAGINE 2016.x reprojection output from IMAGINE 8.7
are shifted, v8.7 output
fine
The Sinusoidal CRS parameters are given below:
Projection Type: Sinusoidal
Spheroid Name: WGS 84
Datum Name: WGS 84
Longitude of Central Meridan: 0:0:0 E
False Easting: 0.0 meters
False Northing: 0.0 meters
ERDAS IMAGINE crashes 1. Try to open an annotation file that contains text that is using a font that is
when selecting text that's not present on the computer
using a font that is not 2. You get a message that the font doesn't exist, and nothing is rendered.
IM-29924
present on the computer
3. Now click where you know the text to be
4. ERDAS IMAGINE crashes.
Area Fill update removed After using the Area Fill tool on an IMG format raster image and saving the image
from image when saving with a new name, the area fill colors are removed and the image reverts back to its
layer as new file. original state.
How to reproduce:
1. Open the image “lanier_fill.img” in an IMAGINE 2D View with the No
Stretch raster option enabled.
2. Draw an AOI polygon in any area of the image.
3. Make sure that the AOI is selected.
4. Select “lanier_fill.img” in the Contents panel.
5. Open the Area Fill tool by clicking on the Fill button in found in the Edit
group under the Multispectral tab.
6. In the Area Fill tool, make sure that the Function option is set to Constant
IM-19471 and leave the Fill With values is set to 0.0.
7. Click the Apply button to convert the pixel values within the AOI polygon
to the new pixel value.
8. An Attention message will pop up saying "This layer is using a data
stretch lookup table. When editing pixel values you may want to remove
the data stretch lookup table. Do you want to do this now? Click Yes.
9. Another warning message will display saying “Since this function modifies
the pixel values of the image, you may wish to recalculate the statistics
and histogram for the layer before doing any other operation that
depends on this data.” Click OK.
10. Close the Area Fill tool.
11. Right-click on the image name “lanier.img” in the Contents panel and
choose Save Layer As.
12. Enter a new filename for the image and click OK in the Save As dialog.
13. Notice that the area fill disappears and the image looks like it originally
did.
ERDAS IMAGINE is not 1. Manage data tab > Export JPEG 2000
displaying pixel values of 2. Export a Signed 16-bit image with default values.
IM-18969 exported JP2 file using
Signed 16-bit as input 3. Display the output file in a 2D VIew, blank file is displayed.
"Cannot create canvas 1. Ensure that their association to Elevation Library is still intact.
bitmap" error roaming 2. Start a 2D View and make sure it is taking up as much room on screen as
calibrated TIFF images possible.
3. Click File Open, select both TIFF images (as separate files), turn on
Orient to Map and Fit to Frame and click OK.
4. Once the data has displayed go to 1:1 zoom.
IM-17902 5. Rapidly use the middle mouse button to pan to the right edge, then down
to the LR corner, then across to the LL corner, then up to UL corner then
start randomly roaming around the images.
6. The Virtual Memory Size will very quickly go up to 4GB and hover around
there. At some stage it will tip over and you will get a "Cannot create
canvas bitmap" error.
Fit to Frame doesn't work Fit to Frame doesn't work for JPEG
for 306 JPEGs (runs out Load all 306 files and click on Fit to Frame, it runs out of memory. The rrds are all
of memory) Imagine rrds.
IM-13775
At 1:1 uses 2.67GB memory and rises as pan and zooming
Crashes at Fit-to-Frame when reaches 3.67 GB memory
IMAGINE ADVANTAGE
Summary – ERDAS Description / How to Reproduce
Issue ID
IMAGINE Advantage
IM-37583 The new option added in FLS "Use Zonal Input Image" option has been added to FLS Image Segmentation dialog. This
Segmentation is not option is not explained in the Online Help of this dialog.
explained in OLH.
MosaicPro output option Customer reported that MosaicPro output option “User Defined AOI” is not working in the
“User Defined AOI” is not case of ECW output. By defining an output boundary via AOI in MosaicPro output options,
working in the case of ECW the output file will not deliver correct results if the output format is ECW. The defined output
output. AOI will generate correct results when using IMG as output format.
To replicate:
2. Add an AOI using the “User Defined AOI” option from “Edit” > “Output options” > “User
IM-37672
Defined AOI” and set to create a single output image.
You will see the output boundary by AOI is not generating a correct subsetted output in the
case of ECW, but does for an IMG output.
MosaicPro stops when the Customer reported when the machine goes into a screen lock mode, the MosaicPro’s mosaic
IM-22772 machine goes into a screen process stops. The mosaic process runs for a while and then just stops. All the power
lock mode settings in the machine are set to never stop or shutdown.
MosaicPro changes negative Customer reported that MosaicPro is changing all the negative values to 1 in the mosaic
values to 1 if feathering is process when they perform Feathering.
selected
The customer’s data are signed 16 bit dems. There is not much overlap between tiles.
To replicate:
Set the ignore input value as -32767 and set output background value as 0.
Mosaic output with Feathering will show all the previous negative values as 1:
However if you do not apply feathering, the mosaic output will retain the original negative
pixel value.
Overlap-based Histogram This contains 2 images from a continuous collect (same day, virtually same time) so the DNs
Matching gives unexpected should be directly comparable image to image.
results
IM-39630 Running MosaicPro to mosaic the two images gives unexpected results.
Basically the only things I've told MosaicPro to do are geometry outlines, overlap-based
Histogram Matching and feathering.
This appears to simply be a case that Run Now and Submit do not honor the Preference. For
Submit you can change the number of Processors to use manually. But Run Now has no
dialog, so it runs just 1 processor at a time. Both need to honor the Preference.
ERDAS IMAGINE 2016 Customer reported that ERDAS IMAGINE 2016’s Warptool crashes while selecting the
Warptool crashes while “SPOT5-Orbital Pushbroom” model. If the same data is used in ERDAS IMAGINE 2015 with
selecting the SPOT5-Orbital SPOT5-Orbital Pushbroom model, the Warptool works as usual.
Pushbroom model
In order to replicate the problem, please do the following:
IM-40226
1. Open the SPOT5 image in the 2D View
2. The Raster > Panchromatic > Transform and Ortho Correct > Control Points
3. From the List of Models, select the “SPOT5-Orbital Pushbroom”> OK. You will see
the Warptool crashes
MosaicPro will crash if a .mop MosaicPro will crash and the .mop file used will be corrupted if you choose to select the .mop
file is chosen from the file from the RECENT Browser. An error message will come up, "Verify Save on Close"
RECENT files browser. .mop Filename dadadada.mop Save changes before closing? If you say NO the message goes
IM-30066
is corrupted. away and everything is fine. You can continue your work. If you say YES, MosaicPro closes
and the .mop file you tried to open is corrupted. If you try to open it again it will crash
MosaicPro again.
configure_csm command line The utility does not appear to be a console app so it runs in the background after launch so
IM-33591 utility does not exit with the return code returned is usually always success. This is unhelpful for running the utility
proper error code from the command line or in a batch setup
ERDAS IMAGINE crashes Customer reported that IMAGINE Warptool crashes while using GCP Tool (Polynomial
when GCP Tool predicts Model) to refine geometry of an input file to that of a reference file. The customer begins with
point location 1st order Polynomial. Take 3 points manually in both frames (input & reference). As soon as I
take 4th point, where the 1st order poly can predict location in other frame then ERDAS
Warptool.exe consistently exits.
4. Take (3) pair of points in Input and Reference frames; GCP#1, GCP#2, GCP#3
IM-41771 Non-Support of 64-bit CSMs ERDAS IMAGINE 2016 v16.1 cannot configure and use 64-bit CSM plugins.
Radar Analyst Look Direction The look direction arrow is pointing in the opposite/incorrect direction for a descending orbit
arrow points in opposite TerraSAR-X high resolution spotlight image.
IM-41443 direction for descending orbit
TerraSAR-X data The problem is the time order the pixels are written to the file. The descending image has
the last image pixels at the beginning of each line while the oldest are at the end.
IMAGINE OBJECTIVE
Summary – ERDAS Description / How to Reproduce
Issue ID
IMAGINE Objective
IMAGINE Objective crashes IMAGINE Objective 2016 crashes when attempting to open feature projects that were
opening projects from earlier created in IMAGINE Objective 2015 if the Java Runtime Environment is not installed with
version if Java not installed ERDAS IMAGINE 2016.
with ERDAS IMAGINE 2016
IMAGINE Objective should provide an error message that Java needs to be installed instead
IM-37591
of crashing.
If you modify the ERDAS IMAGINE 2016 installation to include the Java Runtime
Environment then IMAGINE Objective will be able to open feature projects from earlier
versions.
Outlier Clipper operator using Using VCO Outlier Clipper operator with Clip type set to Convex fails with error. Outlier
IM-36758
Convex clip fails Clipper operator with Clip type set to Concave runs successfully.
IMAGINE PHOTOGRAMMETRY
Summary – ERDAS Description / How to Reproduce
Issue ID IMAGINE
Photogrammetry
Rasterizing LAS from Read- Delete your Proxies directory (in $HOME, typically
IM-35215 Only directory crashes if c:\users\USERNAME\.imagine1600\Proxies). Run the model (probably need to change the
Proxies directory is missing output file). It looks like it can't create the img because the Proxies directory does not exist.
Detect Vertical Obstructions If you execute the GMDX in ERDAS IMAGINE, you get the following:
Model failing in Remove
Background Row While the Extract Spikes sub-model was highlighted it displayed a dialog:
---------------------------
ERDAS IMAGINE
---------------------------
---------------------------
Retry Cancel
---------------------------
If you cancel, the model will continue to run until it hits the Remove background Row
operator, at which point it will throw this error:
Spatial Model failed in Remove Background Row. The error was "<NULL> failed
egda_BaseDataStackCreateContiguous failedArgs".
3. After dismissing the error message notice that the images in SAFI don't overlap.
APM error ORIMA 2016 APM (SP1 is installed) fails with error message: "ERDAS IMAGINE: One or
more files cannot be opened by 64 bit APM Process. Starting in 32 bit." This has been seen
by multiple customers. However this is not an ORIMA issue because same error can be
IM-39887 replicated with IMAGINE Photogrammetry when running APM. A customer reported that the
error cannot be replicated with ORIMA 2016 or with ORIMA 2015, so some customers
reverted back to ERDAS IMAGINE 2016. This may be related to pyramid or statistic issue
because after I regenerated the pyramids in IMAGINE Photogrammetry I could run APM
Blocktool crash Customers reported blocktool crash. This happens only when IMAGINE Photogrammetry is
launched from Toolbox.
IM-38745
All reported the same error code number: “ blocktool.exe exited with status -1073741819”
Customers’ OS is Windows 7.
APM crashes when aux files APM crashes if pyramids and statistics are missing. APM should check the image statistics
are missing. and pyramid layers, and if they are missing or not created correctly, it should prompt you to
IM-39296
create the proper pyramids and statistics as needed. This issue is reported for pushbroom
sensor model, however I can replicate with Altdorf dataset after deleting aux and rrd files.
eATE crashing Customer attempted to use the eATE to extract elevation surface in ERDAS IMAGINE 2016
IM-37581 and the process crashes. However, the customer reported that setting up the same block
with the same settings in ERDAS IMAGINE 2011, he was able to run the eATE.
ORIMA APM fails with 64-bit ORIMA 2016 APM (SP1 is installed) fails with error message: "ERDAS IMAGINE: One or
IM-37595
message more files cannot be opened by 64 bit APM Process. Starting in 32 bit."
64-bit CSM Plugin Manager 64 bit CSM Plugin Manager missing from ERDAS IMAGINE Interface.
IM-37463 missing from IMAGINE
interface Note, the csmPluginManager.exe is actually there and can be run from Explorer.
2. In Block Property setup dialog, enter Average elevation as 1 and click Ok.
Test case2:
1. Create a new block file with Geometric model Category: Orbital Pushbroom and
IM-37172
Geometric Model:SPOT5.
2. In Block Property setup dialog, enter Average elevation as 1 and click Ok.
Test case3:
1. Create a new block file with Geometric model Category: Orbital Pushbroom and
Geometric Model:THEOS1.
2. In Block Property setup dialog, enter Average elevation as 1 and click Ok.
Observe that Add DEM File Name dialog reappears and dem file need to be re-selected.
IMAGINE PROFESSIONAL
Summary – ERDAS Description / How to Reproduce
Issue ID
IMAGINE Professional
The Batch function crashes 1. Open the Spectral Analysis Workstation tool
the Spectral Analysis
Workstation 2. File | Open Project…Material_Mapping.iwp
6. Select Batch
FLS Segmentation crashes Use raw_diff.img as input file and grid_raster as zonal input file.Accept defaults and run.
IM-37701
when using zonal input
Cannot merge two signatures The Signature Editor will crash if you attempt to merge two signatures that were collected
with 16-bit data. using 16-bit data. The session log reports “siged.exe exited with status -1073741819.”
1. Start the Signature Editor (Raster tab > Classification group > Supervised menu >
Signature Editor).
IM-37582
2. Open the signature file “quickbird_16bit.sig”.
3. Select any two signatures in the CellArray and attempt to merge them to create a
new signature (Edit > Merge).
ERDAS Interferometry Customer reported that ERDAS Interferometry module Spectral Shift Filter does not work
module Spectral Shift Filter - with Sentinel-1 SAR and ALOS data. It causes the program to crash.
IM-36986
remove from interface
After Subset in After Subset in Interferometry, semi manual uses original images not subset. This can make
Interferometry, semi manual the subset unusable for some datasets.
IM-40182
uses original images not
subset
6. Now place points Stern and Bow on the image and Click on Extract feature and
observe ERDAS IMAGINE crashes
7. Sometimes you might have to digitize and extract a second feature before it
crashes.
The current ERS-1, ERS-2 Add support for new ERS-1, ERS-2 SAR format (*.E2) from ESA
SAR data products format
(*.E2) is not recognized by The *.*.001 CEOS format of ERS is no longer to be provided in the new On-The-Fly (OTF)
IM-39599
ERDAS IMAGINE infrastructure. ERS-1/2 SAR Level 1 SLC is available via download through EOLI-SA (Earth
Observation Link), the European Space Agency’s client for Earth Observation Catalogue and
Ordering Services.
IM-37765 ILU filtered output is incorrect ILU filtered output is incorrect because it does not contain any information
Multi Temporal Layer Name The MTC result has the incorrect layer names. Should be Ref, Match, Coherence
IM-37663
is incorrect
Slow calculation of products Stats calculation taking too long for ILU/MTC and Texture
IM-37955
within CCD
SPATIAL MODELER
Summary – Spatial Description / How to Reproduce
Issue ID
Modeler
Raster Output operator OLH Raster Output documentation is a little mixed. The Help topic says Filename is required but
needs updating the Properties panel within Spatial Model Editor indicates otherwise and at runtime it does
IM-37700
not actually require it. There isn’t any discussion about the creation of a temporary filename,
and no reference to such a file being deleted either.
Brightness Contrast and The Brightness Contrast Operator and the Photo Enhancement Operator require U8 Inputs
Photo Enhancement and this is not noted in the Help but more importantly neither operator accepts an U8 input
IM-35483
Operator Help incomplete image unless you run it through full range stretch (or similar) before connecting the input to
either of these operators.
ERDAS IMAGINE crashes 1. Launch ERDAS IMAGINE 2016, and launch Spatial Model Editor.
with model containing
Generate Contours and 2. Load the model Featureinfo.gmdx.
IM-36158 Features Information operator
when features concurrency is 3. Provide the input as 1815_1_1subset.las and click on Run button to execute the
enabled model.
ERDAS IMAGINE crashes 1. Launch ERDAS IMAGINE 2016 v16.1, and launch Spatial Model Editor.
with Model containing Vector
IM-36363 Input As Raster, Clump, 2. Open the specific model and provide the input as states.shp
Convert To Features
operators 3. Click on preview to execute the model.
Adding attributes to Feature 1. Launch ERDAS IMAGINE 2016 v16.1, and launch Spatial Model Editor.
output from Line of Sight
operator showing error 2. Load the specific model and provide the inputs accordingly in the model.
message.
IM-35571
3. Click on the preview to execute the model.
4. After preview is loaded select preview > Right click > Show attributes and Observe
an Error message saying Input String is not in a correct format.
ERDAS IMAGINE crashes 1. Launch ERDAS IMAGINE 2016 v16.1, and launch Spatial Model Editor.
with launching the metadata
of point cloud data from 2. Preview any las file using point cloud input and preview.
IM-35212 preview of the Spatial Model
Editor 3. Now try to open the metadata from preview by right clicking on preview in the
contents tab.
Render Map Composition Execute RMC operator. ERDAS IMAGINE shows error that ‘Invalid Arguments for Program:
IM-35461 (RMC) operator is not (null)’. RMC fails.
working
Spatial Modeler Editor The Spatial Modeler Editor crashes when minimizing or switching views. On numerous
IM-39854 crashes when minimizing or occasions edits are lost and models have sometimes become corrupted. In some cases the
switching views model will be saved from the temp version but the latest edits are not always saved.
Spatial Modeler aborts Spatial Modeler fails near the end of the model when pyramid layers are being computed. If
ERDAS IMAGINE when the Compute Pyramid Layers preference is turned off, the model runs to completion.
completing pyramid layers
The .img, .ige, .rrd and .rde, files are written when ERDAS IMAGINE aborts. The .img file is
usable but the pyramid layers are invalid, only showing NULL values.
IM-39952
The Info icon is shown in the Viewer TOC when the image is displayed. Running the
Correction option indicates the pyramid layers are not optimized but the correction action
does not repair the pyramid layers. They must be deleted and recomputed with Image
Command.
Incorrect output when using If you use a single Point Cloud Input operator that feeds into two different processing chains
single Point Cloud Input of a spatial model, only the first chain will produce the correct output. The second chain of
IM-39611
operator with multiple the model to be processed produces an empty raster output file. If you use two Point Cloud
processing chains. Input operators to keep each chain of the model separate it works correctly.
Stack: GMD converted to Customer reports having a GMD model which, when displayed in the Model Maker GUI and
GMDX is hugely (unusably) executed runs in under a minute.
slower to run, possibly due to
IM-22352
processing 48 bands? Open the GMD into Spatial Model Editor (and save as a GMDX if you want - makes no
difference) and try to execute it and it becomes unresponsive (actually, it takes a very long
time to complete)
Opacity attribute field is not Model is producing thematic output to which I assign colors and opacities using the
recognised by Preview appropriate Operators.
IM-22023
However when Previewed, the colors are represented, but the opacity is not.
Spatial Modeler SDK This results with no logs being available when ImageChains is being used.
IM-38108 (SMSDK) does not register
ECW JP2SDK logger.
Subset needs a Batch option When we switched Subset over from Model Maker to Spatial Modeler we did the great thing
which doesn't autovariabalise of automatically variabalising the command when it's added to Batch.
But unfortunately, for most users it over-variabalises. They are presented with numerous
IM-36821
variable columns to fill in that they generally don't want / need to fill in.
Would it be possible to have an option to drop the command into the Batch Editor un-
variabalised?
Create Submodel loses 1. Create a new Spatial Model in the Spatial Model Editor.
model tail
2. Add a Raster Input, a Raster Output, and two Port Inputs. Connect them as you
normally would.
4. Select the Raster Input and the Raster Output and click Create Submodel to put
them in a submodel.
6. When you click on OK on the dialog, the dialog goes away, but the model doesn't
run.
ERDAS IMAGINE crashes 1. Launch ERDAS IMAGINE 2016 and launch Spatial Model Editor.
with model containing Image
IM-36194 Pair operator and Feature 2. Load the specific model and provide the input
Output operator.
3. Click on run button and observe ERDAS IMAGINE crashes.
Complex Expression can Try opening the test model in the Spatial Model Editor.
cause re-opening Model to
crash ERDAS IMAGINE ERDAS IMAGINE crashes.
IM-36138
Customer believes its related to changing the very large expressions once the model is
already built.
OLH of Apply Index operator 1. Launch ERDAS IMAGINE 2016 and launch Spatial Model Editor
should be updated with
Sentinel-2, Gokturk, 2. Drag Apply Index operator and observe Help.
IM-36128 KazEOSat sensor information
3. Supported Sensors should be updated with Sentinel-2 ,Gokturk, KazEOSat in the
Help.
Subtractive Resolution Merge 1. Open the Subtractive Resolution Merge Model in the Spatial Model Editor, and
model runs in Editor (32-bit) click Run.
but not in Background (64-bit)
in ERDAS IMAGINE 2016 2. Provide an output filename. Other parameters should already be set, but you might
have to select the IKONOS-specific weights table from wherever you have ERDAS
IMAGINE installed.
8. But then the meter goes red and the model exits.
Streaming data cannot be If you run the model an error message displays.
IM-35748 passed into Iterator inside
another Iterator operator
4. Note that there is no value-based NoData (or NoData of any kind) set on the output
image even though there's a Set to NoData after the Raster Input and plenty of 0s
to set to NoData in the input image.
Point cloud input taking input 1. Launch ERDAS IMAGINE 2016, and launch Spatial Model Editor.
as raster file and shape file
and creating wrong 2. Connect a model as shown and provide the input as any shape file or raster file from
IM-36179 impression of success. recent as shown in figure
3. Now click on preview and observe that it is showing success which is a wrong impression
to the user and not the case with Raster input and Feature input operators.
OLH of Raster To Bitmap 1. Launch ERDAS IMAGINE 2016, and launch Spatial Model Editor.
operator to be updated.
2. Drag Raster To Bitmap operator and observe help
OLH of Get DRA Params 1. Launch ERDAS IMAGINE 2016, and launch Spatial Model Editor.
should be updated
IM-36127 2. Drag Get DRA Params operator and observe help
Help page should be updated with show all ports and default ports figures.
EML numerical entry can be This problem is not seen with Windows non-English language format in ERDAS IMAGINE
broken with feature input and 2015, and is not seen in ERDAS IMAGINE 2016 with Windows English language format. The
Windows non-English problem is not observed with raster input in Spatial Modeler.
language format
To reproduce:
1. Windows > Control Panel > Region and Language > Format > Italian > Apply
IM-36217 3. Session log should display 'Locale: it-IT'. At this point EML does not honor the
decimal symbol comma ( , ). However Windows does (e.g. Calculator).
5. Open a ‘Define Processing Area’ operator > open Cell Size Rule pulldown menu >
select Specify. In X file type 1,50 <cr>.
Spatial Modeler runs out of Model using Iterator operator with an embedded Iterator operator runs out of memory and
memory and crashes ERDAS crashes ERDAS IMAGINE after processing ~25 of 48 images. Raster operators include
IM-36216
IMAGINE Zonal Mean, Direct Lookup, and Stack Layers. Same model completes successfully when
Run in Background.
Screenshot of List operator in Screenshot of List operator in OLH and User Interface is not in sync with Value1 input port
OLH and User Interface is not
IM-36093
in sync OLH needs update of operator screenshot, displaying Value1 input port as only the required
port.
OptimizePyramidInfo takes a Copy the image to a directory that has LOTS of files in it, for example over 4000 files.
long time if there are many
files in the directory Run the CreateRSETs operator on the image in that directory.
IM-35172
It takes a long time for the operator to actually complete execution after the meters shows
that the RSETs have been created.
Existing data not found on Customer reported that he modified his model, saved it, then when tried to open he got an
port(Expression). error “Existing data not found on port(Expression)”.
IM-35550
Open the model. Simply drag&drop to the model an Expression operator, don't attach to
anything, don't provide any expression. Save your model. Then try to open again.
ERDAS IMAGINE crashes 1. ERDAS IMAGINE 2016 v16.1, and launch Spatial Model Editor.
with model containing Image
Pair and Image Pair 2. Load the model in the SM editor.
IM-35324 Information operators.
3. Provide the Raster inputs
4. Click on Preview to execute the model and observe ERDAS IMAGINE crashes.
Batch Editor uses I have a very simple model which has a Raster Input feeding to a Raster Output and two Port
inappropriate default Inputs for the input filename and output filename.
filenaming for Models
The path for the default output filename does not exist and I don't really want it to be
IM-35250 automatically created and a directory name, rather than a filename, be used to identify the
different outputs from the batch processing.
I would have expected the output variable to be defined with the extension/format determined
from the provided output.
Memory problem when This model attempts to take the sub-image of an input Sentinel-2 SAFE dataset
handling 6 vs 4 bands in corresponding to just the 20m bands (all six of them) and convert them to a different output
Spatial Modeler format. Problems occur when running in the Spatial Model Editor (i.e. 32-bit).
IM-35401
If I output the 20m bands to IMG format, the process gets to almost the end of the Raster
Output operator and then ERDAS IMAGINE simply goes away.
Conditional Operator is losing In some conditions the Conditional operator appears to lose the NoData mask.
IM-34966
NoData mask
Previewing a simple Sentinel- Start Spatial Model Editor and load the Model.
2 Model runs out of memory
Click Preview and select the SAFE Sentinel-2 image as input.
IM-35027
Initially all will look good, but after a couple of "pages" of data you'll start to see numerous
messages appearing in the Session Log related to memory.
APM Operator The APM Operator documentation is incomplete. Inexperienced users are unaware of APM
Documentation Incomplete needs.
Documentation Needs:
Problem with ECW file in SM Customer reported that ERDAS IMAGINE 2016 is having problem with ECW file in displaying
processing with shapefile in and processing with shapefile in Dutch Language settings in English OS. The ECW file is
IM-35109 Dutch Language settings properly loaded using ERDAS IMAGINE 2016 and the regional setting is English (United
States). However the same ECW file is not properly loaded using ERDAS IMAGINE 2016
and the regional setting in Dutch (Netherlands).
ERDAS IMAGINE crashes on 1. Open the gmdx file in Spatial Model Editor.
clicking in the viewer after
volumetric analysis with 2. Open a LAS in a 2D viewer.
metadata of preview
launched. 3. Draw an AOI in the 2D viewer on top of the LAS file.
5. In the volume boundary port of the Point Cloud Measure Volume operator give
Viewer as option and run the preview.
IM-34523
6. Right click on the Preview layer in the Contents panel and select *Show
Attributes*.
7. With the AOI in the viewer selected, go to the Point Cloud tab and select *Load*
from the *Boundary* drop down in the *Volumetric Analysis* group.
10. Click in the 2D viewer within the AOI. ERDAS IMAGINE crashes.
Can no longer really delete If a port the aliased port is connected to has a default value
IM-34384
default values from a model
Create Geospatial PDF Create simple model with Create Geospatial PDF operator. Enter the output file name
operator does not add the without extension. It should automatically add extension pdf if not already provided.
IM-34457
extension to the output file
name
Stream output from Merge Open the specific model and give the shapefile as input. Click the Preview button. Notice that
Features if passed to ERDAS IMAGINE crashes.
IM-34222 Measure Area operator would
crash ERDAS IMAGINE. If a Features Output operator is introduced between Merge features and Measure Area
operators then no such issue exists.
Image Info reports skip of 4 1. Open the specific model in the Spatial Model Editor.
even though Stats operator
was set to 1 2. Note that the Statistics Operator prior to Raster Output is set to a Skip of 1. Run.
IM-34528
3. Open the resulting image in a 2D View and bring up ImageInfo.
Clicking the Help button on 1. Create a Spatial Model with at least one input port.
the smguiprocess dialog gets
an error (no help) 2. Save the model.
3. Select Launch Spatial Model under the Spatial Model Editor dropdown in the
Common group on the Toolbox tab.
IM-33840
4. Select the model you just saved.
5. A dialog is displayed for you to enter values for the input port.
Create Temp Filename with 1. Open the model and click Run.
Extensions causes Create
Geospatial PDF to fail 2. Specify an output PDF filename and OK.
IM-33511 4. On the first Create Temp Filename operator, specify an Extension of .img
5. Click Run again. Click yes, you wish to delete the existing output file.
Need to properly handle No Vertical CRS: should convert the features from 3D to 2D.
Vertical Coordinate
Reference Systems for 1 Vertical CRS: should update the vertical CRS of the primary geometry field
IM-33459 Attach Vertical CRS Operator
N Vertical CRSs: if there are not 'N' geometry fields, throw a mismatched list exception. If
there are 'N' geometry fields apply each item in the list to the corresponding geometry field.
4. While the Preview is running select the custom matrix and convolve operator and
create a sub-model.
3. For the output file select JPEG 2000 for the "Files of type" and give it a file name.
5. Use HFAView to look at the Statistics Parameters in the .aux file created for your
output .jp2 file. The ExcludedValues have a datatype of EGDA_TYPE_U8 and an
objecttype of EGDA_RASTER_OBJECT.
*Do NOT delete the output from this workflow because you will need it for Case 2."
*Close ERDAS IMAGINE between Case 1 and Case 2 to make sure that there's no caching
IM-39239 of the statistics for the .jp2 file*
1. Rename the .aux file created for the output .jp2 in Case 1.
2. Open the .jp2 file output from Case 1 in ImageInfo and confirm that it has mask-
based persisted NODATA and *no statistics*.
1. 7. Use HFAView to look at the Statistics Parameters in the .img file. The
ExcludedValues have a datatype of EGDA_TYPE_U8 and an objecttype of
EGDA_RASTER_OBJECT.
Oblique Stereographic EPSG When the Geodetic Reproject Raster service (spatial model) is called using an Oblique
code not working for Stereographic EPSG code, an error message displays.
IM-39334
Geodetic Reproject Raster
service
South Polar Stereographic When the Geodetic Reproject Raster service (spatial model) is called using a South Polar
IM-39330
EPSG code not working for Stereographic EPSG code, an error message displays.
MrSID DLL reporting MrSID file does not have NODATA (modeler didn't ever deal with NODATA). But if you open
persisted NODATA value for this image in ImageInfo and look at the "NODATA Persistence" on the "Pixel data" tab, it
IM-39213
images without Alpha shows "Value(0)".
channel or Background Pixel
North Polar Stereographic When the Geodetic Reproject Raster service (spatial model) is called using a North Polar
EPSG code not working for Stereographic EPSG code, an error message is displayed.
IM-39335
Geodetic Reproject Raster
service
Buffer Analysis not interacting I have a very simple model (attached to original bug), which has a Raster Input feeding to a
with Batch Editor correctly Raster Output and two Port Inputs for the input filename and output filename.
IM-38774 I have run this model using an input path, and an output path. When run in Batch, the
Variables are not defined correctly. But that path does not exist and I don't really want it to be
automatically created and a directory name, rather than a filename, be used to identify the
different outputs from the batch processing.
Making incorrect Flow Control Start Spatial Model Editor, and add a Raster Input operator.
connection crashes ERDAS
IMAGINE Add a Band Selection operator and select it.
IM-39363
Turn on Flow control. Connect the Raster Input's raster output port to the Previous port
on Band Selection. ERDAS IMAGINE crashes.
UAI / AUX shows correct 2. Start ERDAS IMAGINE and open the ImageInfo dialog. Load the.uai file.
geometry model in ImageInfo,
but incorrect in GetMetadata 3. Note that the Geo Model is correctly displayed as Affine.
7. sensor_model_name: RFunctions
8. sensor_model_type: 3D
9. The model seems to be erroneously getting geometric model information from the
original NITF file, not from the .uai and its associated .aux.
Generic Binary (and ENVI) Seems to be a problem with BIL format handlers - Generic Binary, ENVI, possibly even
format handlers run out of Stripped TIFF.
IM-38979
memory and cause Spatial
Modeler to fail
7. A message displays that the value entered could not be converted to a data type
supported by this port.
“Generate Surface” operator, Customer reports, “Generate Surface” operator, doesn’t create *las output, when in the port
doesn’t create *las output, “PointcloudFilenameIn”, a filename without las extension is entered , even if file type is “Las
when in the port as Pointcloud.”
“PointcloudFilenameIn”
1. Create a model with “Generate Surface” operator
After running the model, an output file will be created without any extension. If you add a .las
extension a valid Pointcloud data will be created.
Color scheme options & File 1. Launch ERDAS IMAGINE and start the Spatial Model Editor.
Statistics shows Help errors
in Unsupervised 2. Drag the Unsupervised Classification operator to the Spatial Model Editor.
Classification operator
3. Double click on operator. Dialog corresponding to unsupervised classification will
open.
IM-37627
4. Click on Initializing options, Color Scheme options, and the corresponding dialogs
will open.
5. Click on Help of the dialogs and observe that help is navigating to Help Errors
page.
Umlauts (special chars) in If you create a sub-model from operators which have Umlauts ( ä,ö,ü,or ß ) in name and then
operator name used in try to open it, ERDAS IMAGINE will crash.
submodel will crash ERDAS
IMAGINE To replicate:
2. Select both “Pixelgröße X” and “Pixelgröße Y” named operators and click Create
Submodel button from Spatial Modeler tab.
LPS Block file should be In the Coordinate Reference System Chooser that is launched from Spatial Modeler, clicking
IM-37599 renamed to Block File in on Import button would launch a file chooser. Notice that the files of type for a blockfile is
order to have consistency. called "LPS Block File". But in other places within ERDAS IMAGINE we have been removing
the "LPS" term and using only "Block File". So for consistency sake can we rename in this
dialog too to "Block File"?
RasterInput should not output The output that doesn't go through the Statistics operator (with ForceRecompute set to true)
IM-37360 existing Stats if the input is ends up with the stats from the input image, even though the data has been recoded to have
being recoded 4 classes instead of 11.
ERDAS IMAGINE 2016 Customer reported that ERDAS IMAGINE crashes completely while running a Spatial model
crashes while running Spatial which for Classify a Las file and then subset by class selection and rasterize as a DEM.
IM-37608
model for Pointcloud subset Customer also found that if they do the Point Cloud Class selection and Subset with the GUI
by using Class select tools then ERDAS IMAGINE works with the same data.
Spatial Model Editor: In the Spatial Model Editor when trying to define a projection for the Construct CRS ID
Projection Chooser Crashes operator, the projection chooser crashes the editor if the user selects certain projections.
IM-37068
when selecting some
Switzerland projections
ERDAS IMAGINE crashes 1. Create a Spatial Model with Feature Input, Filter By Attributes, Feature output
while running a model having operators.
filter by attributes / Attribute
Filter operator with invalid 2. Give any shapefile or gwp file as input to the Feature Input operator.
text in the value for
comparison field 3. Specify output file location from Feature output operator
New port names in normalized_difference.gmdx was recently changed to have alias ports "NIRBand" and
normalized_difference.gmdx "RedBand". Those names are appropriate for NDVI. However, there are 23 other indices
not appropriate for most which also use normalized_difference.gmdx, and those port names are not appropriate for
indices most of the other indices.
IM-23580
For example, start indices, select "WV-SI - World View Soil Index". From the Indices dialog
you can see that the two bands used in this index are labelled Y & G for yellow and green.
Click View to see the model in Spatial Model Editor. Now Run from Spatial Model Editor. The
Model inputs dialog shows NIRBand and RedBand, which is inappropriate for the 2 input
bands in this case.
Default output directory for The eml.default_output_path preference is ".". This is OK in ERDAS IMAGINE, because the
Spatial Model Editor is the estr_ErdasEnvSet sets the current directory to $PERSONAL. Since smeditor.exe is using
IM-31506
directory where smeditor.exe DefaultToolkitContext, this isn't happening. Can we just change the default value of the
is preference to $PERSONAL?
Misleading error message Steps: open the specific block file, and run ortho resampling, CSM cannot handle 64 bit
occurs when run process, automatically switch to 32 bit. but error message in session log should turn off.
IM-12768
orthoresampling with
Visionmap
Relief Operator creates Relief The Relief Operator creates a Relief Shade with ugly artifacts. It has a contour effect and
Shade with ugly artifacts - horizontal and vertical lines as an output. The same occurs in the 2D View and in the Relief
Document Shade tools in the Terrain tools.
IM-8109
These are an artefact of using Nearest Neighbor resampling. Bilinear resampling is usually
sufficient to remove these artifacts.
Conditional operator requires Customer states that: "Conditional statements, our probably most frequent functions, only
all inputs to have same work if all raster inputs have the same number of layers. Also, GMD models can only be
number of bands opened as gmdx models if this is the case. However there is very often the need to combine
IM-19729
raster files e.g. with one layer and those with multiple layers. Work around of this is a bit
cumbersome, as the 1-layer input file has to be transformed in the respective multi-layer
input file to be combined with the other multi-layer files in the expression. "
One extra blank attribute 1. Launch ERDAS IMAGINE 2016 v16.1 (build:627), Launch Spatial Model Editor.
Elevation source is added in
the attribute table for the 2. Load the attached model and provide the input as lnlandc.img
output from profile operator in
IM-36095 ERDAS IMAGINE 2016 v16.1 3. Click on preview to execute the model and observe the attribute table of the output
compared to ERDAS generated.
IMAGINE 2016 v16.0
4. There is a blank elevation source attribute is added which is not the case with
ERDAS IMAGINE 2016 v16.0
Input Ports must not start with Running a model with the ports named with leading numbers will crash ERDAS IMAGINE.
IM-40492
a number Running one with ports without leading numbers works just fine!
DRA Stretch producing 1. Launch ERDAS IMAGINE and start the Spatial Model Editor
outputs differently with
Preview and Raster output. 2. Load model getmutlipledraparams.gmdx
3. Provide the input as a Multispectral NITF image and provide output filename.
4. Execute the model and after execution load the output image in viewer. Note the
IM-41649
resuts are displayed as Multispectral
5. Now Launch another Spatial Model Editor and Load the same model and replace
Raster Output operator with Preview and click on Preview to execute the model
Need to do a better job The output of Raster Expurgation spatial model is a 16-bit image with a range of 1 - 2251, but
IM-41542 setting ABPP in an output Actual Bits Per Pixel (ABPP) is being set to 16. This can cause problems displaying the data
NITF if using SIPS Image Chains.
SAFI crashes if a project with 1. Launch Stereo Analyst for IMAGINE (SAFI) and select File > Open > Stereo
a blockfile offline is loaded Analyst Feature Project.
into it.
IM-36844
2. Select the western feature project in the file chooser and hit OK in it.
Executing Surface Difference 1. Launch both 32bit and 64bit ERDAS IMAGINE
IM-37130 tool in 32bit imagine crashes
64bit Imagine and vice versa
2. In 32bit Imagine goto terrain Tab > Dem Tools > Surface Difference
3. to reproduce the issue same dem file can be placed as input Reference and Test
Files.
6. Repeat step 1-4. In second step use 64bit Imagine. after step4,observe that while
executing, IMAGINE 32bit crashes
File Pixel text field is wrongly In Inquire Cursor dialog, the text shown for File Pixel field is wrongly displayed as
IM-9642 displayed in Inquire Cursor "struct_efio_FdRec Pixel". But it should actually state as File Pixel.
dialog
5. In the Progression Order Options page, note that for "Exploitation Preferred (R-L-
C-P)" it says "Also referred to as EJPE ordering. Select this option when the
images will be exploited or chipped,” which is incorrect. It should be "EPJE."
Export NITF 2.1/NSIF 1.0 Export NITF2.1/NSIF 1.0 will not accept TRE SNSPSB metadata values. After entering
does not accept TRE metadata value, error "Transform not found!" opens, after dismissing error message, Export
IM-35730 SNSPSB metadata values NITF dialogue closes.
To replicate:
7. Edit the field NUM_SNS and replace the default value with any numerical value,
and click Apply
8. An error message, "Transform not found!" is displayed, the windows is closed and
the export process fails
4. With the new geocoded View active, select File / Save As / All Layers as NITF.
IM-37439
5. Provide name and click OK.
8. Error: "We cannot currently combine images with a different number of layers"
Installer features table in the The table in Help needs to be updated with the features currently available for silent
OLH needs to be updated installation.
IM-38406
with the current list of
features.
ERDAS ER MAPPER
Summary – ERDAS ER Description / How to Reproduce
Issue ID
Mapper
IM-37714 3. Now go to ER Mapper standard toolbar and click on save as and select the
vegetation.alg as Vegetation_raster.ers [ER Mapper Raster Dataset (.ers) ]
ABOUT US
Hexagon Geospatial helps you make sense of the dynamically changing world. We enable you to envision,
experience and communicate geographic information. Our technology provides you the form to design, develop
and deliver solutions that solve complex, real-world challenges. Ultimately, this is realized through our creative
software products and platforms.
CUSTOMERS. Globally, a wide variety of organizations rely on our products daily including local, state and
national mapping agencies, transportation departments, defense organizations, engineering and utility companies,
and businesses serving agriculture and natural resource needs. Our portfolio enables these organizations to
holistically understand change and make clear, reliable decisions.
TECHNOLOGY. Our priority is to deliver products, platforms and solutions that make our customers successful.
Hexagon Geospatial is focused on developing technology that displays and interprets information in a
personalized, meaningful way. We enable you to transform location-based content into dynamic and useable
business information that creatively conveys the answers you need.
PARTNERS. As an organization, we are partner-focused, working alongside our channel to ensure we succeed
together. We provide the right platforms, products, and support to our business partners so that they may
successfully deliver sophisticated solutions for their customers. We recognize that we greatly extend our reach and
influence by cultivating channel partner relationships both inside and outside of Hexagon.
TEAM. As an employer, we recognize that the success of our business is the result of our highly motivated and
collaborative staff. At Hexagon Geospatial, we celebrate a diverse set of people and talents, and we respect
people for who they are and the wealth of knowledge they bring to the table. We retain talent by fostering individual
development and ensuring frequent opportunities to learn and grow.
HEXAGON. Hexagon’s solutions integrate sensors, software, domain knowledge and customer workflows into
intelligent information ecosystems that deliver actionable information. They are used in a broad range of vital
industries.
Hexagon (Nasdaq Stockholm: HEXA B) has more than 18,000 employees in 50 countries and net sales of
approximately 3.3bn USD. Learn more at hexagon.com and follow us @HexagonAB.
Copyright
© 2018 Hexagon AB and/or its subsidiaries and affiliates. All Rights Reserved. Hexagon has registered trademarks in many countries
throughout the world. Visit the Trademarks Page for information about the countries in which the trademarks are registered. See Product Page
and Acknowledgements for more information.
PLEASE READ THESE TERMS CAREFULLY BEFORE USING HEXAGON GEOSPATIAL’S DOCUMENTATION ("DOCUMENT"). USE OF
THIS DOCUMENT INDICATES ACCEPTANCE OF THIS AGREEMENT WITHOUT MODIFICATION. IF YOU DO NOT AGREE TO THE
TERMS HEREOF ("TERMS"), DO NOT USE THIS DOCUMENT.
All materials in this Document are copyrighted and any unauthorized use may violate worldwide copyright, trademark, and other laws. Subject
to the terms of this Agreement, Hexagon Geospatial (a Division of Intergraph Corporation) and Intergraph’s subsidiaries ("Intergraph") hereby
authorize you to reproduce this Document solely for your personal, non-commercial use. In consideration of this authorization, you agree to
retain all copyright and other proprietary notices contained therein. You may not modify the Materials in any way or reproduce or publicly
display, perform, or distribute or otherwise use them for any public or commercial purpose, except as specifically authorized in a separate
agreement with Hexagon Geospatial.
The foregoing authorization specifically excludes content or material bearing a copyright notice or attribution of rights of a third party. Except as
expressly provided above, nothing contained herein shall be construed as conferring by implication, estoppel or otherwise any license or right
under any copyright, patent or trademark of Hexagon Geospatial or Intergraph or any third party.
If you breach any of these Terms, your authorization to use this Document automatically terminates. Upon termination, you will immediately
destroy any downloaded or printed Materials in your possession or control.
Disclaimers
ALL MATERIALS SUPPLIED HEREUNDER ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NON-INFRINGEMENT. Hexagon Geospatial does not warrant that the content of this Document will be error-free, that defects
will be corrected, or that any Hexagon Geospatial Website or the services that make Materials available are free of viruses or other harmful
components.
Hexagon Geospatial does not warrant the accuracy and completeness of this Document. Hexagon Geospatial may make changes to this
Document at any time without notice.
Limitation Of Liability
IN NO EVENT SHALL HEXAGON GEOSPATIAL BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL
DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY YOU OR ANY THIRD PARTY, WHETHER
IN AN ACTION IN CONTRACT OR TORT, ARISING FROM YOUR ACCESS TO, OR USE OF, THIS DOCUMENT.
Indemnification
You agree to defend, indemnify, and hold harmless Hexagon Geospatial, its officers, directors, employees, and agents from and against any
and all claims, liabilities, damages, losses or expense, including reasonable attorneys’ fees and costs, arising out of or in any way connected
with your access to or use of this Document.
Use Of Software
Use of software described in this Document is subject to the terms of the end user license agreement that accompanies the software, if any.
You may not download or install any software that is accompanied by or includes an end user license agreement unless you have read and
accepted the terms of such license agreement. Any such software is the copyrighted work of Hexagon Geospatial, Intergraph or its licensors.
Portions of the user interface copyright 2012-2018 Telerik AD.
This Document may provide links to third party websites for your convenience and information. Third party websites will be governed by their
own terms and conditions. Hexagon Geospatial does not endorse companies or products to which it links.
Third party websites are owned and operated by independent parties over which Hexagon Geospatial has no control. Hexagon Geospatial shall
not have any liability resulting from your use of the third party website. Any link you make to or from the third party website will be at your own
risk and any information you share with the third party website will be subject to the terms of the third party website, including those relating to
confidentiality, data privacy, and security.
Trademarks
The trademarks, logos and service marks ("Marks") displayed in this Document are the property of Hexagon Geospatial, Intergraph or other
third parties. Users are not permitted to use Marks without the prior written consent of Hexagon Geospatial, Intergraph or the third party that
owns the Mark. "Intergraph" is a registered trademark of Intergraph Corporation in the United States and in other countries. Other brands and
product names are trademarks of their respective owners.
Notifications of claimed copyright infringement should be sent to Hexagon Geospatial by mail at the following address: Intergraph Corporation,
Attn: Intergraph Legal Department, P.O. Box 240000, Huntsville, Alabama 35824.
Materials are provided with "RESTRICTED RIGHTS." Use, duplication, or disclosure of Materials by the U.S. Government is subject to
restrictions as set forth in FAR 52.227-14 and DFARS 252.227-7013 et seq. or successor provisions thereto. Use of Materials by the
Government constitutes acknowledgement of Hexagon Geospatial or Intergraph’s proprietary rights therein.
International Use
You may not use or export Materials in violation of U.S. export laws and regulations. Hexagon Geospatial makes no representation that
Materials are appropriate or available for use in every country, and access to them from territories where their content is illegal is prohibited.
Hexagon Geospatial provides access to Hexagon Geospatial international data and, therefore, may contain references or cross references to
Hexagon Geospatial products, programs and services that are not announced in your country. These references do not imply that Hexagon
Geospatial intends to announce such products, programs or services in your country.
The Materials are subject to U.S. export control and economic sanctions laws and regulations and you agree to comply strictly with all such
laws and regulations. In addition, you represent and warrant that you are not a national of, or otherwise located within, a country subject to U.S.
economic sanctions (including without limitation Iran, Syria, Sudan, Cuba, and North Korea) and that you are not otherwise prohibited from
receiving or accessing the Materials under U.S. export control and economic sanctions laws and regulations. Hexagon Geospatial makes no
representation that the Materials are appropriate or available for use in every country, and access to them from territories where their content is
illegal is prohibited. All rights to use the Materials are granted on condition that such rights are forfeited if you fail to comply with the terms of
this agreement.
Revisions
Hexagon Geospatial reserves the right to revise these Terms at any time. You are responsible for regularly reviewing these Terms. Your
continued use of this Document after the effective date of such changes constitutes your acceptance of and agreement to such changes.
Applicable Law
This Document is created and controlled by Hexagon Geospatial in the State of Alabama. As such, the laws of the State of Alabama will govern
these Terms, without giving effect to any principles of conflicts of law. You hereby irrevocably and unconditionally consent to submit to the
exclusive jurisdiction of the United States District Court for the Northern District of Alabama, Northeastern Division, or the Circuit Court for
Madison County, Alabama for any litigation arising out of or relating to use of this Document (and agree not to commence any litigation relating
thereto except in such courts), waive any objection to the laying of venue of any such litigation in such Courts and agree not to plead or claim in
any such Courts that such litigation brought therein has been brought in an inconvenient forum. Some jurisdictions do not allow the exclusions
or limitations set forth in these Terms. Such exclusions or limitations shall apply in all jurisdictions to the maximum extent allowed by applicable
law.
Questions