Latest Contributions by Zeke

Using the LGM Parcel Fabric, I successfully imported our subdivision layer into the fabric. But getting an error trying to import parcels: There are topology errors in the data selected for loading. Topology is not valid for import into parcel fabric. But there aren't any errors when I check the Error Inspector. Where are these alleged errors, and how can I fix them when I can't find them? [edit] Fixed, but don't know why. In ArcCatalog, I validated and then generated an error summary on the topology in ArcCatalog, and found one error. Back to the map, and searched for that specific error ("Must Not Intersect..."). The error showed up that way, when it didn't under search for all errors. The error was in a very small area, scale = 0.1 feet. Maybe a bug? ... View more

Our current non-fabric parcel polygons have attributes for address, with all the usual geocoding fields such as suffix, direction, etc, as well as owner mailing addresses. The Parcel Fabric schema in the LGM doesn't appear to have corresponding attributes. I know I could add them manually before importing the data, but is there another way the LGM implements this? I see a dataset for Address with point features, but that wouldn't appear to be associated with parcels. I also see maps & apps for addressing, but nothing mentioning addressing under Land Records on the website. Maybe (probably) I'm missing something. Any ideas on which way I should be heading with this? Thanks. ... View more

I have two polygon layers, parcels and subdivisions, but only working on parcels now. I'm running into what I think is a problem validating topology prior to loading it into a parcel fabric. This is my second set of test data; I was able to get the first set into a parcel fabric with help from a number of folks here (thanks again!). First I validated the parcel polygon layer against itself using the rules Must Not Overlap and Must Not Have Gaps. Then I created lines from the parcel polgons using Features To Lines. Okay so far. Then I added the six rule topology described in step six, page 12 of the white paper "Loading Data into a Parcel Fabric". Everything checked out except the fifth rule - "[Line feature class] Must Not Intersect Or Touch Interior". Every parcel line that shares a boundary with another parcel shows up as an error - 1067 of them (see attached). This can't be right. I don't recall this error with my first set of data, but maybe I did something differently this time. Don't know what, though. Any ideas on what's going on? Thanks. ... View more

I'm unclear on what the difference is between lots and tax parcels. In the video I watched on Bloomfield Twp. editing, they appeared to represent the same spatial area. The city I work for doesn't handle taxes; that's all done at the county level, so we don't use tax parcels. Our areas consist of subdivisions, lots and outblocks (parcels not in a subdivision). Lots and outblocks are stored in the same Parcels layer, but with different attribute values to differentiate them. Subdivisions can also have areas called tracts, Parcels records that aren't actually lots (usually parks, drainage, or areas planned for lots in the future). In migrating to a parcel fabric, I might add blocks as well. In reading the Loading Data... white paper, the PLSS system appears to be used, but not sure it's required. We don't use it in Texas, at least in this area. We use metes & bounds measured from known survey monuments. 1. What is the difference between lots and tax parcels, and are both required? 2. Is the PLSS required, or can we continue with the system we have? Thanks! Sure I'll have more questions as the process continues. ... View more

I'm creating a topology with parcels and subdivisions to learn how to create and use topologies, with the eventual goal of migrating to a parcel fabric. Most, but not all, parcels are in subdivisions; subdivisions are usually, but not always, contigous with other subdivisions (platting subdivisions wasn't required until a few years ago, and thare are quite a few free standing subdivisions). Both parcels and subdivisions are polygons. My question is what topology rules are most appropriate for this arrangement? I'm currently trying: Subdivisions: Must Not Overlap, Must Not Have Gaps Parcels: Must Not Overlap, Must Be Covered By (Subdivisions) I mark parcels that aren't in a subdivision as exceptions, but some parcels have an error where they should be in a subdivision, but part of their area is mistakenly drawn outside the subdivision, a Must Be Covered By (Subdivisions) error. The only right-click fix for this, Create Feature, creates a new subdivision from the entire parcel, which is clearly incorrect. If it created one only from the parcel area in error, which I could then delete, that would be fine, but it doesn't do that. I can fix this manually ok, but not sure if Must Be Covered By (Subdivisions) is the correct rule. The Help page also lists: Area Boundary Must Be Covered By Boundary Of, but this sounds like the subdivision must be filled by parcels, when there are actually streets, rows and other, non-parcel features instead. There's also no fix listed, so I assume this would be a manual fix situation. Also, this marks all parcels in the subdivision, but not sharing a boundary, as errors. While they could be marked as exceptions, this would be a lot of exceptions. Sorry for the long explanation, but am I on the right track for rules and/or fixes? Thanks. ... View more