Latest Contributions by DavidPike

I had a look at the GeoJSON spec and it looks fairly simple.  Same for KML. #GeoJSON { "type": "FeatureCollection", "features": [ { "type": "Feature", "geometry": { "type": "LineString", "coordinates": [ [102.0, 0.0], [103.0, 1.0], [104.0, 0.0], [105.0, 1.0] ] }, "properties": { "prop0": "value0", "prop1": 0.0 } } ] } For GeoJSON could have a python script or powershell or various to populate what is essentially just a list of coordinates in order.  Save it then upload to ArcGIS Online. https://gist.github.com/wavded/1200773?short_path=99c1af9 https://github.com/openlayers/openlayers/blob/main/examples/data/geojson/roads-seoul.geojson?short_path=84daf47 https://developers.google.com/kml/documentation/kml_tut#paths     ... View more

If you don't have access to any desktop GIS, you can likely find an online tool to convert the coordinates into Shapefile, GeoJSON or KML tracks (probably the easiest).  Obviously beware of the data you're sharing and apply common sense if  the website doesn't seem legitimate. ... View more

If you can't find the Survey in the 123 website or the hosted feature layer in ArcGIS Online then it's likely you've republished the survey at some point and made changes which required the hosted feature layer to be recreated (along with the loss of your data - things such as renaming fields and field types etc.). I'd certainly just check through all your content in ArcGIS Online again (also the survey may have changed owner - so someone with admin rights should do a keyword search on organisational content also). ... View more

@BrennanSmith1 that looks perfect.  Just my final recommendations for posterity as I'm sure people will copy your script for future use: # Check if any points were selected # if arcpy.Describe(points_lyr).FIDSet: ### selectlayerByLocation has a derived output for ### number of features selected already. The describe ### operation is quite expensive I think so perhaps this: layer, count = arcpy.management.SelectLayerByLocation(points_lyr, "WITHIN", boundary_lyr, "", "NEW_SELECTION") if int(count)>0: ### may sometimes be issues if boundaries have greater extent ### than the points, resulting in a rectangular clip before reaching ### the boundaries. But this is thinking from ArcMap days, maybe a long ### distant memory in Pro. # Set the extent environment using a feature class #(can also maybe be set outside loop??) arcpy.env.extent = boundary_fc # Create intermediate thiessen polygons temp_fc = r"memory\Thiessen_OID_" + str(oid) arcpy.analysis.CreateThiessenPolygons(points_lyr, temp_fc) ... View more

i think your feature templates exist at the Hosted Feature Layer level.  I've not done much with Field Maps but it seems the Templates tab is just another way to access and edit them. maybe you could create 2 Hosted Feature layer views for Island and Mainland and have different templates for each, but I've not tested that to see if possible. ... View more

Might be worth trying a date string which the API should convert internally.  That would be the (possible) work around to get it working of-course, rather than an explanation. "your_date" : "2025-02-01 09:00:00", "or_maybe_this" : "2025-02-01T09:00:00", ... View more

Very nice.  I wonder if it can be faster by taking the arcpy.management.MakeFeatureLayer() out of the cursor for points and boundaries.  they might be instantiated in each loop unnecessarily, but could well be misinterpreting! ... View more

https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/calculate-geometry-attributes.htm use the area geodesic option ... View more

Ah yes I remember the old 'Union to itself hack'!  very handy unless something better has replaced it. ... View more

I think you'd need to rebuild the Network Dataset. ... View more

Oh no, I have no idea.  That link seems to be for the World Geocoding Service, but certainly worth a try. ... View more

What you're seeing in the popup is default rounding,  I don't think it's truncated your data values.  The easiest way to see this would be to start editing the data and you'll see the true precision of the values. in the general U.S latitude, 8 decimal places would be (roughly) 0.1cm on the ground, 6 decimal places would be 10cm. Are you sure that the coordinates are maybe not a bit funky?  Maybe a check on google maps for 2 values. ... View more