Latest Contributions by DavidPike

Arcade has a Month() function.  It returns 1 (Jan) - 12 (Dec). Date functions | ArcGIS Arcade | Esri Developer this article should have all the code you need, incl. a dictionary to map the number to the month name. How To: Extract Month Names from a Date Field Using ArcGIS Arcade in Map Viewer   ... View more

Yes Raster to Point and Spatial Join seems the only (potentially) viable option in ArcGIS.  I say potentially as it depends on the size of the Raster as it may be possible but not practical in terms of time/processing. With the spatial join you can have a merge/join rule for all intersecting points (new points representing your raster cell centres with raster values) within your quadrants.  If you want to create a quadrant around your points, you can use a buffer and feature envelope to polygon tool How To: Create a Square Buffer around a Point Feature in ArcGIS Pro I also believe Zonal Stats is a SA tool unfortunately. ... View more

How does it show in the layout view in Pro?  Possibly fit-to-page on the print is skewing it? ... View more

Maybe you have unsaved edits? ... View more

You might be lucky and have some pixel values which only correspond to the outlines and the index numbers, but it looks unlikely.  Even so, it would only probably help with somehow turning that into the individual polygons/centroids.  You'd be left with some raster cells which form a picture of the ID text, which is probably only use to a manual digitiser. It sadly looks like some application of AI/ML or laborious digitising, but I'd be interested to see what other options people might come up with. ... View more

Yes I think the doc could be worded more explicitly.   You want the join to take place only if it is the single Closest Point of all other points (matching attributes or not), AND the attributes match? not: The Closest Point from a selection of attribute-matched points (even if not the Closest point of all inputs). It makes sense to me for the latter, which is what the tool is undoubtedly doing.  The set of use-cases for the first seems much much smaller (imho at-least). You could set the Search Radius parameter to limit the search distance or from what you describe as your objective you can simply: Do a normal Spatial Join (closest) with no attribute matching.  Then you have a layer which has the spatially closest record (attributes matching or not). You will then have the attribute appended from that Closest point.  I think it's only then an exercise to find rows where the 2 attribute columns do not match. Perhaps simply done with a Select by Attribute where 'Field1 <> 'Field2' ... View more

Just for clarity, I think that would be a Mosaic Dataset. ... View more

Yes, it would be the new buffer you clip to the yellow features.  This should produce a thin sliver of a polygon which runs along the shoreline and extends a few metres (whatever distance you buffered by) offshore. You then buffer that, then finally clip to the State Polygons (so that it's all inland). ... View more

Thanks ChatGPT ... View more

I'd do the normal reports on blocking transactions etc. you would for a normal DB also.  If people are consuming tables directly from the database, look out for stuff like missing spatial indexes on big datasets. ... View more

Maybe some Planar and Geodesic differences in the tools?  Does your coordinate system preserve distance at that scale? ... View more

Is the Map projected coordinate system the same as that UTM Zone?  I'd guess that's the issue if not. ... View more

For your output you'd probably want Pivot Table (Data Management)—ArcGIS Pro | Documentation or more likely Transpose Fields (Data Management)—ArcGIS Pro | Documentation after the Summary Statistics. ... View more

You don't really need to think about where the output is stored server-side unless you really want to update an SDE table.  Publishing the GP tool wrangles the output paths so it can be a temp output added as a map result each time. Set your tool output type to a Feature Class, ensure direction is Output.   Then run it in Pro with a local output.  Publish it to Server and that copy the REST service endpoint to the GP tool input. ... View more

Manual editing to get the Polylines seems like the most foolproof way if this is only a small number of features.  You mention the perpendicular lines being an issue.  Why not delete those segments after splitting the lines? You could also buffer the State Polygons by a few metres, then Clip that new Buffer to the Yellow features, then run your Buffer (Flat end option).  Finally Clip that Buffer to the original State Polygons.   ... View more