Latest Contributions by MervynLotter

If the above approach does not work, do consider converting it to .tif using the Copy Raster GP tool (not the Clip Raster). Set the output extent in the environment settings. MrSid imagery is not a raster type that works well in Pro. ... View more

After creating your raster mosaic, the next step would be to create a multidimensional layer using the "Make Multidimensional Raster Layer" GP tool. You will them have a set of multidimensional raster tools available to explore your data and extract the necessary information.  See Multidimensional raster data—ArcGIS Pro | Documentation  ... View more

Hi Tanner Is it possible that you do not have any areas in mode where you have a maximum value 5 for every pixel? Perhaps the highest is only 5+5+4 and not 5+5+5? Maybe check this out first as the model should work.  ... View more

"Summary within" is a script tool that strings together several GP tools in the background. I have previously encountered some issues with it. I prefer to use the Tabulate Intersection tool (Tabulate Intersection (Analysis)—ArcGIS Pro | Documentation) for vector overlays to calculate size and proportions. This is very similar to Summarize within. Do take a look at it to see if it meets your needs.  If you are calculating size, be mindful of choice in projection as the default size calculation in this tool is based on the projection of the layers. If you are using a projection like Web Mercator, rather use a geodesic method to manually calculate size and then sum the size field values from the geodesic calculation. Unfortunately, it does require an Advanced license.  ... View more

Hi JohnKelly If I encounter any odd behavior when working with vector data I usually run the Repair Geometry GP tool to find and fix any errors before further working with the dataset. Not sure if it is applicable to your situation but you may want to consider it. To calculate size, I always use the Geodesic area calculation unless there is a specific reason to use a planar calculation, like (1) if my organization has a policy to use a certain projection, or if (2) a local projection (and a local datum) is deemed more accurate than the geodesic method with a global datum (like WGS84). The geodesic area calculation is based on the underlying ellipsoid (model of the Earth's shape) regardless of your chosen projection.  But if your projection uses a different ellipsoid/datum, then you should get different results.  If you have time, create a point file in Web Mercator, then create a point in Canada and then buffer it, first using planar and then geodesic distances. You will be amazed at the difference in shape (and area). One should never use Web Mercator and a planar calculation method.  But don't rely on your Shape_Area value and rather use the Claculate Geometry tool to calculate the size of polygons.  Good luck. ... View more

Wonderful, thank you so much.  ... View more

This is a great new addition to the Living Atlas. Thank you! ... View more

That is unusual as this works for me. Perhaps try toggling between real-world and screen units or reapplying the symbology. Unless anyone else has some other suggestions? ... View more

This is a display property for the layer. Open up the Layer Properties, then click on the Display tab and then ensure that "Real-world units" is checked on.  ... View more

You received the above error because you need to the output of your buffer as input into the Create Spatial Sampling Locations tool, not your drill sites.  The workflow I propose can only really work if you don't have overlapping polygons (buffered drill sites).  I misread your first post. To create the doughnuts, you will need to create 2 buffer outputs (10 and 20 km each) and then use the clip tool to clip/remove the smaller buffer. You will be left with a doughnut. This is what you must use as input into the Create Spatial Sampling Locations tool. You will then create 1 random point within the buffer doughnut. Afterwards, use Add Spatial Join tool with the "Nearest" match option to link up the original drill sites with the new random points to get the attribute data. ... View more

As you will repeat this process, best to do this in ModelBuilder. I would start with buffering each point by 20-30 km (Dissolve Type = No Dissolve), then create a single random point in this buffer using the Create Spatial Sampling Locations GP tool. Make sure to use the "Stratified by individual polygon" sampling method.  Then stipulate that you want 1 sample per polygon.  Then run a Spatial Join to get the details of the oil discovery locations.  ... View more

Can you confirm that the shapefile includes identical files with the following extensions?  .shp, .shx, and.dbf?  If so, then it should show up if not corrupted.  But is there a chance thar your .prj is the wrong projection?  Happens when using define projection tool to change projection.  For example, perhaps the shapefile is a a geographic coordinate system however the projection file says it is in Web Mercator? That kind of mismatch in projections will result in it not displaying.  Lastly, if all of these don't work then perhaps also delete the .sbn and .sbx files (that store the spatial index) as I have had trouble with them before being corrupted. But in these cases, if you zoom out far enough the points do show.  But do first back them up.    From your screengrab I cannot tell what the shapefile extensions were as you are hiding the file name extensions.  You should change these in Windows Explorer from the View tab.    ... View more

If the other suggestions don't work, try running the Repair Geometry tool to recalculate the spatial index.  ... View more