|
POST
|
What data format are you working with? SHP, GDB, MDB, SDE, ETC? I ran into a similar issue when calculating records stored in SDE. If you are try running the calc in a gdb or mdb featureclass. Turned out to be a known issue back then; don't know if the latest sp fixes it or not.
... View more
03-26-2012
11:29 AM
|
0
|
0
|
3284
|
|
POST
|
Several things come to mind: First you have to be on the "Selection" tab in the Table of Contents to view tables that are in your mxd. If you see the red exclamation point you can repair it from there. In the event you don't know where the table was stored you can r-click the layer to access properties and then click the source tab. You may also click the "joins & relates" tab once inside the layer prop's to see what joins the layer is looking for if any.
... View more
03-26-2012
08:49 AM
|
0
|
0
|
383
|
|
POST
|
Tim, I didn't see your scerenshots nor the steps to reproduce the problem. I would be interested in seeing the problem. Everyone should note that "trace" at 10 does not work at very large scales for obvious reasons. IE you can't see what you are tracing and I also suspect it has more to do with the caches/builds referred to above.
... View more
03-26-2012
08:33 AM
|
0
|
0
|
2110
|
|
POST
|
At 10.1 you can isolate out the plans table. If you are able to populate the description field with the correct plan name (from a subdivision layer, say) then if you add the book & page ref fields to the plan table, you should be able to populate the values by joining on the "description."
... View more
03-22-2012
08:34 AM
|
0
|
0
|
1332
|
|
POST
|
Look at the Fishnet Tool. Here's a link to the usage in ArcGIS 10: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00170000002q000000 Can't remember how it has changed since 9.2. Good luck!
... View more
01-25-2012
10:49 AM
|
0
|
0
|
382
|
|
POST
|
Yes, unfortunately the previous method mentioned only works with the Fabric. Have you considered creating a separate line feature class to store your COGO information and geometry? Not only can you store the COGO information in its attribute table but you can work with multiple ones at the same time.
... View more
06-22-2011
09:22 AM
|
0
|
0
|
750
|
|
POST
|
Did you find a good workflow for this? It's sounds like a situation where you want your construction to remain in position with the exception of those 2 points. It would be nice if you had the option to only move SOME of the points to the sketch or vice-versa. Either way, I would love to hear what you've discovered. Thanks.
... View more
06-22-2011
09:17 AM
|
0
|
0
|
940
|
|
POST
|
I am trying to create a natural boundary (creek) as a construction line. The problem is that my feature class has COGO attributes and because of that: "The list of construction tools is filtered to show only the Line tool when working with line templates for layers with COGO attributes, layers participating in geometric networks, or turn feature classes in network datasets." (ArcGIS Online Help: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/About_COGO_and_feature_templates/001t000000n0000000/ ) Thus, when I try to heads up digitize that stream of segments, I end up with a bunch on tiny little segments to select before poly construction. This can be time-consuming and yet was not a problem at previous versions. Has anyone found a solution to this? In other words, is there an option to remove this "filter" or to be able to create a continuos line feature in a layer with COGO attributes??????
... View more
06-22-2011
07:40 AM
|
0
|
0
|
907
|
|
POST
|
FYI, by logging an incident with tech support regarding the formation of an overlapping poly being created when using curves in the fabric, it is now a bug with using the parcel remainder: NIM067973 While they're currently working on patch post SP2, perhaps this will be fixed then.
... View more
05-11-2011
10:49 AM
|
0
|
0
|
2162
|
|
POST
|
Another note: try recalculating the spatial index. Whenever a layer is updated with many new features and you zoom in and can't see them, chances are you need to do this.
... View more
04-28-2011
05:30 AM
|
0
|
0
|
376
|
|
POST
|
With respect to the duplicate lines issue: Are you using one of the map templates? By default it may be set up to use a definition query to manage history on your lines. It appears that the history tab found in the fabric properties only manages the display of parcel polys for now. So check and see if there is a def query on the lines and that your lines are coded properly. If you are not using a template then you may need to create a DQ that says something like: "(SystemEndDate IS NULL)" or "("Historical" = 0)"
... View more
04-28-2011
04:45 AM
|
0
|
0
|
709
|
|
POST
|
.....hmmmm as it turns out there are 2 line points there that are really close together--more like 10 cm. This is something that I've seen hanging out since the original coverage conversion where little slivers created polys, that, once discovered, would be merged to the appropriate poly. If someone forgets to merge the line segments afterwards then the extra line point will get left behind. Is there a GP tool I could run to merge those that would not compromise my line-poly topo relationship?
... View more
04-26-2011
11:26 AM
|
0
|
0
|
2162
|
|
POST
|
Thanks Larry...I already made sure I had the latest tools. I was told to contact the "Land Records Team" that developed the add-in. I haven't had a chance yet to formally contact them regarding the issue.
... View more
04-26-2011
10:58 AM
|
0
|
0
|
994
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-13-2017 11:21 AM | |
| 3 | 03-05-2020 05:54 AM | |
| 3 | 03-05-2020 05:54 AM | |
| 4 | 09-15-2019 04:10 AM | |
| 4 | 06-05-2019 07:42 AM |
| Online Status |
Offline
|
| Date Last Visited |
02-06-2023
02:58 PM
|