|
POST
|
Haven't tried something like this myself, but combining the Extent, Polyline and NearestCoordinate functions might work.
... View more
11-14-2024
08:42 AM
|
0
|
0
|
543
|
|
POST
|
There's a lot of "it depends" here but the RMS fields are the must have fields, there's virtually no reason to bother with GNSS metadata without them. ESRIGNSS_POSITIONSOURCETYPE is also a big one, this is what confirms that your users are using the equipment. The DOP data is less useful in my experience, but I'm sure someone who's spent more time with GNSS workflows can correct me here.
... View more
10-31-2024
03:57 PM
|
0
|
1
|
2188
|
|
POST
|
On the item page for a vector tile service, there's a "Rebuild Cache" button that regenerates all tiles based on the referenced data. This calls into the "Manage Vector Tile Cache" GP service in the system caching controllers which does all the heavy lifting. Unfortunately, I can't find a way to call this service using the REST API. I either get an invalid token error on the initial job submission, or I get "ERROR 001359: Failed to connect to the server." in the resulting job's messages. Has anyone managed to get this workflow functioning? Do I keep trying with the GP Service or is there a better way?
... View more
10-31-2024
01:50 PM
|
0
|
0
|
818
|
|
IDEA
|
Configuring maps in the designer offers a "Collecting new features" option that changes how the app behaves when a new feature collected. I would like to see this option duplicated and tweaked for editing features as well. My org has encountered many users who edit an existing line or polygon and accidentally fat-finger a new vertex because Field Maps enables geometry editing by default, it would be great if we could disable this behavior.
... View more
10-31-2024
11:45 AM
|
3
|
3
|
3555
|
|
IDEA
|
Many vector tile services published to ArcGIS Enterprise can submit a cache rebuild job through the item's options. This is very easy and convenient, but it requires a user to click a button. It would be fantastic if these job submissions were exposed through the Python API as many vector tile caches require frequent rebuilding, and the less REST API interface code I have to write & maintain the better.
... View more
10-31-2024
09:18 AM
|
0
|
0
|
599
|
|
IDEA
|
At first thought, the easiest solution is to pin the required Python versions to the supported versions of Pro when the Conda package for the esri channel is built. The Pypi and non-esri channel Conda packages can continue to list a wider range of Python versions as that's not what Pro's package manager will look for.
... View more
10-31-2024
08:57 AM
|
0
|
0
|
1454
|
|
POST
|
If you have edit tracking enabled on the feature service (along with the tracking fields) that should log the time the service starts processing the transaction. If this isn't the case please report back, that'd be good info for my team to know as well.
... View more
10-31-2024
08:27 AM
|
1
|
2
|
1369
|
|
POST
|
Multiprocessing spins up entire Python runtimes and passes arguments from the current runtime into them. This necessitates data serialization via pickle, and virtually none of the arcpy objects that refer to non-Python data structures meet that requirement. You'll need to redesign your worker tasks to open their own copy of the project to extract the layout, which might work, but could also lead to locking issues that necessitate further fixes. In general, nothing in arcpy was designed to handle more than one thread in one process, so don't be surprised if you have to abandon multiprocessing.
... View more
10-29-2024
12:53 PM
|
2
|
1
|
1800
|
|
IDEA
|
CSV files have an effectively unbound length per field which is why dumping them straight to your EGDB picks that data type. You'd be better off extracting the data to an intermediate table in a File or Mobile Geodatabase where you can clean up the data and schema before loading it into your EGDB. If you're genuinely concerned about database performance you'll want to prep your schemas by hand, then use Append to transform the CSVs into the new format.
... View more
10-28-2024
01:08 PM
|
0
|
0
|
497
|
|
POST
|
Try flipping back to DEFAULT and changing the entry_note to a brand new value, does that prompt a conflict?
... View more
10-25-2024
10:49 AM
|
1
|
1
|
1200
|
|
POST
|
This should be possible with a bit of arcpy, look into Cursors and the Geometry objects.
... View more
10-25-2024
10:45 AM
|
0
|
0
|
874
|
|
POST
|
Excellent, that's progress! If your relationship is working, it's possible you don't have any features. You should add a guard by checking if the Count of the relatedRecords is zero and returning early, but if your test data should return a related record then sort out your relationship query before you do that, otherwise you'll bury the true issue. Good luck!
... View more
10-25-2024
10:42 AM
|
0
|
1
|
3217
|
|
POST
|
Sadly no, and there's no news of a multi-choice domain type on the horizon. In this case you'd need a many-to-many relationship class between the easements and each of the choice tables, then do some stuff with calculating data or attribute rules into a redundant field to get the final table.
... View more
10-24-2024
12:47 PM
|
0
|
0
|
1613
|
|
POST
|
One-to-many relationship classes should work here, but something that works in ArcGIS Pro might fall apart once it gets into a server based workflow due to edit tool limitations. It looks like you just want to tag every easement polygon with an Owner and Type, with a set list of options for both. In that case you might want to use Coded Value Domains to lock those options in, then you can filter on those two fields instead of trying to do relationship-based selections.
... View more
10-24-2024
11:42 AM
|
0
|
2
|
1647
|
|
POST
|
From my testing, replica synchronization (i.e. what offline areas use to update the feature service) appears to attribute rules as series of individual features to C/U/D. If FeatureSetByName is reading the data outside of the current transaction, it'll just see the pre-sync snapshot which will not include new features or changes to those features. If it's reading data from within the current transaction, it might see the other operations but it might not, depending on the execution order, so you should always assume it can't. The safest option is to assume that this type of query could or could not contain the current feature; therefore, always read/modify the input feature in addition to what you get from the query, but also assume this could result in a duplicate action and guard accordingly. This will cover both standard and sync updates. If this'll bloat your scripts too much, test how the rules behave in your environment from a variety of clients, offline and online.
... View more
10-24-2024
11:36 AM
|
0
|
1
|
931
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 05-24-2023 11:47 AM | |
| 2 | 04-09-2026 11:36 AM | |
| 1 | 09-08-2023 10:07 AM | |
| 3 | 03-26-2026 08:11 AM | |
| 2 | 03-12-2026 01:41 PM |
| Online Status |
Offline
|
| Date Last Visited |
Friday
|