ERDAS IMAGINE 2014 Arrives Today!

Today, 64-bit (x64) raster processing is released in ERDAS IMAGINE 2014. All raster formats which support x64 processing with in Spatial Modeler, Spatial Modeler (Legacy), MosaicPro, Export ECW, and more. Because much of ERDAS IMAGINE uses Spatial Modeler (Legacy) for processing, a very wide swath of the product processes raster data in true x64. There are a few very old raster formats that depend on third-party libraries, where the third party has not ported to x64, and these raster formats will run in x86.

Once example ECW Exporter, I ran a test yesterday.... I copied a 22GB file using the DOS cmd.exe 'copy' command. It took longer to copy the 22GB file from local disk to the same local disk than it took to compress the 22GB image file with the ECW Exporter. So, speed is one benefit of x64 bit processing (as if we did not know that already).  

Another example, Image Segmentation... with the x64 processing we released a new version of image segmentation. I will cover that in another blog post at a later time.

LPS Changes Soon in 2014 Annual Release

Intergraph recently notified LPS customers the annual release of ERDAS IMAGINE (2014) will mark the next phase softcopy photogrammetry in ERDAS IMAGINE and LPS.

The ERDAS IMAGINE product line has a long history of digital (softcopy) photogrammetry. Softcopy photogrammetry was first introduced in ERDAS IMAGINE 8.0.2 with ‘IMAGINE Digital Ortho’. The next major upgrade came with the release of ‘IMAGINE OrthoMAX,’ which was introduced in 1995. ‘IMAGINE OrthoBASE’ was the next major upgrade and was introduced in 1999.

In 2004, LPS 8.7 was the next major upgrade and was developed and marketed alongside ERDAS IMAGINE 8.7. In LPS 2013, the ERDAS IMAGINE ribbon interface adoption was part of a major LPS upgrade, and created the tightest product integration to that time.

In the 2014 release version, the integration is even tighter. LPS product family and components have been rebranded and repackaged to become part of the ERDAS IMAGINE 2014 once again. Softcopy photogrammetry in ERDAS IMAGINE suite has been upgraded and expanded yet again.

The packaging of the ERDAS IMAGINE Suite (of which LPS is now part), has been simplified. The details of the packaging will be rolled out by Intergraph soon, as the release of Intergraph Geospatial 2014 is imminent.

There is much more for the LPS community, but I will leave that to the press releases... I will expand on those after they are released.

Did you know... OrthoBASE was the first software product Mladen Stojic managed. Mladen and I often reminisce of OrthoBASE creation days, and the fun we had creating it. (Well he created it; I was someone he could bounce ideas off.)

Are you surprised by a veto on spending from Georgia's Republican governor?

Many in the State of Georgia’s (USA) mapping community were surprised by Republican Governor Nathan Deal’s veto of Georgia Senate Bill 11.  The goal of the bill was to formalize the role of director of Georgia Geospatial Advisory Council (GGAC). This Geographic Information Officer (GIO) position was presented as the only pathway to facilitate managing geospatial data collection and maintenance across the Georgia.

As re-read the Georgia Geospatial Audit (GGA) it again stands out that GGAC is proposing a specific pathway to accomplishing the primary goal of creating and maintaining consistently solid geospatial information to support better and more timely legislative and executive decision making. That singular pathway in and of itself is the problem.

Having a governmental unit responsible for resource mapping in the state of Georgia can be argued as the best way manage mapping in Georgia. Notwithstanding the clear logic, as has been proposed by GGAC (as outlined in the GGA), a GIO approach has not in the past, and will not likely occur in the next few legislative sessions in the State of Georgia.

It is my opinion, as long as GISCC and the Georgia Geospatial Advisory Council (GGAC) push for a new tax payer funded position or department, we will see a failure to accomplish the real geospatial need in Georgia; consistent up-to-date and accurate geospatial information that supports better decision making in Georgia, available to both the legislative and administrative branches.
 

By a large margin, Georgia is dominated by an electorate and legislative culture who are currently opposed to the of new departments and opposed to adding personnel to the state’s payroll. Indeed, these electorate and legislative cultures demand spending be intelligently trimmed now and continuing over the next decade. These demands would wrongly be considered austerity measures. Rather, clearing out wasteful spending before new spending is considered. The pathway GISCC and GGAC have proposed, cannot be done in the current political climate.

GISCC and GGAC need to think outside of the 'GIO is the only way' box. The GIO approach will not work in the in the Georgia's current electorate and legislative cultures. Georgia needs a truly innovative approach to the  real challenge of providing solid, accurate, timely geospatial data to decision makers. 
 

What computer should I buy to use ERDAS IMAGINE?

I often get system configuration questions. Actually, very often. People ask, what computer should I buy to use ERDAS IMAGINE? The posted System Requirements explain the minimum needed. Minimum requirements give the same results, but take a long time to get there.

 

For me, my computer is considered the cheapest employee the company can hire. Pay for it once and use it 24 / 7 / 365 for 3 or 4 years. That is a good employee. :)

 

Here are what I usually tell folks:

1. Everyone using ERDAS IMAGINE should use a 64-bit OS. Everyone. A 64-bit OS is far more valuable in time savings than the cost of the US$125 upgrade from a 32-bit OS.
1. ERDAS IMAGINE has used large address aware (on 64-bit OS) to allow a process to use up to about 3.4GB memory (if needed) in some form or another since ERDAS Desktop 2010. All ERDAS Desktop products are large address aware in v2013 and higher. All.
2. Everyone should use a 64-bit OS, and use more than 8 GB RAM. We use their resources they have invested in. Below you see how you easily exceed 8GB RAM on a typical day.
1. MS Windows OS often uses about 2GB of memory.
2. MS Office uses about 500MB of memory. 
3. The ERDAS IMAGINE Viewer/Ribbon can use up to about 3.4GB of memory. 
4. MosaicProcessPro (MosaicPro engine) can use up to about 3.4GB of memory. 
3. Everyone should use a 64-bit OS, use more than 8GB RAM, and use multi-core processors.
1. ERDAS desktop products has used multiple threads in some form or another since ERDAS IMAGINE / LPS 8.7.
2. We do more work in this area every major release of ERDAS IMAGINE, and salso do some work in some SPs.
3. Even in areas with limited threading,using multi-core processors improves performance.
4. Everyone should use a 64-bit OS, use more than 8GB RAM, use multi-core processors, and use fast disks.
1. This is why moer than 8GB RAM helps so very, very much. Greater than 8GB RAM keeps process intensive memory usage from paging to virtual memory (disk file). All the while you have other applications open on your Windows OS desktop.
2. Because geographic data are so large, reading and writing of these data is a significant slow-down point. Use one fast disk for reading and another fast disks for writing and most valuable disk RAIDs when ever possible.
3. Never process large files using an external USB drive. The time (and money) you waste will likely pay for another internal hard disk.

 

GDAL Work to Support ERDAS ECW/JP2 SDK v5 Almost Complete

To support the ERDAS ECW Plug-in for ArcGIS Desktop 10.1, work was done to add support for the ERDAS ECW/JP2 SDK v5 into GDAL. The new ECW SDK adds support for ECW v3, which supports 16-bit data, RPC, statistics, histograms, and much more in the new ECW file format. The new ECW SDK also supports ECWP v3, which faster than ever.

In the process of working on the ArcGIS/GDAL work, we learned a few things that help the use of the SECW DK in GDAL, and these will be rolled into the final ECW SDK and GDAL products. You will see the GDAL changes about the same time the ERDAS ECW/JP2 SDK v5 is released.

In addition to ECW v3 and ECWP v3 things noted above, the new SDK version will decode JP2 faster thatn ever. Our goal is to be faster than any other tools that decode JP2 data (go big or go home). The new ECW SDK will support Microsoft Visual Studio 2012 compiler and Linux.

So, when will the new ECW SDK v5 be released?

I have been asking the same thing. (I am not longer the ECW SDK Product manager). While I have not gotten a definitive answer, because we see the ECW SDK being used in ERDAS IMAGINE and ERDAS APOLLO 2013 products, many GeoMedia 2013 products, in ECW Plug-in for ArcGIS Desktop 10.1, and the GDAL work now complete (but not checked-in) we can know we are real close.

Latest Version of ERDAS ECW Plug-in for ArcGIS Desktop

The ERDAS ECW Plug-in for ArcGIS Desktop 10.1 has been released by Intergraph. The plug-in is free. This plug-in version will not work on ArcGIS for Desktop versions earlier than 10.1. Esri customers having an earlier version of ArcGIS for Desktop should use the earlier version of the plug-in.

The ERDAS ECW Plug-in for ArcGIS Desktop 10.1 enhances the native ECW / ECWP support Esri has built into ArcGIS for Desktop. This new version of the ECW Plug-in for ArcGIS Desktop adds over 35 enhancements. Among these enhancements are the following:

• Support for Esri's ArcGIS 10.1 for Desktop, released in June 2012
• ECW v3 file support has been added
• Local files will read and store statistics information within the ECW fileheader
• Display speed of ECW v2 files has been improved when compared to Esri’s default v10.1 capabilities
• ECWP v3 has been added for improved streaming performance when connecting to ERDAS APOLLO 2013 servers over low bandwidth and secure environments
• ECWP will continue to work on older ERDAS APOLLO versions
• An automatic 99% clip is now applied to >8 bit JP2 or ECW v3 files when streamed over ECWP
• Projection handling of ECWP layers has been significantly improved to support additional EPSG and now also Esri's defined coordinate systems
• Numerous enhancements to ERDAS ER Mapper ERS and ALG file support
• Added support for catalog searching of ERDAS APOLLO Advantage 2013 servers
• Esri’s ArcCatalog now fully supports managing ECW v2, ECW v3, ERS and ALG files
• Resolved side-by-side compatibility with ERDAS Extensions for ArcGIS. Both products can now coexist in the same ArcGIS for Desktop install

The plug-in is available from Intergraph here:  http://geospatial.intergraph.com/products/other/ecw/ECWPlugins/Downloads.aspx 

ERDAS IMAGINE 2013 Version 13.00.0002 in testing

ERDAS Desktop 2013 v 13.00.0002 (ERDAS IMAGINE, LPS, and ERDAS ER Mapper SP2) is complete and is undergoing quality assurance testing. The post below gives an outline of a few areas we have worked on in the release. We have added support for creating ECW opacity layers using shapefiles. The user no longer has to convert the shapefile polygon into an AOI.

Now that the product is in QA testing, I believe SP2 will be delivered before mid-April 2013.


I will be attending GIA/CAMA is Albuquerque this week. I have a huge interest in Parcel-based change detection and will be speaking at an Intergraph sponsored luncheon on the topic.

ERDAS IMAGINE 2013 Version 13.00.0002 in development

We are always improving our products. Sometimes in major releases and sometimes in service packs (SP). Work is well underway for improving ERDAS Desktop 2013 (ERDAS IMAGINE, LPS, and ERDAS ER Mapper). These improvements address customer reported improvements as well as improvements defined by product managers. The expected product deliver version number is 2013 Version 13.00.0002.

This SP may be limited to customers with current customer support only as it has a lot of enhancements. I am not in a position to outline exactly what we are improving in the SP, yet. But, what I can say, we are improving LAS, ECW, JP2, NITF, Spatial Modeler, Spatial Modeler (Legacy), Virtual Mosaic, and much more. This SP, and what we did in the ERDAS IMAGINE 2013 release (released early December 2012) are very powerful.

This SP development period will be a short time-frame one. I would expect ERDAS IMAGINE 2013 Version 13.00.0002 to arrive on the website well before the Hexagon 2013 conference in Las Vegas (June 3 – 6).

ERDAS ECW/JP2 SDK v4.3 Available

The latest versions of the ERDAS ECW/JP2 SDK (SDK), version 4.3 are now available on the Intergraph Geospatial Products website. These versions are a maintenance release. While addressing some maintenance issues, there were some slight improvement in memory handling of ECW and JP2 data, as well as some performance improvements.

This release it likely the final release for version 4 of the SDK. Version 5 of the SDK is in the final stages of development, and is already being used in various Intergraph products. Version 5 of  the SDK is shaping up to be a powerful product. There is no official date for release, but should not be far into the new year (2013), is my best guess.

Download ERDAS ECW/JP2 SDK v4.3 at the following web page:  

http://geospatial.intergraph.com/products/other/ecw/ERDASECWJPEG2000SDK/Downloads.aspx

The Release of ERDAS IMAGINE 2013 is Coming Soon

The work on ERDAS IMAGINE 2013 is in the final stages. Indeed, all ERDAS Desktop products (ERDAS IMAGINE, LPS, ERDAS ER Mapper) are preparing for release. Keep an eye out for a press release from Intergraph before the end of this year (2012).

What do I like?

• The Model Maker transition into Spatial Modeler 
• Pull architecture for real-time processing to viewer 
• Faster file creation 
• Write real-time to 2D Viewer and create a file faster than Model Maker can make a file  
• Pull architecture based on ERDAS ER Mapper concepts 
• Python in Spatial Modeler 
• Use custom designed applications in a Spatial Model 
• Access other licensed software products in a Spatial Model 
• GeoMedia vector and raster processing objects used in Spatial Modeler 
• High performance asynchronous raster data engine 
• Faster data access in 2D Viewer and Spatial Modeler 
• Will be expanded in 2014 release 
• Use of the new v5 ERDAS ECW/JP2 SDK 
• Used in ERDAS IMAGINE, LPS and ERDAS ER Mapper 
• Multi-threaded encoding 
• Introduce ECW v3 file format (ECW v2 has been around since 1999)
• ECW v3 supports up to unsigned 16-bit data 
• ECW v3 uses GeoTIFF standard for coordinate reference system definition 
• Expanded ECW metadata 
• Faster encoding of ECW 
• Faster decoding of ECW 
• Faster ECW v2 and v3 opacity layer calculation 
• Reduced need for J2I files with JP2 files 
• More robust support for non-standard JP2 data 
• More robust support for ill-defined JP2 profiles 
• Support reading MrSID MG4 Raster  
• Support reading of MrSID MG4 LiDAR 
• Point cloud (LiDAR) support 
• Viewing 
• Automatic classification 
• Manual classification 
• Data preparation 
• Support read and write of LAS 
• New LPS user interface 
• Improved Terrain Prep Tool 
• Improved MosaicPro (we never stop making MosaicPro better) 
• New swipe tools (transitions ribbon) 
• New measurement ribbon for height from shadow and height from building lean and ortho measurements  
• Real-time spectral indices (using Spatial Modeler technology) 
• Vegetation 
• Snow / Ice 
• Minerals
• Water 
• New unsupervised classification tools 
• Faster unsupervised classification tools 
• Use of SAM and SCM in supervised classification 
• New image segmentation algorithm in IMAGINE Objective 
• Numerous interface improvements to make ERDAS IMAGINE and LPS more intuitive to expert and novice alike 

There is more, but these are what I really like. 

So, keep an eye out for the press releases... from Intergraph. Don't forget, ERDAS is part of Intergraph and   Intergraph is part of Hexagon. The Erdasians have helped our fellow Intergraph employees integrate well within Hexagon. 

ERDAS ECW/JP2 SDK GDAL Driver Updated

The ERDAS ECW/JP2 SDK team in Perth Australia has done some work to update the ECW drivers in GDAL. These have been submitted to the GDAL community, and should make their way into a future version of GDAL.

There are multiple changes, but what I want to raise in this post, the performance of GDAL driver was improved in two main areas. While these bottlenecks were not in the ERDAS Desktop and Server product lines, we wanted to ensure our GDAL users had as similar a decoding performance as possible. 

1.  GDAL 1.9 and earlier versions have a performance bottleneck when a single band is decoded line by line. This is not the preferred method of reading ECW data; nevertheless it is done by some folks. 
2. GDAL 1.9 and earlier versions did not use the SDK’s implementation of supersampling, and GDAL’s own implementation was slower. Switching to supersampling using the SDK implementation halved time of the execution. 

While working on this small project, we did notice other areas where we can improve ECW support in the GDAL drivers going forward.

The Perth Team in Australia will improve the GDAL drivers more so when we upgrade GDAL to support the v5 of the SDK and the new ECW v3 file format early in the upcoming new year.

As has been policy, developer tools for decoding ECW and JP2 data using the SDK on desktop continue to be free.

See: http://trac.osgeo.org/gdal/ticket/4822

Example Python Code from ERDAS IMAGINE's Upcoming Spatial Modeler

The chief Python developer, Fengliang provided me an example Python script that will run a resolution merge (pan sharpen) in the upcoming Spatial Modeler. This example model (below) runs outside of the ERDAS IMAGINE User Interface, indeed ERDAS IMAGINE is not running at all when the Py scipt is launched. ERDAS IMAGINE is installed and licensed, but not running.

The Py script finds all the ERDAS IMAGINE Spatial Modeler functions, and runs the model. This model runs 100% in the background. The ERDAS IMAGINE UI never launches. If the user wants to, they can run the model, start the UI and display the results as a real-time preview in the Viewer. Note, the preview is realtime modeling to screen, like ERDAS ER Mapper Algorithms. When using preview, a new file is never actually created. (But you can create one when you need to!) 

This example Py script, and others will be provided when the software is released.

-------------------------------------------

def Sharpen( model, band, summary, panband ):
      return model.CastToFloat( model.Multiply( model.Divide(band, summary), panband))

# import erdas python module for spatial modeler
from erdas import modeler

# create a process
m = modeler.Model();

# create input operators
pan = m.RasterInput( "E:/Demo/Brovey/le7039035000009250_pan.img", "Float", "Nearest Neighbor");
multispectral = m.RasterInput("E:/Demo/Brovey/le7039035000009250_multi.img", "Float", "Nearest Neighbor");

# add three bands together
r = m.SelectBand(multispectral, '4:4');
g = m.SelectBand(multispectral, '3:3');
b = m.SelectBand(multispectral, '2:2');
sum = m.Add(1, r, g, b)

# calculate R, G, B bands for stacklayer
stack = m.StackLayers( Sharpen( m, r, sum, pan ), Sharpen( m, g, sum, pan ), Sharpen( m, b, sum, pan ) )

# to output operator
m.RasterOutput(stack, "E:/Demo/Brovey/output/brovey-output-python-6.img", "u8", Thematicity=modeler.Thematicity.continuous)

# finalize the process
m.Execute();