|
POST
|
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
09-06-2012
11:45 AM
|
0
|
0
|
3061
|
|
POST
|
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
09-06-2012
06:47 AM
|
0
|
2
|
767
|
|
POST
|
Please disregard. Posted in General Questions forum, unable to delete or edit here.
... View more
09-04-2012
05:02 AM
|
0
|
0
|
565
|
|
POST
|
If it's the chord direction you're missing, you can figure that out yourself if you know the start and end point of the arc. Just snap a line between the two arc endpoints, rightclick the line and click on direction/length. This will give you the chord direction. We have to do this when the surveyors give us bad measurements.
... View more
08-27-2012
01:38 PM
|
0
|
2
|
3230
|
|
POST
|
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
08-27-2012
08:19 AM
|
0
|
1
|
2925
|
|
POST
|
I think you can link the Excel table in ArcMap rather than embed it. It should update in the map as you update Excel. Not sure if it refreshes automatically when you update the worksheet or if you'd have to do that manually, but a possible option.
... View more
08-22-2012
12:30 PM
|
0
|
0
|
752
|
|
POST
|
Not sure if you have time to implement this, also unclear if this displays resulte the way you're asking, but ESRI has an Elections module in their LGM framework. It has an Election Results app. Never used or tested it, don't know if results are on the fly or not, but maybe worth a look.
... View more
08-22-2012
08:10 AM
|
0
|
0
|
752
|
|
POST
|
Thanks Chris. I've gotten test data into a parcel fabric, but haven't got as far as the LGM schema yet. The LGM model I downloaded wouldn't open the parcel fabric properties at first, although just now it seemed to work. Hmm. I will check it out. There's an LGM class coming up down in Austin next month at TNRIS, maybe I'll get to go to that.
... View more
08-21-2012
05:33 AM
|
0
|
0
|
4550
|
|
POST
|
As long as the data stays in a gdb field names should be fine, maybe with the table name prepended. If Scott exports to a shapefile as he says, the table will be a .dbf file, which I think is limited to ten (maybe thirteen?) character length field names. He could set up an alias, but can't get around the length limit for a .dbf file.
... View more
08-21-2012
04:54 AM
|
0
|
0
|
1200
|
|
POST
|
I might be misunderstanding your question, but I think this may be correct behavior. Using the table name as a prefix is a standard used in many db designs, particularly on joins. This is primarily to differentiate field names that may be the same in the original and joined tables. I'm not aware of any setup that does this for just identical field names; it happens for all fields, at least in the joined table(s). The truncation is due to the .dbf files in shapefiles having (I think) a 10 character limit to field names.
... View more
08-20-2012
06:28 AM
|
0
|
0
|
1200
|
|
POST
|
Thanks again Chris. I guess all the examples/videos/templates/etc using the term Tax Parcel made me think they were mandatory. I can see their purpose now - they're often the same as lots, but not always - but since we don't maintain tax info, we shouldn't need them. Yes, any new divisions get platted into subdivisions & lots, but there are lots of legacy parcels that aren't platted. Merges and replats are usually, but not always, entered as new subdivisions, although we should always get a new survey for them. I like the PLSS system, used it in Michigan, but they don't use it here. I saw the fields named PLSS in some of the schema data, and used in the white paper. Not sure the white paper is current on everything. For example, step 2, page 5, refers to the Parcels class with a Name field. I don't see that class, or a Name field in Owner or Tax Parcel classes. Maybe in an earlier version?
... View more
08-13-2012
09:15 AM
|
0
|
0
|
4550
|
|
POST
|
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
08-13-2012
06:20 AM
|
0
|
8
|
14507
|
|
POST
|
Thanks Tim. I am working on just a test area now, a copy of the subdivisions, parcels and outblocks (legacy parcels not in a platted subdivision) in one square of the city grid. My understanding from talking with someone at the LGM island at the UC was to first run a topology on the data, then migrate that to the parcel fabric. I actually just finished running and correcting my test topology and have everything cleaned up, at least according to the rules I've set up. I'm just not sure if they're the rules I should be using to prep the data for the fabric, or if I should have others instead of or as well. I'll read the white paper and see what that says.
... View more
08-10-2012
11:59 AM
|
0
|
0
|
592
|
|
POST
|
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
08-09-2012
06:44 AM
|
0
|
2
|
1123
|
| Title | Kudos | Posted |
|---|---|---|
| 6 | 08-22-2019 07:41 AM | |
| 1 | 05-05-2014 04:30 AM | |
| 1 | 08-15-2018 06:23 AM | |
| 3 | 08-06-2018 07:31 AM | |
| 1 | 03-30-2012 08:38 AM |
| Online Status |
Offline
|
| Date Last Visited |
12-12-2021
01:00 PM
|