Hello,
I have a survey block with an area of extent of about 50 square miles. The source multibeam sonar imagery for this survey has 1 meter resolution, with the exception of 5 small areas within the area of extent that contain notable features (referred to as "footprints" in this case). These footprints where mapped at 50cm resolution. In the surveys performed off our coast, It's common to have a survey block with most of the area mapped to 1m and the footprints with features mapped to 50cm. When creating shaded relief maps in ReefMaster using these sonar files, I used to export the Map Project with IMC set to Max Resolution = 512 & Min Resolution = .0625 (to match to highest resolution of the source imagery I'm working with). That works fine and results in some real crisp imagery on my devices, while the at5 file set usually comes in under 64GB (considering I use reformatted 64GB cards). I have had some projects that went over 64GB and that causes all kind of problems having to start over with the Map Project export process and how all the pieces of the imagery mosaic fit together once completed.

To mitigate Map Project exports going over 64GB, I'm exporting the Map Project for each resolution level instead of letting IMC run through all the resolution levels until it's finished. That way I can process the all the 1m & 50cm source imagery down to .0125 resolution, then turn off all the 1m files in the RM layers panel and change the footprint's "clamp to polygon map layer" from the larger area of extent polygon to individual polygons surrounding each small foot print area. I'm required to run the Generate Map process because my map boundaries have changed. when After I run the Generate Map process (between levels .0125 and .0625) Islands & Shoreline layers now appear my layers panel. This is where I get confused because, yes, the footprints are technically island, but when I export the Map Project to process the footprints at .0625 imagery, RM never stops generating .png & .kml files into the Temp -> source folder and IMC never picks up the files or initiates the .0625 at5 file generation phase. I thought running Generate Map in between Map Project exports might has disengaged the IMC utility, So I tested with just one footprint, and it works fine. I have my entire area of extent processed down to .0125 and one little mini-map that's processed to .0625.

Is RM designed to do what I trying to do? Let me know if you have any questions, I'm sure I made it a bit confusing trying to explain all that.

I think I understand what you are trying to do, but just to clarify - when you export at the highest (most zoomed in) level of zoom, are you only exporting the images within the circles?

A few observations:

It looks like you have a set of images, and are simply exporting them either together or with different polygon clips. You shouldn't need to regenerate the map when you change the polygon clipping for the image(s), so I'm not sure what is going on here. Do you have shorelines/islands set up? Are you generating vector layers as well as using the images in your map?

Clipping an image will/should limit the area that RM needs to generate for the IMC raster process, but it will still generate an area defined by the bounds of all visible clips. In your case, that looks similar to the size of the total image, so there is not going to be much saving within RM or the IMC here. The extra time taken by RM to generate the IMC input files might just be because of the zoom level selected. What you could try is exporting each clipped zone independently as a set of raster image files, collating all of these into a single folder and then running the IMC manually. This will save a lot of time within RM.

If I've misunderstood, let me know.

Sorry for the delay on getting back to your questions, and thanks for your informative response.

So my goal was to do this:
Preface - I I have six polygons created before I start the map project exports; one big one that defines the 50 square miles of 1m & 50cm area of extent, and five small circular polygons that define only the areas of higher resolution 50cm imagery. Only the big polygon is checked and visible at the time I start the exports, the 5 small ones are unchecked and not visable in the RM map dispaly (yet).
1. Define the large area of extent containing the 1m & 50cm imagery with the big polygon (as seen in image #1 above).
2. Then export each resolution level (from 512 down to .125, one level at a time) making sure the Project Base Naming and Atlas Description remain the same throught the map project exporting process.
3. After level .125 completes exporting, I uncheck the big polygon bounding all the 1m & 50cm imagery, then activate the five small circular polygons that bound only the 50cm resolution imagery (as seen in image #2 above). So all the 1m imagery is clipped out, and (in theory) RM exports only those five small areas of 50cm imagery to be processed by IMC at resolution level .0625 WHILE still retaining the same Project based naming & Atlas Description that I exported all the other resolution levels under.
4. The resulting compilation of .at5 files would load as one chart on a plotter (since all files have the common Project base naming and Atlas Description; and from a users perspective, all imagery would display seamlessly until the chart is zoomed down to the highest resolution threshold that supports 1m imagery, whereas the all 1m imagery would disappear and only the five clipped areas of 50cm imagery would display. So I still get to see my 1m and 50cm imagery as one chart without the 60gb of unnecessary data on my(reformatted 64gb sd card), and I don't have to go to my Chart Sources to select separate 'mini-map' which I would have had to create to accommodate only the 50cm imagery at resolution level .0625.

So long confusing story made short:
1. Export all imagery areas defined by one large polygon (roughly 50 squares miles) for levels 512 down to .125, then....
2. Deactivate large polygon, then activate the five small polygons which contain only 50cm imagery and clipping out all 1m imagery, then export only 50cm imagery at level .0625.

But I think what you're saying is that RM can't selectively process only those five polygons (islands?) of 50cm imagery when running the final export at resolution level .0625., It will also process all the no data which surrounds the 50cm imagery as well, which subsequently exports a huge data set of useless .at5 files at resolution level .0625?

I'm still a little confused, because I thought if I have islands defined by polygons, RM would ignore everything except the islands areas when doing a map project export? I guess I need to read up on the RM Help topics again to try to understand how island, land and shoreline settings work so all the surrounding nodata is ignored and only my areas of interest are exported.

Not a typical Reefmaster Use Case scenario, I know. I wouldn't be at all surprised if you just posted a 'roll eyes" emoticon as a reply to this post, locked the thread and moved on. haha. J/K, and again I really do appreciate all the hard work and support you've provided over the years.

Thanks.

Matt.

Hi Matt,
I'm resurrecting this topic because I have higher resolution imagery now. You offered a possible workaround that could possibly create individual images at .0625 resolution with busting the 64 GB size limit. I'm trying to visualize your instructions but need further clarification. Assuming I've already successfully exported my map layers from max resolution 512 down to min resolution 1D8 and they are in the 'shaded relief' folder generated during the first export. Now I'm trying to export the 0625 while maintaining reasonable at5 file sizes...(I've create a whole new description of what I'm doing further down in this reply).

You said: "What you could try is exporting each clipped zone independently as a set of raster image files, collating all of these into a single folder and then running the IMC manually. This will save a lot of time within RM."

My questions:
1. I have 53 images with their individual polygons populated in the 'Clip to polygon map layer' dropdown. Are you saying that I export each on of the 53 images separately to 53 individual folders?? Or run 53 exports to one folder? I have tried to export each layer to a one folder I created (separate) from the RM shaded relief folder but the exported at5 file gets overwritten by the next exported at5 file. So only one at5 will always exist in the folder which is the last one I exported.
2. What do you mean by 'clipped zone"? Is a clipped zone just one of the 53 layer or??
3. What do you mean by 'set of raster image files'?
4. 'collating all of these into a single folder'...Do I create this folder after I've exported all 53 layers (a total of 53 RM exports)? But I'm still confused about where I should export the 53 images and where I should copy the images after I've exported them all.
5. 'and then running the IMC manually'. The exported files are in at5 format in folders or folder now, so how it possible to run IMC manually with the files in at5 format?

======================================================================================
Here's the long description I created.
I'm creating a hi-res shaded relief bathymetry image map in RM that has the following zoom levels:
Max Resolution = 512
Min Resolution= .06255

I've successfully created high-resolution maps with a large area of extent using RM many times before, but usually stop the export at a minimum resolution of .0125 because the zoom level (.0625) would bust the 64GB size limit.

To manage the file sizes of the .at5 files as the resolution increases with each zoom level, I'm using the RM Export 'clip image to polygon map layer' feature to clip imagery layers, so I'm not unnecessarily exporting imagery that will be outside of the visible map extent as I'm zooming in to specific areas of interest.

I'm trying to fit the compilation of at5 files (max = 512 - min = .0625) on a 64 GB chip (formatted to FAT32).

I've created polygons to clip the imagery layers, displaying only the visible area of the extent as I zoom from max resolution 512 down to min resolution 0625. The area of extent of these polygons becomes progressively smaller as the zoom level increases, ending with 53 small polygons for each of 53 localized areas of interest (high-resolution imagery structures). Using this method, I'm able to manage the file sizes of the at5 files all the way down to min resolution .0125.

At min resolution .0625, I've turned off all the imagery layers in the RM layers list except for the 53 localized (small) clipped images, each of which has a polygon associated. I've also turned off the boundary polygons used to clip the larger imagery layers as I zoomed in.

My issue is that the combined size of the 14 at5 files created at min resolution 0625 (at5_1D16) is 41.5 GB.

The sizes of all the RM map exported at5 files are broken down by resolution levels as follows:

at5_512 = 194 KB
at5_256 = 802 KB
at5_128 = 2.53 MB
at5_64 = 8.50 MB

---

{Clipped images down between exporting zoom levels 64 and 32}

---

at5_32 = 33.0 MB
at5_16 = 130 MB
at5_8 = 516 MB
at5_4 = 2.0 GB

---

{Clipped images down between exporting zoom levels 4 and 2}

---

at5_2 = 474 MB
at5_1 = 716 MB

---

{Clipped images down between exporting zoom levels 1 and 1D2}

---

at5_1D2 = 2.76 GB
at5_1D4 = 4.02 GB
at5_1D8 = 11.4 GB

---

{Before exporting the last zoom level - .0625, I unselected all the larger images and polygons so only the 53 individual image layers and the 53 corresponding polygons (associated to their corresponding images) remained for export at min resolution 0625}

---

at5_1D16 = 41.5 GB

Since I only want RM to export the 53 images at min resolution .0625 and ignore everything else, I prepared each of the 53 images by doing combinations of the following:
1. Uploaded each of the 53 individual images and the 53 corresponding individual polygons, then associated each polygon to its corresponding image using the 'clip image to polygon map layer' feature. The at5_1D16 output files totaled 41.5 GB
2. Merged all the 53 images into one mbtiles file, then uploaded the single file to RM. Then I merged all 53 polygons into a single SHP file and uploaded it to RM. I then associated the merged polygon SHP file with the one merged imagery mbtiles file using the 'clip image to polygon map layer' feature. The at5_1D16 output files were even larger than 41.5 GB (I deleted them, but I think the total size was about 67 GB).
3. Export a single clipped localized image, then repeat. The single at5_1D16 file in the 'shaded relief' folder that RM creates when exporting a map is overwritten by the next at5_1D16 file that's RM exports.

I haven't done the math on the total area of the combined 53 images, but the size of the visible area I'm trying to map at 0625 should be way, way smaller than 41.5 GB. It looks like RM is exporting all the dead space around the 53 images at 0625, but I don't know what area RM is including in the hi-res at5 files. around those clipped 53 files. As I mentioned before, I had disabled all layers except the clipped 53 localized images and their polygons

1. How can I get RM to export the visible 53 image layers in the 0625 map export and ignore whatever else it's including that balloons the size of the at5_1D16 files to 41 GB?
2. Why are the exported at5_1D16 so big when the actual combined area of extent of the 53 images is so small?
3. What are the boundaries that RM uses when I have turned off all other image layers and polygons and clipped the 53 images before exporting the map at 0625 resolution?
4. Is my objective of reducing the size of the at5_1D16 files to a manageable size by clipping everything out except the 53 images layers even possible??

#0_ATLPOLYZOOM512.png
#1_DELMARVAPOLY.png
#2_LOWERBAYOUTERPOLY.png
#4c_LOWERBAYWESTPOLY.png
#5b_STRUCTUREPOLYS.png
#6_MIN0625STRUCTURES.png
#8a_KML7199ZOOM0625.png