POST
|
Hi, I have tried to find some (or any) documentation that describe limitations for the path/filename for TIN datasets. All I could find was one old forum post that mentioned a limit of 128 character, but I have found 118 seems to be the actual limit (making sure to remove any spaces in the path, of course!). We are trying to set up an automated processing environment for our data (which includes TIN datasets), so any documentation that lists out any rules for TINs would be very helpful. Thanks, KW
... View more
10-23-2012
10:12 AM
|
0
|
1
|
325
|
POST
|
The version available is a new release, so there might still be a bug or two. I will work with our team to see what the issue could be.
... View more
04-25-2012
09:32 AM
|
0
|
0
|
1368
|
POST
|
Hello, I work on a project that involves the use of a total station to make high resolution topographic maps of streams for salmon habitat studies. We encountered this same problem with georeferencing the survey data. The problem is due to the higher accuracy of the total station compared to the accuracy of the gps coordinates collected for the control points. When you try to "lock on" to all of the control points, you end up distorting the survey data. To solve this problem, we developed an Add-In that our field crews use to project total station survey data in to a real-world coordinate system: http://ctt.joewheaton.org/home I hope this helps!
... View more
04-23-2012
07:08 AM
|
0
|
0
|
1368
|
POST
|
As part of a set of data processing tools I am developing, I need to attribute a set of polylines using a text field ("Description") from a point cloud (that contain the vertices as well as other points). The points all have the same description code for each line, so using the "First" merge rule works most of the time, however occasionally a point with a different code intersects or is close enough to the line and the merge rule uses this code instead of the code in the majority of the intersecting points (i.e. it takes the alphabetically first code regardless of how many times it appears). Basically, I want to use the Merge Rule "Mode" for a text field, as described in the ArcGIS help guide: "Mode???Use the value with the highest frequency (most common). If there is more than one value with the highest frequency (i.e., a tie), then the list of Mode values will be sorted (smallest first for numeric, alphabetical for text), and the first one will be used." This is not appear to be available as an option in both the geoprocessing tool or via Python. Is this a bug, or an illusion of a function that was neglected to be added to the processing tool? (Or the third option I am missing something very basic here, which is always a possibility). [ATTACH=CONFIG]13705[/ATTACH] Any help on this would be greatly appreciated. Thanks!
... View more
04-20-2012
09:29 AM
|
0
|
1
|
479
|
POST
|
I've been having similar frustrations with FieldInfo in my script as well. I ran a quick test in the python window: >>> test = arcpy.FieldInfo() >>> test.addField("Name","NewName","VISIBLE","NONE") >>> test.setVisible(0,"HIDDEN") >>> test.getVisible(0) u'VISIBLE' >>> test.getSplitRule(0) u'HIDDEN' The setVisible method appears to be changing the SplitRule instead. Looks like a bug to me...
... View more
12-30-2011
12:34 PM
|
0
|
0
|
1599
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|