POST
|
All good points Amir, and sure I think more like a DBA, but some of my requirements cannot be fulfilled with the service as it presently is configured to work. At the moment, the way an Archive behaves limits me to a calendar representation of our data. Which I am sure for many people is fine. However, many changes to the land record, do not necessarily fall within the calendar year in which an edit could be reasonably applied. Further complicating that point, a lot of our data requirements have me posting 'stale' data for the public at large to consume for not just the current version, but past versions as well. Legally, certain changes to the property record can go back as far as 5 years, and in some limited scenarios, they can go back 10. Creating a View of those transactions outside a calendar, allows us to preserve the data for a tax year in which something was applied. We may have to change parcels in place in the Fabric, that had a change filed lets say today, but was effective for 2 years ago. While the service can easily show this change today, it is not great at having to present data that was for 2 years ago, and still show how that changed progressed to today, something I know that I have spoken with both you and @DanielStone about at length. Were I just showing people today information, I would not hesitate to just putting out a simple service as opposed to ETL, wouldn't argue that point at all, and if my reality was that simple, well, I wouldn't be talking about it here.
... View more
11-16-2023
06:47 AM
|
2
|
0
|
458
|
POST
|
@JohnFell Glad to see you guys are still working toward your goals in getting into the Pro Fabric. I can't speak to the 3.2 question (still testing it locally myself atm), but I can say that those two links from earlier do not 'completely' address your concern from what I recall. We've spent some more time with some of the Land Records group and a different individual in Services to flush out some more of the details in the SQL in the back end to deal with that. We've got a lot of things that happen with the View we've been working with the teams on from a bunch of runs at this. Some of our findings are editing workflow specific, meaning we could easily avoid some of the duplication or potential errors by being more mindful of our workflows. Some of my other findings, would suggest some interesting behaviors in the Archival methods as they exist presently. There are quite a few things that I could enumerate on this topic, but it would be a fairly lengthy list to post up here! Let me know if you want me to go through them.
... View more
11-15-2023
04:34 AM
|
1
|
0
|
518
|
IDEA
|
Presently, when you fire up the Enterprise Patch Updater for Server or Portal, there are limited settings available. You can choose a Proxy, or some basic installation directory locations. Due to numerous security reasons we have internally, we would like to limit where the Patch Updater is allowed to get these updates from. Without going into specifics, we have a need to be able to limit the countries of origin where these edge caches are being looked at to pull from. My option at the moment is to manually review the updates and grab the appropriate ones that I need (as this is still unblocked). Is there a way we can introduce some method to limit where the Enterprise Patch Updater gets its patches pulled from?
... View more
08-22-2023
12:24 PM
|
3
|
0
|
253
|
POST
|
Would like to know this myself, as we are getting ready to do environment upgrades soon, and if I can add time to the next iteration, so much the better.
... View more
12-01-2022
11:35 AM
|
0
|
0
|
2539
|
IDEA
|
@AmirBar-Maor I'll accept anything that helps the team out during their Traverse. Thank you for looking into enhancing the performance of the grid entry in general.
... View more
11-19-2021
05:15 AM
|
0
|
0
|
708
|
IDEA
|
We've been expanding our Parcel Types recently to include several layers for Administrative Boundaries now that we are working with 10.9/2.8. In total, we are adding an additional 18 types to our Fabric to support both Jurisdiction Boundaries, as well as their Annexations. Adding a Parcel Type works as you would anticipate. Input a Fabric, name a Feature, check the Admin Boundaries box, and you get two feature classes and their respective relates and Topology. What is not working for me, and perhaps for all of you as well, is if you are going to then prime and load your existing data into this newly created set of features. Since none of your existing fields in your data are going to be present when you first create these new features, you have to step out of the Add Parcel Type, and then go into Design and add those fields. If you were only adding one feature class, this would likely not be a big deal. If you are adding more than a couple, doing this process repeatedly adds a considerable amount of time to creating the Parcel Types you need. I have two suggestions/enhancements to this process. Allow the ability to select a Feature Template from an existing Feature Class, or allow the ability to add fields before Add Parcel Type executes.
... View more
06-21-2021
06:27 AM
|
3
|
1
|
727
|
IDEA
|
Amir, Thanks for getting back. The user that requested that functionality was wanting to have an option to do explicit curves as you understood it. Thanks.
... View more
10-04-2020
11:28 AM
|
1
|
0
|
1391
|
IDEA
|
In ArcMap, the Traverse grid allowed certain curve parameters before keying in the data. I'd like an option to use the "Classic" interface of the Traverse Tool for ease of working with curve data, instead of typing in various "shortcut" abbreviations while entering curve data. I've added the ArcMap Traverse window with one of the curve options for reference as an attachment.
... View more
10-01-2020
06:44 AM
|
9
|
3
|
1467
|
IDEA
|
In ArcMap, the Traverse Grid and Parcel Fabric grids did not auto-commit data every time I entered a new row in the Traverse. I would like the option to pause the auto-commit while entering the Traverse so that I could enter all the information before it draws. There are several members of my team who are rather proficient in entering Metes-and-Bounds, and this longer pause during the auto-commit is adding significant time to their keying of those descriptions. Imagine writing a COGO distance, then waiting 5-10 seconds for the line to make the loop back and forth from the database/feature service. Then do this again for dozens of lines. If you were to type too quickly, you end up creating mistakes that you then have to go back and edit, again, and still wait for the commit. Barring that, have the Traverse draw data locally instead of sending the information back to the feature service, the same way that the Links and Anchors do during an Alignment so that the grid works faster.
... View more
10-01-2020
06:36 AM
|
17
|
15
|
3320
|
POST
|
Raju, Exam Preparation Info from the GISCI Website has the majority of links you might need to get started with preparing for the Exam. There is also a Practice Exam that has recently become available: Practice Exam . A number of people have also written Quizlets (an app) to practice with. Good luck!
... View more
09-29-2020
05:56 AM
|
3
|
0
|
2138
|
IDEA
|
Larger edits in Branch Versioning workflows. These seem unavoidable when working with larger amounts of Land Records data. Think about what goes into making a subdivision for a moment. Create Subdivision lines. Build a Subdivision polygon from those lines. Points get created from these first two. Create Lot Lines. Build Lots. Points get created here as well. Duplicate Lots to Parcels (assuming they are the same of course.) This creates more lines, and points. A record is being generated if you are working within one in a Parcel Fabric. Don't forget about all those attributes you need to update! Now imagine you did this for 100 lots or more in this subdivision, and that you are not the only person working on similar projects within your Enterprise. When you have larger transactions like this one occur, things tend to get locked up when you send off for Reconcile/Post. If you have 5-10 people do this, the fact that they happen in a synchronous fashion, timeouts against the service start to occur, even if you have them set out as far as 600 seconds (10 minutes). No one likes to lose hours of work! If the reconcile/post became asynchronous, the risk of losing work could be greatly diminished. Barring that, is there any way that the Reconcile/Post can be done faster than it is currently? Please make the Reconcile/Post Process faster or asynchronous!
... View more
09-25-2020
06:43 AM
|
44
|
0
|
1504
|
IDEA
|
As I am sure many of you doing edit workflows in Pro are aware by this time, you get a status window when you Reconcile back. For whatever reason, there is no window for this when you Post. Leaving you with only three ways I know of something is still happening in the system. Look for the spinning wheel. If you look down at the bottom right of the screen for pausing or refreshing the map, you can see that the wheel is turning during longer Post-backs. Once a Post-back has gone through, the Map will flicker. Be an admin in your respective RDBMS environments, and look for long running transactions. This works for me just watching for Active Expensive Queries in SSMS, but there are likely similar methods for Oracle and PostGRES that I do not know. Please show a status Pop-up like you do for Reconcile.
... View more
09-24-2020
06:02 AM
|
35
|
2
|
1862
|
Title | Kudos | Posted |
---|---|---|
1 | 11-15-2023 04:34 AM | |
2 | 11-16-2023 06:47 AM | |
3 | 08-22-2023 12:24 PM | |
3 | 06-21-2021 06:27 AM | |
3 | 09-29-2020 05:56 AM |
Online Status |
Offline
|
Date Last Visited |
01-24-2024
10:48 PM
|