POST
|
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
06-10-2021
12:44 PM
|
0
|
2
|
1068
|
POST
|
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
06-09-2021
11:43 AM
|
0
|
1
|
1909
|
POST
|
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
06-09-2021
11:20 AM
|
0
|
3
|
1930
|
POST
|
See Using Lidar data in ArcGIS Pro & Las to Raster Function Also take a look at Managing Lidar Data Imagery Workflow
... View more
05-24-2021
01:09 PM
|
1
|
0
|
1038
|
POST
|
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
04-14-2021
07:51 AM
|
0
|
5
|
2242
|
POST
|
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
03-15-2021
08:06 PM
|
0
|
0
|
2792
|
POST
|
If you include a screen shot of what you are seeing it will be easier to identify the issue. At what scales to you or don't you see these gaps? If you load the two as separate datasets in Pro do you also see gaps? If the gaps appear at the smaller scales the issues could be related to the pyramids in the dataset and how they were created. Each pyramid level is typically 1/2 resolution of the previous. If the number of rows/columns is not divisible by 2 then the apparent image may shrink by 1 pixel, which can appear as a gap if there is not overlap between the images. This is why it is always better to have some overlap between datasets that are cut into tiles. The other issue maybe related to if the image is being clipped by footprints or boundary. Check following settings Clipping the imagery by footprints or boundary is an optimization (especially for overlapping images), but if they are not defined well then they can results in gaps. Try turning the clipping off to see if this is the case. Remember if you have generated overviews then then the overviews would have been created based on the settings when the overview was created, so you may want to exclude them or use lockraster on the source images to see the effect without overviews
... View more
03-15-2021
01:43 PM
|
0
|
2
|
2799
|
POST
|
You need to set the mosaic dataset \ properties \ general \ Raster Information \ Source Type as 'Vector-UV', 'Vector-Magnitude' or 'Vector-Direction'
... View more
03-02-2021
10:55 AM
|
2
|
2
|
1657
|
POST
|
.PIW is a proprietary format from Pictometry/EagleView. It appears to contain meta information about a collection of images, but there is no public way to read it that I know. Typically a .PIW has a set of related .PSI files that are JPEG images with specific metadata in them. These should work in Drone2Map (if you rename them), but you would need to request the metadata from Pictometry to provide the camera location information. I would recommend connecting back with Pictometry to determine if they can provide the .DBF files that is sometimes provided and check on the usage licensing.
... View more
01-27-2021
06:56 PM
|
1
|
0
|
1974
|
POST
|
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
10-29-2020
09:20 PM
|
2
|
2
|
3093
|
POST
|
Integration with Cyclomedia exists. It requires Cyclomedia to grant access to create the OICs. Suggest you request Cyclomedia for it.
... View more
10-22-2020
12:49 PM
|
0
|
0
|
754
|
POST
|
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
10-17-2020
01:03 PM
|
0
|
0
|
888
|
POST
|
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
10-13-2020
04:41 PM
|
0
|
0
|
4027
|
POST
|
Gregory Following is a sample of the data directly in ArcGIS Pro with the hillshade function applied (Ie in the native projection of the raster, Virginia NAD83 State Plane North) The checker pattern that is seen is a result of the original data being resampled during the reprojection. Any resampling (including all reprojection) will cause artifacts in the data. I can not confirm but it would appear that nearest resampling was used (vs bilinear). It is highly recommended that source data is not resampled. If the data was collected in a specified projection, sampling and pixel alignments then is it best to keep it as it is and only resample if required for display. If resampled then use bilinear. The issue here is that the data is resampled and then applying hillshade will extenuate the artifacts. Further resampling will only make it worse.
... View more
10-02-2020
02:56 PM
|
0
|
2
|
2195
|
POST
|
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
09-30-2020
01:37 PM
|
0
|
5
|
2195
|
Title | Kudos | Posted |
---|---|---|
1 | 09-13-2021 04:39 PM | |
2 | 08-09-2023 05:08 PM | |
1 | 05-09-2023 11:25 AM | |
1 | 04-30-2019 07:41 AM | |
1 | 01-10-2023 12:33 PM |
Online Status |
Offline
|
Date Last Visited |
02-14-2024
12:20 AM
|