Select to view content in your preferred language

The estimated cache size (739 MB) is greater than 500MB,

5211
4
Jump to solution
05-31-2013 10:35 PM
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

The estimated cache size (739 MB) is greater than 500MB,

As I tried to cache a map with two scales (5000 and 1000) I got the message below:

[ATTACH=CONFIG]24883[/ATTACH]

What might this indicate for? Why the comparisons made with 500MB? What might the 500MB be?

Scenario:
Given a map 130km X66km which is required to be cached based on two scales (5000 and 1000) then how the following items can be calculated:

1. Time (based on the CPU/RAM/Video Card)
2. Number of tiles
3. Size on the hard drive

[ATTACH=CONFIG]24884[/ATTACH], [ATTACH=CONFIG]24885[/ATTACH], [ATTACH=CONFIG]24886[/ATTACH]

The data is attached

Thank you

Best

Jamal
0 Kudos
1 Solution

Accepted Solutions
AlexeyTereshenkov
Deactivated User
Jamal,

When publishing a cached service, ArcGIS returns a warning message box when the estimated cache exceeds a given size. The 500MB you see is a default value which ArcMap sharing settings have been set for. This value is just something to make you aware of when you start caching perhaps because you have not planned to cache the map in all scales but forgot to deselect the certain ones. This value can be accessed from the ArcMap > Customize menu > Sharing tab.
You can change the threshold for the warning by entering a new size. If you do not want the warning message to appear, uncheck Show warning when cache exceeds.

The Estimated Cache Size estimate, displayed on the Caching tab of the Service Editor dialog box, is a very rough approximation based on average tile sizes for the image format you chose and the number of tiles expected in your cache. The estimate assumes a vector map for non-JPEG image formats and raster imagery for JPEG and MIXED formats. For JPEG and MIXED formats, the estimate assumes a compression quality of 75. Some deviation of the cache size is acceptable and this is something you should be aware of, so what you've shown on the screenshot is not wrong (several MBs difference is a very good estimation for ~800MB cache).

When deriving estimates when your area of interest is a feature class, it???s important to note that the estimates only reflect rectangular map extents. If you specified a feature class as the area of interest for your cache, the estimate is based on the rectangular bounding box of each polygon in the feature class, not the exact feature class boundary. If you're going to cache an irregularly-shaped geographic feature, you may get a more accurate estimate by clipping a grid to the boundary of your feature class, effectively breaking up your feature into large grid cells. You can use the Create Fishnet tool to make a grid.

View solution in original post

0 Kudos
4 Replies
AlexeyTereshenkov
Deactivated User
Jamal,

When publishing a cached service, ArcGIS returns a warning message box when the estimated cache exceeds a given size. The 500MB you see is a default value which ArcMap sharing settings have been set for. This value is just something to make you aware of when you start caching perhaps because you have not planned to cache the map in all scales but forgot to deselect the certain ones. This value can be accessed from the ArcMap > Customize menu > Sharing tab.
You can change the threshold for the warning by entering a new size. If you do not want the warning message to appear, uncheck Show warning when cache exceeds.

The Estimated Cache Size estimate, displayed on the Caching tab of the Service Editor dialog box, is a very rough approximation based on average tile sizes for the image format you chose and the number of tiles expected in your cache. The estimate assumes a vector map for non-JPEG image formats and raster imagery for JPEG and MIXED formats. For JPEG and MIXED formats, the estimate assumes a compression quality of 75. Some deviation of the cache size is acceptable and this is something you should be aware of, so what you've shown on the screenshot is not wrong (several MBs difference is a very good estimation for ~800MB cache).

When deriving estimates when your area of interest is a feature class, it???s important to note that the estimates only reflect rectangular map extents. If you specified a feature class as the area of interest for your cache, the estimate is based on the rectangular bounding box of each polygon in the feature class, not the exact feature class boundary. If you're going to cache an irregularly-shaped geographic feature, you may get a more accurate estimate by clipping a grid to the boundary of your feature class, effectively breaking up your feature into large grid cells. You can use the Create Fishnet tool to make a grid.
0 Kudos
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

Jamal,

When publishing a cached service, ArcGIS returns a warning message box when the estimated cache exceeds a given size. The 500MB you see is a default value which ArcMap sharing settings have been set for. This value is just something to make you aware of when you start caching perhaps because you have not planned to cache the map in all scales but forgot to deselect the certain ones. This value can be accessed from the ArcMap > Customize menu > Sharing tab.
You can change the threshold for the warning by entering a new size. If you do not want the warning message to appear, uncheck Show warning when cache exceeds.

The Estimated Cache Size estimate, displayed on the Caching tab of the Service Editor dialog box, is a very rough approximation based on average tile sizes for the image format you chose and the number of tiles expected in your cache. The estimate assumes a vector map for non-JPEG image formats and raster imagery for JPEG and MIXED formats. For JPEG and MIXED formats, the estimate assumes a compression quality of 75. Some deviation of the cache size is acceptable and this is something you should be aware of, so what you've shown on the screenshot is not wrong (several MBs difference is a very good estimation for ~800MB cache).

When deriving estimates when your area of interest is a feature class, it�??s important to note that the estimates only reflect rectangular map extents. If you specified a feature class as the area of interest for your cache, the estimate is based on the rectangular bounding box of each polygon in the feature class, not the exact feature class boundary. If you're going to cache an irregularly-shaped geographic feature, you may get a more accurate estimate by clipping a grid to the boundary of your feature class, effectively breaking up your feature into large grid cells. You can use the Create Fishnet tool to make a grid.



Thank you very much Alexey for the input. It is more obvious now

I could see that the warning for the cache size is optional

[ATTACH=CONFIG]24975[/ATTACH]

But couldn�??t figure out precisely:

�?� What 75 compression might refer to?

[ATTACH=CONFIG]24976[/ATTACH]


�?� What Fair/good/best estimation quality might indicted for?

[ATTACH=CONFIG]24977[/ATTACH]


Best

Jamal
0 Kudos
AlexeyTereshenkov
Deactivated User
What 75 compression might refer to?


JPEG compression level

�?� What Fair/good/best estimation quality might indicted for?

In principle, how many random cache tiles will be generated in order to give you a rough estimate on what size the cache is likely going to be. Best - more tiles will be generated (more accurate estimate but takes longer time), Fair - less tiles will be generated (less accurate estimate but takes less time).
0 Kudos
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

JPEG compression level


In principle, how many random cache tiles will be generated in order to give you a rough estimate on what size the cache is likely going to be. Best - more tiles will be generated (more accurate estimate but takes longer time), Fair - less tiles will be generated (less accurate estimate but takes less time).



Many thanks Alexey for the elaboration. Now it is clear

Cheers

Jamal
0 Kudos