Latest Contributions by PeterBecker

Typically this is an issue with a share and file access in that the server can access the directory that contains the overviews (stored with the geodatabase), but not the primary data. If you say this is not the case here and that any zoom in results in the display disappearing then one possibility is that the Max Size of Request (Cols,Rows) in the default properties has been set too low. Check also the values on the server. Typically the defaults are 4100,15000 which enable requests large enough for the biggest screens and plotting to be allowed, while by default stopping large exports. If these values are set small (eg 1024x1024) then you may get the case where zoomed out the image does not cover the whole screen and is within the limit, but with any zooming the image covers the whole screen and so turns off. ... View more

Note that ECW is a proprietary format.  Access to the format is controlled by Erdas, who put restrictions on the use of the format on any server technology. Erdas provide a for fee extension for ArcGIS Server to enable the serving of ECW files. This essentially licenses a GDAL driver that enables ArcGIS Server to read the format. An alternative is to convert the imagery to map cache. This can be done easily in ArcGIS 10.1 by first creating a mosaic dataset of the different images that you want (No need to create overviews). Then use the DataManagement\TileCache\ManageTileCache tool to generate a map cache. A map cache is also highly compressed although not as compact as ECW. It will generally be about 30% larger for the same quality. Such a map cache can directly be used as a raster within ArcGIS and also easily and very efficiently served through ArcGIS Server (Create a map based on a feature class that covers the extent, and use the cache in place of the map cache). Alternatively map cache can also be packaged and then shared and published through ArcGIS Online. ... View more

Larry There should be not issue creating thumbnails. Note that thumbnails are only compressed RGB rendering of the imagery to which not analysis etc can be performed. They are only used in aspects such as metadata and not drawn directly to the map as one can not apply different enhancements, band combination etc. If you create a mosaic dataset you can always see the footprints and the mosaic dataset acts as a catalog of all the imagery. The images are displayed based on the MinPS and MaxPS values. (This ensures that by default the system does not try to load too many images). Within ArcGIS for Desktop,  if you select the required images and use �??Lock to Selected Rasters�?? or �??Add Selected Rasters to Map�?? then the images will he displayed at all scales, but still enable different renderings. If you look at the item description of any of the rasters you will see the thumbnail if created. Within WebMaps the functionality is similar. Again the app can display any of the images along with the footprints but also including the processing. For a typical example see http://landsatlook.usgs.gov/  (This did not require the creation of Thumbnails. Note aspects such as image enhancement work at all scales). Web maps can though also display thumbnails for the imagery included with the metadata. The Image Search Functionality in 10.2 will enable similar functionality to find images, display footprints etc within ArcMap, by crawling and cataloging the different imagery repositories. This is advantageous for repositories of imagery that are not structured and often used prior to creating more structured mosaic datasets. ... View more

Larry Mosaic Dataset do support these features. You can have the system generate thumbnails for all images in a mosaic dataset. The REST APIs enable one to access these and do a wide range of structured queries to return appropriate imagery and footprints. Different applications have been created to make use of this capability. Note that in 10.2 there is also an image indexing search capability added to ArcGIS Desktop. This enables catalog to search and index images on different local and network drives as well as mosaic datasets and items within mosaic datasets. Through the standard ArcGIS desktop search tools you can then search and find image and raster datasets based on location and a wide range of attributes. The system not only reads the images, but interprets the various metadata such as cloud cover, sun angle etc that are part of the wide range of different metadata standards. ... View more

10.2 will support both Pleiades 1A and 1B as well as SPOT6 products. As with 10.1 RPCs are directly supported and georeferencing can be refined using the georeferencing tools in which control points can be used. ... View more

If you want None then set the MosaicDataset Property - Source Types to Processed. In this case desktop will not apply a stretch to the service by default. If you want uses to have the option to select a range of different enhancement and have something else as a default then use Raster Function Templates (available in 10.1) that enable a range of functions to be associated with a published image service. You can define a default function to be applied. AS above set the Source Type as Processed to stop Desktop from applying an additional stretch. Alternatively in ArcMap Options,Raster, Raster Layer there are options to control custom rendering defaults. ... View more

The suggest workflow is: Create for each years (or subset) worth of imagery a mosaic dataset (will call this the source mosaic dataset) In each source mosaic dataset create suitable overviews and apply any required enhancements clipping etc to remove areas of NoData Add a field (say YEAR) to each of the source Mosaic datasets and use calculate to fill the appropriate value. (Include the overviews) Do any required QC for each source mosaic dataset and ensure imagery is displayed at all scales Create a new Derived Mosaic Dataset Use the 'Table' Raster type and point to the Source Mosaic Dataset.   ENSURE THAT YOU TURN OFF 'Update Cell Size Ranges' (Else the system will combine all image based on scales) (Note in versions before 10.0, the MinPS,MaxPS fields were not copied across so it was necessary to create in the source mosaic datasets a _MinPS and _MaxPS fields. Then after adding to the Derived Mosaic Dataset using calculate to set the MinPS and MaxPS back to the _MinPS and _MaxPS values) Set the appropriate properties for the Mosaic Dataset including:    Allowed Compression methods (set JPEG 80 as default)    Allowed Mosaic Method (Set to ByAttribute, Year, and put a base value in the future  (eg 2050)    Always Clip the Raster to its Footprints - Yes       Footprints may contain NoData - No    (These last two enable the system to optimize by geometrically clipping the data vs looking for NoData     Use Time - Yes     Start Time Field - YEAR     End Time Field -YEAR In Properties/Index add YEAR as an indexed field (just for to aid performance) Depending on the overlap of the imagery, you may want to create a new overview, but force the system to create overviews only at a very small scale (Put BasePixel size as say width of the Mosaic Dataset/5000). This is only to help ensure that when zooming to extent the system does not need to open too many different years of overlapping imagery. You will now find the you can use the different time sliders as well as tools such as timeliner available on the resource Center. In the above example I was using YEAR which is quite coarse. You could instead. If you have finer details on the dates of the imagery use say AcquisitonDate as a Date field. If each of the images has a range of dates then you can also define say StartDate, EndDate and set the Time properties appropriately. ... View more

Using STL is one option, but I would recommend in stead that you create a reference mosaic dataset. I the reference Mosaic Dataset do to the functions then add any required colormap or color ramp. Prior to setting a color ramp you may want to include a stretch to bring say 32bit float value to a range 0-255. Also after applying a colormap it is advisable to add the colormap to RGB Function. The resulting service will provide an RGB rendered map back to the client. As with other service consider the most appropriate default compression to transmit the data back to the client. If using the ArcGIS web APIs then one can instead create a collection of such functions as part of the service and the client applications can select the required functions and define additional parameters as well. For performance also consider how best to transmit the imagery to the client application. If the resulting image is discrete then use LZW (or PNG) while if the data is continuous and does not have NoData areas then JPEG will provide much better compression. ... View more

Statistics are primarily required to enable the system to better display that data especially when the imagery is 16bit or 32bit. When they are not being used for specific analysis, approximate values are sufficient. When creating statistics of a mosaic dataset that has overviews then the simplest is to set the skipfactor to a sufficiently large value so that only a representative number of samples are used. In many cases the simplest way to do this is set skip factor to the total width of the mosaic dataset / 1000. This will then compute very fast based on the overviews, but contain only approx values. If the mosaic dataset contains a lot of no data areas you may want to set the processing extents to a suitable sample area first. The alternative in V10.1 is to use the 'Data Management Tools/Raster/Raster Properties/Set Raster Properties' tool just set the stats to known values. This takes as input an XML file that defines the stats. Such XML files can be created by using the Save As XML option in the Symbology tab of any raster layer. Then if necessary edit the values. For example in elevation for the complete globe simplest is to set the Min as -450 and max as 8700 with a mean of 400. ... View more

See   http://resources.arcgis.com/en/help/rest/apiref/isadd.html The location where the raters get stored on the server are defined as part of the Image Service properties. ... View more

To make requests using Python you need to 1. use the soap url (without �??rest/�?�) 2. Make image server layer 3. Use the imageserverlayer as input see the following blog post on getting a geoprocessing service to work with image services: http://blogs.esri.com/esri/arcgis/2011/02/01/designing-a-geoprocessing-service-to-work-with-image-service-part-one/ ... View more

Yes you can include a wide range of attributes in a mosaic dataset and then control what is returned using them. In the mosaic dataset you can add additional fields, just like you add fields to a feature class. In the Properties of the Mosaic Dataset then ensure these fields are included in the 'Allowed' list. When you publish the service you will then see these fields listed in the Service Directory. There a various ways you can then interact with the fields. You can define a query to get all the attribute information and also use 'where' clauses and/or mosaic methods in the Export. As an example specifically for this being done with elevation data. Look at the WoldElevation Services. You will need to register to the WorldElevation Group on ArcGIS online, which will then give you access. In the group there is a silverlight application that show how images services can be queried and locked to specific rasters if required. These services link to elevation.arcgisonline.com/arcgis/rest/services. Using REST, queries can be made to the service to get attribute information. You can use the to define 'Where' clauses as well as using the 'ByAttribute' Mosaic method to have the imagery ordered by specific fields.  On larger mosaic dataset be sure to Index fields that you intend to query frequently on. ... View more

Dan Its not clear to me what you mean by time for the first image displayed. If the service has not been used for a while, then the very first request may take longer, due to a number of system and software components that may need to get reset. What is the time for subsequent pan/zoom at different scales? If the app in initiated with a zoomed in area vs overview, is the performance different? I think there are a number of different things going on. Structure of the original data- You mention that tiling is None. This is an indication that the original data is not tiled. Tiling the imagery can have a significant positive effect on the performance especially on slower disk systems. If the data is not tiled and the width (in columns) is large then the disk need to do a lot of reading to read even a small part of the disk. Tiling the source will often increase the performance Disk Subsystem - The performance of the disk system can have a substantial effect on total performance. Is the current data running on an external SAN or similar. If possible copy some of the data to a local storage and see if the performance changes. NoData - Please check on the setting of NoData on the imagery. What type of imagery is being served. Does it need NoData. If no data is set then additional processing is required to check for NoData and find pixels to fill in those areas. With 10.1 there are specific properties of the Mosaic Dataset that define how NoData should be handled. If your data has large borders of NoData then is is also very advantageous to rebuild the footprints to exclude NoData areas. ... View more

The difference in the coordinate system is not the issue. The coordinate conversion does have an influence on performance, but it generally not so large to warrant converting it. Most likely is the issue is related to pixel size ranges. You had mentioned that you have two mosaic datasets. One of NAIP imagery with overviews and another of Local imagery without overviews. Please check if both of these on their own perform as required. Note that the projection of the Mosaic Datasets is only the default projection. Client applications specify the required projection. Is you are using a Flex app and the base map is in WebMercator then the imagery from the image service will also be requested in WebMeractor and the server will perform the required conversion. Please check the performance of each Mosaic Dataset as a service separately. For the local service no imagery will be displayed till you zoom in. Now when you create the derived Mosaic dataset and load into it the NAIP and Loca lMosaic dataset, ensure that cell sizes are not recomputed. It is possible that they have been recomputed and the display range of the Local imagery has been changed such that they now get displayed at small scale an as a result a lot of separate image need to be loaded slowing down the initial zoom. Not also that the first time you connect to a service is may be slower as the server may suspend the service if it is not used. When starting up again it may take a while to get up to speed. Is the speed issue you are having there after the initial start up image? ... View more

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. ... View more