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).
Showing posts with label ERDAS IMAGINE. Show all posts
Showing posts with label ERDAS IMAGINE. Show all posts
Thursday, February 21, 2013
Friday, August 3, 2012
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();
Thursday, June 28, 2012
Last Few ERDAS Desktop 2012 Development Weeks Deliver Solid Results
During the last few weeks the ERDAS Desktop software development teams have delivered solid results.
Oh yes, and did I tell you that ERDAS IMAGINE functions are being placed into GeoMedia? Yes... Vector coming into ERDAS IMAGINE and raster id going into GeoMedia.
Finally, I had wanted to do some webinars on the LiDAR tools, but have decided to wait until we complete the changes gathered from user feedback at Hexagon 2012. I expect to do the webinars before too late in July.
- We have seen Point Cloud (LiDAR) display performance speed up significantly.
- User feedback from the Hexagon 2012 Conference prompted refinement in the LiDAR Ribbon controls.
- ERDAS IMAGINE’s Spatial Modeler providing real-time results from over 30 indices as well as pan sharpening.
- Python is now running Spatial Modeler without launching ERDAS IMAGINE UI.
- Asynchronous multi-threaded raster data delivery engine plugged into Spatial Modeler and into the 2D Viewer.
- Began work placing the latest ERDAS ECW/JP2 SDK into ERDAS IMAGINE, LPS, and ERDAS ER Mapper.
- MosaicPro improvements improves how customers can handle mosaicking images with clouds.
Oh yes, and did I tell you that ERDAS IMAGINE functions are being placed into GeoMedia? Yes... Vector coming into ERDAS IMAGINE and raster id going into GeoMedia.
Finally, I had wanted to do some webinars on the LiDAR tools, but have decided to wait until we complete the changes gathered from user feedback at Hexagon 2012. I expect to do the webinars before too late in July.
Wednesday, June 6, 2012
Intergraph Announces Point Cloud support Coming in ERDAS IMAGINE 2012
The announcement below is the fruit of software development work being done in Atlanta, Georgia USA; Pasadena, California USA; and Singapore as well as the press release written in Atlanta. The Intergraph corporate headquarters are in Huntsville.
Steve du Plessis and I will begin a series webinars on this topic later this month.
The reason we use the term Point Cloud rather than LiDAR, point cloud covers more data sources than LiDAR. LiDAR is but one data source.
The announcement is as follows:
HUNTSVILLE, Ala., June 6, 2012 – At the Hexagon 2012 conference, Intergraph® is demonstrating a new technology that enables you to fully leverage the wealth of information in point cloud data. The centerpiece of the new functionality is the augmented viewing capability embedded in ERDAS IMAGINE®, which allows users to simultaneously view LiDAR spatially linked in 2D, 3D and as a user-specified profile that can reveal cross sections of the point cloud.
“Intergraph’s new functionality truly unlocks the potential of LiDAR, taking full advantage of its rich three-dimensional content,” said Steve du Plessis, Global Product Line Executive – Remote Sensing, Intergraph. “You can open up these dense point clouds, see inside them and break them apart to reveal the information they contain to gain a new perspective of the world.”
Within the three new views, ERDAS IMAGINE provides a range of options that make it easy to understand and extract the information contained in the point cloud. Different filtering options allow you to view the points in dozens of permutations. For example, you may only want to see first-return points classified as vegetation. To improve interpretability, flexible colorization settings offer the ability to view by elevation, return, classification, file, intensity or the RGB encoding of each point which provides a lifelike, three-dimensional color view of a point cloud. Additionally, you can view the point cloud draped over your 2D imagery, thereby obtaining a better understanding of the above-ground features portrayed by the points.
The profile view provides unique capabilities for analyzing point clouds. While the standard profile view is defined by a user-specified box drawn over the 2D view of the point cloud, you can also use a polyline vector to obtain a profile view of a longer strip within the cloud. ERDAS IMAGINE can then automatically roam at a user-specified speed along this long profile view. These features are especially useful in the utilities market, where they can be used to inspect power line corridors for encroaching vegetation or other line issues. As problems are visually detected, you can pause, make measurements, record the position and add notes. ERDAS IMAGINE can then export this information to a spreadsheet that can be given to field crews who maintain the corridors.
ERDAS IMAGINE’s new point cloud technology also offers a set of tools to classify, RGB encode, subset and filter your point data. The classification tool will enable you to specify criteria for automated point classification. Users can then leverage the editing tools within the 2D and profile views to refine the results. For example, you can delete, reclassify, bias or set a constant elevation on selected points with the security of multiple-step undo and redo capabilities. In addition to thorough views of the point clouds themselves, ERDAS IMAGINE provides comprehensive views and editing of the associated metadata. You can batch and distribute all these functions for faster processing, which is especially helpful since many users opt to create smaller tiles from large LAS files.
“Intergraph is in a unique position to provide the leading point cloud solution on the market,” continued du Plessis. “As part of Hexagon, our portfolio includes in-house airborne and terrestrial LiDAR hardware technology from our sister division Hexagon Geosystems, powerful GIS analytics from GeoMedia®, the world’s leading remote sensing capabilities in ERDAS IMAGINE and LiDAR data management and serving capabilities in ERDAS APOLLO. In addition, Intergraph’s vertical market approach offers extensive domain expertize in utilities, transportation, government and security. Together, not only will our point cloud technology strengthen any organization’s LiDAR-handling capabilities, but also its user-centric implementation streamlines workflows so users can quickly and easily obtain the most from point clouds and maximize the return on your LiDAR investment.”
To learn more about the Intergraph geospatial product portfolio, please visit http://www.intergraph.com/geospatial/products
Steve du Plessis and I will begin a series webinars on this topic later this month.
The reason we use the term Point Cloud rather than LiDAR, point cloud covers more data sources than LiDAR. LiDAR is but one data source.
The announcement is as follows:
Intergraph® Highlights Advanced Point Cloud Capabilities at Hexagon 2012
New ERDAS IMAGINE® Features Enable You to Better Understand Your LiDAR Data
HUNTSVILLE, Ala., June 6, 2012 – At the Hexagon 2012 conference, Intergraph® is demonstrating a new technology that enables you to fully leverage the wealth of information in point cloud data. The centerpiece of the new functionality is the augmented viewing capability embedded in ERDAS IMAGINE®, which allows users to simultaneously view LiDAR spatially linked in 2D, 3D and as a user-specified profile that can reveal cross sections of the point cloud.
“Intergraph’s new functionality truly unlocks the potential of LiDAR, taking full advantage of its rich three-dimensional content,” said Steve du Plessis, Global Product Line Executive – Remote Sensing, Intergraph. “You can open up these dense point clouds, see inside them and break them apart to reveal the information they contain to gain a new perspective of the world.”
Within the three new views, ERDAS IMAGINE provides a range of options that make it easy to understand and extract the information contained in the point cloud. Different filtering options allow you to view the points in dozens of permutations. For example, you may only want to see first-return points classified as vegetation. To improve interpretability, flexible colorization settings offer the ability to view by elevation, return, classification, file, intensity or the RGB encoding of each point which provides a lifelike, three-dimensional color view of a point cloud. Additionally, you can view the point cloud draped over your 2D imagery, thereby obtaining a better understanding of the above-ground features portrayed by the points.
The profile view provides unique capabilities for analyzing point clouds. While the standard profile view is defined by a user-specified box drawn over the 2D view of the point cloud, you can also use a polyline vector to obtain a profile view of a longer strip within the cloud. ERDAS IMAGINE can then automatically roam at a user-specified speed along this long profile view. These features are especially useful in the utilities market, where they can be used to inspect power line corridors for encroaching vegetation or other line issues. As problems are visually detected, you can pause, make measurements, record the position and add notes. ERDAS IMAGINE can then export this information to a spreadsheet that can be given to field crews who maintain the corridors.
ERDAS IMAGINE’s new point cloud technology also offers a set of tools to classify, RGB encode, subset and filter your point data. The classification tool will enable you to specify criteria for automated point classification. Users can then leverage the editing tools within the 2D and profile views to refine the results. For example, you can delete, reclassify, bias or set a constant elevation on selected points with the security of multiple-step undo and redo capabilities. In addition to thorough views of the point clouds themselves, ERDAS IMAGINE provides comprehensive views and editing of the associated metadata. You can batch and distribute all these functions for faster processing, which is especially helpful since many users opt to create smaller tiles from large LAS files.
“Intergraph is in a unique position to provide the leading point cloud solution on the market,” continued du Plessis. “As part of Hexagon, our portfolio includes in-house airborne and terrestrial LiDAR hardware technology from our sister division Hexagon Geosystems, powerful GIS analytics from GeoMedia®, the world’s leading remote sensing capabilities in ERDAS IMAGINE and LiDAR data management and serving capabilities in ERDAS APOLLO. In addition, Intergraph’s vertical market approach offers extensive domain expertize in utilities, transportation, government and security. Together, not only will our point cloud technology strengthen any organization’s LiDAR-handling capabilities, but also its user-centric implementation streamlines workflows so users can quickly and easily obtain the most from point clouds and maximize the return on your LiDAR investment.”
To learn more about the Intergraph geospatial product portfolio, please visit http://www.intergraph.com/geospatial/products
Friday, June 1, 2012
ERDAS IMAGINE 2012 is looking really good.
This release is going to be hot. What’s going to be in it?
The upgraded Spatial Modeler is more than an upgrade. This is more than an update of Model Maker that sits on top of the Spatial Modeler Language. All the Modeler Maker capabilities that Esri copied to create Model Builder are there, plus the things customers have demanded.
The Python Scripting is very powerful. Customers will be able to connect other software applications with Spatial Modeler as part of their data processing work-flows. ERDAS IMAGINE's Spatial Modeler can act as a agnostic geoprocessing hub.
There is more….
Last year at Hexagon 2011 I discussed that the wall between raster and vector was coming down. It is more than that, mush more.... raster, vector, point clouds, imagery, photogrammetry, radargrammetry, and more all in one software.
I am again working on a research love of mine, change detection. We have the algorithms and processing performance we need to make high resolution change detection work for the whole geospatial community, not just the expert. This is expected post 2012. Exciting times are here.
The upgraded Spatial Modeler is more than an upgrade. This is more than an update of Model Maker that sits on top of the Spatial Modeler Language. All the Modeler Maker capabilities that Esri copied to create Model Builder are there, plus the things customers have demanded.
- Faster file to file processing
- On-the-fly raster processing (lessons learned from ER Mapper)
- On-the-fly vector processing (lessons learned from GeoMedia)
- Replacement of Model Maker User Interface
- Python Scripting
The Python Scripting is very powerful. Customers will be able to connect other software applications with Spatial Modeler as part of their data processing work-flows. ERDAS IMAGINE's Spatial Modeler can act as a agnostic geoprocessing hub.
There is more….
- Point Cloud (LAS, MrSID) visualization in 2D and 3D, profiles, measuring, point editing, RGB encoding… I am working with Steve du Plessis to put together a Webinar on point clouds.
- 16-bit ECW, and ECW is faster… not just a little faster, but must faster and scalable.
- Better and faster support for JPEG2000 data.
- LPS is fully Ribbonized.
- New Segmentation algorithm that customers are saying is the best they have seen to date.
- Improved ER Mapper Algorithm capabilities.
- GeoMedia Vector and GRID capabilities. The GeoMedia Buffer in Spatial Modeler is real time. You can test your buffer processes in a trial and error method in the viewer and then write to file (if you want to).
- Faster edge detection in MosaicPro.
- New real-time spectral indices tool.
- Radar analyst work-flow tools in the ribbon, including ship tracking capabilities.
Last year at Hexagon 2011 I discussed that the wall between raster and vector was coming down. It is more than that, mush more.... raster, vector, point clouds, imagery, photogrammetry, radargrammetry, and more all in one software.
I am again working on a research love of mine, change detection. We have the algorithms and processing performance we need to make high resolution change detection work for the whole geospatial community, not just the expert. This is expected post 2012. Exciting times are here.
Wednesday, May 9, 2012
Update on ERDAS ECW/JP2 SDK v5.0
As promised earlier.... here is an ERDAS ECW/JP2 SDK update
The ERDAS ECW/JP2 SDK (SDK) and ERDAS APOLLO Essentials Image Web Server (IWS) development teams in Perth, Western Australia are well along the way towards the latest version of the SDK, v5. The motivations behind this release of the SDK are increasing encoding performance, 16-bit ECW support, decreasing file size without lowering quality, expanding beyond Windows OS support (all without hurting decoding performance).
The best way to improve encoding performance is to more fully utilize system resources by expanding the use of multiple threads. This is being done.
In the v4.x SDK versions we see a 25MB/second encoding throughput of 3-band 8-bit image data. That is very fast for wavelet compression and we could have just sat on our hands and said, “We are the champions (my friend).”
But sitting back and wondering at our own accomplishments is not our way. Tests have confirmed SDK v5 is encoding 3-band 8-bit data between a 65 to 85MB/second. When encoding 3-band 16-bit data, encoding speeds close 25 MB/second are being observed. Final tuning will tell where we end up, but so far when using an 8-core CPU, encoding performance seems to be primarily limited by disk i/o.
To add support for 16-bit, we need to change the ECW file format. So, at the same time the Perth team decided to do some other things to the ECW file format. File format changes have provided a decrease in file size when using the previous target compression ratios. In short, smaller files with the same image quality (the preverbal ..yet true.. win-win scenario).
The work is being done to add support for Linux, with a foundation for the SDK to be ported to other OS versions as demand requires.
Also, metadata support in the new ECW v3 file format has been expanded. We have added better projection definition options, imbedded statistics (min, max, mean, median, mode, etc.), and much more.
Also provided when using the SDK to stream in ECW and JP2 encoded image data via ECWP from IWS, faster ECWP streaming. (BTW, in case you didn't know, ECWP performance leaves JPIP performance in the dust.)
There is one thing to note, the ECW v3 file format cannot be read by earlier ECW SDKs. The old v2 ECW file format could not be expanded to allow the file format improvements needed, so we created ECW v3. Of important note, the desktop read-only SDK will continue to be made available at no charge.
What is the ‘un-official’ time-table? Expect to see ERDAS ECW/JP2 SDK v5 in the ERDAS IMAGINE / LPS, ERDAS ER Mapper, ERDAS APOLLO Essentials (aka IWS), and GDAL after the northern hemisphere’s autumnal equinox, and an upgrade of ERDAS' ECW for ArcGIS Server made available a few months following following the ERDAS Desktop releases.
Keep an eye on the ECW Web Page.
The ERDAS ECW/JP2 SDK (SDK) and ERDAS APOLLO Essentials Image Web Server (IWS) development teams in Perth, Western Australia are well along the way towards the latest version of the SDK, v5. The motivations behind this release of the SDK are increasing encoding performance, 16-bit ECW support, decreasing file size without lowering quality, expanding beyond Windows OS support (all without hurting decoding performance).
The best way to improve encoding performance is to more fully utilize system resources by expanding the use of multiple threads. This is being done.
In the v4.x SDK versions we see a 25MB/second encoding throughput of 3-band 8-bit image data. That is very fast for wavelet compression and we could have just sat on our hands and said, “We are the champions (my friend).”
But sitting back and wondering at our own accomplishments is not our way. Tests have confirmed SDK v5 is encoding 3-band 8-bit data between a 65 to 85MB/second. When encoding 3-band 16-bit data, encoding speeds close 25 MB/second are being observed. Final tuning will tell where we end up, but so far when using an 8-core CPU, encoding performance seems to be primarily limited by disk i/o.
To add support for 16-bit, we need to change the ECW file format. So, at the same time the Perth team decided to do some other things to the ECW file format. File format changes have provided a decrease in file size when using the previous target compression ratios. In short, smaller files with the same image quality (the preverbal ..yet true.. win-win scenario).
The work is being done to add support for Linux, with a foundation for the SDK to be ported to other OS versions as demand requires.
Also, metadata support in the new ECW v3 file format has been expanded. We have added better projection definition options, imbedded statistics (min, max, mean, median, mode, etc.), and much more.
Also provided when using the SDK to stream in ECW and JP2 encoded image data via ECWP from IWS, faster ECWP streaming. (BTW, in case you didn't know, ECWP performance leaves JPIP performance in the dust.)
There is one thing to note, the ECW v3 file format cannot be read by earlier ECW SDKs. The old v2 ECW file format could not be expanded to allow the file format improvements needed, so we created ECW v3. Of important note, the desktop read-only SDK will continue to be made available at no charge.
What is the ‘un-official’ time-table? Expect to see ERDAS ECW/JP2 SDK v5 in the ERDAS IMAGINE / LPS, ERDAS ER Mapper, ERDAS APOLLO Essentials (aka IWS), and GDAL after the northern hemisphere’s autumnal equinox, and an upgrade of ERDAS' ECW for ArcGIS Server made available a few months following following the ERDAS Desktop releases.
Keep an eye on the ECW Web Page.
Wednesday, July 6, 2011
ERDAS Desktop 2011 Version 11.0.3 is Available
ERDAS has released ERDAS Desktop 2011 Version 11.0.3. This version is available to customers with current desktop software maintenance (SWM) and contains all issues from 11.0.1 and 11.0.2. There are quite a few customer requested enhancements as well as customer reported bugs addressed in this version.
A very brief list of what ERDAS IMAGINE customers can now expect:
Use Spectral Angle Mapper and Spectral Correlation Mapper classifiers in Supervised Classification
Distribute MosaicPro image tile creation to internal Cores or to external CPUs on their network
Rescale data from 16-bit down to 8-bit in MosaicPro and in LPS ortho processes
Expect higher performance from the Mosaicpro Preview
Improved performance on MosaicPro histogram matching
And more…
There are LPS and ERDAS ER Mapper issues addressed in Version 11.0.3 as well.
This version does not include any server enhancements and fixes. (Hence the use of the word Desktop).
See for yourself at http://www.erdas.com/service/support/fixes_enhancements/ERDASIMAGINE2011.aspx
After looking at what is in Version 11.0.3, if you want the version, you must log-in with your current SWM account to download the version. If you have current SWM, go here and log-in:
A very brief list of what ERDAS IMAGINE customers can now expect:
Use Spectral Angle Mapper and Spectral Correlation Mapper classifiers in Supervised Classification
Distribute MosaicPro image tile creation to internal Cores or to external CPUs on their network
Rescale data from 16-bit down to 8-bit in MosaicPro and in LPS ortho processes
Expect higher performance from the Mosaicpro Preview
Improved performance on MosaicPro histogram matching
And more…
There are LPS and ERDAS ER Mapper issues addressed in Version 11.0.3 as well.
This version does not include any server enhancements and fixes. (Hence the use of the word Desktop).
See for yourself at http://www.erdas.com/service/support/fixes_enhancements/ERDASIMAGINE2011.aspx
After looking at what is in Version 11.0.3, if you want the version, you must log-in with your current SWM account to download the version. If you have current SWM, go here and log-in:
http://www.erdas.com/service/support/fixes_enhancements/details/ERDAS_Desktop_2011_Version_11_0_3.aspx
Friday, June 17, 2011
Joel Campbell GIS Cafe Interview at Hexagon 2011
Did you miss Hexagon 2011? Make sure you plan on Hexagon 2012 June 4 - 7 in Las Vegas, NV, USA!
Here are some links to help you get an idea of what happened at Hexagon 2011 in Orlando.
GISCafe posted and interview with Joel Campbell, ERDAS' President, and Sanjay at Hexagon 2011. As a post conference note, in my opinion, ERDAS received a boost from meeting ERDAS customers, distributors and partners. Also, the interest in ERDAS technology from all the other Hexagon companies was also tremendous.
http://www10.giscafe.com/video/ERDAS-Joel-Campbell-President/35179/media.html
Watch Joel's interview read the other links on "The Field Guide" concerning Hexagon 2011, what is coming with the ERDAS - Intergraph synergy effort, and what is coming in ERDAS 2012 when I return from vacation.
Mladen Stojic discusses the synergy efforts and the new development projects ERDAS is currently working on, and showed at Hexagon 2011: http://www10.giscafe.com/video/ERDAS-Mladen-Stojic/35210/media.html
Ryan Hughes of Skygone has some interesting thoughts on how he believes Hexagon should approach addressing the software product (ERDAS-Intergraph) synergy effort in this article: http://cloudcomputing.sys-con.com/node/1860109%20. His interview at Hexagon 2011 is found here: http://www10.giscafe.com/video/Skygone-Ryan-Hugheshttp://www.blogger.com/img/blank.gif-COO/35180/media.html.
Other Hexagon 2011 links:
Movie showing ERDAS IMAGINE Live Link with GeoMedia narrated by Paul.
3D the Way Forward for GIS Industry
The Future of Spatial Analysis Through Intergraph and ERDAS
Hexagon 2011 international Conference Attracts 2,500+ Attendees From 65 Countries
Hexagon 2011 Kicks Off with Game-Changing Vision for the Future
Field Report: Hexagon 2011 International Conference
Hexagon 2011 Facebook Page: http://www.facebook.com/media/set/?set=a.206253446083641.50370.169045849804401&l=de2f88525b
Here are some links to help you get an idea of what happened at Hexagon 2011 in Orlando.
GISCafe posted and interview with Joel Campbell, ERDAS' President, and Sanjay at Hexagon 2011. As a post conference note, in my opinion, ERDAS received a boost from meeting ERDAS customers, distributors and partners. Also, the interest in ERDAS technology from all the other Hexagon companies was also tremendous.
http://www10.giscafe.com/video/ERDAS-Joel-Campbell-President/35179/media.html
Watch Joel's interview read the other links on "The Field Guide" concerning Hexagon 2011, what is coming with the ERDAS - Intergraph synergy effort, and what is coming in ERDAS 2012 when I return from vacation.
Mladen Stojic discusses the synergy efforts and the new development projects ERDAS is currently working on, and showed at Hexagon 2011: http://www10.giscafe.com/video/ERDAS-Mladen-Stojic/35210/media.html
Ryan Hughes of Skygone has some interesting thoughts on how he believes Hexagon should approach addressing the software product (ERDAS-Intergraph) synergy effort in this article: http://cloudcomputing.sys-con.com/node/1860109%20. His interview at Hexagon 2011 is found here: http://www10.giscafe.com/video/Skygone-Ryan-Hugheshttp://www.blogger.com/img/blank.gif-COO/35180/media.html.
Other Hexagon 2011 links:
Movie showing ERDAS IMAGINE Live Link with GeoMedia narrated by Paul.
3D the Way Forward for GIS Industry
The Future of Spatial Analysis Through Intergraph and ERDAS
Hexagon 2011 international Conference Attracts 2,500+ Attendees From 65 Countries
Hexagon 2011 Kicks Off with Game-Changing Vision for the Future
Field Report: Hexagon 2011 International Conference
Hexagon 2011 Facebook Page: http://www.facebook.com/media/set/?set=a.206253446083641.50370.169045849804401&l=de2f88525b
Wednesday, June 8, 2011
Hexagon 2011; the razing of the wall
The ERDAS portion of the Hexagon conference began on June 5, 2011 with customer training and ERDAS Ignite 2011. I arrived Sunday evening the 5th and on Monday morning attended the ERDAS International Distributors Meeting. In this meeting, ERDAS outlined what we are developing for the 2012 release, due in the next service packs and the development synergies we are working on with Intergraph GeoMedia and ERDAS IMAGINE. Our distribution partners are as excited as ERDAS employees about where ERDAS is going, and that ERDAS is aggressive in our plans and execution strategies.
As for me, I may be more excited about a different theme than others. Yes, the new modeling environment is exciting. Yes, the viewing environment moving to a more advanced form of the ER Mapper dynamic processing viewer is powerful. Yes, faster data processing is always enticing. And yes, LiDAR is needed by the mapping market and I love we are moving to deliver solutions there. And yes, Hexagon renting out Universal Studios, including Harry Potter World, for all conference attendees Tuesday evening was great too!
But, the theme of my excitement dates back to conversations I had with the ERDAS management in 1991 and have continued until today; saying ERDAS should be the one to tear down the wall between raster (remote sensing and raster GIS) and vector; by putting a powerful vector processing and database capabilities into ERDAS IMAGINE.
I have long believed this artificial segregation of data formats and processing techniques hurt the greater geospatial community, and ERDAS should raze the wall. Other than a purely academic or research exercise; remote sensing without significant vector capabilities limits what the customer can accomplish. Soon, for the first time ERDAS will have an arsenal of vector processing capabilities and significant database access.
The restrictions are being removed, the raster/vector barrier will be removed at the dawn of the point cloud data processing era. This time next year, you will see a very different ERDAS IMAGINE product. A product that makes the best remote sensing product in the world better, faster, uses dynamic processing, has new photogrammetry tools, new LiDAR tools, has many vector and database tools, and offers more than these to the GIS world.
This is not a token move, this is real. This is the path customers have asked ERDAS to take for 30 years; tearing down the raster – vector wall. The wall will be down before the Hexagon 2012 meeting.
Thank you Mladen Stojic, Joel Campbell, John Graham, Jürgen Dold, and Ola Rollén for giving the GIS community what they have long requested.
As for me, I may be more excited about a different theme than others. Yes, the new modeling environment is exciting. Yes, the viewing environment moving to a more advanced form of the ER Mapper dynamic processing viewer is powerful. Yes, faster data processing is always enticing. And yes, LiDAR is needed by the mapping market and I love we are moving to deliver solutions there. And yes, Hexagon renting out Universal Studios, including Harry Potter World, for all conference attendees Tuesday evening was great too!
But, the theme of my excitement dates back to conversations I had with the ERDAS management in 1991 and have continued until today; saying ERDAS should be the one to tear down the wall between raster (remote sensing and raster GIS) and vector; by putting a powerful vector processing and database capabilities into ERDAS IMAGINE.
I have long believed this artificial segregation of data formats and processing techniques hurt the greater geospatial community, and ERDAS should raze the wall. Other than a purely academic or research exercise; remote sensing without significant vector capabilities limits what the customer can accomplish. Soon, for the first time ERDAS will have an arsenal of vector processing capabilities and significant database access.
The restrictions are being removed, the raster/vector barrier will be removed at the dawn of the point cloud data processing era. This time next year, you will see a very different ERDAS IMAGINE product. A product that makes the best remote sensing product in the world better, faster, uses dynamic processing, has new photogrammetry tools, new LiDAR tools, has many vector and database tools, and offers more than these to the GIS world.
This is not a token move, this is real. This is the path customers have asked ERDAS to take for 30 years; tearing down the raster – vector wall. The wall will be down before the Hexagon 2012 meeting.
Thank you Mladen Stojic, Joel Campbell, John Graham, Jürgen Dold, and Ola Rollén for giving the GIS community what they have long requested.
Thursday, May 12, 2011
Virtual Mosaics using images from multiple directories
Many ERDAS IMAGINE customers think of Virtual Mosaic as a Viewer capability. ERDAS added ‘Virtual Mosaic’, along with ‘Virtual Layer Stack’ and ‘Virtual Independent Files’ into ERDAS IMAGINE 8.6, which was released in 2002.
The .vmc file is created using the Multiple option when multi-selecting images in the File Chooser, for most any process (Multiple tab pops up on the file chooser when shift-selecting images). Because the File Chooser does not support the ability to select across multiple directories at the same time, a .vmc file containing files from multiple different folders cannot be created with the file chooser.
Because the .vmc is a ASCII text file, the customer can easily create a file containing images from a multiplicity of file folders.
Below is an example of a .vmc file containing MrSID images from multiple different folders. Started the creation with windows command as follows: dir *.sid /b /s > glenville_virtual-mosaic.vmc. I then had to do some editing of the file to make sure the slashes ‘/’ were in the right direction, add VMC at the topeof the file and so forth…..
This is what glenville_virtual-mosaic.vmc looked like when I was finished with my text-smithing.
VMC
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville/glennville_ne.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville/glennville_nw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville/glennville_se.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville/glennville_sw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_ne/glennville_ne_ne.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_ne/glennville_ne_nw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_ne/glennville_ne_se.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_ne/glennville_ne_sw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_se/glennville_se_ne.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_se/glennville_se_nw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_se/glennville_se_se.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_se/glennville_se_sw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_sw/glennville_sw_ne.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_sw/glennville_sw_nw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_sw/glennville_sw_se.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_sw/glennville_sw_sw.sid
The .vmc file is created using the Multiple option when multi-selecting images in the File Chooser, for most any process (Multiple tab pops up on the file chooser when shift-selecting images). Because the File Chooser does not support the ability to select across multiple directories at the same time, a .vmc file containing files from multiple different folders cannot be created with the file chooser.
Because the .vmc is a ASCII text file, the customer can easily create a file containing images from a multiplicity of file folders.
Below is an example of a .vmc file containing MrSID images from multiple different folders. Started the creation with windows command as follows: dir *.sid /b /s > glenville_virtual-mosaic.vmc. I then had to do some editing of the file to make sure the slashes ‘/’ were in the right direction, add VMC at the topeof the file and so forth…..
This is what glenville_virtual-mosaic.vmc looked like when I was finished with my text-smithing.
VMC
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville/glennville_ne.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville/glennville_nw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville/glennville_se.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville/glennville_sw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_ne/glennville_ne_ne.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_ne/glennville_ne_nw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_ne/glennville_ne_se.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_ne/glennville_ne_sw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_se/glennville_se_ne.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_se/glennville_se_nw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_se/glennville_se_se.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_se/glennville_se_sw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_sw/glennville_sw_ne.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_sw/glennville_sw_nw.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_sw/glennville_sw_se.sid
//atlbck1/data/georgia/georgia-99doqq-mrsid/g_quads/glennville_sw/glennville_sw_sw.sid
Monday, May 2, 2011
ERDAS IMAGINE and GeoMedia, where are they going?
Over the last few months people have asked me what is going to happen with ERDAS IMAGINE and Intergraph's GeoMedia, two leading geospatial products under one roof. Ola Rollѐn sat down with Joe Francica this past January and at the end of the interview discussed this very point.
Basically Ola says, both products have been around a long time and have their own audiences and customers. He states Hexagon must be respectful of the two markets the products are serving. Longer-term, the GeoMedia and ERDAS IMAGINE products need to be able to speak and communicate one to another.
Here is the Joe Francica / Ola Rollѐn interview.
As the GIS market grows, there is a lot of room for growth for the old pioneers and the new arrivals. This because, the GIS pie is still growing. I believe the market is about positioned for a very big surge in growth. GIS companies can fight over the same piece of the pie, or companies can position themselves by improving and innovating, and grow as the whole GIS market pie grows.
Basically Ola says, both products have been around a long time and have their own audiences and customers. He states Hexagon must be respectful of the two markets the products are serving. Longer-term, the GeoMedia and ERDAS IMAGINE products need to be able to speak and communicate one to another.
Here is the Joe Francica / Ola Rollѐn interview.
As the GIS market grows, there is a lot of room for growth for the old pioneers and the new arrivals. This because, the GIS pie is still growing. I believe the market is about positioned for a very big surge in growth. GIS companies can fight over the same piece of the pie, or companies can position themselves by improving and innovating, and grow as the whole GIS market pie grows.
Tuesday, March 22, 2011
Q/A From Today's ECW/JP2 SDK Webinar
Below are the questions and answers that we covered in today's ERDAS ECW/JP2 SDK Webinar.
Q1: Compression is always followed by the loss of detail information, right? How does ECW handle that? Which compression rates are useful?
A1: ECW does not support numerically lossless compression at this time. However, if you use a target compression of 4 to 6:1 on RGB data, you should have a visually lossless image at a 2x zoom. See my blog for more information: http://field-guide.blogspot.com/2010/07/understanding-target-compression-ratio.html
Q2: Would you recommend ECW over JP2?
A2: I would recommend ECW over JP2 for all applications where an 8-bit lossy compression works. In the GIS community, a visually lossless setting is usually fine. We did a test when I was at Georgia Tech to see what compression was needed for the majority of users using a statewide dataset. The results are documented on my blog, linked above.
But remember, the ERDAS ECW/JP2 SDK supports JP2 very solidly! Any product using the SDK will have fast JP2 support and even faster ECW support.
Q3: It seems ECW cannot be used on ArcGIS Server and image server, any comment?
A3: ERDAS will release a new product, ECW for ArcGIS Server, spring 2011 to address this very issue. Look for it!
Q4: For aerial photos and orthophotos, which is better for delivering products without losing resolution and data, ECW or JP2?
A4: Pixel resolution is never lost in compression. The first thing you’ll notice in compression is very minor loss of contrast. As you compress further, a little more contrast is lost, and in heavier compression artifacts appear around road lines, edges and other linear features on aerial imagery. The question to ask is, “Do I need visually lossless or numerical lossless compression?” In most GIS applications, visually lossless compression works very well. In some (but not all) remote sensing applications, numerically lossless compression is needed.
The reason data vendors deliver numerically lossless data is that the data provider does not know if you are a GIS user doing imagery analysis or an image expert doing detailed remote sensing. They deliver one version to all, numerically lossless JP2. No problem, the ECW/JP2 SDK supports this!
Q5: Does a standard/report exist for the compression rates for several products (vector map production, base ortho maps, etc.)?
A5: I wish I knew of one, but I do not. This is an area for cartographers and remote sensing researchers to look for research grants. We need a standard.
Q6: How much faster can ERDAS ECW/JP2 SDK make image compression?
A6: I tested and documented this on my blog. Some SDK customers say their applications using v4.2 ECW encode 7x faster than it did in v3.3. Our research indicates most applications will experience greater than 2 x improvements over v3.3. But, JP2 is faster in v4.2 as well. Please see the following link for some tests I ran: http://field-guide.blogspot.com/2010/04/single-core-vs-multi-core-image.html
Q7: What can I provide a customer if he cannot read the ECW format - can I offer him a simple/free ECW reader/decoder?
A7: Many GIS applications can read ECW. ERDAS has a free viewer, ER Viewer that can be used as well. See: http://www.erdas.com/products/ERDASERMapper/ERDASERViewer/Details.aspx
Q8: At times, ECW cannot be opened directly in ArcGIS 10. Any suggestions about how to do that?
A8: There are two possibilities. One, ArcGIS 10 uses a version of GDAL that uses an older version of the ERDAS ECW/JP2 SDK . GDAL has now addressed that and supports v4.2; ESRI will pick up the ball and do the rest.
Two, some organizations who have licenses for the ERDAS ECW/JP2 SDK have added things to the ECW file that are not in compliance with the file format. This will cause problems. You might want to contact the organization that created the data to make sure they do not add any ‘goodies’ to the file format.
Q9: Are there any plans to use GP-GPU for compression?
A9: Yes. I cannot give specifics at this time, but I can say ‘yes.’
Q10: Can I lose accurate pixel value when I compress ECW data?
A10: At the present time, ECW has a visually lossless capability, not a numerically lossless capability.
Q11: Do you have any plans to support the updating of parts of an existing ECW file?
A11: Yes, this is under discussion. I will assume your question indicates an interest and will put your name in the request column. Thanks!
Q12: What would you use for storing floating point data, e.g. DEM data?
A12: Up until now, geospatial people have been using some sort of DR-RLE compression, such as that found in ERDAS’s IMG file format. Going forward, as the floating point JPEG2000 standard takes hold we will see more people use JP2 for lossless floating point data.
The question to ask is whether the maximum 2.5x reduction in file size on encoding worth the slowdown in decoding?
Q13: Which format is useful for signed16-bit data, ECW or JP2?
A13: ECW does not support signed data right now. Therefore, JP2 is the solution at this time.
Q14: Spanish users are having issues with plug-ins when using the Spanish version of the ERDAS ECW/JP2 SDK. Are you going to solve this soon?
A14: The ECW/JP2 SDK should not have a problem with this. If there is a problem with the free plug-in, it is in the plug-in code, not the ECW/JP2 SDK. We are working with Autodesk Germany on the AutoCAD 2011/2011 Plug-in to solve language support issues right now.
Q15: Paul, can you say anything publicly about when the AutoCAD 2010 plug-in will appear?
A15: We are waiting on Autodesk to help with a few installer questions. After that, we are ready to go.
Q16: Does ECW support stereo imagery data?
A16: Not inside the ECW file format. There are some companies that have modified the ECW file format (breaking the file for others), to support stereo parameters inside the file format. We have asked them to work with us to get it formally supported in the formal standard.
Until that time, the stereo parameters can be stored in the external .aux file.
Q17: Why is it necessary to have a plug-in to work with ECW in ERDAS software?
A17: When older versions of ERDAS software were made, ERDAS had not purchased ER Mapper and ECW support was incomplete. ERDAS purchased ER Mapper in May 2007, so that is when native ECW support became standard.
Q18: For unsigned 8-bit, unsigned 16 bit mss data, which format is more useable, ECW or JP2?
A18: ECW is an unsigned 8-bit data format. It can store panchromatic, RGB and multispectral data. 16-bit data should be stored in JP2 at this time.
Q19: Can the ECW format support hyperspectral data?
A19: ECW is a lossy, unsigned 8-bit data format that supports 65,535 bands. Give ECW a try!
Q20: We need to be able to make the background pixels of imagery transparent in ArcMap. ECW doesn't support this, but JP2 does. Is there any way to get the background pixels in ECW files to "disappear" in ArcMap (i.e. set the bg values to 255 or 0)?
A20: ECW added support for transparency in ECW/JP2 SDK v4.1, released in the fall of 2010. We had beta versions available in the summer, but this was too late for ESRI to get it supported in ArcGIS Desktop 10. GDAL is now updated, and the ball is in ESRI’s court. Let them know you want it!
In the ERDAS IMAGINE 2011 Exporter and MosaicPro, we enable you to define whatever value you want to be transparent; you can even define a region using a polygon.
Using ERDAS IMAGINE 2011’s “Create ECW Transparency” feature, you can also add a transparency layer to an existing ECW file via DNs or polygons without recompressing.
Q21: ECW or JP2 - where can I use each format and I how do I know?
A21: Both file formats are broadly accepted in the geospatial industry. If you wish to buy a product that does not support ECW/JP2, tell that product’s manager to give me a call. Remember, the SDK to provide desktop/client ECW, JP2, ECWP reading is free to the software developer.
Q22: Will you post the webinar.
A22: As usual, I forgot to record the webinar! I will re-record and post it later this week.
ERDAS ECW/JP2 SDK Product Page Link: http://www.erdas.com/products/ERDASECWJPEG2000SDK/Details.aspx
YouTube Video: http://www.youtube.com/watch?v=y6rjEgOkhoc&feature=plcp
Q1: Compression is always followed by the loss of detail information, right? How does ECW handle that? Which compression rates are useful?
A1: ECW does not support numerically lossless compression at this time. However, if you use a target compression of 4 to 6:1 on RGB data, you should have a visually lossless image at a 2x zoom. See my blog for more information: http://field-guide.blogspot.com/2010/07/understanding-target-compression-ratio.html
Q2: Would you recommend ECW over JP2?
A2: I would recommend ECW over JP2 for all applications where an 8-bit lossy compression works. In the GIS community, a visually lossless setting is usually fine. We did a test when I was at Georgia Tech to see what compression was needed for the majority of users using a statewide dataset. The results are documented on my blog, linked above.
But remember, the ERDAS ECW/JP2 SDK supports JP2 very solidly! Any product using the SDK will have fast JP2 support and even faster ECW support.
Q3: It seems ECW cannot be used on ArcGIS Server and image server, any comment?
A3: ERDAS will release a new product, ECW for ArcGIS Server, spring 2011 to address this very issue. Look for it!
Q4: For aerial photos and orthophotos, which is better for delivering products without losing resolution and data, ECW or JP2?
A4: Pixel resolution is never lost in compression. The first thing you’ll notice in compression is very minor loss of contrast. As you compress further, a little more contrast is lost, and in heavier compression artifacts appear around road lines, edges and other linear features on aerial imagery. The question to ask is, “Do I need visually lossless or numerical lossless compression?” In most GIS applications, visually lossless compression works very well. In some (but not all) remote sensing applications, numerically lossless compression is needed.
The reason data vendors deliver numerically lossless data is that the data provider does not know if you are a GIS user doing imagery analysis or an image expert doing detailed remote sensing. They deliver one version to all, numerically lossless JP2. No problem, the ECW/JP2 SDK supports this!
Q5: Does a standard/report exist for the compression rates for several products (vector map production, base ortho maps, etc.)?
A5: I wish I knew of one, but I do not. This is an area for cartographers and remote sensing researchers to look for research grants. We need a standard.
Q6: How much faster can ERDAS ECW/JP2 SDK make image compression?
A6: I tested and documented this on my blog. Some SDK customers say their applications using v4.2 ECW encode 7x faster than it did in v3.3. Our research indicates most applications will experience greater than 2 x improvements over v3.3. But, JP2 is faster in v4.2 as well. Please see the following link for some tests I ran: http://field-guide.blogspot.com/2010/04/single-core-vs-multi-core-image.html
Q7: What can I provide a customer if he cannot read the ECW format - can I offer him a simple/free ECW reader/decoder?
A7: Many GIS applications can read ECW. ERDAS has a free viewer, ER Viewer that can be used as well. See: http://www.erdas.com/products/ERDASERMapper/ERDASERViewer/Details.aspx
Q8: At times, ECW cannot be opened directly in ArcGIS 10. Any suggestions about how to do that?
A8: There are two possibilities. One, ArcGIS 10 uses a version of GDAL that uses an older version of the ERDAS ECW/JP2 SDK . GDAL has now addressed that and supports v4.2; ESRI will pick up the ball and do the rest.
Two, some organizations who have licenses for the ERDAS ECW/JP2 SDK have added things to the ECW file that are not in compliance with the file format. This will cause problems. You might want to contact the organization that created the data to make sure they do not add any ‘goodies’ to the file format.
Q9: Are there any plans to use GP-GPU for compression?
A9: Yes. I cannot give specifics at this time, but I can say ‘yes.’
Q10: Can I lose accurate pixel value when I compress ECW data?
A10: At the present time, ECW has a visually lossless capability, not a numerically lossless capability.
Q11: Do you have any plans to support the updating of parts of an existing ECW file?
A11: Yes, this is under discussion. I will assume your question indicates an interest and will put your name in the request column. Thanks!
Q12: What would you use for storing floating point data, e.g. DEM data?
A12: Up until now, geospatial people have been using some sort of DR-RLE compression, such as that found in ERDAS’s IMG file format. Going forward, as the floating point JPEG2000 standard takes hold we will see more people use JP2 for lossless floating point data.
The question to ask is whether the maximum 2.5x reduction in file size on encoding worth the slowdown in decoding?
Q13: Which format is useful for signed16-bit data, ECW or JP2?
A13: ECW does not support signed data right now. Therefore, JP2 is the solution at this time.
Q14: Spanish users are having issues with plug-ins when using the Spanish version of the ERDAS ECW/JP2 SDK. Are you going to solve this soon?
A14: The ECW/JP2 SDK should not have a problem with this. If there is a problem with the free plug-in, it is in the plug-in code, not the ECW/JP2 SDK. We are working with Autodesk Germany on the AutoCAD 2011/2011 Plug-in to solve language support issues right now.
Q15: Paul, can you say anything publicly about when the AutoCAD 2010 plug-in will appear?
A15: We are waiting on Autodesk to help with a few installer questions. After that, we are ready to go.
Q16: Does ECW support stereo imagery data?
A16: Not inside the ECW file format. There are some companies that have modified the ECW file format (breaking the file for others), to support stereo parameters inside the file format. We have asked them to work with us to get it formally supported in the formal standard.
Until that time, the stereo parameters can be stored in the external .aux file.
Q17: Why is it necessary to have a plug-in to work with ECW in ERDAS software?
A17: When older versions of ERDAS software were made, ERDAS had not purchased ER Mapper and ECW support was incomplete. ERDAS purchased ER Mapper in May 2007, so that is when native ECW support became standard.
Q18: For unsigned 8-bit, unsigned 16 bit mss data, which format is more useable, ECW or JP2?
A18: ECW is an unsigned 8-bit data format. It can store panchromatic, RGB and multispectral data. 16-bit data should be stored in JP2 at this time.
Q19: Can the ECW format support hyperspectral data?
A19: ECW is a lossy, unsigned 8-bit data format that supports 65,535 bands. Give ECW a try!
Q20: We need to be able to make the background pixels of imagery transparent in ArcMap. ECW doesn't support this, but JP2 does. Is there any way to get the background pixels in ECW files to "disappear" in ArcMap (i.e. set the bg values to 255 or 0)?
A20: ECW added support for transparency in ECW/JP2 SDK v4.1, released in the fall of 2010. We had beta versions available in the summer, but this was too late for ESRI to get it supported in ArcGIS Desktop 10. GDAL is now updated, and the ball is in ESRI’s court. Let them know you want it!
In the ERDAS IMAGINE 2011 Exporter and MosaicPro, we enable you to define whatever value you want to be transparent; you can even define a region using a polygon.
Using ERDAS IMAGINE 2011’s “Create ECW Transparency” feature, you can also add a transparency layer to an existing ECW file via DNs or polygons without recompressing.
Q21: ECW or JP2 - where can I use each format and I how do I know?
A21: Both file formats are broadly accepted in the geospatial industry. If you wish to buy a product that does not support ECW/JP2, tell that product’s manager to give me a call. Remember, the SDK to provide desktop/client ECW, JP2, ECWP reading is free to the software developer.
Q22: Will you post the webinar.
A22: As usual, I forgot to record the webinar! I will re-record and post it later this week.
ERDAS ECW/JP2 SDK Product Page Link: http://www.erdas.com/products/ERDASECWJPEG2000SDK/Details.aspx
YouTube Video: http://www.youtube.com/watch?v=y6rjEgOkhoc&feature=plcp
Monday, March 7, 2011
ERDAS Desktop 2011 Version 11.0.2
From the ERDAS desktop product download pages.... Released March 2, 2011. ERDAS Desktop 2011 Version 11.0.2 provides fixes and enhancements to the ERDAS Desktop 2011 products (ERDAS IMAGINE 2011, LPS 2011, and ERDAS ER Mapper 2011) and requires at least one of the ERDAS Desktop 2011 products to be installed before this version can be installed. This version installs the fixes found in ERDAS Desktop 2011 Version 11.0.1, which is superseded and no longer available.
See: http://www.erdas.com/service/support/fixes_enhancements/ERDASIMAGINE2011.aspx
See: http://www.erdas.com/service/support/fixes_enhancements/ERDASIMAGINE2011.aspx
Tuesday, December 28, 2010
Expanding Lidar Value in Local Governments
I often hear local governments who are flying Lidar to establish the terrain component of their aerial ortho projects. These local governments request a copy of the ‘raw’ Lidar data. What does ‘raw’ mean?
Typically, what the local government really wants is not the ‘raw’ Lidar data, but all Lidar returns further down the processing line. Commercial tools to process ‘raw’ Lidar imagery are not easy to use, nor are they currently cost effective. ERDAS, the inventor of commercial remote sensing, has historically been the company to introduce cost-effective remote sensing tools into the market-place. (I see Lidar as a remote sensing tool that heretofore has been used most successfully by photogrammetrists.)
It is understandable that local governments want more than detailed terrain model from their Lidar collection. Heretofore, Lidar collections have centered on elevation, but there is much more value available in Lidar data than only an elevation model. It is my belief, to use Lidar only as an elevation source, is like using imagery only as a backdrop to a GIS vector dataset; valuable, but very wasteful of the tax payer’s money.
Local governments need more value from their Lidar collections than just elevation, but that value is not easily captured in the ‘raw’ data. What Lidar data do local governments need to request? They need Lidar data that has been bore-sighted. Bore-sighting removes the small imprecision found in the GPS and IMU. These errors can be quite significant errors at a flying height of 5,000 feet (1500m).
After bore-sighting, the data are edited to define ground points and other features. This is a needed step to prepare the point cloud for terrain purposes. Yet, the Editing process can introduce very valuable information. Here is where vendor can classify the points into categories. The philosophy that points should be flagged with a classification, rather than be deleted from the dataset, emerged during the development of the LAS data format standard.
Of the several classification categories that can be defined in a LAS file, the categories local governments may wish to take advantage are: Ground; Low Vegetation; Medium Vegetation; High Vegetation; Building; and Water.
It is my opinion; the local government should obtain the intermediate product at this stage. All returns, bore-sighted and classified, no points added or removed. And, a full QA/QC report. If it were me, I’d ask for the intensity information as well.
The final need, the LAS tiles should each have fully defined horizontal and vertical coordinate systems (as ASPRS suggests). So many times local governments accept LAS tiles that only have the horizontal datum defined. Without knowing the vertical datum, you do not really know the height. Also, putting the vertical datum inside the LAS file rather than on a yellow sticky note on the DVD is far more appropriate. (And what happens when the yellow sticky note looses its sticky?)
Local governments ask, what can I use to work with my Lidar data? I said earlier, “Commercial tools to process ‘raw’ Lidar imagery are not easy to use, nor are they currently cost effective. ERDAS, the inventor of commercial remote sensing, has historically been the company to introduce cost-effective remote sensing tools into the market-place.” Now, ERDAS is presenting tools to convert your Lidar data to raster for further processing.
But why raster?
- Raster conversion of the point cloud can shrink LAS file to a IMG file ¼ the file size of the LAS (you only store x & y values once in the raster UL corner). But that is not the main reason, as I suggest keeping the LAS files in backup for the day when point processing engines are cost effective.
- The files being converted into raster allows a visual QA/QC of the data.
- Open Lidar collections up to the ERDAS community in a very cost effective manner (no additional costs). Once the data are in raster, the Spatial Modeler, Model Maker, Classification, Expert Classification, and Objective are available to the customer to process the data.
Subscribe to:
Posts (Atom)