Latest Contributions by LarryGaudieri1

I'm not a surveyor but having worked with / for them for over 20 years there are a couple approaches you could take. According to Wattles ("Writing Legal Descriptions", 1979), monuments cited or existing physically hold over everything. So, if the record data had "calls" to a right-of-way or any other cited / recorded land corner or line will hold over distance and direction. Next is distance. Distance is weighted over bearings particularly because of objectivity in portions of the basis-of-bearing or because of contrasting adjoining descriptions disagree. So, if any of your adjoining parcels are cited within one of the non-closing others, and one of them is closing within a reasonable error, then hold that parcel as described to test better alignment or fit.  This is one of the primary elements associated with raw record data requiring cogo to prepare parcel fabric data. It won't always be correct. In your traverse editor there are options to adjust a polygon and the results can be evaluated to see if they'll still agree with the rest of your fabric. In reality, the parcel is closed by 4 bounding monuments of some type. The misclosure is due to insufficient calculations or a scrivener's error  ... View more

Mike and all. Last week ESRI sent a Land Records Professional Services person to look at our parcel fabric. Since my last post we've tested 2 SQL server FGDB's each containing one each version of our fabric in both GEOMETRY and BINARY. We tested one-for-one edit tasks and recorded our results. Of course, you are all aware of the latency within GEOMETRY but I discovered that the fabric performs much better when it is autonomous in it's own DB. Also, Anna speaks rightly about DB maintenance.  Additionally, i recall the guy mentioning that 10.4 (DB & Desktop) is the last version that will be stable with BINARY. 10.5 was said to have possessed 2 bugs of which the fixes did not restore 100% stability. His advice was to skip to 10.6 for both server and desktop. Mike mentions above, moving to GEOMETRY in 10.5 should alleviate latency issues in editing. He did not see any problems with keeping a dataset within the 10.4 release as a production workspace until 10.6 is rolled out. Here is the surprising this I learned: It was recommended that for near every fabric related task, one should create a version, execute said tasks (minor or extended edits, parcel migration or imports), reconcile and post, then delete and recreate a version for the next tasks. In multi-editor environments, we are reconciling and posting multiple times a day with daily compress, spatial index refresh and other tune-ups at DB level. We're looking forward to adopting some of these best practices and seeing positive results.  ... View more

Hi Mike, did you ever translate your fabric data to SDEBINARY? We had good success with local workstation performance but our DBA would like us to return to the ST_GEO. We are due to have that happen this week. This time we are reserving a server-side FGDB exclusively for our fabric to see what happens when the indexes and domains are not mixed with other FC's in a DB and how effective it will be to run index delete and rebuilds, compresses, (which occur maybe at least once during a work day as well?) and reconcile and posts (if any edits are not pushed up)) With ArcGIS Pro, I cannot say one-way-or-the-other because we weren't aware of any ESRI solution at the time but we've not tested yet. ... View more

I know it was a regressive solution but I'm not privy to server characteristics in that department. I provided ESRI's docs on implementation and trusted that would be done but as soon as we went to edit, all systems basically locked. Someone added another 4GB chip to my PC and it helped but once I suggested the regression, it was flying. So, not sure what we will do going forward. ... View more

Thank you Jim! Looking into your solution. Appreciate the help. ... View more

Mike, I don't work to closely with IT-GIS but I believe it's SQL and version 10.1?  ... View more

Jim, did you get an answer elsewhere or are you still experiencing severe latency? We experienced the same when we loaded our fabric to SDE. I read an article and found that there are two geometry types within the server environment; ST_Geometry and a binary form (of which I heard that ESRI is phasing out). We moved all of our data to the binary form and it was like night and day. Hope this helps. ... View more

Hey Mike, yeah....the points originated in SPC....trying to not have to bring the service down, reproject and republish....any JSON that can put them in geographic? ... View more

Hi Kelly, thanks for your response! Yes, someone inadvertently deleted about 10 points from a service in which there wasn't yet a back-up in place. The features had global ID's tied to a related table hosted in agol. So, that's the picture at this point. ... View more

Johnathan, Thanks for your reply (Mike, thank you but we're not using receivers). I've read the 'Understanding Survey123's custom URL Scheme' before posting and I understand '&center={CoordField}' but the question remains for me is how do I calculate the lat & long values to a feature service? I used the field calculator online and it was pre-populated with the ability for X and Y but the results look more like SPC for my zone. I haven't done anything special to enable a projection (except that maybe the original data was published from one) so, I'm still a little stuck. I'd like not to have to republish this service so can anyone speak to this? Thanks in advance. ... View more

Amir, Thank you for your reply and update. I was not aware of any code for that. Can you elaborate or provide a link for direction? Thanks ... View more