Latest Contributions by JohnWatt

Hi Deepa.  You can think of a raster as a table with a certain number of rows and columns, so is always rectangular, even if some of the cells don't contain a value. Having lots of Nodata values might seem untidy, but they're just a product of the tabular raster data structure.  They are transparent to raster analysis so shouldn't slow things down in GIS.  Converting from Raster to Poly will solve your problem, but then you'll lose the analytical flexibility of having the layer as raster. For R, you may need to change NoData to NULL, NA, NaN or similar - part of the fun of data wrangling 🙂 ... View more

Hi Aidan.  Good problem. Some raster tools expect an integer data type as input - so double check that data-types match.  Looks like your dealing with floating point rasters.  To do the other things - should be a matter of some sequential math operations. eg subtract euclid dist cell value from dataset highest value (summary stats) to reverse, and normalise.  Re using raster calculator in modelbuilder - try separating the operations using 'Spatial Analyst Tools\Math' gp tools instead of Map Algebra\Raster Calculator  - might simplify things and help debugging. ... View more

Hi Justin.  This is doable, but my approach has been 'computationally expensive'.  Involves running a viewshed as an iterated process (using model-builder iterator) on a point sitting on each cell (Raster to Point), then a table operation to turn Boolean 'visible' cell values into 'total visible cell count' for each cell.  Once you have a nice table with X,Y,Count as columns, you can easily map and symbolise, and translate cell count to viewable area.     ... View more

Hi MShairah - Try deleting the spatial index - this has solved most of my 'some features are showing but not all' errors.  ... View more

Try deleting the spatial index.  With shapefiles you may also want to check there are no 'lock' files belonging to someone else - might be fighting someone else for write access on the network.     ... View more

Just ran into this same problem.  What worked for me was to delete the spatial index for the layer in layer properties. ... View more

Thanks Naicong.  It's just a small efficiency if an empty instance of Pro is already open.  I tend to work within a project folder, and have Pro open since it saves ~20 seconds loading an aprx from scratch.  Also an ArcMap equvilancy, but not a biggy.  Can always copy-paste the file path.  Thanks for responding. ... View more

Had the same problem and blugeoned a work-a-round out of my PC using Excel to get points for each bookmark - which were then used as an index for a map series. Basically you can export the bookmarks to a BKMX file, drag that into Excel (Excel recognises the rows as a bkmx is just xml I think), use text-to-columns, a filter, an INDIRECT formula, and some helper columns to transpose into a simple table with 'name' 'x' and 'y' columns.  Then bring that back into Pro as XY point data. Ugly, but it worked 🙂 ... View more

Hi Elise. To achieve this in ArcGIS for a river centreline, I've used the Create Thiessen Polygons tool.  If you convert the polygons to lines, then split the lines into small segments (the smaller the segment, the smoother the centre-line), then create points from the line segments - creating Thiessen polgons from these points will create a centre-line in the middle for any irregular polygon - albeit with a bit of superfluous geometry. I had to manually edit to leave only the centre-line, but there might be a way to do this without manually editing.  Which you'll need with over 2800 polys 🙂 ... View more

Would be great if the Export Map dialog had a 'Home ' button to take you straigt to the project folder too.  Was part of  ArcMap, but didn't make it to Pro. Great time-saver. This fella:  Discussed here (duplicate) https://community.esri.com/ideas/15177-better-version-of-the-pro-windows-file-explore ... View more