POST
|
If I missed a similar answer forgive me. 1: most addressing is done on the local level. Most of that data is derived from developers for the road names and then the addressing is up to the addressing side (typically in the Plan. Zone Depts.) . That information is then pushed upward ON REQUEST to third party vendors. Some areas have restrictions, others don't on pushing that data. But given that it is public record in the US the data can usually be had, but the errors spoken of are part of the beast in general. 2: This concept has been banted around for the better part of 50+ years with no real solution, mostly because most places do not have a mandate nor the general ability to do so. 3: As to the privacy issue. In the US, the information is considered public information and is open to anyone.
... View more
10-20-2016
12:30 PM
|
0
|
0
|
500
|
POST
|
That did it! it also kept the parts that were contiguous where they needed to be. Thank you.
... View more
02-16-2015
10:06 AM
|
0
|
1
|
4511
|
POST
|
This may seem like a no-brainer, but I am running into several problems with this. I have a large multi part polygon that is merged as a single entity. The polygon represents multiple but separate land ownership ares. For the purpose I have, many of those polygons must be split into separate parts and be recognized as such. The problem is that all forms of editing to split the polygon has not succeeded. This included a copy-paste, polygon split, re-shaping the polygon and bridging them, then slitting them, etc. Both of those polygons are separate but are part of one single parcel. Any ideas how to split them into two? Thank you.
... View more
02-16-2015
09:43 AM
|
1
|
6
|
15103
|
POST
|
Quick question: Is SA a requirement for parcel editing, and if not, what advantages to having it v. not? Thanks.
... View more
10-02-2012
07:05 AM
|
0
|
1
|
1918
|
POST
|
Our office is developing a fairly large parcel index and the people who will be using this information are mostly: 1: Not regular Arc View users. 2: Need information quickly. 3: Be able to pull different information without having to go through long winded or difficult queries. What we have developed so far: Data driven pages that show individual lots with all necessary data shown. (owner, address, legal disc., Lat Long, etc.). Ancillary data such as legends, North arrows etc. are added in. The maps will display each and every single lot separately in a pre-formatted .mxd that is printable. The background data is Read-only to prevent overwrites or inadvertent edits. Each parcel is easily viewed by simply inputting the key value in the "Page Name" attribute of the DDP command bar which is directly linked to the key attribute in the data table. The problem comes in that many of the parcels we index have missing key data (most �??fake numbers�?� are typically 0). So to find various parcels, the assessors, field techs and most everyone else who is NOT a mapper, uses various means to find that data. Including the above listed attributes and inputting owner names, Situs addresses, etc. But, the DDP system only allows for a singular query from only the DDP command bar. So, is there a way to set up a query wizard, or some other means of say a window or radio button of some kind where the address data, account number, owner, Lat/Long or any other data could be entered for a query and the DDP can then query that data and display the lot as normal? Thank you in advance.
... View more
08-28-2012
01:50 PM
|
0
|
2
|
825
|
Title | Kudos | Posted |
---|---|---|
1 | 02-16-2015 09:43 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|