|
POST
|
Matthew, I wanted to recommend for future using of cursors that you use the new data access cursors(arcpy.da.SearchCursor e.g.). They are significantly faster than the old style cursors you were using in your code. The parameters and syntax are somewhat different from the cursors you were using, but still easy to use. Here is the link for the new cursors versus old cursors. ArcGIS Help (10.2, 10.2.1, and 10.2.2)
... View more
06-18-2015
11:27 AM
|
2
|
0
|
641
|
|
POST
|
Yes, your was set-up for a true first response, while mine was set-up for a false. Either way, he got what he needed, thanks for the input.
... View more
06-18-2015
11:16 AM
|
1
|
0
|
641
|
|
POST
|
That was probably the better one to use, my general python gets rustier and rustier I feel like since I am only use python within the arcpy module these days(and with a limited usage at that!).
... View more
06-18-2015
08:31 AM
|
1
|
8
|
3120
|
|
POST
|
should be fairly easy to use a counter or something similar to check. rows = arcpy.SearchCursor(Layer)
textValue = ""
for row in rows:
count = 1
if count/2.0.is_integer() == False:
textValue += row.getValue(Value1) + ' '
count += 1
else:
textValue += row.getValue(Value1) + '\r\n'
count += 1
ParcelText2.text = textValue
del rows
... View more
06-18-2015
08:06 AM
|
1
|
0
|
3119
|
|
POST
|
Agreed Darren, that is a much easier procedure then trying to get a bunch of polygons to be coincident with each other. Sometimes its worth it even if you already started drawing since it saves so much time trying to line up vertices and edges.
... View more
06-17-2015
01:22 PM
|
0
|
0
|
4529
|
|
POST
|
Thanks for posting, saw you were the original author and figured you had a newer one. I didn't need a copy, but I figured this thread should link to a new version if it was available. I'll probably go ahead an bookmark, never know when I might need it.
... View more
06-17-2015
01:20 PM
|
0
|
0
|
4113
|
|
POST
|
What sort of table is your input for Table to Excel?
... View more
06-16-2015
02:25 PM
|
0
|
1
|
7286
|
|
POST
|
If you dissolve without selecting an attribute, it dissolves based on being contiguous, so if they features touch they should dissolve into a single feature.
... View more
06-16-2015
07:59 AM
|
1
|
2
|
2725
|
|
POST
|
Have you tried dissolving the resulting dataset? ArcGIS Help (10.2, 10.2.1, and 10.2.2)
... View more
06-16-2015
07:46 AM
|
1
|
4
|
2725
|
|
POST
|
If you have the 3D Analyst Extension, you can try the Stack Profile Tool. ArcGIS Help (10.2, 10.2.1, and 10.2.2)
... View more
06-16-2015
07:22 AM
|
0
|
1
|
6922
|
|
POST
|
Just adding my own two cents to this. I do this sort of work fairly regularly, but instead of using DDP, I just have several map templates which already have the polygon feature, make a feature layer based on each ID number zoom to extent then change text elements based on attribute fields and export to PDF. It loops through each row with a cursor and exports out each map to pdf. Haven't tried with DDP, but might look into it in the future.
... View more
06-15-2015
03:33 PM
|
1
|
0
|
3285
|
|
POST
|
Really I think that utility companies are more worried about how close to transmission lines are to forest canopies than anything. I know we have to go and trim down or remove trees in our transmission Right of Way(ROW) on a regular basis(I'm not involved in this but I know it is something that is done regularly). So I think they would be more interested to know if they are in the ROW as Sephe mentioned and how high each feature was. It would be fairly easy to use a Conditional Statement in the raster calculator to extract pixels of minimum height(say 10,15 feet or whatever they were interested in) that would be deemed features that need to be looked at for cutting/removal in the future.
... View more
06-15-2015
03:22 PM
|
2
|
2
|
5235
|
|
POST
|
On a spot by spot basis, you could always use the identify tool to get your pixel value for individual pixels, which would be the height of the object at that point. I tend to call a DSM minus a DEM a Digital Height Model(DHM) for it is the height of the objects scanned above ground(bare earth). Differentiating between trees and other high features can be challenging, though research has been done for classifying different feature types from LiDAR. If all they need are to be able to get the heights on a case by case basis, then the DHM and the identify tool to get the pixel value would be all they need.
... View more
06-15-2015
03:05 PM
|
2
|
4
|
5235
|
|
POST
|
Once you import your .las files into a Las Dataset(.lasd), you can control what return values you want the las dataset to use and which point types in the Las Dataset properties, or you can make a Las Dataset Layer file, with only the return types you want. For a DEM, you would want to use only returns classified as ground(I sincerely hope they are already broken down into ground/non ground) in your las dataset, then can use the Las Dataset to Raster tool, for a DSM, you would want only First returns in your Lasd Dataset, since it the DSM is showing the return of those surfaces that are hit first by the lidar pulse. Choose your value field(elevation in this case) and interpolation type(see the help about selecting one). Output cell size is a sticky topic, a fair number of published journals have recommended you can use a cell size that is equivalent or so to the nominal point spacing of your lidar data. ESRI suggests using a cell size 2-3 times larger than the nominal point spacing, but from personal experience, using the same as the nominal point spacing works well. Making Las Datasets ArcGIS Help 10.1 Las Dataset to Raster ArcGIS Help 10.1
... View more
06-10-2015
04:01 PM
|
1
|
0
|
6125
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 02-22-2017 08:58 AM | |
| 1 | 10-05-2015 05:43 AM | |
| 1 | 05-08-2015 07:03 AM | |
| 1 | 10-20-2015 02:20 PM | |
| 1 | 10-05-2015 05:46 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:23 AM
|