Latest Contributions by anna_garrett

you can also look at the plan table as you would any kind of table in arcmap! just open up your fabric and it's the table labelled "plans". you'll have to tell it to show you all the fields again, as far as i can recall, but it'll at least show you the name of the plan. ... View more

the plans correspond to a table in the parcel fabric where you can store record information. i use it to store subdivision and plat recording numbers, dates, notes about surveys, bizarre problems, just helpful information for the future.  if you're not the only person working on your parcel fabric, it could have been changed that way. if the parcels were imported from another parcel fabric, it might have retained the old PlanID that doesn't correspond to anything on your table. like i maintain a "scratch" fabric to sketch out subdivisions and surveys. it's a stop-gap solution to help me really visualize where everything goes without affecting my production data. i'll import those parcels using the save as XML/append file options in the parcel editor menu. if that's a workflow that ya'll use it could have easily occurred there.  ... View more

to see the PlanID: open the attributes table from your table of contents window click on "table options" in the upper-left corner select "turn all fields on" you should be able to see the PlanID field after that. it's easier to select your problem parcel and a couple of other properly responding parcels adjacent to (preferably ones abutting the problem parcel) and then using the "show selected records" option on the attribute table to narrow down what you're looking at. if all of those PlanIDs match, something else is wrong. i've done this before in the past to figure out what the heck is wrong with my parcels before as well: in the catalog: navigate to your parcel fabric expand the tree so you can see all of the individual points, lines, polygons (etc etc) feature classes that make up your parcel fabric add the polygon feature class to your display and navigate to where your problem parcel is select that polygon. inspect it carefully in relation to other surrounding properly responding parcels.  ... View more

can you see the parcel in the attribute table? i've run into this problem a few times and these are the causes that i can recall: there's something wrong with the parcel when it was created and the parcel has no shape.area or shape.len. this has happened to me before when i have complex remainder parcels or parcels where the fabric spontaneously generates a connection line in the new parcels.  the PlanID doesn't match the surrounding layer's PlanID - i did this by accident once by changing the PlanID manually in the attribute table for a neighborhood through the field calculator to a specific plan and typoing the PlanID.  ... View more

can you use the identify tool on the points? it will give you the OID of the parcel they're attached to and you can find it that way as well. i've run into this before in my LGIM fabric but it looks like you're not using that specific model.  ... View more

is this in arcmap or pro? if it's in arcmap, add the polygon feature class inside your parcel fabric and see if that underlying parcel got marked as historic by mistake or something like that. essentially you're looking for something in the table that makes the parcel that's there not draw correctly. examine the polygons surrounding it to make sure everything matches up in the table. you can't do this in the normal parcel fabric, which is why you have to go examine the polygon feature class. if it's in pro, i have no idea ... View more

hi cici, no offense but i've already figured out a solution to my issue. this comment is about three years old. ... View more

okay cool, i'm okay as long as there's an effort. i haven't even started to transition over to pro yet since i'm right in the middle of new subdivision season.  ... View more

Amir Bar-Maor‌ why wasn't there more effort made to make sure terminology was the same between arcmap and pro fabrics?  ... View more

when i came across easements similar to yours that don't show up on any of the documentation (plat, survey, metes & bounds description, etc) and i  make a placeholder parcel for it in my lots & units layer. i set up a plan for it with any relevant information and recording numbers for the ghost ROW. i don't cut it out from my tax parcels - which is what gets exported for public use - because it doesn't appear in the legal parcel description. it's just there for reference.  that's the really sticky part - like you'll have to make a determination on how to best handle that by your state's applicable laws and your office's purpose. i maintain what ESRI calls assessor parcels, so i'm pretty hard bound by legal descriptions. conflicts and issues like this are a total pain.  ... View more

ohhh man get ready to find like 20 years worth of mistakes. i recall finding mistakes that dated to before i was born (34 year old mistakes!!!!). if you have centerline data, you should be able to make a temporary "fix this" polygon by doing a select by location with your centerlines and parcel data. that should make the QA process go faster. ... View more

yeah. i found from talking to another office similar to mine that they migrated from shapefiles that were held in a topology and they had a worse time migrating than i did. they didn't have any COGO data or anything really to work with. when i came on in 2015 we migrated straight from the old coverages we'd been using for decades and apparently that's why we didn't have a boatload of problems. some of my issues were only unique because of the age of the software we'd been using.  don't forget that legacy systems have unique problems so a solution may have to be hammered out without specific help from the documentation. you got this. ... View more

i'd work on making sure your data is accurate before migrating over to a parcel fabric, which would probably require at least a GIS person and not a CAD staff.  you can also just start from scratch in a parcel fabric if you have all your original surveys. ... View more

i'm still trying to learn how to use my fabric in pro but this is what i've done in vanilla arcmap - the performance of the fabric went down significantly when i imported my ROW polygons and unless they were *absolutely* *perfectly* *aligned* with my parcels it didn't look for function right. so those are kept in a regular polygon FC under the fabric. i maintain a street centerline line FC in the same way. when you import a line FC like that, it gets converted into a .5' or 1' polygon and it was nightmarish.  anyway your townhome or landlocked parcels will be fine. the fabric will generate connection lines between the surrounding parcel and the interior parcel that keeps everything in line. what i did initially to test the landlocked or donut parcels (because i had the same concerns!) was just find the most complex part of my parcels and make it into a test fabric to see what it did. some of the documentation is murky and i just made a sandbox fabric to mess up and i could just delete and start over with no real tangible loss.  just as an aside, these are some things to watch out for if you have these master planned subdivisions that have huge sweeping curves and a ton of tiny lots: -MAKE SURE ALL YOUR CURVES MATCH EXACTLY!!!!!!! THEY WILL CAUSE GAPS IF THEY DON'T! -the fabric may generate rogue connection lines where they don't need to be when you're working block by block. i don't have an example handy - but if there's a multilot block that you're constructing from a parent parcel there's a chance the fabric will think it needs a connection line but it doesn't. i'm still not sure what causes it.  ... View more