Latest Contributions by DavidSolari

For clarification: would your workflow support collecting the geometry in Field Maps, hiding the attributes from editing, and providing an Arcade expression that opens the feature up in Survey123 via Global ID? This way you're only editing one feature between both apps. Alternatively you can make an Arcade link to a different feature layer (or a table layer in the same feature service) and pass in the GlobalID to a foreign key field, this works better if you need to do offline work. If neither option fits then that's a tough one, this level of app ping-pong is beyond what I've worked with. ... View more

For the two points where the blue vertices hit the edge of the orange square, are there matching vertices on the orange square? I've had issues with spatial selections where minute imprecisions along edges cause the inner feature to bleed out of the outer feature, even if it seems mathematically sound. If there are matching vertices then yeah this is a bug. ... View more

The List Domains function is what you're looking for, this will work on any EGDB. The sample code on that page should get you started. ... View more

This happens all over the place in ArcGIS, GUID/Integer fields are technically different from GlobalID/ObjectID fields even though they hold the same data types so many tools reject them, even in cases like this where compatibility makes perfect sense. A full sweep of the standard tools for cases like this to loosen up the data type matching would be appreciated. ... View more

Did some digging around and found two really good links. First is this old college course that covers the math involved in calculating the sun's position relative to Earth, among other things. If you're interested in the mathematical foundations this looks like a good starting point. Link. Second is pvlib, a Python library that models many aspects of photovoltaic phenomena, including the sun position given a certain date and location. You can either add the library to your Python environment and use the functions as-is (docs) or go diving through the source code to see how it's implemented (link). ... View more

I haven't dug into your specific form, but in general: If you aren't linking your survey to an existing feature service then you can create "repeat" question blocks in the survey. Each repeat block adds a new layer to the Survey's feature service with a 1-M relationship class ready to go. You can then have the rest of your workflow make edits to those related layers outside of Survey123, just make sure to use the "relevant" or "readonly" columns as needed to keep the repeats off limits to the initial survey. Alternatively, you can create the related table structure in your own feature service, then link the survey to that service. This requires more work than letting the Survey123 tools build the service itself but you get the ability to bolt Survey123 as an interface over existing workflows, use registered services that store your data in an EGDB, and maybe some other benefits. Either method has the same result: the Survey123 user fills out their part of the data, and then the rest of your org can populate related records for each form submission. ... View more

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