Latest Contributions by LR

Diagonal length / sqrt(2) equals a square's width. So you could align the scope to the geometry, split in x-direction, then split that part again to get a square, then rotate the scope by 45 degrees and do a third split, this time in the middle. ... View more

It looks like the pre-cropped images method blurs the texture less than the global one. See images below.. a 4000x4000 terrain, with a 4000x4000 texture. Because the cell size is 0.5, this equals a X/Z size of 2000 in the scene a circle textured with the global method. Texture scale and offset equal the terrain's values in the scene (w/h=2000) same circle, textured by clipping the texture to its bounding box first and then applying the clipped image by using the building's scope and x/z position Good to know the aerials get cropped now. Many roofs end up pretty funky looking when opened in ArcScene 10.5, though. However, they do look as expected in Pro. FME also displays them correctly.   ... View more

Great, looking forward to it. ... View more

Great! ... View more

The file is not PDF/A compliant, that's why it won't open in Reader. File exporttest3.pdf Compliance pdf1.7 Result Document does not conform to PDF/A. Details Validating file "exporttest3.pdf" for conformance level pdf1.7 XML line 11:3: error parsing attribute name. XML line 11:3: attributes construct error. XML line 11:3: Couldn't find end of Start Tag Description line 9. XML line 15:19: Opening and ending tag mismatch: RDF line 3 and Description. XML line 42:16: Opening and ending tag mismatch: Alt line 40 and Bag. XML line 48:34: Opening and ending tag mismatch: PDFVersion line 48 and Keywords. XML line 52:11: Opening and ending tag mismatch: xmpmeta line 2 and RDF. XML line 53:1: Extra content at the end of the document. The document does not conform to the requested standard. The document's meta data is either missing or inconsistent or corrupt. The document does not conform to the PDF 1.7 standard. Done. ... View more

I found an old test rule where I tried to get that to work, looks like I made two sets of variables with two sets of display fields and a switch. Needless to say, a rather convoluted solution.. If you want to try to solve it with Python, look up setAttributeSource. @Group("0 Switcher") @Range("SubMulti","Total") attr Mode = "SubMulti" #------------------------ @Group("1-1 SubMulti") attr UA_sub = 5 attr UA_multi = 5 @Group("1-2") attr A_total = UA_sub*UA_multi attr A_sub = UA_sub attr A_multi = UA_multi #------------------------ @Group("2-1 Total") attr UB_total = 10 attr UB_multi = 2 @Group("2-2") attr B_total = UB_total attr B_sub = UB_total/UB_multi attr B_multi = UB_multi @StartRule Lot -->           case Mode == "SubMulti": extrude(A_total) split(y){A_multi: X.}*           else: extrude(B_total) split(y){B_total/B_multi: X.}*‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Grabbing the map.osm in the maps folder from CE 2016 also works. I ran into another OSM problem: the streets don't stay aligned properly in any non-EPSG 4326 project when exported to a CE webscene. This affects only the streets, buildings stay in the proper place. ... View more

It's mostly for performance and ease of use. Combining meshes reduces draw calls, which is always good. I also found that most GIS-derived objects have little reason to have separately addressable components. As for Unity, it's not a requirement. It's possible to use the parent-child hierarchy for the attribute linking (i.e. give each child the parent's attributes) and to manipulate the other children (e.g. highlighting). Alternatively there's the option to make a second set of single-material simplified models to use as collider with the parent. ... View more

Separate points? ... View more

Importing works. I guess Pro still doesn't like playing nice with Excel files..  ... View more

Forgot to mention: I wanted to avoid offsets/image sampling if possible because they don't work in ArcGIS Pro. The above method works in CE, I just had to shuffle the sizing and offset down to the roof part. Also the reason why I'm using cut out images instead of a single aerial image is because Multipatch export exports the whole image per roof, creating gigantic datasets. ... View more

It doesn't, but why? Seems inconsistent. Adding reporting does work but also always adds summary fields which I need to remove again. ... View more

Points are in a GDB, the tabular data in xlsx. ... View more

I've read those but the join plain and simple does not produce more than six visible entries (the first one for each ID) despite claiming it's 1:n. The data is fine, as at least the relate shows every row when I query a point. In ArcMap, mind, Pro just tells me it's related. ... View more