Latest Contributions by DavidPike

I'm not sure about some things here.  You have points and a DTM.  I would attribute the Raster DTM values (the elevation) to your feature points using Extract Values to Points (Spatial Analyst)—ArcGIS Pro | Documentation  How To: Extract Raster Values at Point Locations in ArcGIS Pro  then Filter features with definition queries—ArcGIS Pro | Documentation use a Definition Query on your attributed point layer (WHERE RASTERVALU is Greater than 0 and RASTERVALU is less than or equal to 15) Your contours will have a height attribute to use the same Definition Query method to limit their display by elevation - Unless your contours are part of the raster basemap.  If that's the case, there's not much you can do other than source some alternate contour data, or produce contours from your DTM.  How To: Create Contour Lines in ArcGIS Pro and Youtube / Google. ... View more

That doesn't really make sense.  I'd ensure you have Join One to One as the option and are setting the point layer as the Target.  Some pictures and examples if the issue would be beneficial. ... View more

I'd just Select by Location (Intersect or Within a Distance or whichever spatial relationship suits best) to select the Points which are within the intersection. You could also export the selection to  a new layer if that makes it conceptually easier. then run a Spatial Join between the Points and Lines.  target = Points.  One to One or One to Many depending on your requirements. ... View more

It depends on your layer source.  If it's from an Enterprise Geodatabase you could create  SQL view and publish that.  If it's AGOL, you might need some workarounds.   A Layer View on the record table probably won't work as the SQL is too limited.  But... An option might be to create a Joined View Layer How To: Create a Joined Hosted Feature Layer View in ArcGIS Online You could join your Hydrant and Inspection layers (I guess Hydrant_ID is the join field). Join One to One and Keep only first matching record (remember to sort by OBJECTID DESCENDING).  Join Type = Inner ... View more

Any issues I've ever had have been with the data being corrupted or incomplete in some way after an automated scheduled copy process.  The more obvious ones have been missing layers from the .mapx I don't think there's any functional difference in sharing it into AGOL as it's just creating the MMPK in scratch/temp locally then sharing to AGOL (is my understanding). ... View more

there might be a few hacks.  You could have a MaxRecordCount (always return max 10 for example) query parameter added to the service URL, or set it to 1 until a previous question is answered, then alter the variable size. You could also have your search/filter parameter preset in the same way to some default value, which then updates dependent on that previous question being answered. ... View more

Might be stating the obvious but pressing 'd' to restrict length when digitizing.  Could probably have it set as a 'task' Introduction to tasks—ArcGIS Pro | Documentation ... View more

Tabulate Area (Spatial Analyst)—ArcGIS Pro | Documentation Then calculate the area from the raster cell size. ... View more

You have pending Edits, possibly save them. Your Zones and Classes are the wrong way around. Zones =  water Class = Lines https://pro.arcgis.com/en/pro-app/latest/tool-reference/analysis/tabulate-intersection.htm Using a higher dimension Input Class Features value than the Input Zone Features value is not supported. If the Input Zone Features values are points, the Input Class Features values cannot be polygons or lines. If the Input Zone Features values are lines, the Input Class Features values cannot be polygons. If the Input Zone Features and the Input Class Features values are different dimensions (polygon zone with line class, polygon zone with point class, or line zone with point class), the output PERCENTAGE field records the percentage of the class intersecting the zone polygon. A LENGTH field is included in the output table when the Input Class Features values are lines. The LENGTH field contains the length of intersection between the Input Zone Features and the Input Class Features values. ... View more

Did it work before?  If the password for the account that created the key has changed then I believe you need to create a new key (maybe create a new key anyway to check).  Otherwise I think more information would be beneficial. ... View more

Yes also be aware (unless this is now fixed in later Pro versions) that the generated Python script references the .aprx for some reason.  i.e. ensure you save the .aprx Project before scheduling the model. then go into Windows task scheduler and set all the options, run as Admin (maybe?), run when not logged in etc etc.  and best to have it run and a Service Account. ... View more

possibly BUG-000155515 for ArcGIS Pro Solved: Cannot Apply Symbology From Layer Using Python Scr... - Esri Community - details setting the symbology as an output parameter instead. I've also seen it set as 'layer.symbology' as an alternative. ... View more

These seems like a use case for a Dashboard or Experience Builder.  Do you have access to these? ... View more

Might be misunderstanding - but I feel a spatial join then a calculate field would work. ... View more