More on Consolidated Mosaic

Well, it has become well known by now that MosaicPro will be included as a native part of IMAGINE Advantage and LPS Core in ERDAS IMAGINE 2010, due Fall 2009. The new MosaicPro had an internal working name of Consolidated Mosaic. MosaicTool, MosaicPro, lessons from ER Mapper and more were used to create the new MosaicPro (http://field-guide.blogspot.com/2009/06/consolidated-mosaic.html). Moreover, we have optimized MosaicPro to be much more RAM and CPU scalable, and that it touches each pixel the fewest times possible.

Yet, let me yell this from the house top.... all ERDAS IMAGINE and LPS customers with current Software Maintenance (SWM) will be receiving this 'new' MosaicPro in version 2010. It is a real gem. You will be impressed.

Here are some early tests:
Dual-core 2 GHz CPU, 4GB RAM, standard disks, Vista Business

Load 3840 images:
9.3.2 16:40 minutes; 463 MB RAM
2010 3:05 minutes; 98 MB RAM

Load 4896 images:
9.3.2 35:06 minutes; 669 MB RAM
2010 4:16 minutes; 113 MB RAM

Cutline Generation on 4896 images:
9.3.2 45:47 minutes; 1,606 MB RAM
2010 01:41 minutes; 125 MB RAM

Mosaicking 127 images:
9.3.2 41:41 minutes
2010 29:11 minutes

Dual Quad-core 2.328 GHz CPU, 16GB RAM, average speed disk array, XP-64
Mosaicking 3982 images:
9.3.2 Not possible
2010 >700GB output file in under 2.5 days

Mosaicking 1147 images:
9.3.2 Not possible
2010 >2.6TB output file in under 5.5 days

All processes used a maximum of just over 800MB of RAM. We researched using more RAM with MosaicPro and found it does not help. This is because we have tuned it so thoroughly that the bottleneck is now the operating system’s thread handling, and hard disk I/O. So, it is time to test fast disks.

But, when using the new added ECW / JPEG2000 direct-write from MosaicPro, MosaicPro will need more RAM. We are working on that as well. We expect we can protect the speed while shrinking down the memory requirement significantly. We expect this will occur in version 2010.1 (Sprilg 2010) or version 2011 (Fall 2010).

Now, we are ready to take MosaicPro to 64-bit. As you can see, when ERDAS goes to 64-bit, we will really take advantage of what 64-bit can really do. Many companies have used a 64-bit port to mask their sloppy coding by accessing more RAM. Not at ERDAS! We know there are a lot of issues surrounding true speed improvement and large file handling. We want our loyal customers to have it all! (http://field-guide.blogspot.com/2009/02/benefits-of-64-bit-architecture-in.html)

Personally, I enjoy looking at ERDAS IMAGINE as a CPU race-car entry. Maybe we can get Intel to test MosaicPro as it does ECW in its performance testing matrix?

Return to Singapore

After 16 years and 11 months, I am returning to Singapore. In September 1992 I traveled to Singapore with Karen Willoughby, Bruce Rado and Jack Dangermond; followed up by Adelaide, Australia. The trip was to attend the 1992 South Asia and OZRI User Group Meetings (UGM). In those days, ERDAS and ESRI held joint international UGMs as most of our distributors sold both companies products and the companies were considered business partners.

At the UGMs I presented a pre–release version of ERDAS IMAGINE 8.0.2. The products I presented were the recently released IMAGINE Digital Ortho and the soon to be released WYSIWYG Map Composer, IMAGINE Vector Module, and the graphic flow chart model builder enhancement to Spatial Modeler script language, Model Maker.

During the same meetings, Jack presented ESRI’s soon to be released product, ArcView. This was ESRI’s move to a graphical user interface. While ERDAS IMAGINE had already made the jump in 1991, ESRI was making the jump in 1992.

When we had some quiet time, Jack demoed ArcView to me and answered my questions. I was impressed at the simplicity of the product. I recognized it a difficult task to take niche technology and create a product to reach out to a wider, non-geospatial trained community. As I discussed ArcView with him, I saw that the product could make that transition.

After we finished looking and discussing ArcView, Jack said he wanted to see IMAGINE Model Maker. Of course, I ran the models that I had planned to run and knew the models would run. Then, as I did to Jack, he asked me to do things that were not planned. He wanted a specific model built from the beginning. I cannot remember the models, but I built and ran them… no problems (ArcView had crashed all over the place on Jack when I asked for specific things).

Almost 17 years later, ArcView has grown up to ArcGIS. For the release of ArcGIS 9.0 in 2004, ESRI copied the Model Maker idea to create Model Builder. ArcView targeted a horizontal expansion of the market and Model Maker targeted a deeper penetration in the existing market. Both product ideas are powerful and have succeeded.

Where will geo-processing be in another 16 years and 11 months? As for ERDAS IMAGINE, imagine that ERDAS IMAGINE 2010 is just the beginning.

IMAGINE Your Future (The Map of the Future is an Intelligent Image)

Here is a corporate video I believe was created from interviews made during the 1991 ERDAS User Group Meeting at SwissHotel; and completed during the spring of 1992. I am in this video at about 3:48. Thanks are due to Rob Luxeder (in the video at 6:08) for finding this jewel.

http://www.youtube.com/watch?v=F2L0dJBHZBw

People I see in the video are: Doug Stowe, Rudolph Richter, Bob Parrott, Kass Green, Richard Lacey, Gail MacAulay, Bill Newland, Roger Hoffer, Oliver Weatherbee, John Althausen (both then students at South Carolina), Bruce Rado, Lawrie Jordan, Brad Skelton, Jeff Dooley, Steve Sperry, Cheryl Brantley, Andy Zusmanis, Andy Bury, Xinghe Yang, Stan Quinn, Donn Rodekohr, Kurt Schwoppe, Barrie Collins, Rob Luxeder, Mike Schlemmer, Fred Woods, Andrea Gernazian, Hongyue Lin, Bill Sharp, Lynn Davis and Paul Beaty.

Who can you find?

See the Brief History of ERDAS IMAGINE in this blog here: http://field-guide.blogspot.com/2009/04/brief-history-of-erdas-imagine.html

Reprojecting Compressed Images

Have you ever had a very large compressed image you needed to reproject? The challenge is, you do not want to reproject to a new uncompressed version of the image file and then re-compress.

Have you used Calibration in ERDAS IMAGINE?

Let’s say you have a 2GB 20:1 MrSID compressed color infrared (CIR) image you need to deliver to an ArcGIS user in your organization. The last thing you want to do is resample and re-compress, right? That takes too much disk space and time.

Display the image in the Viewer, select Raster > Geometric Correct > Reprojection. On the dialog that appears, select the new projection and then select the ‘ruler’ on the Geo Correction Tools dialog to calibrate the image.

This process will create a .aux for you MrSID file storing the mathematical model to reproject the image on-the-fly.

Deliver both the MrSID image and the .aux file to your ArcGIS friend. That as fast and simple.

Notes:

1. Starting ERDAS IMAGINE 9.2+, the IMAGINE MrSID encoders write full projection information to the MrSID header. WKT strings are written to MG2, and WKT strings and GeoTIFF tags to MG3 data.
2. With this change, the need for .sdw files and .aux files for map and projection data are no longer needed, but are available.

ERDAS IMAGINE 2010 will have a Shoebox, what is that?

In the new Ribbon Interface for ERDAS IMAGINE 2010 we will add a new feature named, "Shoebox." The idea is to provide the customer a easy to use tool where a list of the data they are likely to use in a project are readily available. The Shoebox will not load the data in a database, but rather create an XML list of the locations of the data.

Hammad Kahn outlines some of the basic concepts of the Shoebox in, “Kicking Around With the Shoebox,” found at labs.erdas.com. Some of you have commented and asked questions below the article.

We may seem a little vague at times when discussing things on labs.erdas.com because it may not be the right time to discuss the more strategic features and future of new tool. Please do not feel we are offended when we side-step a question. In fact, we will use the specific question to help refine the new tool and from time-to-time contact you in private for clarification.

Anyway, please check out Kicking Around With the Shoebox at: http://labs.erdas.com/blog_view.aspx?q=6098

Consolidated Mosaic

Consolidated Mosaic is a working name for a new mosaic paradigm that will be introduced in ERDAS IMAGINE 2010. Consider the different tools ERDAS, Inc. has for mosaicking images:

• ERDAS IMAGINE's MosaicTool (original mosaic tools, good defaults options)
• ERDAS MosaicPro (advanced MosaicTool, easy cutlines, ortho-correct from block files )
• ERDAS ER Mapper Mosaic (fast virtual mosaic, a lot of capacity, limited capability)
• ERDAS ER Mapper Color Balance (fast color balance, limited to true color)
• ERDAS Image Compressor (fast ECW and JPEG 2000 compression)
• ERDAS IMAGINE's MosaicDirect (Wizard to feed to MosaicPro and batch)
• ERDAS IMAGINE's MosaicWizard (Wizard to process mosaic)
• ERDAS IMAGINE's Virtual Mosaic (more capability than ER Mapper Mosaic, less capacity)

What if we combined these products in a single product? What if you could mosaic >2.5 terapixels of data straight into a single >2.5 terapixel IMG, or to a 20:1 compressed ECW, or to a lossless compressed JPEG2000 image. What if you could break that >2.5 terapixel mosaic into tiles with your shapefiles (and it has no temp files)? What if you could do all this within a 32-bit operating system environment?

If you think this can help you, keep your eyes open for a WebEx or an erdas labs discussion on this topic very soon.

I gave you a hint of where we were going when I asked Hammad to post to The Field Guide in: http://field-guide.blogspot.com/2009/02/benefits-of-64-bit-architecture-in.html

Web Demo of ERDAS Enterprise Server Products

Recently, ERDAS placed web demos of ERDAS Enterprise Server Products on the web for the world to play with. The data are from Cherokee County, Georgia. I believe the speed is incredible. Give it a look at: http://demo.erdas.com/

If you wish, compare to the online mapping of: http://www.richlandmaps.com/#mapping

Preview the Future of ERDAS IMAGINE and more on ERDAS Labs

This is going to be fun....

ERDAS Inc. announces the launch of ERDAS Labs, an informative new site highlighting technology currently being developed.

“ERDAS Labs provides the market and our customers a window into our product development activities; whether it’s a concept or idea we’re exploring, or a new feature under development for a product,” said Bruce Chaplin, Senior Vice President, Product Development, ERDAS. “We’ll showcase projects under active development, engaging our customers in conversations about these projects and soliciting their feedback.”

Whether it is an innovative new idea being explored or a major new feature being implemented for the next version of a product, ERDAS Labs provides a forum for discussion with the development team.

Visit http://labs.erdas.com/.

Vote Early and Vote Often

Please cast your vote for the image file formats you use.


Пожалуйста отдайте свой голос за формат или форматы, которые Вы чаще всего используете.

Para favor lance seu voto para os formatos de arquivo de imagem que você usa.

Vote para favor para los formatos de archivo de imagen que usted utiliza.

S'il vous plaît voter pour les formats de dossier d'image vous utilisez.

使用されている画像フォーマットの投票に参加してください。

请为你使用的图像文件格式投票。

Stem alstublieft op de raster formaten die u het meest gebruikt.

Bitte wählen Sie die Bildformate, mit welchen Sie arbeiten.

Per favore di lanciare il suo voto per i formati di file di immagine lei usa.

Behag støp din stemme for avbildene arkivene formatene som du bruker.


The "Vote Early and Vote Often" phrase in the US is a humorous way of saying, "Make sure you vote, and vote in each election." It appears I am saying, "Vote early in the morning and vote many times during the same election." That is illegal and morally wrong. I would be disappointed in someone who would do that.

Scanned Aerial Photo Pixel Size Determination

Many GIS people are collecting historical aerial photos to understand the changes in their areas of responsibility. I became interested in historical aerial photos when a student of Drs. John Jensen and Dave Cowan at the University of South Carolina (Dept. of Geography). One of Jensen’s graduate teaching assistants gave us a stereo pair of black and white aerial photos for us to use in our aerial photo interpretation lab. Among the tasks we had to perform was to decide what part of the US the photos covered. It was a trick question.

The stereo pairs were from the late 1930s, had smoothly rolling terrain, and were mostly covered by hay, corn and other crops. Trees were only located to provide shade for homes and along the larger streams. All but one student guessed Kansas was the area. The one who guessed differently said Nebraska (he was from Nebraska). We were all wrong. It was from Laurens County, South Carolina about 60 miles north of the university. Look on Google today.

We missed it because in 1989 (and today) when we drove through the area, there was little farming and the area was mostly covered by trees. But if we had looked carefully, we would have noticed that most of the trees were less than 50 years old.

So, thus began an interest in historical aerial imagery. The chart below was born at that time when I was a graduate student and working at South Carolina Department of Natural Resources.

			1:40000		1:9600		1:4800		1:2400		1:1200
DPI	Microns	Feet	Meters	Feet	Meters	Feet	C'meters	Inches	C'meters	Inches	C'meters
508	50	6.56	2.00	1.57	0.48	0.79	24.00	4.72	12.00	2.36	6.00
635	40	5.25	1.60	1.26	0.38	0.63	19.20	3.78	9.60	1.89	4.80
847	30	3.94	1.20	0.94	0.29	0.47	14.40	2.83	7.20	1.42	3.60
1016	25	3.28	1.00	0.79	0.24	0.39	12.00	2.36	6.00	1.18	3.00
1270	20	2.62	0.80	0.63	0.19	0.31	9.60	1.89	4.80	0.94	2.40
1411	18	2.36	0.72	0.57	0.17	0.28	8.64	1.70	4.32	0.85	2.16
1814	14	1.84	0.56	0.44	0.13	0.22	6.72	1.32	3.36	0.66	1.68
2540	10	1.31	0.40	0.31	0.10	0.16	4.80	0.94	2.40	0.47	1.20
3629	7	0.92	0.28	0.22	0.07	0.11	3.36	0.66	1.68	0.33	0.84

1. These are in photo scales; not in map scales.
2. Diapositive or negative transparencies provide the best results. The original scan resolution should be at least 20% smaller than the final pixel size. Scanning images above 50 microns will make it difficult to measure fiducials correctly, and is discouraged when doing ortho-correction.
3. The best available resolution is determined from the "Camera Calibration Report" in the "Lens Resolving Power" section. Depending on the quality of the camera, lens and film; resolution quality will vary across the image. 1000 / Tangential Line value will calculate the available resolution of the image in microns. As an example, cameras used to capture US Geological Survey (USGS) National Aerial Photography Program (NAPP) imagery typically had a maximum resolving ability from 8.85 to 15.38 microns. Using this information, the USGS typically scanned CIR NAPP imagery at 14 microns.
4. Below is a graphic Spatial Model to convert scanned negatives to positives. It is simply each digital number minus 255 (if the data are 8-bit). You may wish to add another step to the model to the model eliminate all zero and 255 values. Remote sensing software (including ERDAS IMAGINE) like zero as the background values (black). ESRI's ArcGIS likes 255 as the background value (white). The difference comes from image analysts wanting a black background to ease eye strain, while GIS analysts wanting a white background for the map composition. Although the ArcGIS user could make the 255 values transparent, many are not familiar with this option. Thus ESRI made it simple for their customers.

PAGESIZE 6, 8 INCHES;
CELLSIZE MINIMUM;
PRINTERPAGESIZE 8.5, 11;
MARGINS 0.5, 0.5, 0.5, 0.5;
ORIENTATION PORTRAIT;
PRINTSCALE 100;
WINDOW UNION;
PROJECTION DEFAULT;
AOI NONE;
OPTIMIZE NO;
RASTER {
ID 1;
TITLE "n1_memory";
POSITION 0.833329, 0.666667;
TEMPFILE;
INTERPOLATION NEAREST;
ATHEMATIC;
DATATYPE FLOAT;
DECLARE "Integer";
COMPRESSION UNCOMPRESSED;
COORDINATES MAP;
RECODE NO;
CHILD 2;
}
FUNCTION {
ID 2;
TITLE "$n1_memory";
POSITION 1.68889, 1.91111;
VALUE "$n1_memory - 255";
AREA UNION;
CHILD 3;
}
RASTER {
ID 3;
TITLE "n3_memory";
POSITION 2.54444, 3.28889;
TEMPFILE;
NEWFILE;
INTERPOLATION NEAREST;
ATHEMATIC;
DATATYPE FLOAT;
DECLARE "Integer";
COMPRESSION UNCOMPRESSED;
COORDINATES MAP;
RECODE NO;
}

Fill Holes and Slivers in Imagery (Table of Values)

Here is a graphic Spatial Model (PaulBeaty_HoleFiller_Table.gmd) I created when I was at Georgia Tech. It fills DEM and other raster data (including imagery) holes and slivers with data calculated values from surrounding pixel values. These 1, 2 and sometimes 3 pixel wide artifacts are common to users who have reprojected butt-matched raster data. This model finds the "to-be-replaced" values from a table of values and determines whether a 3 x 3 or 5 x 5 focal mean should be applied. The model ignores the replacement values when calculating the focal mean.

Copy and paste the text below into a text editor and save as ANSI text file without the text editor's formatting. Save as PaulBeaty_HoleFiller_Table.gmd and open in Model Maker.

PAGESIZE 6.04444, 8.73889 INCHES;
CELLSIZE MINIMUM;
PRINTERPAGESIZE 8.5, 11;
MARGINS 0.5, 0.5, 0.5, 0.5;
ORIENTATION PORTRAIT;
PRINTSCALE 100;
WINDOW INTERSECTION;
PROJECTION DEFAULT;
AOI NONE;
OPTIMIZE YES;
RASTER {
ID 1;
TITLE "n1_PROMPT_USER";
POSITION 0.855556, 1.4;
PROMPT;
IGNORE 0;
INTERPOLATION NEAREST;
ATHEMATIC;
DATATYPE UNSIGNED16;
DECLARE "Integer";
COMPRESSION UNCOMPRESSED;
COORDINATES MAP;
AREA RECT 26, -2.079167 : 26.628333, -5.184167;
AOI NONE;
RECODE NO;
CHILD 2;
}
FUNCTION {
ID 2;
TITLE "EITHER";
POSITION 2.18889, 3.21111;
VALUE "EITHER (FOCAL MEAN ( $n1_PROMPT_USER , $n6_Low_Pass , IGNORE_VALUE $n28_Custom_Integer , APPLY_AT_VALUE $n28_Custom_Integer ) ) IF ( (FOCAL MAJORITY ( $n1_PROMPT_USER , $n3_Low_Pass ) == $n28_Custom_Integer) ) OR (FOCAL MEAN ( $n1_PROMPT_USER , $n3_Low_Pass , IGNORE_VALUE $n28_Custom_Integer , APPLY_AT_VALUE $n28_Custom_Integer ) ) OTHERWISE";
AREA UNION;
CHILD 4;
}
MATRIX {
ID 3;
TITLE "n3_Low_Pass";
POSITION 3.42222, 5.36667;
SIZE 3, 3;
DATATYPE SIGNED32;
BUILTIN LOWPASS;
VALUE 1, 1, 1,
1, 1, 1,
1, 1, 1;
NORMALIZE NO;
CHILD 2;
}
RASTER {
ID 4;
TITLE "n4_PROMPT_USER";
POSITION 0.944445, 5.24444;
PROMPT;
NEWFILE;
IGNORE 0;
INTERPOLATION NEAREST;
ATHEMATIC;
DATATYPE UNSIGNED16;
DECLARE "Integer";
COMPRESSION UNCOMPRESSED;
COORDINATES MAP;
RECODE NO;
}
MATRIX {
ID 6;
TITLE "n6_Low_Pass";
POSITION 3.26667, 1.68889;
SIZE 5, 5;
DATATYPE SIGNED32;
BUILTIN LOWPASS;
VALUE 1, 1, 1, 1, 1,
1, 1, 1, 1, 1,
1, 1, 1, 1, 1,
1, 1, 1, 1, 1,
1, 1, 1, 1, 1;
NORMALIZE NO;
CHILD 2;
}
TEXT {
ID 7;
TITLE "Repair Holes and Slivers using a Table of Values";
POSITION 2.67778, 0.344445;
FONT "new century schoolbook";
SIZE 18;
}
TEXT {
ID 8;
TITLE "5 x 5 filter";
POSITION 3.26667, 0.988889;
FONT "new century schoolbook";
SIZE 12;
}
TEXT {
ID 10;
TITLE "Value(s) to Replace";
POSITION 0.788889, 2.57778;
FONT "new century schoolbook";
SIZE 12;
}
TEXT {
ID 11;
TITLE "3 x 3 filter";
POSITION 3.52222, 4.66667;
FONT "new century schoolbook";
SIZE 12;
}
TEXT {
ID 13;
TITLE "Conditional statement to determine";
POSITION 3.8, 2.78889;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 14;
TITLE "which filter is more appropriate. If a majority";
POSITION 4.06667, 2.96667;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 15;
TITLE "of the pixels are the \"Value(s) to Replace,\"";
POSITION 4.01111, 3.18889;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 16;
TITLE "the 5 x 5 filter is used. Otherwise, ";
POSITION 3.8, 3.38889;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 17;
TITLE "the 3 x 3 filter is used.";
POSITION 3.4, 3.58889;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 18;
TITLE "Be sure to define the correct";
POSITION 1.03333, 6.23333;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 19;
TITLE "\"Data Type\" in the output file.";
POSITION 1.03333, 6.43333;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 20;
TITLE "Created in IMAGINE 8.4 - Developed by Paul Beaty";
POSITION 2.72222, 7.08889;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 21;
TITLE "Center for Geographic Information Systems";
POSITION 2.72222, 7.47778;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 22;
TITLE "Georgia Institute of Technology - Atlanta Georgia, USA";
POSITION 2.82222, 7.65556;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 26;
TITLE "Both filters ignore the \"Value(s) to Replace\"";
POSITION 4.06667, 3.77778;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 27;
TITLE "when calculating the mean.";
POSITION 3.58889, 3.98889;
FONT "new century schoolbook";
SIZE 10;
}
TABLE {
ID 28;
TITLE "n28_Custom_Integer";
POSITION 0.744445, 3.21111;
SIZE 4;
DATATYPE SIGNED32;
VALUE 0, 10, 20, 30;
CHILD 2;
}
TEXT {
ID 29;
TITLE "Add and delete values";
POSITION 0.8, 4.08889;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 30;
TITLE "Integer or float?";
POSITION 0.777778, 4.27778;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 31;
TITLE "Modified in IMAGINE 8.7 - Paul Beaty";
POSITION 2.71111, 7.27778;
FONT "new century schoolbook";
SIZE 10;
}

Fill Holes and Slivers in Imagery (Single Value)

Here is a graphic Spatial Model (PaulBeaty_HoleFiller.gmd) I created when I was at Georgia Tech. It fills DEM and other raster data (including imagery) holes and slivers with data calculated values from surrounding pixel values. These 1, 2 and sometimes 3 pixel wide artifacts are common to users who have reprojected butt-matched raster data. This model finds the "to-be-replaced" value and determines whether a 3 x 3 or 5 x 5 focal mean should be applied. The model ignores the replacement value when calculating the focal mean.

Copy and paste the text below into a text editor and save as ANSI text file without the text editor's formatting. Save as PaulBeaty_HoleFiller.gmd and open in Model Maker.

PAGESIZE 6.04444, 8.83889 INCHES;
CELLSIZE MINIMUM;
PRINTERPAGESIZE 8.5, 11;
MARGINS 0.5, 0.5, 0.5, 0.5;
ORIENTATION PORTRAIT;
PRINTSCALE 100;
WINDOW INTERSECTION;
PROJECTION DEFAULT;
AOI NONE;
OPTIMIZE YES;
RASTER {
ID 1;
TITLE "n1_PROMPT_USER";
POSITION 0.8, 1.7;
PROMPT;
INTERPOLATION NEAREST;
ATHEMATIC;
DATATYPE SIGNED16;
DECLARE "Integer";
COMPRESSION UNCOMPRESSED;
COORDINATES MAP;
AOI NONE;
RECODE NO;
CHILD 2;
}
FUNCTION {
ID 2;
TITLE "EITHER";
POSITION 2, 3.3;
VALUE "EITHER (FOCAL MEAN ( $n1_PROMPT_USER , $n6_Low_Pass , IGNORE_VALUE $n5_Integer , APPLY_AT_VALUE $n5_Integer ) ) IF ( (FOCAL MAJORITY ( $n1_PROMPT_USER , $n3_Low_Pass ) == $n5_Integer) ) OR (FOCAL MEAN ( $n1_PROMPT_USER , $n3_Low_Pass , IGNORE_VALUE $n5_Integer , APPLY_AT_VALUE $n5_Integer ) ) OTHERWISE";
AREA UNION;
CHILD 4;
}
MATRIX {
ID 3;
TITLE "n3_Low_Pass";
POSITION 3.3, 5.9;
SIZE 3, 3;
DATATYPE SIGNED32;
BUILTIN LOWPASS;
VALUE 1, 1, 1,
1, 1, 1,
1, 1, 1;
NORMALIZE NO;
CHILD 2;
}
RASTER {
ID 4;
TITLE "n4_PROMPT_USER";
POSITION 0.988889, 5.5;
PROMPT;
NEWFILE;
INTERPOLATION NEAREST;
ATHEMATIC;
DATATYPE SIGNED16;
DECLARE "Integer";
COMPRESSION UNCOMPRESSED;
COORDINATES MAP;
RECODE NO;
}
SCALAR {
ID 5;
TITLE "n5_Integer";
POSITION 0.6, 4;
DATATYPE SIGNED32;
VALUE -32767;
SHOW;
CHILD 2;
}
MATRIX {
ID 6;
TITLE "n6_Low_Pass";
POSITION 3.2, 1.8;
SIZE 5, 5;
DATATYPE SIGNED32;
BUILTIN LOWPASS;
VALUE 1, 1, 1, 1, 1,
1, 1, 1, 1, 1,
1, 1, 1, 1, 1,
1, 1, 1, 1, 1,
1, 1, 1, 1, 1;
NORMALIZE NO;
CHILD 2;
}
TEXT {
ID 7;
TITLE "Repair DEM Holes and Slivers";
POSITION 2.4, 0.5;
FONT "new century schoolbook";
SIZE 18;
}
TEXT {
ID 8;
TITLE "5 x 5 filter";
POSITION 3.2, 1.1;
FONT "new century schoolbook";
SIZE 12;
}
TEXT {
ID 10;
TITLE "Value to Replace";
POSITION 0.644444, 3.4;
FONT "new century schoolbook";
SIZE 12;
}
TEXT {
ID 11;
TITLE "3 x 3 filter";
POSITION 3.4, 5.2;
FONT "new century schoolbook";
SIZE 12;
}
TEXT {
ID 13;
TITLE "Conditional statement to determine";
POSITION 3.7, 2.8;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 14;
TITLE "which filter is appropriate. If a majority";
POSITION 3.8, 3;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 15;
TITLE "of the pixels are the \"Value to Replace,\"";
POSITION 3.83333, 3.18889;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 16;
TITLE "the 5 x 5 filter is used. Otherwise, ";
POSITION 3.7, 3.4;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 17;
TITLE "the 3 x 3 filter is used.";
POSITION 3.3, 3.6;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 18;
TITLE "Be sure to define the correct";
POSITION 1.2, 6.4;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 19;
TITLE "\"Data Type\" in the output file.";
POSITION 1.2, 6.6;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 20;
TITLE "Created in IMAGINE 8.4 - Developed by Paul Beaty";
POSITION 2.7, 7.4;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 21;
TITLE "Center for Geographic Information Systems";
POSITION 2.7, 7.6;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 22;
TITLE "Georgia Institute of Technology - Atlanta Georgia, USA";
POSITION 2.8, 7.8;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 26;
TITLE "Both filters ignore the \"Value to Replace\"";
POSITION 3.9, 3.8;
FONT "new century schoolbook";
SIZE 10;
}
TEXT {
ID 27;
TITLE "when calculating the mean.";
POSITION 3.48889, 4;
FONT "new century schoolbook";
SIZE 10;
}