Setting the Maximum image size per request for an Image Service

[KentAnness]

We have several image services running but some of our MicroStation users would like to extract imagery that is larger than the default setting of (rows x columns) 4100 x 15000. However, we are unable to enter any value larger than the default values. It just won't accept the larger values for some reason. I've looked at the Help and so forth but have seen nothing that indicates that we should not be able to do this.

Has anyone ran into this issue before?

Thanks for any assistance or guidance!

[KentAnness]

I have learned that you must make the change in the underlying Mosaic dataset and then totally recreate the service. Refreshing the service will not work as it does not recognize the changes.

Now we've learned that we cannot make any requests larger than about 6000 x 6000 or it just won't work. Anything below that size works well and quite fast. We've also increased the Maximum number of rasters per mosaic from 20 to 40 but that doesn't help.

Still stumped!

[PeterBecker]

The max value that can be entered in the Service Properties for 'Max size of request' is the default value from the Mosaic Dataset properties. First change the mosaic dataset properties to a larger value and then you will be able to set the Service Properties to a larger value. There is no need to recreate the mosaic dataset or the service. You will need to restart the service for the revised properties to take effect, as well as make a new connection from the client application.
I have just tested with 15000x15000 and it works fine for my testing. There should not be any 6000x6000 limit. Please check again.

The max number of rasters defines the maximum number of individual rasters that may partake in the creation of a single exported image. When making larger requests (including cache generation) it is advisable to increase the values. Unless the input is a lot of small overlapping images (such as browse imagery) it should be very rare for more then say 40 rasters to cover the request extent.

[KentAnness]

Peter,

Thanks for the response! I have increased both the "Maximum image size per request" and the "Maximum number of rasters to mosaic" within the Mosaic dataset but refreshing the service will not honor the changes. Documentation indicates that the service must be re-created and in fact, that did fix that issue. Now our service shows the increased values accordingly.

We've continued to test against a couple of our services and it appears that there is still some threshold where the export image request fails. There also seems to be some tie between image size and image format. For example, I can export a JPEG that is 9000,9000 but requesting a TIFF for that same extent fails. If I back down the size to 6000,6000 the TIFF export function does work.

More than anything, I'm trying to figure out what the upper limits may be so that we can program around it accordingly.

We're getting closer!

Appreciated!

Kent

Below is one of the services we are testing with and a sample Bounding Box:

http://kyraster.ky.gov/ArcGIS/rest/services/ImageServices/Ky_NAIP_2010_1M_4Band/ImageServer

Bounding Box:                   5249275.0529,3971681.0569,5259275.0529,3981681.0569
Image Size:                      6000,6000
Image Format:                  tiff
Interpolation:                    RSP_BilinearIntermpolation
Export Image (GET)

[JeffreySwain]

In testing here, I had to make a few changes to my default properties to get an output of greater than 6,000 by 6,000.  I adjusted 4 different settings in order to allow the REST page to return the values.  In addition to the Maximum Size of Requests, I also adjusted the number or records returned, the maximum number of rasters per mosaic and the max number of downloads. After the service was re created here, it was possible to return an REST request of greater than 7,000 by 7,000.  In your provided example the largest export I could achieve was 15,000 by 4,100, which seems to indicate that you have not adjusted the default setting of 1,500 by 4,100.  I would recommend adjusting the default properties as explained.  Once they are changed you should be able to get the desired results.  Also be sure to clear the cache after changes are made to see them. 

Working Rest request with your data.

For my test, I used 227 combined tifs and overviews that covered total of 30,720 columns and 28,672 rows.  When I increased the values indicated to exceed the total number of rasters in the mosaic dataset, the larger area was able to be obtained via REST.

[KentAnness]

Jeff,
Thanks for the response. You are correct, the service for the REST endpoint I provided had not yet been updated in terms of the maximum parameters. My NAIP 3 Band Service (http://kyraster.ky.gov/ArcGIS/rest/services/ImageServices/Ky_NAIP_2010_1M/ImageServer) had been updated but not the 4Band version I referenced above. I apologize for the oversight. I just updated the parameters on the 4Band service and will do some testing to see if that resolved the issue.
Your assistance is appreciated,
Kent

[KentAnness]

Below is a sample extent for an Interstate resurfacing project here in Kentucky that would leverage either one of our NAIP 1 meter services.

5015976.5434,3952452.4034,5079496.9466,3969921.3668

The associated image size should be about 19000,5335

I am unable to get this to work on our end.

[JeffreySwain]

What have you increased the downloads to?  Have you put a value in larger than your total source rasters plus overviews?  Or just adjusted the rows and columns?  The options are collected as columns and rows, so the columns and rows option should be greater than 19000,5335 and like I mentioned before increase the total number of number or records returned, the maximum number of rasters per mosaic and the max number of downloads.  In my testing here, once I increased the values to exceed what was available in the mosaic dataset, It worked. 

I am also assisting on your incident if you reply to that as well. 

The only other question I have is if you are trying to get the entire raster into MicroStation, why not simply export the mosaic dataset and then add it there, rather than try to get them to download the export this way? The purpose of the image service is to make it more convenient not more problematic than pushing out the actual raster.  The output from the REST page is just a new raster that is not in as fine a resolution as the original. If you are not consuming it over the internet, but consuming it locally, why create a new coarser version? 

The download capabilities that you are modifying on the mosaic dataset are configured that way to allow some access to the underlying rasters via the web, but if you are trying to basically create a new raster from the web, there are easier ways.

[KentAnness]

Please the image below. I have increased all values to exceed the maximum number of images (records) within the underlying Mosaic Dataset.

[ATTACH=CONFIG]15215[/ATTACH]

We are not trying to get the entire raster in Microstation but rather a specific area of interest that relates to individual highway projects.

Additionally, the goal is not to have them access the source images of the Mosaic Dataset as those images are in UTM meters. The Microstation users need the imagery in our native Kentucky Single Zone coordinates with US Feet. Thus export the imagery from the service for a defined area of interest is the primary desire.

[WenxueJu]

It appears that exported image size exceeds the default heap size limit per arcsoc process, which is controlled at the server level. Please refer to this kb article to increase the soc max heap size:
http://support.esri.com/es/knowledgebase/techarticles/detail/40890