Latest Contributions by NeilAyres

Just to underline what Ian has said, once you have imported the las files into a lasd dataset, you can check the various statistics in ArcCatalog. Then in ArcMap, layer properties, filter, you can set which returns you want. Look at the data carefully for badly classified points. Once happy, save this as a layer file and use as the input into the LAS Dataset to Raster (in Conversion tools). ... View more

Have you looked at the help "Reading Geometries", here : http://resources.arcgis.com/en/help/main/10.2/index.html#//002z0000001t000000 The example is exactly what you need. ... View more

Sephe, spot on! ... View more

And, if you didn't want to simply truncate your double into an integer you could do this : Field_Long = Int([Field_Double] + 0.5) ... View more

Creation of a las dataset (*.lasd) does not actually load the data into anything. Its simply a box to keep indexes and statistics to enable Arc to draw it. It has pointers to the actual location of the las files. So, a well organized sub-directory system is probably the way to go. With the *.lasd at the top of the structure. Where you would put any derived products (raster dems or whatever) will also need to be organized by survey location, date etc. ... View more

If the datum (underlying GCS of the coordinate system) of the input is not WGS84, then a transformation is required if you want WGS84 based coordinates to come out. I have never actually used the spatial reference option when opening an Update cursor. Generally, the feature exists and it knows what coordinate system it is in.... The help files here are unclear as to how this option affects the outcome. I have in the past used the .projectAs(SR2) method on the geometry object to re-project geometries on the fly inside python. Specifying a transform is a little trickier and you have to set this via environment setting. ... View more

My sympathies. Yes, it is a fact that for many other systems, the shapefile seems to have become the de-facto standard for interoperability. But there must be other ways of getting stuff into and out out the Schlumberger software.. Have you looked at data interop? ... View more

Although I am uncertain about encoding character sets beyond utf8, I am sure you would have more success if you moved away from using shapefiles (a close to 25 year old technology) and migrated your data into geodatabases. ... View more

Just a guess, can you remove spaces from your directory path and try again. ... View more

The *prj file (or the coordinate system definition) is part of the metadata of the feature. The coordinates in the "blob" are just a bunch of numbers. Without knowing what those numbers represent, ie the projection that they are in, the system would still not know how to map these coordinates on to a map in their correct real world location. ... View more

Dan, do you mean to say that you havn't done a code snippet somewhere on how to calculate the geometry for an arc segment.... ... View more

Have you looked at the "Minimum bounding geometry" tool. But that is probably not going to solve your problem with concave boundaries. Can you thin the input points or subset them so that you can use a Tin instead of a Terrain. Then you have the "Deliniate Tin Data Area" tool ... View more

And, to add to Sephe's comments... Step 10. You do not project a shapefile by using the "Define Projection" tool. This simply overwrites the "metadata" about what the coordinate system is. It does nothing to the underlying geometry. Define Projection should only be used if you have a dataset with an undefined projection and you know what that projection is.. ... View more