|
POST
|
A new web application called "Parcel Drafter" will be released in a couple of months. It will use line and polygon feature services (hosted from ArcGIS Online or from your on premise ArcGIS Server). We will demo it on the Land Records Meetup
... View more
08-17-2016
09:01 AM
|
0
|
0
|
719
|
|
POST
|
We would love to get your feedback on the Traverse functionality in the current release (1.3) as well as future releases. We are not sure the re-ordering of courses will make it to the next release (1.4) but it is on our road map for traverse. We can rephrase "saving a polygon for each traverse" to "every polygon (parcel) has it's own set of lines". That is also on the orad map for parcel editing in Pro. BTW - using python one can easily select lines and export them to multiple formats, including a text file. Reading tabular information and populating a traverse is part of the future SDK capabilities. Thanks, Amir
... View more
08-10-2016
01:37 PM
|
0
|
0
|
2889
|
|
POST
|
Thanks Sarah, So if I understand it correctly the text files were used to save lengthy description and pick it up / modify an error at a later time. In Pro, each course is saved as a 2 point line feature. The next release of Pro (1.4) will also allow you to select any sequence of courses and modify them as a traverse. Given that option would you still need to save them as a text file? Thanks, Amir
... View more
08-09-2016
12:27 PM
|
0
|
0
|
2889
|
|
POST
|
Hello Sarah, Could you please share with us what is the source of the text file you are trying to read from? Or are you trying to save it to a text file and then read from the saved text file? If it is the latter, the COGO values are stored on the COGO fields as soon as you save your edits. Are you using the text file as a backup to your geodatabase? Thanks, Amir
... View more
08-08-2016
12:12 PM
|
0
|
1
|
2889
|
|
POST
|
The parcel fabric does support overlapping parcels from the same type (e.g. historic tax parcels) or different parcel types (e.g. subdivisions and tax parcels). If you have unintended overlaps and gaps it could be due to the following reasons: It was always a problem and migrated that way - in this case consider remigrating the data. Having good data integrity and vertical alignment between parcels is highly recommended for data migration. There is a variety of tools and procedures you can apply to your data prior to data migration depending on your source data. Missing line points - After data migration we recommend running the merge courses tool to create line points. After line points are created, you will not see a gap/overlap a line that has other parcel corners along it moves ("T junctions without breaking the line). Bad Join links - if a join line of any type is missed you might see overlaps and gaps when any of the parcels move. the fix is easy - use rejoin to create and link that was missed. You can also contact technical support to work on your specific issue Amir
... View more
07-29-2016
11:50 AM
|
0
|
0
|
1578
|
|
POST
|
It certainly depends on the amount and extent of data you are adjusting as well as on the number of displacment vectors that got created in your parcel fabric. If you think it takes too long please contact technical support. If you created data outside of the spatial extent by mistake, it can also have negative impact on the associated features adjustment. Amir
... View more
07-29-2016
11:38 AM
|
0
|
0
|
1146
|
|
POST
|
Hi Katherine, There are a few options: 1. Best option: have all departments ./ agencies working on the same parcel fabric. With this option everybody are always in vertical alignment, no setup is needed. Downside: requires everybody to be on the same network and/or host the geodatabase and clients on the cloud (which is basically a shared network) 2. If you are only interested in the vertical alignment and not so much on the data the other agency is creating, you can populate a global ID on all the points and then share the parcel fabric between the agencies. From now on the parcel points can be published as a feature service and consumed using in ArcMap. Use the Fabric Point Move To Feature Add-in to move parcel points when they get updated between the parcel fabrics. 3. Geodatabase replication - this requires more effort to setup (network, permission, identical schemas) as well getting rid of relationship classes between parcel fabric classes. It also requires some one to physically sync and handle any conflicts. If both agencies are already on the same network they might as well use the first approach. With geodatabase versioning and appropriate QA processes in place the need for replication is questionable.
... View more
07-29-2016
11:35 AM
|
0
|
0
|
1108
|