Latest Contributions by DavidSolari

If you need to implement this yourself you'll have to search for "JSON Stringify" and see if you can find an implementation to copy. Doing a serializer 100% to spec is a daunting task (and might not even be possible at an acceptable speed in Arcade) but it'll give you a lead on the type of data you need to parse to meet your requirements. Worst case you'll get some practice writing a pushdown automata in cut-down JavaScript, they don't teach you that in GIS school! I'd also recommend posting an Idea to get ToJSON added to the function library, ESRI developers can bridge to the relevant runtime's JSON.stringify under the hood so I doubt it's an onerous request. Also the usual caveat: make sure you validate any user data before you serialize, you don't want to risk webhook payload injection from malicious inputs! ... View more

I've never had any ArcGIS project lose file geodatabase data in the way you're describing so unless this thread gets a lucky traveler I suggest contacting your support rep and see if you can replicate this with some test data. This could be a rare bug with Pro but it could just as likely be issues with your disk drive or Windows install. ... View more

Agreed, I can't find a way to draw labels under other layer features. If an annotation class leads to maintenance issues, you can convert labels to graphics using the same Convert Labels section of the right-click menu, that stores the labels in the map file instead of a database. It's pretty fast to wipe out the old graphics layer, convert the labels again and reposition the new layer before publishing and you don't leave behind any junk in your default GDB. ... View more

Priority number 1: make sure you're reviewing the data from the source and double-check your layers. I've had panic attacks caused by people adding definition queries behind my back! If it's Enterprise Geodatabase data, see if any missing data is visible in a regular SQL query against the database. For anything on the file system, see if the drive it's stored in has backups, either a full copy system or a shadow copy that you can see by right clicking on the file/folder and selecting "Restore previous versions." Hosted data is the trickiest, check with your admins to see if they've done any backups of the data store, either directly with ESRI backup tools or with full system imaging. ... View more

An alternative if you need cross-compatibility between Arcmap and Pro for a transitional period is to use an older release of Pro for a bit. For example, here's the same support page for Pro 3.1 which can handle older Postgres releases. Note that upgrade warning on the page, getting Postgres ready for future Pro releases will break Arcmap compatibility and require some migration tools. ... View more

This would be a great addition, I manage a ton of two-stage forms and getting quick access to either mode would be great. Bonus points if we can edit all the other implicit variables (device type, hidden type fields etc.) to quickly see how the form will behave under other circumstances. ... View more

Just thought of one last thing to try: if you have a 3D Analyst license you can extrude your block areas into extremely tall buildings and poke around the Visibility tools. This might be the most accurate way to figure out which areas are "in shadow" and can be culled. ... View more

Alright, given the limited test data I've made, I think I have a working concept. This requires that the roadway segments don't have any gaps in each working area, and the block areas touch the roadway segments in at least two places. Run Feature Vertices to Points on the block areas, then Delete Identical on the Shape field to remove the double origin vertices. Spatial Join the vertices to the roadway, unchecking the keep all option. You now have just the block vertices that touch the roadway, with the roadway segment attributes as well. Make a polyline feature class and add two fields: a field to hold a related Object ID, and a field to track left vs. right side. We'll call this "Traces". It's Python time! Use a Search Cursor to make a dictionary of roadway keys to "SHAPE@" geometry data. Create an Insert Cursor for Traces (related OID, "SHAPE@" geometry and side fields) and a Search Cursor for the spatially joined points ("OID@" object ID field, "SHAPE@" geometry field). For every point: Get the line geometry from the dictionary. Use the line's measureOnLine method to get the measure of the point along the line. Get a  "p1" point from the line with the positionAlongLine method and subtracting a very small distance from the measure. Do it again to get a "p2" point but add a very small distance to the measure. Use the angleAndDistanceTo method of p1 to p2 to get the rough heading angle of the line at that point. Use the pointFromAngleAndDistance method of the original point with the buffer distance and the heading minus 90, this creates an endpoint from the original point out to the left. Use the Polyline constructor to turn these two points into a line. You can get the spatial reference from the original point. Insert the polyline, the point's Object ID and a "left side" side value into Traces using the Insert Cursor. Repeat steps 6-8 but add 90 to the heading instead, and use a "right side" value. You now have a bunch of perpendicular lines shooting out from the roadway. We need to turn these into polygons, so start by Dissolving the roadway segments into one single line feature. Get a sorted list of those spatial join points with their Object IDs, sorting on their measure along the dissolved roadway line. I'll toss in the code for this one as sorting with a key is a bit more advanced than your usual Python: line = next(arcpy.da.SearchCursor("Dissolved Roadway Segments", "SHAPE@"))[0] def _sort_by_length(row): return line.measureOnLine(row[1]) sorted_points = sorted(arcpy.da.SearchCursor("Spatial Join Points", ("OID@", "SHAPE@")), key=_sort_by_length)​ Search Cursor through the Traces and build a dictionary of related Object ID to "SHAPE@" geometry twice over. The first time filter to just the left side lines and the second to the right side lines. Create a Polygon feature class to hold the data from the next steps and create an Insert Cursor for it, no extra fields required. Get the first point from the sorted points as the "last_point". For all the remaining sorted points: Use the OID of the last_point on the left side trace dictionary to get the first line geometry. Use the OID of the current sorted point on the left side trace dictionary to get the second line geometry. Build a Polygon using these points: firstPoint of first line, lastPoint of first line, lastPoint of second line, firstPoint of second line, and firstPoint of first line again to close it. Insert that polygon using the Insert Cursor. Repeat steps 1-4 but use the right side traces dictionary to get the two lines. Set last_point to the current point so it's ready for the next loop iteration. Erase the block areas from these new polygons. Select all erased polygons that "Share a line segment with" the block areas. Remove from selection any erased polygons that "Share a line segment with" the roadway segments. Phew, that was a lot! But from my limited testing this gives you a bunch of polygons that indicate points to exclude from further processing. Hope this gets you started on something. I also welcome anyone reading this to reply with better ways to do all the geometry nonsense I laid out. ... View more

If Preserve Global ID won't fit your workflow: create the destination feature class with the "Guid" field type for every Global ID field. When you append the Global ID will be stored as-is in that Guid field. This also works with Object ID fields, just use "Long" (or the new 64-bit field type if needed) instead of "Guid". ... View more

I was staring at this for minutes trying to figure out where the polygons were until I broke out the eyedropper tool. For anyone else with some red-green color blindness, here's a version of the OP's image with the polygons' contrast blown out:   I don't have a solution right now, but to confirm some things: is the attached data and image consistent with how your data is laid out? Have I classified my demo points correctly based on the results you're looking for?   ... View more

Closest to real-time is the webhooks feature. ... View more

Correct! Use the arcpy.mp module to loop through your map layers. ... View more

If the schema hasn't changed between annual versions, you can create a new hosted feature service with the same layers and schema as the previous year, then follow the existing feature service workflow to glue the new form to the service manually. This also removes the automatic service management features that Connect provides, which adds some overhead every time you add a new field or need a new hosted view, but it prevents Connect from clobbering your data accidentally. ... View more