Latest Contributions by PeterBecker

This issue is that the imagery is 16bit an it appears that you have not specified any stretch. By default with no stretch being specified the display is stretching all 65535 to 256 values and so since the image has about 4096 (12bit) values the image appears dark. You need to either when you are adding the imagery define a stretch, compute stats for the services (in which case the system will by default stretch when adding to ArcMap) else in ArcMap go to the layer properties and set the stretch to say Standard Deviation based on current display extent. ... View more

Yes time, date or any other attributes can be queried and returned to the client application. You need to create a new fields in the attribute (Footprint) table. This then needs to be filled with the correct values. Some of the raster types will automatically add fields such as acquisition data if available in the metadata. In the Mosaic Dataset properties, Defaults, Catalog Properties, Allowed Fields you need to ensure that the field is selected and so will be transmitted to the client applications. Specifically for Time support you can in the same properties page define the StartTimeField and EndTimeField (can be the same), which is then used by the time series tools. ... View more

�?mer The issue in this case is probably that you are using ECW. See below Generally first ensure that the mosaic datasets works. It is not clear to me in what you wrote whether that is the case. Create the mosaic dataset of your datasources, ensure all works as required and do any required QC. For large areas with NoData I would recommend that you modify the footprint around the datasets to exclude the non wanted areas This works better then setting 0 as Nodata especially for imagery that is lossy compressed. If setting 0 to NoData you may end up with no data areas in say shadows, where lossy compression may set some other values to 0. Using No data will also result in artifacts at the edges as data near the edge may not be 0 exactly. Once the Mosaic dataset works you can then publish it. Ensure though that that the server has access to the imagery. The issue with serving as an image service in this case will be ECW files. ECW is a proprietary format with a number of restrictions on use of the libraries used to read the format. The licensing by Erdas does not allow a server product to serve ECW images without an additional license from Erdas. To server ECW files you need to either get special license from Erdas else convert the imagery into other formats for example TIF (BigTIF with YCBCR JPEG compression) will give you images that are a about 50% bigger than the ECW files for the same quality. Performance of TIF with JPEG compression is very  good. There is a �??Compress Imagery�?� tool in the Imagery Samples gallery of the resource center (http://resources.arcgis.com/gallery/file/image-management)  that you may find very useful. ... View more

Yes this can be done. When an Image Service (or Mosaic Dataset) is added to ArcMap it can be queried and searched. Users can make selection sets and by right clicking on the Image Service Layer and clicking on table open, they can view a table of the selection with associated attributes and refine the selection. IE user can easily select a range of raster datasets. If Downloading is enabled on the service then when users rightclick on the Service Layer, Download, Download selected rasters they can download the selected rasters. Either the complete raster or a clipped subset can be downloaded. This will optionally clip and download the individual rasters, without any resampling of the data. Exporting is a bit different in that the server resamples (eg projects) and mosaicks together the imagery into a single raster. A user could export the imagery for different years by first locking the service to each specific year in tern and for each using Data, Export. The imagery can be locked to a specific year by using the lock raster feature. (Right Click on the service layer, Selection, Lock to Selected Rasters.) Alternatively create new layers for each of the selected rasters (Right Click on the service layer, Selection, Add Selected Rasters to Map). Each raster would need to be exported separately. The same functionally can be implemented in web applications as all the required functionality is exposed through the REST and SOAP APIs. ... View more

After the data has been added, the system attempts to get information about resulting #band/bit depth by making a request to one of the images. In this case the one referenced in 11122209021968000000.RPDef. It seams that the system can not open the file. It should not need write access, but it is possibly trying to create a lock file and being denied. I would recommend: 1 -Check opening the file in ArcMap to see that there is an issue with that fie 2- Copy some of these files locally and try to see if that works. If it does then its probably some locking issue. Note that the ISDef that was created may still be valid even if this state failed. The issue may be that some stats are incorrect. Try opening the ISDef created and doing a build. The real recommendation though would be to use Mosaic Datasets in Version 10 instead. Especially with elevation data you will find the workflows much easier and more efficient. As an example of what can be created have a look at the World Elevation Services See http://www.esri.com/worldelevation. Details of how to build such services are also provided inhttp://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Part_1_About_elevation_data/009t0000023w000000/ ... View more

First of all I would generally not recommend the generation of RRD files. Some users still do for backward compatibility. In ArcGIS 10.0 the default method to create pyramids in ArcGIS was changed to using .OVR files. They were also supported in older 9.3 based Image Server. (I mention this as I�??m assuming that you may be still using this as you mention ISCommands). OVR files are actually TIF files with internal pyramids. They are given the same name as the original file but with the additional .ovr extension. The advantage is that they are fast to read and also enable different compression methods. You can create pyramids that are compressed even if the source data is not compressed. The other alternative is to use internal pyramids in the original files. This reduces the number of files and is backward compatible with older versions of most sw that does not support .ovr files, but its harder to remove the pyramids later, should you want to remove it.. I�??ll indicate how create internal pyramids below. There are four ways you can create pyramids for large collections of rasters: 1) In ArcGIS use the �??DataManagement/Raster/RasterProperties/Build Pyramids And Statistics�?� tool. (available in 10.0). This enables the definition of a workspace and will optionally traverse all subdirectories and generate pyramids and statistics for each raster. This was designed specifically to do what you want to do. Ensure you set the Raster Storage Environmental Variables to define the required resampling and compression options. 2)  Create a python script to run the BuildPyramids_management function. This is documented with samples in the help system. 3) There is a �??Compress Imagery�?� tool in the Imagery samples gallery of the Resource Center. See http://resources.arcgis.com/gallery/file/image-management/details?entryID=BCB3B8AB-1422-2418-3411-530474DD4825 This is a python processing tool that can be used to compress imagery using GDALTranslate and GDALaddo and includes options for creating pyramids. It can be easily modified to only create the pyramids and you will see internally it uses GDALAddo. 3) Create your own batch file to generate pyramids using the GDALAddo command (available from FWTools.maptools.org). The command line is: gdaladdo.exe -r average -ro --config COMPRESS_OVERVIEW QQQQ --config USE_RRD NO --config JPEG_QUALITY 80 --config TILED YES --config PHOTOMETRIC_OVERVIEW RGB output.tif 2 4 8 16 You need to set appropriate parameters for QQQQ (NONE,JPEG,LZW); Refine or remove the JPEG_Quality parameters. The PHOTOMETRIC_OVERVIEW parameter depends on the type of imagery. If using natural color set to YCRCB else set to RGB. If you want to create internal pyramids remove the �??ro flag. If you want to create RRD files, set USE_RRD YES Similar to GDALAddo, there is a GDALTranslate command that can be used to convert and potentially optimize the files eg by ensuring they are tile and compressing using JPEG or LZW compression. ... View more

Each image services defines its extent. The extent show initially by an application is defined by the applicaitons. For example in WebMaps you can define the initial extent. The extent of the sources are used only as the defaults for the apps. ... View more

Grids contains internal Pyramids. Leave these as they are. If you do convert the data to TIF then create pyramids for larger files. These can be RRD files (but do not compress well), Internal overviews or at 10.0 we have defaulted to using .OVR files (these are actually a lower resolution TIF file with internal pyramids) ... View more

>1) Do I need to reformat the DEM (or preprocess/prepare the DEM in any way) or can I go straight to the step of creating the image service definition. You can directly use the grid data and add it to an Image Service Definition (ISDef). I would generally recommend converting the data to TIF (either 16bit signed or 32bit float) with LZW compression and then create pyramids. As you are using 9.3.1 directly it is better to create internal pyramids or RRDs. At 10.0 I would recommend creating pyramids OVRs (or internal). Although Grid files are supported, the performance of TIF can be better especially when serving to multiple users simultaneously. If you are primarily using Desktop, I would recommend that you keep the existing files and possibly convert later to TIF when you transition to 10.0 or 10.1 and are looking to serve the data. If you do convert the data, ensure that the data is not re-projected in the process as an type of sampling will always negatively affect the accuracy of the data. >2) Given that I am just utilizing the images in ArcGIS Desktop does ArcGIS Server even come in to the equation? If you are just using in Desktop then you can directly use the Image Service Definition editor that will provide quick access to collection of elevation data. To use the Image Service Definition editor requires a license of the Image Extension for ArcGIS Server, so it would make more sense to create the ISDef and then serve it as an image service. I would strongly suggest that you look to upgrading to 10.0 (or 10.1 Beta2) and use Mosaic Datasets instead. These have replaced Image Service Definitions. Mosaic Datasets are a similar concept to ISDefs, but are more more capable, integrated and scale better. Mosaic Datasets are a a core component of ArcGIS Desktop at 10.0. They can be created with ArcGIS Desktop (Editor or Info License) and can be used with all ArcGIS Desktop application. This enables them to be used in a local or work group setting directly as well as served as image service through ArcGIS Server and the Image Extension. You will find it much easier to create mosaic datasets of a wide range of different image and rasters. There are a number of workflows the detail how best to create Mosaic Datasets and Image Services from elevation data (see http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Part_1_About_elevation_data/009t0000023w000000/) Also review the World Elevation Services that are currently (as of 15th Nov 2011) in Beta. See http://www.esri.com/worldelevation. These services provide direct access to a wide range of multi-source, multi-resolution elevation data and derived products. These can be directly used in a range of applications including 9.3 desktop. Similar Mosaic Datasets can be create using using your own data with ArcGIS 10.0 and then if required served as a range of image services. ... View more

Are you sure the Service Startup is defines as Automatic in the Service Properties ... View more

The issue may be related to the definition of the projection within the rasters. It may be that the datum in the raster is not defined such that it is recognized. I got the same issue with some rasters that had DHDN defined internally. This was resolve by defining the specific projection when the rasters are added. In the AddRasters use Advanced Options, Coordinate System for Input Data, then select National Grids, Germany and the appropriate projection. I tried is out by defining the mosaic dataset in Web Mercator as well as defining it in the DHDN and it worked. ... View more

The issue you are seeing with the apparent shifts are most probably related to the definition of the datum transform. When using data with different transforms (eg Potsdam DHDN-WGS84) you need to define the transform to use as part of the Mosaic Dataset. If you look at the Mosaic Dataset|Properties/Defaults you will see a transforms section. You need to define all the transforms that you with to use with the Mosaic Dataset here.  This is required as access to image can involve multiple transforms (eg client in UTM, Mosaic Dataset Defined in UTM Clark and source in DHDN). If not defined then defaults will be used, but these may not be suitable. In the older Image Server (using ISDefs) this was also handled by using a Datums.dat file. Concerning caching. If the data is just a set of tiles then one solution is to create a Mosaic Dataset and create the required overviews (all in the original projection). Then create the original files and overviews set of Raster Catalogs (1 for each pixel range). The Raster Catalogs can be added to a MXD document (set scales for different layers) and then cached. The simpler solution is to have the image extension. Then you add the Mosaic Dataset to a blank MXD and cache. (Note its is always recommended to keep the images in a separate cache as the vectors. This way you can use JPEG for the images and PNG for the vectors). ... View more

It is most likely what you are see is the effect of statistics having being computed on the datasets and then stretch being applied. When you add a raster dataset to ArcMap, if statistics have been previously computed and included with the dataset, then ArcGIS by default applies a 2 standard deviation stretch renderer to the imagery. This has the effect of increasing the contrast of the imagery and for many 16bit datasets results in the data being visible vs seeing near black. This stretch can be turned off for a specific layer by going to the layer properties and changing the stretch to None. Alternatively if by default you do not want a stretch to be applied when adding imagery,then go to Customize, ArcMap Options, /Raster/, Stretch type and set this to None. When you add a raster to a mosaic dataset a stretch by default is not applied to each individual raster. As a result it may appear to be darker. Multiple images may be added to a mosaic dataset and in many cases you do not want each image to have a separate stretch applied. When overviews for a service are built the system computes statistics for the complete mosaic dataset. When this mosaic dataset is then added to ArcMap either directly or via an Image service, ArcMap will again apply a default stretch. A typical example of where this of most use is when say adding multiple elevation datasets. IE the data is NonProcessed and by default you want ArcGIS to apply a stretch renderer to the complete mosaic dataset when is is added for display, so that the data can be seen. If you do not ArcMap to add a stretch based on the statistics of a Mosaic Dataset then you can set MosaicDataset Properties, /Defaults/, Is Preprocessed Data to Yes. IE the mosaic dataset includes images that have already been processed and so no additional stretch should be applied. Typically this would be used when creating a mosaic dataset of pre-processed imagery or when the mosaic dataset includes processes to color correct imagery. If you have a case where you have a set of images and you want each to be stretched individually in the Mosaic Dataset there are two options: 1 - When Adding the Raster Datasets to the mosaic dataset, click on the Raster Type properties button and change the Processing Template to 'Stretch'. The type of stretch can be changed by going to the Functions tab and opening the Stretch\StretchFunction item that details the stretch to be applied to each image when added. 2 - If the data is already added, then use the 'Batch Edit Raster Functions' (Accessible by making a selection set of the rasters and then right click on the Footprints, Selection, Batch Edit Raster Functions). This will enable you to 'Insert' a function into the process chain of each raster. In this case you would probably want to add the 'Stretch' function with Standard Deviation stretch. Note that when adding a stretch you can also define the bit depth of the output. Keep in consideration what the bit depth of the mosaic dataset is. You may want to specifically define the mosaic dataset as 8bit when you create it. Doing either 1 or 2 above and then setting Is Preprocessed to Yes would result in you seeing the same result as if you had added each raster individually to ArcMap with the default stretch being applied. ... View more

With ArcGIS10 you do not need to install anything on the desktop to use the Image Extension. The Image Extension is the capability for ArcGIS Server to serve Mosaic Datasets. These allow large collections of imagery to be served as image services with the server performing any required dynamic mosaicking and on-the-fly processing. The ArcEditor license for ArcGIS Desktop is sufficient to be able to create MosaicDataset. For help look to the "What is a mosaic dataset?" section in the help. This will show you how to create mosaic datasets using the tools available in ArcToolbox: DataManagement\Raster\MosaicDataset You should find that you can quickly created mosaic datasets of your image collections. Mosaic Datasets can be directly accessed using ArcGIS Desktop. This enables other users to easily access the image collections in a workgroup type environment. Mosaic Datasets can be served as image services (which requires the image extension) to make the imagery quickly accessible to large numbers of users on the web. In ArcGIS 10, the Image Service Definition Editor is a set of tools to provide backward compatibility for the 9.3 versions of Image Server that used ISDef files. It requires a separate install and license. It is only required by users that have created workflows in 9.3 based on ISDef files and wish to use them at V10 of ArcGIS. From your description it appear that you have not used ISDef files in the past, so I would recommend only using Mosaic Datasets which are even more capable. ... View more

With ArcGIS10 you do not need to install anything on the desktop to use the Image Extension. The Image Extension is the capability for ArcGIS Server to serve Mosaic Datasets. These allow large collections of imagery to be served as image services with the server performing any required dynamic mosaicking and on-the-fly processing. The ArcEditor license for ArcGIS Desktop is sufficient to be able to create MosaicDataset. For help look to the "What is a mosaic dataset?" section in the help. This will show you how to create mosaic datasets using the tools available in ArcToolbox: DataManagement\Raster\MosaicDataset You should find that you can quickly created mosaic datasets of your image collections. Mosaic Datasets can be directly accessed using ArcGIS Desktop. This enables other users to easily access the image collections in a workgroup type environment. Mosaic Datasets can be served as image services (which requires the image extension) to make the imagery quickly accessible to large  numbers of users on the web. In ArcGIS 10, the Image Service Definition Editor is a set of tools to provide backward compatibility for the 9.3 versions of Image Server that used ISDef files. It requires a separate install and license. It is only required by users that have created workflows in 9.3 based on ISDef files and wish to use them at V10 of ArcGIS. From your description it appear that you have not used ISDef files in the past, so I would recommend only using Mosaic Datasets which are even more capable. ... View more