Latest Contributions by PeterBecker

Check out Oriented Imagery. See https://marketplace.arcgis.com/listing.html?id=19b5028e59c141239d0a262117639f81 You can create an Oriented Imagery Catalog in Pro from data stored locally and have the system push the data to cloud storage. Or have the images in cloud storage and create an Oriented Imagery Catalog. The Oriented Imagery Catalog can then be accessed in Web Apps and Pro. It handles a range of imagery including from Ladybug. One issue with some Ladybug data is that the orientation of the imagery is not always recorded and there is a solution coming up to determine this based on the direction of travel. ... View more

You can control the maximum size of an export request (default is 4000x15000  Cols,Rows), but you can not disable export. Export is what the clients do when they pan and zoom, but the request size is based on display views size. The max cols/rows is a parameter in a mosaic dataset and parameter of the service. In many cases  you can reduce this to about 2000x2000, but this may stop people using it on large high res displays. Export can not be turned off in the same way that you can not turn of screen capture in all apps. You can control the raster functions that users set on the services so that the original data values can not be accessed.   ... View more

Greg Please try with the version recently released last week. The Oriented Imagery Management tools are now directly accessible in https://www.arcgis.com/home/item.html?id=36ee0bbedca64a5a8b68d7c69ab51728 ... View more

Not quite sure what you are trying to achieve. It appears you are using an RFT that contains remap and then colormap function during publishing an image service. This is possible but don’t quite get what result you are trying to achieve. You sate: “However, the pixel values in the raster file were not changed”, this is as expected since the server will be processing and change the values per the functions on-the-fly. Note there is a sample sample RFT with colormap and remap in doc: https://developers.arcgis.com/documentation/common-data-types/raster-function-objects.htm#ESRI_SECTION1_769B8F65B9A441F5A073623D1B1F1280 ... View more

Use CopyRaster GPTool using format .bsq (band sequential) or .bip (band interleaved by pixel). These RAW formats mean that the data is output an noncompressed images one pixel after the other. The difference between .bsq and .bip is how the pixels from seperate bands are organized. With these files there is an auxiliary .hdr file that defines the ordering, number of cols,rows, pixel depth etc. I typically would not recommend using. These formats are really only used for interchange to legacy applications that do not support more standard image formats such as TIF. Not these Esri and photoshop raw formats are not the same as 'Camera RAW' formats which are lowest level output from digital cameras. Each camera manufacturer has their own version of camera raw format. Its rare for software to export to these camera raw formats. ... View more

Depends what you mean by "two unclassified lidar imagery layers". If these are Digital Surface Models then you can subtract one from the other and assuming the foliage exist on one and not in the other the different will be very apparent and the resulting raster you that threshold, filter (remove noise) and convert to polygon. Similar if the data is multispectral and you can create a vegetation index and subtract the two then you can do similar. If though the multispectral data is taken in winter and summer in a deciduous area, you are going to get incorrect results.  ... View more

Looking at the first image above. There are horizontal and vertical footprint lines. I presume in this case that you have already crated overviews. I believe at smaller scales you are seeing the overviews which were created prior to the clipping of the footprints. Please re-generate the overviews. ... View more

One possible explanation is that the imagery you are using has a color map associated with it. ie the imagery is not 3band RBG, but represented by an 8bit image with a colormap. It is then possible that in the Preview app that two differerent value are being used for NoData. When you load the image individually, each is using its own NoData, but when in a mosaic the the system is confused by two different nodata values. Even if using rgb it may be that something is different in the no data values. In this case the simplest solution is to manually edit the footprints for these image. Use editor, start editing, select the appropriate footprint (sometime easier to user table to select) then redefine the footprint. If the clip to footprint property is on then the image will be clipped and the black will disappear. Note that the recommended way of working with such imagery is to take the data directly from the scanner and convert to a suitable format (eg TIF with JPEG or LZW compression). I'd suggest making the tif files (not directory) read only. Then use the tools in ArcGIS to georeference the imagery. Do not save as a new image, but save the georeferencing with the tif. Now create the mosaic dataset. Then edit the footprints to remove any part of the image that should not be displayed. This way you clip out any non required data while maintain the full integrity of the original image. If a user does a lock raster to a specific image then they can also get the clipped out imagery that often contains details such as legends or other remarks of interest. If you want a single base image cache the mosaic dataset. For more details see Managing Scanned Map Workflow in ( ArcGIS Imagery Workflows | ArcGIS )   ... View more

I have a similar screen with slightly larger 2560x1440 resolution and have no issues. There is nothing on the these specs that indicate that it would work with Stereo Glasses though, so you might not be able to use the active stereo mode available with the Image Analyst Extension. ... View more

Note that a updated version 1.0.2 was released today. ... View more

Hard to say without seeing some of the images. I assume that the images when displayed are positioned correctly and at the correct scale so that there is overlap. Is the source pre-generated orthos? If so then the the only think I can think of that you have the shrink parameter set. Set this back to 0. The only other way I have seen this is if the source are on-the-fly generated orthos and you are using the Geometry option, but have a parameter such as the average terrain height, focal length or affine transform parameter incorrectly set in the transform. When doing the recompute footprint by geometry the system attempts to determine the image to ground transform. For this some estimate of the ground height is required so the parameters such as average terrain height are used. If incorrect (Average height too large) then the initial estimate may be much too small and cause this. ... View more