|
POST
|
Edit management is tricky to keep track of in ArcGIS because you have multiple types of "transactions": Database transactions/file locks: These are the fundamental locks that everything else is built upon. Proper databases (EGDBs, File GDBs, Mobile GDBs etc.) can start and stop transactions of various lengths depending on how you edit them, these limit how other users can write data to the same DB while they're in effect. EGDBs run on full relational database engines so transactions are usually kept as short as possible to avoid locking up other users, this is why your ability to save or undo edits are heavily limited when you work with them directly. The file system DBs only allow one active writer so they can keep a transaction going much longer. Other file types try to behave like File/Mobile GDBs by creating lock files during edits if possible. Edit sessions: These open a transaction/lock and only release the lock when you finish your edits. GDBs will keep a stack of your edits to allow you to undo, redo, and fully discard the edits before saving. Other file types are usually more limited in how granular the edit tracking goes. You can also have an edit session with an EGDB, but only if you use ... Versions: Concurrent streams of edits that are merged into one EGDB object. Every individual edit uses a short transaction and the ability to undo/redo/discard involves manipulating the table data through these short transactions, with various version control mechanisms used to isolate these potentially incomplete edits from other versions. This would be the "have your cake and eat it too" option if it weren't for the extra complexity brough by reconciling, posting, conflict detection etc. as well as making the underlying DB tables less performant than a straight list of features. My advice is to avoid thinking of "short" vs. "long" transactions and instead think about how you need to manage a piece of data over the long term: who needs to edit it, do they need to do so concurrently, is it worth giving them access to an undo stack in exchange for adding version management etc. If you field calculate 1 million records directly against an EGDB feature class with no undo enabled you're technically doing a "short" transaction, but you can probably guess that you're locking the database up far longer than if you move one point in a "long transaction" branch version.
... View more
03-06-2026
08:58 AM
|
1
|
1
|
432
|
|
IDEA
|
The Angular parse error makes me wonder: will standard Angular Control Flow Syntax work out of the box? If not that'd be my vote for getting conditionals in, seems better than writing yet another DSL on top of JavaScript.
... View more
03-05-2026
03:57 PM
|
0
|
0
|
195
|
|
POST
|
Not too familiar with the kernel functions, but if you project your raster into a coordinate system that uses meters that should make it easier to get square kilometers out. I'd go with an equal-area system appropriate for your study area that has the same datum as your current raster to avoid datum translations.
... View more
03-05-2026
11:24 AM
|
0
|
0
|
311
|
|
POST
|
I double-checked a few of my tools and yes, you want to get your file into arcpy.env.scratchFolder and then set a derived File output parameter to the full path to that file. I forget exactly how to configure the parameter during publishing but I don't remember any gotchas. You can even leverage the zipfile module to write your output(s) into a nice little file for the user.
... View more
02-26-2026
02:45 PM
|
0
|
0
|
798
|
|
POST
|
I've had success with making the file an output parameter, this outputs a URL in the old Web AppBuilder geoprocessing widget (I hope the ExB widget does the same thing, can't test that yet) and if you're doing manual HTTP work you should get the URL somewhere in the response data (sync) or you follow the URL trail from the final status update (async). What's the client you're using to run the tool?
... View more
02-26-2026
02:18 PM
|
0
|
2
|
804
|
|
POST
|
If the 4 parts each have their own table in the service, what you can do is have "repeat" sections limited to one record each, this gives the appearance of a question group but saves the data in those separate tables. This help page gives a quick overview of how to associate a survey with an existing feature service, as long as your main point layer and all 4 table layers are in the same service this'll work.
... View more
02-25-2026
10:56 AM
|
0
|
0
|
339
|
|
POST
|
If you're fine going outside of the Survey123 apps you can upload data directly to the feature service that comes with every survey form. Just make sure all your domain codes and whatnot are valid and you can do mass updates in Pro, a web app, etc. etc.
... View more
02-24-2026
01:17 PM
|
0
|
1
|
328
|
|
POST
|
I usually just generate the vtpk file in Pro, upload that directly to the Portal, then publish it out as a service. I'm pretty sure that should only keep one copy of the data around.
... View more
02-24-2026
01:15 PM
|
0
|
1
|
373
|
|
POST
|
An addendum: as your dataset grows you'll run geometry checks against the entire Pole dataset (at least, the entire set that the map has access to) and your edit performance will slowly grind to a halt. The usual fix is to run a Buffer on your anchor point, then use Intersects to reduce the available poles. You can also use Count to see if that intersection is empty and return an error to prevent adding anchors in the middle of the Atlantic.
... View more
02-12-2026
08:44 AM
|
0
|
0
|
586
|
|
POST
|
My faint memories of high school trig tell me something's wrong with how you're calculating the angle. Thankfully, nobody writing arcade has to remember how to do this right thanks to the Angle function. Replace the last few lines of calculations with Angle(referencePoint, nearestPoint) - 90 and you should be golden.
... View more
02-12-2026
08:38 AM
|
1
|
1
|
590
|
|
POST
|
Doing heavy actions inside Update Cursors like creating a new feature class is a bit buggy from what I remember. Fortunately there's a solution: don't! The only thing you're doing with those new feature classes is capturing a single feature and then using that to location select the input data. Instead, try using Make Feature Layer to make lightweight views into your data that you can select freely, this should avoid the issue you have and speed up your script by a good deal.
... View more
02-11-2026
04:46 PM
|
0
|
0
|
510
|
|
IDEA
|
Always annoying when you just need 2 or 3 columns from a giant table but you either have to screw around with the visible fields or copy out a giant field set and trim it down in Excel. This would be very nice!
... View more
02-11-2026
04:36 PM
|
0
|
0
|
270
|
|
POST
|
Is your script running against Pro's python environment or ArcMap's? If it's the latter then it'd explain why the Pro geodatabases are tripping it up. Easy way to find out is to throw these two lines at the top of your script, then check the output: import sys
arcpy.AddWarning(sys.path)
... View more
02-09-2026
12:01 PM
|
0
|
0
|
416
|
|
POST
|
Not an immediate fix by any means, but I suggest filing an Idea to get a "spinner" appearance for integer questions added to the forms. The teams have to reassess the form spec for other pending changes to Field Maps so this might be the perfect time to sneak something simple into scope.
... View more
02-06-2026
09:01 AM
|
0
|
0
|
273
|
|
POST
|
Another entry in the list of random ArcGIS features that keel over and die when they have to handle a GUID, one of the six-ish standard data types, glad you figured out a workaround at least.
... View more
02-05-2026
11:48 AM
|
0
|
0
|
602
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | a month ago | |
| 1 | 09-08-2023 10:07 AM | |
| 3 | 03-26-2026 08:11 AM | |
| 2 | 03-12-2026 01:41 PM | |
| 1 | 03-06-2026 08:58 AM |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|