Latest Contributions by PeterBecker

The display in Pro and via Web should be very similar (the same). I noticed in the screen shot that the source imagery is 4cm and has pyramids to 32cm. The display range for this is up to 96cm and the overviews appear to start at 2.88m.   There appears to be a gap. I would suggest doing define pyramids with a pixel size of 32cm. Then Build Pyramids and see if that works. Do create a copy of the mosaic dataset and delete the source image to see what scale you see the overviews. ... View more

Please split into two parts a) Just create mosaic only using raster proxies. They should display only at larger scales (based on maxPS). Check in the raster proxy where the cache is to be written to. It must be a dedicated drive on each machine. Not a shared drive. Check this works on Pro and Server.  b) Determine how you want to handle overviews. These will be written to a local drive and you can handle similar to other rasters then. Another alternative is to create a CRF and use that as an overview ... View more

I'm not sure why the 1 above works, but 3 does not. Likely related to the resolution of the export. Is it possible that the export is a different resolution? Also are you sure this is the same services.  Doing export of an image with DRA is always problematic as larger requests get split into multiple smaller requests ... View more

The issue is that you are using as input a layer that includes dynamic range adjustment. The Sentinel2 imagery is returned as apparent reflectance (with values ranging from 0 to 10,000) that cover the complete dynamic range. For optimized display the stats of the current view are used to stretch (eg using standard deviation) the image for suitable display on the screen. When you do export the system is splitting the extent into blocks and each block is having the dynamic range adjustment applied. Hence the result you see. What you need to do is use a layer that does not have DRA applied. Check the different included raster functions. You can then also define specific stretch values to get the rendering you need. ... View more

Check the options in ArcGIS Pro that World files are being used. You will need to set this before you add the image. If the image falls in the correct place then you can ignore the analyzer warning.   ... View more

Yes, looks like an issue with either the source images not actually being 100% connected or footprints clipping and the projection of straight lines causing some artifacts. Also consider using the merge option on each set of source dataset. This will virtually merge the images into a single item the mosaic dataset. Don't go overboard on this. IE try to keep the number of rasters per merge to <100. ... View more

You need to set the mosaic dataset \ properties \ general \ Raster Information \ Source Type as 'Vector-UV', 'Vector-Magnitude' or 'Vector-Direction'   ... View more

Looks to me like on one of the following:  (most probably 2) 1- Looks like the source data may consist of a large number of small tiles. If this is the case check the level at which overviews are created. The smaller the tiles the larger the resolution the overviews need to be. If you dont have sufficient overviews then system will need to open many files which can degrade performance and lead to issue if 'Max number of rasters per mosaic' is not large enough. If the source is many tiles consider mosaicking them together into much larger tiles (same projection/pixel alignment). 2- If the issues is with raster proxies then check Appedix D in the Optimize Rasters documentation. The issue is often related to running desktop and server on the same machine that causes locks on the cached files. This may have caused corruption of the tile cache indices. Delete the cache. Also ensure the cache is on a local drive (preferably a fast ephemeral drive). Do not point the cache to a network drive or some location shared with multiple machines. ... View more

Integration with Cyclomedia exists. It requires Cyclomedia to grant access to create the OICs. Suggest you request Cyclomedia for it. ... View more

By the look of it: you have georeferenced imagery that originally had a black frame. In the georeferencing the pure black was identified as NoData and turned to white. There are though other pixels that were not pure black and so there remain as the black artifacts at the edges. In the image white is not defined as no data so when you overlay one image on the other you are seeing the extent of the overlapping image. I assume if you change the image order the gap will move but still be there. Turning pixels to NoData will not help due to the artifacts. If you only have a couple of images then do the following: Create a feature class (polygon), Start editing and draw a polygon that is just within the extent of useful pixels. Repeat for second image. Select the record for the first image. In Imagery,raster functions, open the Clip raster function. Select the 1st raster, Clipping type:Outside, Clipping geometery: (select the feature class with selected record). Create New Layer. This should result in an layer with the outside clipped out. Repeat for the second image and then use the mosaic function to mosaic both together. The other way to do this is to create a mosaic dataset, add the rasters, then use recompute footprint by radiometry with say 80 vertices and suitable buffer (I'm guessing 20m). This will automatically clip the images based on the footprint, which you can also edit if needed.  ... View more

Note that if your imagery just natural color images and you don't need any of the dynamic feature of an image service (IE you are just looking for the image as a background image in webmap) then you can create the mosaic dataset and just convert it to tile cache and publish it directly to ArcGIS Online. See (Serving Cached imagery). No Image server is required for this, it can be done directly in ArcGIS Pro. ... View more