topic Re: Best approach to publish heavy images: size and numbers, in ArcGIS Enterprise Questions

Best approach to publish heavy images: size and numbers,

JamalNUMAN — Fri, 29 Mar 2013 09:59:16 GMT

Best approach to publish heavy images: size and numbers,

I wanted to publish images (around 78 images) with different sizes (from 5 MB to 133 MB) that have ecw extension.

1. To cover come the issue of the ecw, we purchased the �??ECW for ArcGIS Server 10.1�?� to be able to publish this sort of images as publishing the ecw images is not supported by the ArcGIS

http://forums.arcgis.com/threads/62836-Publishing-mxd-files-containing-*.ecw-images?p=218401#post218401

2. Now, publishing this amount of images (around 6.38 GB in total) is not an easy job. Then I�??m wondering if there might be better approach to be able to publish these images with optimal time

[ATTACH=CONFIG]23073[/ATTACH]

What might be the best practice to publish this amount of images?

Thank you

Best

Jamal

Re: Best approach to publish heavy images: size and numbers,

MarcoBoeringa — Fri, 29 Mar 2013 11:18:48 GMT

2. Now, publishing this amount of images (around 6.38 GB in total) is not an easy job. Then I�??m wondering if there might be better approach to be able to publish these images with optimal time

Jamal,

Could you be a bit more specific as to why "publishing this amount of images... is not an easy job"?

Is the problem with the publishing of the service itself? Is it taking excessively long?

Or is the problem actually not related to the publishing process, but are you merely unsatisfied with the ECW services performance as a web service when accessed from the internet?

These are two different problems...

In case of excessive publishing times, you definitely should check out if ArcGIS for Server is accessing the data directly (as it should), or if the publishing process is actually creating uncompressed copies of the data on the server where ArcGIS for Server runs. This could be a huge penalty with something as highly compressed as ECW, even clogging up your entire server's hard disk space.

You should make sure ArcGIS for Server uses the data directly as the ECW format it was stored in, which is the whole purpose of buying the ECW for ArcGIS for Server product.

In case of inadequate performance of the created web service, how does accessing the data directly from ArcMap perform? Are your file servers up to the task of serving this data? There are several other options offered by ArcGIS for Server, most notably though, the ones offering tiling schemes, cutting up your data in small pieces and predefined pyramid zoom levels, to ensure maximum performance. Read the ArcGIS for Server Help pages for the options. Be aware though, that most of these options will require a decompression of the original data and only very limited re-compression to another format compared to ECW. The penalty in file size increase may be unacceptable in some cases.

Re: Best approach to publish heavy images: size and numbers,

nicogis — Fri, 29 Mar 2013 11:26:44 GMT

try and see:
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-026.pdf
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-054.pdf
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-014.pdf
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-058.pdf

I also suggest you evalute http://www.esri.com/software/arcgis/arcgisserver/extensions/image-extension

Re: Best approach to publish heavy images: size and numbers,

JamalNUMAN — Wed, 03 Apr 2013 16:20:27 GMT

try and see:
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-026.pdf
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-054.pdf
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-014.pdf
http://proceedings.esri.com/library/userconf/devsummit13/papers/devsummit-058.pdf

I also suggest you evalute http://www.esri.com/software/arcgis/arcgisserver/extensions/image-extension

Many thanks Marco and Domenico for the help,

Sorry for the confusion! My issue was regarding the performance (speed)

1. The most efficient way to publish such 78 images which are in total around 6GB
2. The performance of the web application that will handle such heavy images

�?� A colleague suggested to collect all these images in one mosaic and then to publish this mosaic! This is much more efficient than publishing them in the mxd file while they are separate! correct?

[ATTACH=CONFIG]23173[/ATTACH], [ATTACH=CONFIG]23174[/ATTACH]

�?� Sure Marco, cashing is one option to enhance the performance of the web application. But the disadvantage is that the user will be limited to some zooming scales!

[ATTACH=CONFIG]23175[/ATTACH]

Bets

Jamal

Re: Best approach to publish heavy images: size and numbers,

AnthonyGiles — Wed, 03 Apr 2013 16:42:28 GMT

Jamal,

The way we publish images is to leave them in there raw format as flat files, calculate statistics and pyramid layers on them (if required). Then create a file geodatabase at the root folder of the images, inside this create a raster catalog (unmanaged) that points to your images.

Put the image catalog in arcmap and then publish to a service. This does not require an image service license and performance is pretty good on images that are around a GB each.

Just remember to use a UNC path to your images so that your server can access them

Regards

Anthony

Re: Best approach to publish heavy images: size and numbers,

JamalNUMAN — Thu, 11 Apr 2013 21:10:05 GMT

Jamal,

The way we publish images is to leave them in there raw format as flat files, calculate statistics and pyramid layers on them (if required). Then create a file geodatabase at the root folder of the images, inside this create a raster catalog (unmanaged) that points to your images.

Put the image catalog in arcmap and then publish to a service. This does not require an image service license and performance is pretty good on images that are around a GB each.

Just remember to use a UNC path to your images so that your server can access them

Regards

Anthony

Many thanks Anthony for the help,

Then what is the asset of the �??raster catalog�?� over the �??raster dataset�?�/�?�mosaic dataset�?�?

[ATTACH=CONFIG]23427[/ATTACH]

Re: Best approach to publish heavy images: size and numbers,

AnthonyGiles — Fri, 12 Apr 2013 04:53:13 GMT

Jamal,

To publish a mosaic data set you need an image server license, where as a raster catalog you don't

Regards

Anthony

Re: Best approach to publish heavy images: size and numbers,

nicogis — Fri, 12 Apr 2013 07:17:21 GMT

these links can help you:
http://resources.arcgis.com/en/help/main/10.1/0154/01540000045v000000.htm
http://resources.arcgis.com/en/help/main/10.1/0154/0154000003z1000000.htm

Re: Best approach to publish heavy images: size and numbers,

JamalNUMAN — Mon, 06 May 2013 19:53:56 GMT

Jamal,

To publish a mosaic data set you need an image server license, where as a raster catalog you don't

Regards

Anthony

Many thanks Anthony and Domenico,

But why adding rasters to catalog dataset takes longer than mosaic dataset particularly when adding like 80 images?

[ATTACH=CONFIG]24083[/ATTACH]

Is there a better practice?