Latest Contributions by NeilAyres

Tricky.... A python approach would be fraught with difficulties like Z this side and that of a particular point. Which is "correct"? Do the lines at least go in the correct direction ie down stream? Not saying that you would get a programmatic solution here though. Would be difficult in my estimation. ... View more

Do you have access to the original dem from which these stream lines were derived? Because I think the best solution would be to create a hydrologically correct dem first, then derive the stream lines, using the work flow outlined here : an-overview-of-the-hydrology-tools ... View more

Just to be a little picky about naming variables.... This is a list of field objects (not a straight list) : fieldList = arcpy.ListFields(feature) This is a list of strings (not a string) : fieldString = [str(x.name) for x in fieldList] I must agree with Joshua. Coverages, really.... Havn't met one of those for a very looong time. ... View more

The numbers (Height) etc could be added as any value Also see here : defining-parameter-data-types-in-a-python-toolbox ... View more

Not strange at all. There is on the surface a level of cooperation, but a fierce rivalry lurks not far below... Remember when Erdas was the image processing software of choice for esri users? Then it was bought into the Hexagon group along with ER Mapper, Microstation etc etc. Out went Erdas, in came PCI (Envi). We still have a good lot of cooperation here with the local Leica agents because their survey kit and field devices are just better than most. As regards the original subject I would say.... Don't worry about the opposition. Just make sure that what you say about the features of collector are actually true ie, go out and use it with real, live data. Don't just believe the sales talk.  ... View more

The methodology is pretty easy. As you can see i did construct a simple polygon to cover the area of the data with its Z also at 0. In ArcScene, extrude it to a ht bigger than your building, I think I used 20m. Then save this as a layer file. Then in tool box, use the 3d Analyst tools / Conversion / Layer 3d to Feature class to make this a multipatch. Then use the 3d analyst tools / 3d features / Intersect 3d tool to intersect the big box with the shadows. You are left with only the parts of the shadows which are above ground. ... View more

Just be aware of this bit of course... "4. Use of Wintopo to register the output into the designed coordinate system (just input 4 corners of X,Y)". How do you know where those 4 corners are in real world coordinates? And are the 4 corners marked on the image?? ... View more

Just had a look at WinTopo. Looks good. Just doing the vectorisation process from image to vector. Report back on its capabilties. It will really depend on the quality of the image inputs. Go for it.... ... View more

I have sucessfully used udc (universal document converter) to translate pdf pages to image files like jpg or tiff. Even in batch mode. After that then you will have to georeference the images and capture the data either manually (by editing) or with tools like ArcScan. Sorry, no auto magic solution. ... View more

Okay, did have a look at this. And, yes, those shadow multipatches produced by the shadow volume tool do look rather odd. (my version 10.4.1). Bit of a mystery why they should protrude into the ground like that. Did load the original shapefile into a fgdb. Then added Z, set to 0.0. Checked the geometry as well. These shadows from a single time at 12 noon today. Is this a bug? Been a long time since I used any of this shadow stuff. I can't recall it generating shadows which are +200m under the Z values. Is there someone in the 3d analyst team we could tag here? ... View more

As a GIS person I always advise clients when I see a business (mines, utilities, many others), having their main db in a coordinate system based on a classical datum, to bite the bullet, and transform the data now. Otherwise the problems just keep mounting up. Every new data capture project (aerial imagery, lidar, ground GPS etc etc), has to be transformed by some means on to the old datum. Question is, how is that transformation achieved. This part of the workflow is rarely, if ever, documented properly (usually because most people don't understand the implications). So you end up with a db which contains a whole bunch of historical stuff and more modern layers which never, ever, quite line up. And it is impossible to ever get everything sorted out. ... View more

There is no attachment as far as I can see. ... View more

And, not sure what that [-12] is doing. >>> n = "fkghthsyfgtrekh" >>> n[-12] 'h' >>> n[:-12] 'fkg'‍‍‍‍‍ ... View more

Never dealt with this sort of data before, but that error is obviously your indexing of the value in Nowfile. >>> n = "dngthrysdfg" >>> n[-12] Traceback (most recent call last): File "<pyshell#5>", line 1, in <module> n[-12] IndexError: string index out of range >>>‍‍‍‍‍‍‍ So, as Dan says, perhaps have a look at that variable before this step. ... View more

So, what happens at the moment? What errors are you getting or are you asking to validate this code prior to actually trying it? I can see one problem with this : arcpy.CopyRaster_management(nowFile, outname, +".tif","", "", "", "NONE", "NONE", "") Shouldn't you add the "*.tif" to outname in the line above. Here the "*.tif" is the 3rd parameter. Which I am sure will not work. ... View more