POST
|
totally going to toot my own horn - the OP in that post said my solution worked. its towards the bottom of the page.
... View more
01-10-2020
11:33 AM
|
1
|
2
|
1736
|
POST
|
this poster had a similar issue! check it out: https://community.esri.com/thread/245774-parcels-with-no-functionality-when-i-click-on-a-parcel-all-i-can-do-is-copy-all-other-options-greyed-out
... View more
01-10-2020
11:22 AM
|
0
|
4
|
1736
|
POST
|
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
12-26-2019
12:45 PM
|
1
|
0
|
567
|
POST
|
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
12-26-2019
12:42 PM
|
1
|
1
|
2603
|
POST
|
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
12-26-2019
12:22 PM
|
1
|
5
|
2603
|
POST
|
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
12-26-2019
09:02 AM
|
0
|
7
|
2603
|
POST
|
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
11-12-2019
11:47 AM
|
0
|
0
|
2347
|
POST
|
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
11-12-2019
10:01 AM
|
0
|
2
|
2347
|
POST
|
hi cici, no offense but i've already figured out a solution to my issue. this comment is about three years old.
... View more
08-27-2019
12:07 PM
|
1
|
0
|
2093
|
POST
|
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
08-19-2019
07:14 AM
|
0
|
0
|
582
|
POST
|
Amir Bar-Maor why wasn't there more effort made to make sure terminology was the same between arcmap and pro fabrics?
... View more
08-19-2019
06:20 AM
|
0
|
2
|
582
|
POST
|
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
07-31-2019
05:11 AM
|
0
|
2
|
1159
|
POST
|
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
07-30-2019
02:59 PM
|
0
|
4
|
1159
|
POST
|
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
07-26-2019
11:33 AM
|
1
|
8
|
1159
|
BLOG
|
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
07-26-2019
07:18 AM
|
0
|
0
|
761
|
Title | Kudos | Posted |
---|---|---|
2 | 03-23-2022 10:04 AM | |
1 | 05-18-2021 06:02 AM | |
1 | 03-28-2023 11:29 AM | |
1 | 03-15-2023 09:14 AM | |
1 | 12-05-2022 12:27 PM |
Online Status |
Offline
|
Date Last Visited |
Wednesday
|