|
POST
|
The URL you feed into pulldata("@layer") can accept most URL parameters that work with the REST API's query endpoint. Try adding returnCentroid=true as a parameter so the polygon is transformed into a point. If that fails @AustinAverill's method should work well.
... View more
03-27-2025
10:22 AM
|
1
|
1
|
1848
|
|
POST
|
Thanks for all the extra context, my company hasn't worked with this tech yet. Might be a long shot, but could you model each microduct like a ribbon cable to work around this limitation? Or is the model not good enough for that either?
... View more
03-27-2025
10:08 AM
|
1
|
0
|
1397
|
|
POST
|
ArcFM has fibre capabilities now, might be worth getting a rep to run a demo for your company. Have you played around with the standard Utility Network setup? You might be able to model the strand to conduit associations you need without extra software.
... View more
03-26-2025
01:24 PM
|
0
|
2
|
1426
|
|
POST
|
If the issue is just copy-pasting those last few empty items: alterFieldsDescription = [
['FIELD_1', 'newName_1'],
['FIELD_2', 'newName_2'],
['FIELD_3', 'newName_3']
]
alterFinal = [x + ["#", "#", "#"] for x in alterFieldsDescription]
arcpy.management.AlterFields(featureClass, alterFinal)
... View more
03-24-2025
12:53 PM
|
1
|
0
|
3586
|
|
IDEA
|
This would be a great QOL change, as long as there's a popup explaining that the layer can't be regrouped into a map service after they're split up.
... View more
03-21-2025
08:20 AM
|
0
|
0
|
1397
|
|
POST
|
There's probably some fancy mathematical property to combine this into one operation, but I'm no mathematician so all I can suggest is: use the OR operator to combine multiple bit tests together: MOD((error_codes / 4), 2) = 1 OR MOD((error_codes / 32), 2) = 1
... View more
03-20-2025
03:18 PM
|
0
|
0
|
2923
|
|
POST
|
You can check if a certain bit is set using this standard query: MOD((error_codes / n), 2) = 1 Where n is 2 to the power of whatever bit you want to test. E.g. to see if the 4th bit is set, that's 2 to the power of 4, or 16, so the final query is MOD((error_codes / 16), 2) = 1.
... View more
03-20-2025
02:10 PM
|
0
|
2
|
2935
|
|
POST
|
When I tried running the code I got 20 processes in (and 200-something VSCode subprocesses) and I was using almost 10 GB of RAM! If you're doing so much number crunching that you need 400-something concurrent processes you need to find a Python library that manages its own thread pool (polars is my go-to, numpy might also work here?). Failing that, you can rewrite your program to import arcpy after every future has resolved. This cuts the size of each runtime process from ~200MB to ~35MB on my machine, which kept my process below 8GB (and it'll probably run faster overall as you're writing all the data in a single cursor).
... View more
03-20-2025
01:39 PM
|
0
|
1
|
3156
|
|
IDEA
|
Due to the lack of portal view layers for registered feature services (or the ability to proxy access to restricted layers through a map's/app's sharing options) I often have to create multiple feature services with minor adjustments to ensure the correct group gets the correct access. This leads to the following dilemma: If every service is dedicated with 1 minimum instance, there's a high static load even if a small number of user types are accessing the data. Cut the minimum count to 0 and now every new group has a terrible experience as their service fires up. Setting the time this instance stays alive is an impossible tightrope act as user activity varies day by day, so it's either active too long or inactive too often. The shared pool is unsuitable for this type of service as this project is now at war with every other project. My proposal: allow admins to create their own shared pools (with their own max core counts, max active services etc.) and allow users to choose if they want to publish to these shared pools or the default one. Admins can now balance server load at the pool level and the pool can balance service access using its work balancing methods. This isn't a trivial addition to the platform but I think the efficiency gains in larger deployments are well worth it.
... View more
03-20-2025
01:19 PM
|
0
|
0
|
565
|
|
POST
|
If you're validating more than one survey question you'll want to store the pulldata results in a hidden question, then extract answers from the JSON object it returns in your "constraint" column, something like: . >= pulldata("@json", ${previous_survey}, "attributes.meter_level") Or whatever your field names are, you get the idea.
... View more
03-20-2025
01:07 PM
|
0
|
0
|
2094
|
|
POST
|
You can combine the pulldata("@layer") function with some additional URL parameters such as orderByFields to sort the results appropriately. That way the data you pull (which is the first record returned by the query) will have the previous results, which you can extract with further pulldata calls and stuff into your comparison functions.
... View more
03-20-2025
12:53 PM
|
0
|
5
|
2126
|
|
POST
|
Unless something's gone sideways, closing the widget should trigger a re-render, which passes the updated state into the widget. Try adding an effect that has props.state as a dependency and it should only fire when that changes. If you need to explicitly look for a change instead of blind-firing on a certain state you can try something like this SO post.
... View more
03-20-2025
12:46 PM
|
0
|
0
|
3180
|
|
POST
|
Ah, found it, it's props.state which is a member of the WidgetState enum. To illustrate what a mess finding this was: functional/pure widgets have no state beyond what you define, what's yoinked from a data store, or what's passed down through the props. All standard widgets take an AllWidgetProps object, which is the sum of WidgetProps and WidgetInjectedProps<T> (where T is the config object?). Buried in the injected props is the RuntimeInfo object which is where the state is stored, presumably because all of this info is coordinated by ExB and drilled into the widgets to keep a nice state tree. So yeah, easy, all you have to do is keep half of the jimu-core types in your head and you can find anything!
... View more
03-20-2025
11:45 AM
|
0
|
4
|
3201
|
|
POST
|
ExB widgets aren't unmounted when you close the widget, they're just hidden. This is normally where I would say how to get that state but the API reference makes it incredibly difficult. You might be able to crawl through this example widget to find an answer, although I think this is more concerned with checking other widgets' states through the redux store.
... View more
03-20-2025
10:57 AM
|
1
|
7
|
3227
|
|
POST
|
The hidden geopoint should be a distinct question, then a separate question has the pulldata call to extract whatever info you need. Note that if you're trying to get the polygon data from the parks to use as your form's spatial data, you'll also have to bind the hidden geopoint to the "null" esri type, otherwise you'll get errors due to the multiple spatial questions.
... View more
03-19-2025
02:26 PM
|
0
|
0
|
2233
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Tuesday | |
| 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 |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|