Latest Contributions by Syvertson

‎09-28-2020

The database is a sql database and the format of that filed is numeric 14 characters and no decimal. See below. Every table that is in this database uses the same format for parcel number. I never once had an issue with this in ArcMap. Even though I used double for the field type in the spatial databases, they always respected the format of no decimal point. A better question that I have is "Why would the parcel dataset EVER need to add digits behind the decimal point? Thanks for all of this help. I really do like the parcel fabric, and ArcGIS Pro, but I am always running into little "gotchas" like this that just cannot be explained.

‎09-28-2020

Yes. I have to be able to link to a database that uses this format, which is exactly the reason why it is a problem when you start adding digits behind the decimal point.

‎09-28-2020

Thanks Xander. I understand now, but I would then need to find a different way to handle the problem I was trying to solve. For some reason when I am storing 50290115605026 in the double field, ArcGIS Pro is adding extra digits behind the decimal point. See below: How do I tell the database that I need to store only whole numbers that are larger than a "long" integer?

‎09-28-2020

OK.; This is exactly what I was trying to do. It must be something else going on. Here are some screen shots: What I am trying to do: Table structure: Error messages:

‎09-28-2020

I am trying to do something that is probably simple, but in reviewing the Arcade functions, I didn't find the one that will do this. I created a new field as an integer, and I now want to move contents of another field into it using calculate field. The other field is a double field type (even though all should be whole numbers).

‎09-22-2020

I am moving workflows over to ArcGIS Pro and some require the usage of attribute rules. I like the functionality, but I am very new to arcade. So, here is my latest challenge. I have a point feature that has X and Y columns for coordinates of the point. The feature is in North Dakota State Plane South, and if I use the code "return Geometry($feature).X" it will return the x coordinate in state plane feet. I want to auto populate with longitude. Suggestions?

‎07-14-2020

In the traverse tool, which I use a lot, you click "enter" to move from field to field while entering the cogo. When I am drawing outside the traverse tool and want to enter a curve, I right click and select "circular arc." When entering the parameters, I always accidentally use the "enter" button to move between the fields, like we do in the traverse function, and it ends my entry. I have to delete and try again. I wish there was an option to allow "enter" to be used to move through the three fields in the entry and after the third, it could commit the entry (sort of like the on screen constraints work for straight line segments).

‎06-08-2020

OK. I guess my usage is not typical. When I brought over the old fabric, I brought over whole areas that just need to be redone. So I deleted them assuming the points would go with, and then redrew them. now I zoom in and there are a lot of points from the old stuff that make everything "not so clean."

‎06-04-2020

Hello all. I am using the new Parcel Fabric in Pro, and am noticing a growing number of orphaned points. I know there were tools in the ArcMap based fabric to find and delete them, but I can't seem to find a tool like this in the new fabric. Can anyone point me in the right direction?

‎11-08-2019

I just found, what I believe to be, a glitch in the fabric. I am wondering if anyone else has experienced similar problems. Here is the glitch: After joining a table, I get strange errors when editing. Using the clip function, I get an error that the line must pass through the feature in two places, when it was passing through it correctly. Remove the join and try the same edit, and it works just fine. When rotating or moving a parcel, everything looks fine, until I click finish and it would then the parcel moves right back, but I get an indication that it was successful in the edit pane. This is demonstrated in the video (below):

‎11-01-2019

Amazingly enough, I stumbled into a solution. In the past, I had attempted to delete all lines and build the fabric and hoped it would attribute the record field. That did not work. I tried multiple times. So, I decided to try it differently. I delete all parcel lines that were not associated with a record. I selected all parcels that were associated with a specific record. I made that record active, and I then built the fabric, thinking that it would build just the highlighted records. It did build the highlighted records and attribute them with the appropriate record. But it also built the rest of the fabric. It associated all of those with the appropriate record as well. So, problem solved.

‎10-29-2019

Yes. I ran a build and it had no effect. It would build lines, but not relate them to the record for the parcels.

‎10-28-2019

I ran the "Create parcel record" tool and associated the parcels with the township from attribute table, and this solved the problem for the parcels themselves. This did not, however, add the parcel lines to the record. So I still have almost 100,000 errors for the lines not being associated with a record. Any ideas how to attach them? I figured out how to fix it manually, but it is way too many to go through like that.

‎10-01-2019

I am working in pro and trying to design a symbology for my own basemaps. My road layer has a field called "ZORDER" for the purpose of modeling roads. If roads meet and one road is supposed to pass under the other, it will be given a lower value in the ZORDER field. I assume the answer is in symbol layers, but it only gives options in relation to the drawn symbology, not another field. In the example shown below, The orange lines should pass below the yellow lines, but at another intersection it may be reversed. As you can see in the drawing, some went over and some under, seemingly randomly. Any ideas how I can do this?

‎09-27-2019

We do connect to our assessors database and tax databases, but it is kind of a "convoluted" process and would not work for this purpose. I think I will have to just make a dummy record for the purposes of cleanup work and then later deleting the dummy records and except in topology. Do you see any downside to this approach?

Online Status	Offline
Date Last Visited	‎01-13-2026 02:57 PM

My Ideas

Latest Contributions by Syvertson

Re: Convert Double to Integer (Arcade)

Re: Convert Double to Integer (Arcade)

Re: Convert Double to Integer (Arcade)

Re: Convert Double to Integer (Arcade)

Convert Double to Integer (Arcade)

Converting Coordinates with Attribute Rules

Circular Arc Entry in Parcel Fabric

Re: I need help deleting orphaned points

I need help deleting orphaned points

Parcel Fabric "Gotcha"

Re: "Parcel Must Have Record" Rule

Re: "Parcel Must Have Record" Rule

Re: "Parcel Must Have Record" Rule

Symbolize Overpass by Attribute

Re: "Parcel Must Have Record" Rule

Re: Enterprise Basemap with High Resolution Imager...

Query data using URL Parameters

Create "Zip" file in Model Builder

Re: Move Parcel Fabric

Re: Move Parcel Fabric