Latest Contributions by PeterBecker

For both Mosaic Datasets and the older ISDefs, the georeferncing is determined at the point the data is added to the mosaic dataset or ISDef. In both methods you can define if the World file should be used or not. As you are using JPEG images there is no option except to user the world files. Is it possible that the world files have been changed since you added them to the ISDef? It is not clear to me why you are looking for the duplicated .jgw files. The simplest way to find such duplicates is to re-create the ISDef (or mosaic dataset) and see the duplicates. Concerning the pixel values changing: The values will not change if you copy rasters. The issue is potentially that when copying the rasters to another format statistics are being computed and by default ArcMap will stretch images that have stats and so you see different imagery. There is an option in arcmap to turn this off. On a separate note related to file formats. I would generally recommend agains using JPEG images for such imagery unless the images are small (<5MB). The reason is that opening a JPEG file required the complete image to be decoded if the last pixel is to be viewed. On larger images this can slow things down. For larger images it is better to use TIF with JPEG compression. Such files are tiled allowing only parts of the image to be accessed. I would also suggest you look into using the Mosaic Dataset available in V10. This will also provide the ability to quickly catalog the imagery and serve them up. ... View more

There is no 'out of the box' capability currently. An interesting idea thought. Currently in ArcMap you can make a selection set using the selection tool on the required AOI. You can then from Layer,Selection,AddSelectedRastersToMap have each raster added as an individual layer in a group layer. The standard tools to turn layers on/off, swipe etc can then be used. Such capability could be added as a AddiIn relatively easily and then be customized to your exact requirements. Similarly the same can be done through any Web application. There are samples on how to work with selections and then use the LockRaster capability to display only on (or selection) of rasters. ... View more

Is it posisble that you are serving something like Elevaiton data that is >8bit/channel. If so check to add a renderer on the ImageServcies. Also please first check out the following: Samples are under image services folder: http://help.arcgis.com/en/webapi/flex/samples/index.html API reference to the Image Layer http://help.arcgis.com/en/webapi/flex/apiref/com/esri/ags/layers/ArcGISImageServiceLayer.html Here are some links that would help debug: http://help.arcgis.com/en/webapi/flex/help/index.html#references/debugging_tips.htm# http://help.arcgis.com/en/webapi/flex/help/index.html#references/using_crossdomain_xml.htm# http://help.arcgis.com/en/webapi/flex/help/index.html#references/faq.htm# After that bset to review what is being returned using something like Fiddler. ... View more

The ArcGIS Server Image Extension at V10 works on Unix. It is not avialble for 9.3 ... View more

MaxNumer of rasters is a property of both an Image Service Definition and a Mosaic Dataset. When a users pans/zooms, the system needs to mosaic together multiple sources. At large scales this is likely only to be a few images, as the scale increases the number of images can increase quickly. At the smaller scales generally overviews are created or other lower resolution imagery used to remove the requirement to open many files. This parameter stops the system from possibly needing to open thousands of files for a single request. The default value is 20, which is sufficient for most applications. The value can be increased (look in Service Provider or Mosaic Dataset-Default properties). It is generally advisable not to increase it though. Instead look to create overviews at a larger scale (smaller Base Pixel value). There are some valid reasons to increase the value when working for example with large collections of overlapping thumb nail images. ... View more

Yes 9.3 does not have color correction. There does exist a trend capabiltiy in 9.3, but it can be complex to setup. I reocmmened upgrading to V10. ... View more

For clarification this is Image Server 9.3 This could be related to some RPC ports being closed or a DMZ changing IPs. When doing a direct connect to the Server Manager, the server returns the IPs, and Names of the service provider machine(s) that have the required services. It is possible that a DMZ may change the IP address. If this is the case the documentation defines how define an external IP for each service provider. Also check \Documents and Settings\All Users\Application Data\ESRI\Image Server\Logs the log files may provide some other information. ... View more

I presume you are using Image Service Definitions and you are serving an ISDef file. In this case you can open the Reporter (Start,ArcGIS,ImageServer,Reporter). This will display as text all the request being made to the image server, the processing being performed and the errros. Alternatively access service provider logs stored in "\Documents and Settings\All Users\Application Data\ESRI\Image Server\Logs\ServiceProvider". This will detail any errors occurring. By looking at this it is likely that you will find that some of the rasters are not accessible. ... View more

I'd like to use this as an opportunity to answer a common question about best to handle multiple projects such that it is easily accessible. Serving hundreds of different images services is certainly not recommended. Replacing hundreds of image files with hundreds of service end points is not what users want. Most users that connect to images service prefer to have a single endpoint to access all the imagery that is accessible to them and not have to unnecessarily search.  As new imagery is added they get the new imagery without needing to change their applications. They prefer to open an image service, then directly zoom to any area of interest and see the most suitable imagery. �??No questions asked�??. The system should handle all the re-projection, mosaicking of the different sources, etc. �??What is most suitable?�??. In most cases it is the latest highest quality imagery, but some users will have other requirements. With image services the user can query for metadata about the displayed and hidden (overlapped) imagery. The order of the imagery can be changed either by defining a new mosaic rule (e.g. By Attribute closest to a date) or specifically locking the service using a query to a specific set of images. Accessing imagery this way is similar to how in a map you may access a set of overlapping polygons and making use of capabilities that are inherent in a complete GIS. Users can control the selection and ordering as required, similar to queries and views of a database. The aim is to create as few image services as possible. The recommendation is to create image services that are application specific and not data specific. For example, you may create an image service that has all the imagery optimized for visualization and another optimized for image analysis, or an elevation image service with the best available elevations. The aim  is to put all the imagery that is similar into a single ISDef (in V9.3) or Mosaic Dataset in (V10). In theory you can put all your images into a single ISDef or mosaic dataset with associated metadata and then using attributes define the optimum ordering of the imagery. However,this can become impractical, so the optimum solution is to create separated ISDefs or mosaic datasets for each project that can be separately managed and then combine these into the few services to be published. I�??ll briefly describe this method first using mosaic datasets, which is what I recommend using and then how to do something similar using ISDefs for those that do not want to upgrade yet. Mosaic datasets at V10 have replaced ISDefs (used at 9.2 and 9.3) and are the recommended method for image data management. They are more scalable and integrated better with ArcGIS using the geodatabase. They are also easier to query. The creation and editing of mosaic datasets are core to ArcGIS Desktop and no extension is required. (You need an ArcEditor or ArcInfo license to create and edit them but you can use ArcView to use or query them.) You had mentioned �??pre-mosaicked�?? datasets so initially I�??ll assume you have many projects and each project has a potentially thousands of images. For each project you can create a mosaic dataset and add the imagery using the Raster Dataset raster type. Each of these mosaic datasets could be created using the projection suitable for the project or just use one that covers all your projects. You may want to create overviews of each mosaic dataset to enable fast access at small scales. Overviews may not be a requirement if lower resolution imagery for the area exists. I would also recommend you add some standardized attribute fields, such as Year (Integer), Date (Date),  Project (Text), Source (Text), LeafOn (Yes/No) to each of the mosaic dataset. This can be done using geoprocessing tools and ModelBuilder .  Each mosaic dataset can be individually QC checked. Only a small amount of additional data storage is required. Some of these mosaic datasets (or image services if served) could be pan, some 3-band (RGB) and some 4-band (including a near infrared band). You can manage your collections of imagery in each of these mosaic datasets and, as required, easily change things such as add or remove images, change the footprints to clip the imagery, or add different enhancements. You can also create a �??BestVisualImagery�?? mosaic dataset. The projection for this should be suitable to cover all the imagery you will be using. For most users I recommend Web Mercator Auxiliary Sphere, as it covers the whole world and has some advantages for mashups later. Now use the Table raster type and point to each of the project-based mosaic datasets as the source. This will create a derived mosaic dataset that contains the records from each of the project-based mosaic datasets. For this mosaic dataset, set the default Mosaic Method to By Attribute with Field= Year and Base=3000. This will ensure that the latest imagery is displayed on top by default. This is only an example. You could create other fields that provide better default ordering based on your users�?? general requirements. This workflow currently does have a know issue related computing the pixel sizes. If you have overlapping imagery it is often better to use the pixel visibility ranges of the original mosaic dataset. Currently when using a table based raster type the MinPS and MaxPS value are not transferred. If you re-compute them in the BestVisualImagery mosaic dataset then it is possible that with overlapping imagery that the system will exclude some images from different scales as they overlap sufficiently. The way to resolve this is to create two new fields in the project-based mosaic datasets called MinPS_Src, and MaxPS_Src that can calculated as being the same as MinPS and MaxPS within each. Then when adding the projects to the BestVisualImagery mosaic dataset uncheck �??Compute cell sizes�?? on the Add Rasters To Mosaic Dataset tool. Instead of running this calculation, set the MinPS=MinPS_Src and MaxPS=MaxPS_Src. (If you are using different coordinate system units for the different mosaic datasets some factors will need to be included; therefore, it is better to use the same units). You can work with mosaic datasets directly in ArcMap, and serve them as image services to make it accessible to a wider audience. At any time you can update this with new data, properties, etc. A very large range of applications including ArcMap (V9.2 -10), ArcGIS Explorer, Web Apps, and WMS or WCS clients can access these image services. ArcMap, ArcGIS Explorer 1500 and Web Apps can make use of the more advanced capabilities to do things such as changing the compression for transmission, obtaining detailed metadata, and changing the default mosaic methods. For MicroStation users the best way is to use WMS�?? some properties can be controlled by this, but there are no query capabilities. With ArcMap 10 and using Web Apps, users can also define extensive queries and selections to obtain only specific imagery. The advantage of this method is that you can manage each project individually, but easily create and publish a single image service. In a similar manner you can create other image services for analysis-type applications. You had mentioned using TerraShare. I gather from this that you also have frame-based aerial imagery from a DMC camera. If this is the case, you can also use mosaic dataset to orthorectify imagery on-the-fly. The workflow for this is very similar to above, but instead of using the Raster Dataset raster type you would use the ISAT raster type. Terrashare can export ISAT project files that contain all the required parameters for OTF orthorectification. The beauty of this is that you can create such projects very quickly as soon as the imagery is available. Over time you can refine parameters such as orientation and color enhancement. As the parameters are updated you only need to synchronize the mosaic datasets to update them all. If you do create �??certified�?? orthos as part of your production process, these would be added as a project and the OTF projects could be either removed or the images could be marked with a lower priority. So what about V9.3? The same thing can be done, by creating individual ISDefs for each of the projects and then creating a new ISDef in which you add the RPDef Raster type and point to the ISDef directories for each of the projects. The method works, but does not take advantage of the geodatabase capabilities available in V10 mosaic datasets. I would therefore recommend that you upgrade at least the machines that you use to manage and server your imagery to V10. Useful links: A good overview of the mosaic dataset from ArcUser Online:http://www.esri.com/news/arcuser/0610/mosaicdataset.html V10 �?? Imagery management recommendations http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Imagery_management_patterns_and_recommendations/009t000001vr000000/ What is a mosaic dataset? http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/What_is_a_mosaic_dataset/009t00000037000000/ ... View more

Add the Image services to a map document. Then right click on the legend and you will see an option to save as ISRef. This creates an XML file that contains all the connection information and properties required to establish a connection with an image service. (In V10 this is replaced by using standard LYRs). When creating an ISDef the requires elevation for orthorectificaition this ISRef file can be used as the source. Prior to using an ISRef (or LYR) as a source, ensure that overviews are generated, as the orthorectifiaiton process can depending on scale make very low resolution (large PixelSize) request to the service. ... View more

Please clarify what you are trying to do. Do you want to: 1 - Create an Image Service from DTED data? In which case you can create a Elevation based Image Service definition and then add the DTED files using the DTED raster types. 2 - Use DTED to do orthorectificaiton. In which case you can create a DTED ISDef, publish it, create and ISRef to point to it and then use this as the elevation source for orthorectification of aerial or satellite imagery. (If using Satellite imagery is most likely that the elevation requirement is for Ellipsoidal heights in which case you will want to add an ellipsoid model as a service level function.) I would recommend moving to V10 which users Mosaic Datasets for such data management and has more integrated workflows. ... View more

Note this is the procedure for V9.3.1. When using Mosaic Datasets at V10, the method is similar, but terms have changed. I'm assuming that you already have an ISDef that has been created with overviews defined and generated, and you want to add new imagery with say a newer date. - Create a new field eg Year    In Service Properties, Field Properties, click on + for add Field. Set to metadata, Integer, Width 10    A Year field should be added. - Select all records and use Calculate to set the Year of the previous data. - In Service Properties, Client Interface control, Order Field - Highlight Year, so that it can be used as an Order field - In Service Properties, Client Interface control, Allowed mosaic method - Highlight By Attribute, so that the By Attribute method is allowed - In Service Properties, Default Client properties. Set default Mosaic Method to ByAttribute. Set the Order field to Year,  Set Order base value 3000  (some value in the future) - Add new data using the required raster type. When adding uncheck the option to generate overviews, so that overview a not automatically updated. - Open table, select new records and use calculate to set the Year to the new value - If you pan and zoom at larger scales you should now see the new imagery. At smaller scales (when overviews are being used) the older imagery will be displayed. - In table also check the MaxPS values for the newly added data. It should be equal or larger then the values of smallest Service Overview values. If this is not the case then you will need to define new service overviews or force the MaxPS value to be larger. - Build using the Generate derived images option. This will re-generate the overviews. Overviews that are no affected by the new imagery will not be changed. The system will only generate overviews for the tiles covering the new imagery. - When zooming out you should now see the newer imagery. ... View more

The system will directly re-order the imagery based on the mosaic method defined and the MinPS, MaxPS range defined for each raster. It appears in your case that you have different resolution imagery and the lower resolution imagery is fully covering the higher resolution imagery. As a result the MaxPS of the higher resolution imagery is being set to the LoPS of the lower resolution imagery. This represents the general case that most users want, IE higher resolution imagery at the larger scales, but at smaller scales use most appropriate imagery. To change this you need to change the MaxPS values of the higher resolution imagery to a larger values. As a general rule the MaxPS should not be set to more then about 4-5x the HiPS value though. IE you do not want to be sampling the imagery too much as this can really slow things down. (With larger images that have pyramids this is less of an issue and you will notice that that the HiPS value is larger). So one thing you can do is select the required images and then use 'calculate' to set MaxPS = LoPS*4 (or other value of your choosing). You also need to set a suitable Mosaic Method to define which of the overlapping imagery displays on top. This needs to be changed in the default properties of the mosaic dataset (accessible by right clicking on the mosaic dataset in the catalog window). This may not change the properties of the currently loaded version of the mosaic dataset that you have currently loading in ArcMap, so you may need to re-open the mosaic dataset.  In most cases you would probably set the method to ByAttribute and define a field and base value to be used. For example you could create a field called Year and set this to by default display the latest imagery on top. (Set base value to 3000 or something in the future.) Users of the Mosaic Dataset or resulting Image Services can redefined the mosaic method and fields etc. To Guenters note about the units. Yes all the units are now in the units of the SRS used for managing the mosaic dataset. This is a change from 9.2,9.3 where all units were in meters. Using the units related to the projection does make it more standard in how ArcGIS handles scales etc. The following can be used to Covent between scales and PixelSizes in meters.       Scale = Cell Size x 96/0.0254 Therefore, if the scale is 1:20,000, the cell size is 5.29 meters.      Cell Size = Scale x 0.0254/96 This is covered in the "Cell size ranges in a mosaic dataset" section of the help. If using Decimal degrees then divide the meters by 111111 to get an approx value in degrees. If using feet divide the meter value by 3.28. I'm hoping in the future we can provide a better way to view and defined pixels sizes in different units. ... View more

It would appear that you have the base imagery and then created Service overviews. When you now add new imagery and define this as having a higher priority it will display at higher priority at the large scales, but the smaller scales where overviews are used the older imagery will be displayed as the overviews were created with the older imagery. You need to Build the overviews again. This will detect the areas that need updating and update these tiles. ... View more

At V10 Mosaic Dataset can handle rasterized Lidar data well. A big improvement over 9.3.1 is better handling of NoData areas. The LAS files (that contain the original point data with different catagories) can not be directly used (yet). ... View more