|
IDEA
|
How this extremely basic quality of life feature has not been added yet is crazy. My organization doesn't even use AGOL much, but our directory is still cluttered because some dashboards and apps can contain 10-20 individual components. Having the ability to better sort that data is crucial.
... View more
02-16-2024
02:39 PM
|
0
|
0
|
4061
|
|
IDEA
|
How this extremely basic quality of life feature has not been added yet is crazy. My organization doesn't even use AGOL much, but our directory is still cluttered because some dashboards and apps can contain 10-20 individual components. Having the ability to better sort that data is crucial.
... View more
02-16-2024
02:38 PM
|
0
|
0
|
1799
|
|
IDEA
|
Amazing! Can't believe I missed this. I'm currently on 3.3 and usually read the patch notes. This is amazing and is going to make my life so much easier. Thank you!
... View more
02-15-2024
07:12 AM
|
0
|
0
|
2937
|
|
IDEA
|
I frequently find myself cycling between different imagery layers for the same location. This means constantly having to cut imagery layers on/off or just suffer the consequences of increased draw time due to all the active rasters. It would be nice if there was an alternative type of group layer that would only allow one item within that group to be active at a time. For instance, you have a group of imagery for 2021, 2022, and 2023. You have 2022 active. You enable 2023, and the 2022 layer automatically cuts itself off. Would be a very helpful quality of life option to have that I could see myself using in many different circumstances.
... View more
02-15-2024
07:05 AM
|
2
|
4
|
2958
|
|
POST
|
We initially had a single, catch-all record for our fabric but were experiencing a lot of long draw times and other random bits of weirdness. One of the suggestions I got from our consultant was that having one record that was essentially the extent of the entire county could be causing delays because it would be looking at the topology for the whole county rather than just the smaller individual polygons. We pretty much followed your steps, except in the expression builder we added the parcel number. So ours read like "A-01-002 | Legacy data - source unknown." That way, each individual record was still only the size of a regular parcel. This completely resolved our issues.
... View more
02-14-2024
04:21 AM
|
1
|
2
|
3692
|
|
POST
|
This was precisely the issue I ran into. It doesn't happen often because I try to stay away from shapefiles, but it is unavoidable with some of our departments, and it drives me nuts having to decipher the codes.
... View more
02-09-2024
02:54 PM
|
0
|
0
|
3123
|
|
POST
|
Is there any reason not to use the fully qualified attribute in the 'Code' column as well as the 'Description' column? I have been using numeric codes for a while now but they are sometimes a bit annoying to deal with. Specifically if I ever export the data. I'm contemplating just converting the field to a text field and using the fully spelled out attribute for both columns. Are there any real reasons not to do this?
... View more
02-08-2024
05:20 AM
|
2
|
14
|
6950
|
|
POST
|
I only have a small organization to worry about with ~ 200 items or so between all users but I'm still fed up with how cluttered our AGOL organization feels. The lack of subfolders is just baffling to me. I'm sure there is probably a reason it hasn't been implemented, but having only one folder level to work with is just awful. I have one dashboard that is a combination of 5 other dashboards. Trying to remember which one I need to edit every time is just annoying. I've started including a prefix of "1 - " on the main one and "2 - " on the sub-dashboards, but if I had additional folders, I could group the sub-dashboards together and leave the primary one up one level, leaving only one option to work with, but just not possible with the current implementation. Does anyone have any tips for better organizing your AGOL data? Any good white pages on effective strategies for cleaning up your org's data?
... View more
02-02-2024
12:53 PM
|
0
|
1
|
1787
|
|
POST
|
We currently have an enterprise database that contains nothing but old raster data. This setup predates my time here but I've kept it going because I haven't had a compelling reason to change it. The mosaic datasets are pretty large (most are over 1k high resolution images). I'm examining our current practices and looking for potential ways to increase efficiency and this got me to wondering if there is a reason to have it in an eGDB at all? Is there a performance impact on keeping those rasters in an eGDB? The rasters are never edited aside from when they are created. So I'm not sure what benefit there is to it being in an eGDB vs. a regular file geodatabase. Compounding on that, I'm wondering if it wouldn't be a good idea to explore the option of using a tiled service to share the imagery out to the organization. How are you guys handling your large raster datasets these days?
... View more
02-02-2024
05:38 AM
|
0
|
3
|
2879
|
|
POST
|
This also happens in cases where a portion of a neighboring parcel is ceded to the current record like in the example below: After doing the align and clip, the stated area and stated area units was nulled out of TP D 02 023B. This is annoying because I then have to cut on the historic layer to find out what the acreage for that parcel was and then figure out the new acreage. I'm not 100% certain, but I thought on other parcels, when something was clipped out of it, the area that was removed was automatically subtracted from the stated area of the parcel it came from. I could be mistaken on this. Either way, I'd rather it do nothing if it is only going to <Null> out the area fields and make me have to dig them back up.
... View more
01-19-2024
06:16 AM
|
0
|
0
|
1511
|
|
POST
|
I mainly went with the clip in this instance because it would have been substantially quicker than deleting and redrawing lines on a different record. I just found it odd that it cleared out the stated area for those parcels. Seemed like an unintended behavior but I could be wrong.
... View more
01-17-2024
07:30 AM
|
0
|
0
|
1563
|
|
POST
|
In the image below, parcels 25B, 15B, and 14B (Selected) had a boundary that was just completely incorrect. Not sure where it came from, to be honest, because I have been unable to find a We got a new plat in for surrounding parcels (the red ones with COGO) so I drew those in. Since the boundary was so wildly inaccurate I just figured that I would clip that area out, rather than aligning it since there were far too few points to do so and it was too far away to make the align features point feasible. After doing the clip, however, the stated area and the area unit of those three parcels was nulled out. Those two fields were set to <Null> for some reason and I can't figure out why. Is this an expected behavior? I've attached a short gif that showcases the issue. Please let me know if I am missing something. Thank you!
... View more
01-16-2024
07:33 AM
|
1
|
3
|
1835
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 5 | 12-19-2025 11:10 AM | |
| 1 | 10-02-2024 07:04 AM | |
| 1 | 05-23-2024 02:54 PM | |
| 1 | 07-29-2025 01:09 PM |
| Online Status |
Offline
|
| Date Last Visited |
17 hours ago
|