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
|
12
|
754
|
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
|
311
|
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
|
381
|
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
|
323
|
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
|
375
|
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
|
647
|
POST
|
Perfect! I'll keep it enabled then! Makes life much easier being able to search for things!
... View more
12-06-2023
10:40 AM
|
0
|
0
|
357
|
POST
|
What would be considered large? I have two eGDBs with probably ~150 feature classes between both of them. All of them hold datasets at the county level. Nothing globe spanning.
... View more
12-06-2023
10:23 AM
|
0
|
1
|
363
|
POST
|
My options look a bit different than that. Either way, though, I was aware of the location. My primary question is if there is any reason I SHOULDN'T enable. Since it is disabled by default, I figured that there must be a reason. I just wanted to make sure there weren't any potential performance issues that could result from having it enabled.
... View more
12-06-2023
08:39 AM
|
0
|
3
|
375
|
POST
|
By default, the option is off. I'd like to cut it on because it would be nice to be able to use the search function in enterprise geodatabases. But I wasn't sure if there was a reason it was off by default. I don't want to enable it, forget I did it and then find out about some weird issue caused by it a few months from now! Thank you for any information you can provide.
... View more
12-06-2023
05:05 AM
|
0
|
6
|
421
|
POST
|
It's a one to many relationship and I did set it up in Pro.
... View more
11-28-2023
10:06 AM
|
0
|
2
|
288
|
POST
|
Can confirm that this is a bezier curves issue. Had it myself in the past. One area of our parcel dataset had bezier curves in it. I went and manually converted them to true curves, deleted all the extra points and lines that were created, and it completely resolved the issue.
... View more
11-28-2023
08:09 AM
|
0
|
0
|
222
|
POST
|
I have an AGOL feature class that has a relationship class between a polygon layer and a table. The table contains case numbers that are associated to each polygon. I would like to configure experience builder to search for those case numbers, select the associated polygon, and then zoom to it. Unfortunately, I can only get two-thirds of the way there. I have gotten the search configured to use the table as a source. I have an action configured to select the related polygon of the selected table entry that was selected via the search bar, but unfortunately, I can't get it to zoom to the selected polygon, despite having a map trigger set up to zoom to that layer. Here are the settings I have: Search Widget settings Framework settings for selected the related polygon Map settings to zoom to selected polygon Any ideas why this doesn't work? I have gotten it to work on feature classes that don't have a related table. Is it just not possible on a feature class with a related table?
... View more
11-22-2023
07:30 AM
|
2
|
2
|
411
|
Title | Kudos | Posted |
---|---|---|
1 | 2 weeks ago | |
1 | 3 weeks ago | |
1 | 02-22-2024 07:57 AM | |
1 | 4 weeks ago | |
1 | 03-20-2024 08:41 AM |
Online Status |
Online
|
Date Last Visited |
4 hours ago
|