Latest Contributions by PeterBecker

Can you provide the coordinates of the area you are looking at. From the graphic I can see -77.2835062, 38.8017132 but that does not appear to be the same location. Preferably also send me a similar small section of the original DTM  (wihtout any resampling) that I can try on. ... View more

Primary difference is related to when the sampling is performed. Spatial Analyst (or a raster function directly on the source) will perform the hillshade on the data to create a hillshade greyscale image in the source projection. When you display it in a different projection the hillshade mage will be resampled. By default in a raster function the input rasters are sampled to the required output projection (and pixels size) and then the hillshade is applied. Note that with image server / raster functions you can also control if the function should be applied before or after the function is applied. IE are you applying the hillshade on each item or are you applying the hillshade on the service output?  ... View more

Best if you send this to support. They should be able to dig into this in more detail. ... View more

Agreed it is strange. The values in the OIC appear to be correct, else the location point on the road would be wrong. Looks more as if the ImageryViewer is not reading the view angle correct. I just realized that the viewer you are using looks very old. Please use the following instead: 2D app : https://oi1.img.arcgis.com/app/index.html 3D app : https://oi1.img.arcgis.com/app3D/index.html Lets see if this fixes it. _Peter ... View more

Hard to answer this from details provided. Not sure if you have defined a DTM or are using average height above ground. Is it possible that you AvgHtAboveGround is set too large. From the image I would expect about 2.5m. That would be one explanation of why when you are looking directly forward the bottom of the view appears further away. Also check the that HFOV=360 and VFOV=180. (Possibly you have VFOV=90?) ... View more

Simplest is to create mosaic datasets of that data that you have and published as image services that users can directly used. Then create an app based on WABIS discovery Tool. (See sample app),  that can be used to drive a download script. You could also extend it to include Export (Ie extracted enhanced section in define projection and pixel size) as shown in the EOExplorer.  The code for both exist in the GiHub/ImageryApps and WABIS ... View more

Image Service provide Export and Download. With export the user defines the extent (including projection) and pixel size of the required output and the server processes the mosaic (which can included projection, orthorectification, pansharpening, mosaicking multiple images etc) to create a product as required that is then transmitted to the client application. This requires the server to process pixels and typically the administrator of the service puts a limit on the max size of such requests. The server could process a very large extent at high resolution, but typically such requests are not allowed. Download is a separate request where the client application defines a specific raster and optional extent. The server does not do any processing but just clips the input image and transmits this to the client application. Again the administrator can define if this capability is on or off and the max size of such a request. The third alternative is to have the app return the URL of the full image stored on some cloud accessible storage. The Image Discovery tool (also part of WABIS) provides and example of this.  If you use the tools to select images and add them to the cart, 'review&submit' and export to CSV you will see that the output includes the URL to the source imagery. Typically an image service from a mosaic dataset does not provide access to the source imagery, but if this is something that you want you can include the URL as an attribute or in the code provide the logic to create the URL. In a similar way that you can just call such a URL, you could also call a GeoProcessing service or similar to perform clip,zip,ship or similar. There are very many alternatives depending on what exactly you want to achieve and what restrictions you want to place on the exports. In most cases users the server to enable download to massive datasets is not wanted due to potentially high egress costs. ... View more

If you just want users to download ZIP files that contain a set of data and the required user experience is that users select what they want and then download file fro use in a desktop application, then you only need to load the zipped images into cloud storage and create a feature class with the appropriate attributes to enable search. Clicking on the dataset it enable downloaded. This is not a modern user experience. If you create a mosaic dataset that references the images and then serve that, users gain a single service that enables them to directly added the imagery to applications and use the imagery without the need to download. This provides access to the imagery without the need to download. As image services uses can export (extract sections of imagery) to be stored locally if required. Download can also be enabled, but typically is not required. If you have a collection of imagery from different dates you can create a mosaic dataset image service that contains all the image as one service.  This makes it easier to add image or make changes without changing applications. Alternatively you could serve each image as a separate dataset.  ... View more

Nada You should see following and so get a TIF file If you load TIF in ArcGIS Pro you should see following.  (Ensure you apply a stretch) to see the 16bit image. Note that you in EOExplorer or ArcGIS Pro you can can define function chains that can be transmitted to the Server that will be processed and the results returned. If you want to download the full Sentinel 2 tiles with associated metadata etc then see Sentinel Data Access Overview - Sentinel Online  One downloaded they can be accessed as Raster Products (or added to mosaic datasets)  ... View more

We just released an updated version today which did include some updates to portal integration. Could you please try the latest version and confirm if you are still seeing the issue.  Please confirm that you were able to publish the items and that you can view the items (OIC, Exposure points and coverage) in your content pane. ... View more

There are cases where you may be creating imagery from collections of data and there are no overviews for that data. In that case when zooming out users will not see anything. This can be confusing for users. One recommended option is to ensure that overviews exist for each of the different dates. If combining into a single master mosaic dataset it is important to ensure that date attribute is appropriately set. An alternative creating overviews is to use some other service data source as an overview. One can for example use ArcGIS World Imagery as an overview which will then be displayed at small scales. If you create a layer it you can then add that layer as a raster in the mosaic dataset and set the attributes so that it will be displayed at the appropriate scale or dates.   ... View more

Best is to use the DevTools available in a browser such as Chrome. Press F12 and DevTools should open up in a separate window.  In the Map view click on a location were there should be an image. In the network tab you should see a list of all requests. Near the end you should see the request to the image. Select it and look at the headers section. If you can not read the file, then you should see an error message. The most probable cause is that you have not set the Cross-Origin Resource Sharing (CORS) to enable an application to gain permission to access a web- or REST service from a server on a different domain than the site currently in use.  ... View more

I would recommend against using value from an image to define NoData. There are two issues. 1 - It is often difficult to determine these values and here may often be exceptions (eg shadows and compression artifacts). 2 - Using NoData in this way is computationally expensive when you start working with collections of overlapping images. The recommendation is to use a mosaic dataset and use a footprint to clip the imagery. Footprints are much more efficient as the system can geometrically determine what pixels should and should not be included in any computation.  For a general discussion on this see Clipping Raster in the Imagery Best Practices Also check out the High Resolution Imagery Workflow  The aspect of clipping such imagery by footprints is also covered in  Managing Preprocessed Imagery and Build Footprint Help ... View more