Windows 7 Home Basic Key ArcGIS Server Blog Achi

[henane123]

Welcome to ESRI Blogs
Indicator in Be part of Electronic mail


In your ArcGIS Server application you may have purpose to work with adjacent map and image providers. This is most typically happens when you wish to exhibit your authoritative information for the modest area even though making use of a general public services (ArcGIS On the web, Bing Maps, or Google Maps) for the encompassing region. This really is extremely widespread when viewing your providers in ArcGIS Explorer. By way of example,Office 2007, you may have current aerial photography for your location,Windows 7 Home Premium Product Key, so you want to mix it with all the basemap imagery offered in ArcGIS Explorer. This can present a challenge due to the fact your service might incorporate a white collar around the map. The discussion below focuses regarding how to remove this white collar for different services configurations.
Dynamic map solutions
The illustration below is actually a dynamic map service containing aerial photography for Jefferson County, Kentucky proven in ArcGIS Explorer.



With this dynamic map support, ArcGIS Explorer is requesting a JPEG image simply because the service contains so many colors. Since JPEG does not support transparency, you get a white collar around the picture. To clip the white region out of a map service for the desktop clients (ArcMap, ArcGIS Explorer, etc.), simply create a feature class that represents the boundary of your knowledge. Then you can use the Information Frame Clipping capability as described below.
In the ArcMap table of contents, right-click the information frame and click Properties. Click the Data Frame tab and then check Enable under Clip to Shape.
Choose Outline of Features and choose your boundary layer.
Click OK to all the dialogs.
After updating your map document you need to restart your map service for the changes to take effect. Then the map support will exhibit in ArcMap or ArcGIS Explorer nicely without a collar as in the instance under.

Image providers
When dealing with image solutions you could run into the same white collar around your picture. In this case the boundary feature and footprint features need to be clipped to the exact boundary of your imagery. Again, a feature class made up of the exact boundary of your imagery would be very useful. You could replace the default boundary feature with your boundary feature and then clip all the footprints to the new boundary. Simply start an edit session, delete the existing boundary and copy and paste your existing boundary into the boundary feature class. After you save your edits and stop editing, right-click on the Footprint layer and click Recompute Footprint > By Clipping to Boundary. You can read about the many other ways to adjust image service footprints in the on the web help.
NoData and Web APIs/ADFs
The above two approaches for dynamic map services and images solutions use a boundary feature to differentiate between info and NoData. Any areas outside of the boundary features are NoData. The desktop clients like ArcMap and ArcGIS Explorer don’t render the NoData values. However, all of the Web APIs (JavaScript, Flex, Silverlight) and ADFs (.Net and Java) do render the NoData values as white if the requested picture does not support transparency.

In the aerial photography illustration above,Windows 7 Home Basic Key, the Web software should request a JPEG image to preserve appropriate quality. Since JPEG does not support transparency, this image could not be used with another basemap support. In cases where a PNG image would perform, the white collar will not show, but PNG should only be used with companies that contain fewer colors than an aerial photo.

Since your basemaps should be cached anyway for Web applications, the dialogue below dealing with cached map companies is more appropriate for Web software basemaps.
Cached map companies that use JPG tiles
Cached map solutions can produce an even larger white collar, as the illustration beneath illustrates.


This is actually a cached map services making use of JPEG image format. As has been discussed in another post, JPEG is by far the best picture format for cached map companies that contain aerial photography to be used in a Web software. You can see in this example that the cached map service doesn't operate all that well in ArcGIS Explorer. The larger white boundary is from the empty cache tiles around the map. Since the JPEG image format does not allow for transparency, you get a white collar. There is nothing you can do to get rid of this white collar in ArcGIS Explorer, ArcMap, or any of the Web ADFs or APIs. To mitigate this problem with JPEG services in ArcGIS Desktop or ArcGIS Explorer you have three options:
Use layer files to control the visibility of the map service Incorporate the bordering info inside your map cache Provide a second dynamic map services for desktop clients Making use of layer files to control the visibility of the map support
Using a layer file, you can use scale dependent rendering to make sure the layer only turns on when zoomed way in. To do this follow these steps.
Add the cached map support to ArcMap Zoom in on the knowledge until you can start to see reasonable amounts of detail (that wouldn't otherwise be in ArcGIS Online or Bing maps). Right-click on the layer and click Zoom to Nearest Cache Resolution. This ensures your layer visibility corresponds to your cache tile level. Open the properties for your layer and set the minimum scale to your current scale. Right-click the layer and click Save As Layer Package.
Now you can share the layer file with all of your desktop users. The white collar will still be visible, but only when zoomed way in. At this larger scale, your users will likely be more interested inside your map support than the bordering data.
Including the surrounding knowledge in your map cache
The second option of adding encompassing data to your map cache can also improve the usability of the support by your desktop clients. This will be done for that smaller scales of your map cache with little overall impact to the total size of your cache tiles. For more on map caching see the on-line help. This does mitigate the problem but essentially you have pushed the problem further away from your study location.
Providing a second dynamic map support for desktop clients
The third option is to use two services: a cached map services for the Web applications, and a dynamic map service for ones ArcMap and ArcGIS Explorer users. If you are working with imagery like that in this instance, an image services would be preferred to the dynamic map service. Since ArcMap and ArcGIS Explorer have local caching capabilities after the first time an location is drawn, a dynamic image service would likely perform really well. To make this easily consumable by your desktop clients you could simply share a layer file pointing to the picture support for those users. You should also set the minimum scale in the layer as described above to control the number of dynamic requests and only show your basemap when appropriate.
Cached map solutions that use PNG tiles
Cached map services that use PNG do not exhibit a collar because PNG supports transparency. This is a good solution for StreetMap-type basemaps, which can use PNG 8 or 32 (you should never use PNG 24 due to IE 6 limitations). Under is really a cached streets basemap services that uses PNG32.


PNG is an acceptable choice in this instance simply because it maintains crisp lines and text whilst still keeping the file size low. If this map contained a lot of gradient fills and other shading affects,microsoft Office 2010 Activation, JPEG with compression quality 90 would be a better choice. Utilizing JPEG would mean the services would not be really useful with other basemaps but it would give you the best performance and quality in a Web application.

Warning! Be extremely careful when employing PNG 32 for the basemap services. As the number of colors increase, so does the file size. Utilizing PNG 32 for aerial photography, for instance, can result in tiles being approximately ten times larger than the same service cached making use of JPEG. If the tiles are ten times larger, then the map will be ten times slower. Utilizing an picture format like JPEG 90 would give more consistently sized tiles for all scales,Office 2010 Keygen, whereas PNG 32 would have much larger tiles at the modest scales but smaller tiles at the large scales. The best approach is to build a test cache and validate that all scales have acceptable tile sizes.
Summary
With dynamic map services and picture providers you can easily clip the imagery to the extent of your knowledge allowing you to mix multiple adjacent basemaps with your desktop applications like ArcMap or ArcGIS Explorer. You will still have the problem of getting the base maps to look similar in a single software but the published map templates should help in this region. With cached map providers that use JPEG tiles you should consider maintaining two providers: the JPEG cache and a dynamic map or image service. The JPEG cache would be used in web applications and the dynamic services would be used in desktop applications like ArcMap or ArcGIS Explorer. Cached map service that use PNG operate very nicely for integrating multiple adjacent services but should not be used as an "ultimate" solution as JPEG caches can be much more efficient for map services with high color variation.

Contributed by Tom Brenneman of the ESRI Technical Sales team.