Latest Contributions by LR

AFAIK you can't query the raster. You could however create a fine triangular mesh and project it onto the terrain. That way you could use the occlusion query with the terrain height - the accuracy of this would depend on your triangle size. As for the query itself, it doesn't report the touching height. To save polygons, you could do incremental querying. For example, if you have a wall with four floors you'd first check if the whole wall is touching the ground at all (maybe add a little offset from the bottom or else it'll always trigger). If it returns a positive, divide it (floorcount/2) and check again with the separate parts. The parts that don't touch won't need further splitting. ... View more

Try comp(e){all: print (scope.sx)}. ... View more

I've already read that up and down, added fields, tried using a DWG as seed, nada. I only had limited success so far with the data interop extension which produces slightly less unsighty curves by creating more vertices. ... View more

extrude(world.up.flatTop, value) ... View more

Puh. I'll try   You basically already did the required stuff: add reporting to your rules so buildings, trees, etc. report what they are (layer). Exporting as One Feature Per Leaf Shape means every object generated in the lot, whether it's a building or a tree, is a separate entity, with its reported value(s) as attribute. What's left is opening the GDB in AGP and running the geoprocessing tool "Split by Attribute", like in ArcMap. If you use your "Layer" attribute as split attribute, you'll end up with two new layers in the DB, one containing the trees and one containing the buildings: ... View more

ArcGIS Pro has a "Split By Attributes" tool you could use with your layer attribute. ... View more

If you only need rasters you'd probably have more success with SAS.Planet. ... View more

I haven't used the get map feature beyond a few tests but as far as I can tell it downloads WMS tiles or at least tries. Results vary as not every location has hi res imagery available, e. g. you can get 1x1 km 4k imagery around the white house, but can't in rural areas. By decreasing the image resolution (e. g. 500x500 px) but keeping the bounding area the same you're basically requesting a chunk of a low resolution tile that may be available. ... View more

Did you try unchecking the elevation raster option? Maybe it's causing problems due to its low resolution (if the service is using SRTM data, 90m would equal 1 pixel). ... View more

You're trying to extrude using text as parameter. You're also never calling the Extrude rule. Case rules also can't have any commands but cases. Try this instead: @Range ("Bungalow","SplitLevel","TwoStorey","ThreeStorey") attr myUseType = "Bungalow" @Hidden attr myUseTypeHeight = 0 @StartRule Lot --> SetHeight SetHeight --> case myUseType == "Bungalow": set(myUseTypeHeight, 2.75) Extrude case myUseType == "SplitLevel": set(myUseTypeHeight, 4.15) Extrude case myUseType == "TwoStorey": set(myUseTypeHeight, 5.5) Extrude case myUseType == "ThreeStorey": set(myUseTypeHeight, 8.25) Extrude else: set(myUseTypeHeight, 1) Extrude Extrude --> extrude(myUseTypeHeight) comp (f) {top:Roof |side:Wall}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Using python you could set a cga rule  generate the building export the report as csv read the csv back write the csv data as attribute set another cga rule generate the building using the new attribute ... View more