Latest Contributions by BenLeslie1

‎10-27-2014

I could be wrong but aren't all projected systems flat - could you just pick one and ignore its implied Earth location? But I'd recommend picking one that matches your base units - most are in metres but the State Planes are in feet if you like things to be more difficult.

‎10-27-2014

Huh. Well it's not you who is brain damaged. I guess these things can happen when one's away from CE for a few months. Thanks

‎10-23-2014

Even though it was kind of a question I did this as a discussion instead - so maybe that's why you don't have the button you want.

‎10-23-2014

I see.... do it all in a single RemoveBottom--> rule at the end...... good plan.

‎10-23-2014

Yep - trouble is a border and an inside is created for both the hole and the proper shape, so the following code produces the following image: offset(-2) comp(f){border:NIL|inside:Cyan}

‎10-23-2014

I seem to spend a lot of time writing the following for buildings and roofs: comp(f){bottom:NIL|...... I think it would be useful if there were a global control to prevent bottom faces being created - or an option in the extrude and roof creation rules to exclude bottom faces......or have I missed something?

‎10-23-2014

Similarly the offset rule also fills holes in 2014.1 if a negative offset value is used. Is there a way to procedurally remove this unwanted hole-offset-geometry? comp(f) doesn't seem to have necessary options.

‎10-14-2014

I'm trying to measure the width and height of a raster in metres. I'm working in WGS84 (degrees) so Raster Properties aren't much good - and I don't like the results when I re-project the raster. So I have constructed two lines based on TOP, BOTTOM, RIGHT, LEFT raster properties, then I reproject those and get their lengths. They are separate features and they will be deleted once I know their lengths. Pieter GvdB's answer works for me. I'm pretty new to python, I tried Greg Keith's answer but my knowledge isn't good enough to know how to fit it in my code.

‎10-13-2014

I'm on version 2014.1 and have found that the Subdivide tool doesn't work with holes. See attached - behaviour is the same using shp or gdb.

‎10-10-2014

My script geterates two lines in a temp shapefile. I'm then using SearchCursor and Describe to get the lengths of these lines, like this: rows = arcpy.SearchCursor(tempSHP) len = 0 shapeName = arcpy.Describe(tempSHP).shapeFieldName for row in rows: feat = row.getValue(shapeName) len = feat.length print len What I really want is to set the length of each line to a different variable - I tried various things like below but haven't found the right way to approach this little problem (the error for the code below said "row does not support indexing"): for row in rows: featX = row[0].getValue(shapeName) lenX = featX.length featY = row[1].getValue(shapeName) lenY = featY.length

‎10-09-2014

I don't remember experiencing anything similar. Have you tried any of this?: checking that everything is on the correct layer check that you're really generating the models for everything you want check all your shapes are assigned the correct rule file and start rule Inspect the model hierarchy for those that are not generating and compare it to those that are working maybe try copying your data to a new workspace Sorry if these are very simple suggestions - there's not much info to go on.

‎10-08-2014

Waaait a minute - this (probably) isn't a rounding issue at all - (I tried Append to put my point into an existing shapefile that has an SR and I get the same geometry) my input numbers after the decimal point are: RasterLeft: .36184...... RasterBottom: .694507..... whereas the geometry is created at: x: .36181........ y: .694519...... any ideas?

‎10-08-2014

Working in lat long. I'm doing a bit of code to get the bottom-left coord of a raster and then put a point in a shapefile at that location, however it appears that the lat/long coords are rounded to 3 decimal places when the shapefile is created - in the instance that I'm testing this means the point in the shapefile is offset by approx 2m which isn't good enough. How can I prevent this rounding (it looks like I really want 13dp). Here's my little bit of code: #get coords RasterLeft = arcpy.GetRasterProperties_management(myraster, "LEFT").getOutput(0) RasterBottom = arcpy.GetRasterProperties_management(myraster, "BOTTOM").getOutput(0) #create geometry point = arcpy.Point() point.X = RasterLeft point.Y = RasterBottom pointGeometry = arcpy.PointGeometry(point) #copy geometry into shapefile arcpy.CopyFeatures_management(pointGeometry, "test.shp")

‎09-26-2014

Here's CE help Help - The relevant section is CGA Shape Grammar Reference --> Shape Operations basically, assuming you have an attribute in your shapefile for Z_Value you'll need to define it in the rule file then you can use it with the translate function: attr Z_Value = 0 Lot--> t(0, 0, Z_Value) (I think it depends on how you have your workspace set up as to whether CE uses y or z as up.... I can never remember)

‎09-26-2014

Maybe I misunderstand the problem.... why not write it into a rule file using the t() operation to translate your floor vertically by the z value?

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

My Ideas

Latest Contributions by BenLeslie1

Re: Using a non-georeferenced coordinate system

Re: bottom faces

Re: bottom faces

Re: bottom faces

Re: "Hole" in cityengine

bottom faces

Re: "Hole" in cityengine

Re: for row in rows - set values to different variables

Re: "Hole" in cityengine

for row in rows - set values to different variables

Re: City Engine does not generate all shapes

Re: Prevent rounding of Coordinates

Prevent rounding of Coordinates

Re: Floors with unique base levels

Re: Floors with unique base levels

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...