Latest Contributions by BenLeslie1

‎10-19-2015

I reckon Micah's answer is correct - just be sure that the 'Source for attribute' is set to 'Object attribute' via the Inspector.

‎10-14-2015

My first guess would be that it's an accidental move as a result of not having set the Sticky move tolerance in: Editor-->Options-->General

‎09-28-2015

That works very nicely. Thank you. For anyone else referencing this - the correct syntax for the sql statement is a single equals sign: outSetNull = SetNull(BlackPixRast, 1, "VALUE = 0")

‎09-28-2015

BlackPixPoly = "BlackPixPoly.shp" arcpy.RasterToPolygon_conversion(BlackPixRast, BlackPixPoly, "SIMPLIFY") #delete black pixel polygons to leave non-black pixels arcpy.MakeFeatureLayer_management(BlackPixPoly, "BlackPixPoly_lyr") arcpy.SelectLayerByAttribute_management("BlackPixPoly_lyr", "NEW_SELECTION", "\"GRIDCODE\" = 0") arcpy.DeleteFeatures_management("BlackPixPoly_lyr") Here is an extract of my script that converts a raster to polygons and then deletes the polygons that represent black pixels. The script has been used many times successfully but has hit a problem with a particular file. I get: ERROR 999999 Failed to execute (DeleteFeatures) For this particular file it is attempting to delete almost 1.2 million polygons - my guess is that this is the cause of the problem. I tried DeleteRows (is there a difference?) but got the same problem. I tried adding a line to RepairGeometry prior to deletion but get the same problem. Is there something I can do to help it get through this task?

‎09-25-2015

Ah ha - it is the same, thank you.

‎09-25-2015

I cannot see this option in 10.2 - is it possible to remove the spatial reference in 10.2?

‎09-24-2015

I don't think you can use a number as the first character of a rule, so Jawadh's example should be altered to something like this: comp(f){1 : First | 2 : Second | ..... and so on to n th face} Otherwise tell us what doesn't work - is it an error or a particular reason it doesn't work for what you're trying to achieve.

‎09-15-2015

I have used Build Overviews each time. I have tried again with default settings but I still get a chessboard - except, as before, in one tiny corner where it seems to have worked (less than 1%) (the extent in the overview tool covers the whole dataset). In the tool messages there is one about "Marking stale and missing overviews" otherwise I don't see anything to be concerned about.

‎09-15-2015

I'm a bit confused about mosaic overviews. I have approx 65000 tiles of 3-band colour imagery in my mosaic and I'm trying to create overviews so I can pickup on any obvious errors - corruptions, mis-coloured tiles etc. Basically I'm not getting anything useful out of the tools - it just produces a checker board. I used the default settings - no. rows = no. columns = 5120. Result = nothing. So I tried - no. rows = no. columns = 2560. Result = little bits of apparently random checker board. Ok lets try something more extreme - no. rows = no. columns = 320. Result = if I zoom to the extents of the imagery I get full coverage of checkerboard, but if I zoom-in I just see little bits of checkerboard. I'm not finding the help docs very enlightening, I'm struggling to understand how the tools work and how the results correspond to the settings, and I don't understand why I'm just seeing chessboard. If I load the raw overview files into arc it's not much more useful - their total coverage is just a tiny portion of my total imagery coverage (although the content looks correct) -- is 65000 images too much for these tools to deal with? Any advice on how to proceed? Arc10.2 Windows 7 64 bit - top end speed and memory.

‎09-14-2015

No, unless I misunderstand your question you only need to set the offset once. Every object should be offset by the same value otherwise they will not maintain their positions relative to one-another. The offset does not have to be anything specific - just something to get your model close to 0,0 in Maya - infact you may want to round the values so they are easier to recall should you need to refer to them later. Picking a vertex is just a way to get a value.

‎09-14-2015

You want to use values that will offset your model so it appears at approx 0,0 in Maya. So, click on one of your street graph objects and open up the Vertices section in the Inspector. Try using the negative of the values of one of the vertices as the offset..... Fingers crossed....

‎09-09-2015

I had a go and this looked pretty good to me - I'm not sure you'll get the sizes identical unless each wall is the same length. Lot--> extrude(10) comp(f){top:Top|side:Sides.} Top--> offset(-0.5) comp(f){inside:Roof.|border:Battlement} Battlement--> split(x){~1:Merlon|{~2:Crenel.|~2:Merlon}*|~2:Crenel.|~1:Merlon} Merlon--> extrude(2) (edited to correct terminology)

‎09-08-2015

I think this section of CE documentation should help split Operation Unless I misunderstand what youre asking..

‎09-03-2015

I assume this is because CE understands spatial references whereas Maya does not. So CE understands how to handle data that is a long way from the origin, and sets up the scene accordingly, but Maya does not. There is a 'Global Offset' option on the FBX export I think this should help fix the problem when you load into Maya (it's been a while since I did this)

‎08-25-2015

Ah.... It's caused by the line coming from the porch roof to the hip end. You might have to draw the main house and the porch as two boxes - hold shift when drawing so they remain completely separate.

Online Status	Offline
Date Last Visited	‎10-12-2021 02:38 AM

My Ideas

Latest Contributions by BenLeslie1

Re: How to assign height attribute to each grid in the grid mesh?

Re: Strangeness - gaps unintentionally created while editing

Re: Deleting very large number of polygons

Deleting very large number of polygons

Re: Raster Projection Removal

Re: Raster Projection Removal

Re: CityEngine - comp and split operations

Re: Mosaic overviews

Mosaic overviews

Re: Flickering Issue / jagged model issue:

Re: Flickering Issue / jagged model issue:

Re: split parapet walls

Re: split parapet walls

Re: Flickering Issue / jagged model issue:

Re: geometry.isOriented and even issue on roofs.

Re: Dissolve polygon and retain attribute fields

Re: Building height with roof

Re: geometry.isOriented and even issue on roofs.

Re: roofShed generates at half height when the roo...

Re: Strangeness - gaps unintentionally created whi...