Latest Contributions by LR

Maybe you're using very large textures? As for the rule error, what does the message say? I remember having some trouble because "@Startrule" validates in CE, but AGP expects "@StartRule". ... View more

Theoretically you could use NP++ for this. However the grammar definition isn't public, so you'd have to define your own. I just switch the language highlighting to Python, it's usually good enough for me. ... View more

Last time I tried to get the coordinates (of building polygons) in lat/long I ended up writing my own coordinate transformation in Python. The formulas depend on the current and target coordinate system, but you should be able to google up the right formulas. A little warning, it's not going to be as simple as x2 =x1*2+20  .  ... View more

Here's a simple one I made. You could use some recursion to make smooth arcs, but I try to keep the poly count low. Only works on straight lines, unfortunately. Change the nodes to crossings. version "2016.0" attr shapeType ="" attr streetWidth = 0 attr sidewalkWidthLeft = 0 attr sidewalkWidthRight = 0 import EsriStreets: "/ESRI.lib/rules/Streets/Street_Modern_Standard.cga" @StartRule Lot --> case shapeType == "Street": MakeTunnel EsriStreets.Street case shapeType == "Sidewalk": EsriStreets.Sidewalk else:NIL MakeTunnel --> extrude(streetWidth/1.2) alignScopeToGeometry(zUp, any, world.lowest) s('1,streetWidth+sidewalkWidthLeft+sidewalkWidthRight+2,'1) t(0,-1*(sidewalkWidthLeft/2+sidewalkWidthRight/2+1),0) color(1,0,0) rotateScope(45,0,0) split(y){1: NIL | ~1: OuterSplit1 } OuterSplit1 --> rotateScope(90,0,0) split(y){1: NIL | ~1: InnerSplit1} InnerSplit1 --> color(0,1,0) rotateScope(-45,0,0) split(y){1: Wall | ~1: InnerSplit2} InnerSplit2 --> color(0,1,0) rotateScope(90,0,0) split(y){1: Wall | ~1: InnerSplit3 | 1: Wall} InnerSplit3 --> rotateScope(225,0,0) split(y){1: Wall | ~1: InnerSplit4 } InnerSplit4 --> rotateScope(90,0,0) split(y){1: Wall | ~1: NIL } Wall --> color("#BBBBBB")‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Sounds like the model's origin is off. Try loading the model into the scene and then check it using the move tool. The axes and yellow circle should be in its center. ... View more

I'd need to read and write them like you can with getVertices / setVertices. Basically like: vertex[xpos, ypos, zpos, curvehandleangle, curvehandledistance] Haven't found anything in the doc about values beyond xyz, unfortunately. Sample data isn't really necessary, just make a two-dot line with the polygonal street tool. ... View more

If you have ArcMap ArcGIS for Desktop , you could try this*, however I only had decent success with very simple stuff, and even that required manual cleanup. You could also buffer the lines by 0.5*street width, then convert the buffers to lines, then cut the lines.. or get the streets elsewhere like Micah Taylor suggested.. * Collapse Dual Lines To Centerline—Help | ArcGIS for Desktop ... View more

Untested, but this should get you pretty close: layerName = "yourLayerName" shapeRule = "rules/yourRule.cga" if __name__ == '__main__':     layer = ce.getObjectsFrom(ce.scene, ce.isLayer, ce.withName(layerName))             for x in layer:        shapes = ce.getObjectsFrom(x)                    for shape in shapes:        ce.setRuleFile(shape, shapeRule)        ce.setStartRule(shape, 'Lot') ... View more

As far as I can tell from the screenshot you apparently aligned the footprints onto the terrain using projection. This moves their vertices seperately, resulting in twisted footprints. Either use the translate option or try extrude(world.up.flatTop, yourHeight). ... View more

That's the first thing I look for, but it looks like something's wrong with the file reading. See below ... View more

Some new findings: when I copy the data into a new workbook (copy paste, values only), the attribute fields are recognized in AGP. Manually doing anything in a sheet (adding a field, or a formula) seems to break something. Once a workbook is busted (= contains any table that causes problems), adding a new sheet and copying data into it, from within itself or another workbook, results in sheets with the same problem. This problem only exists when the excel file is used directly, when converting the sheets to a table, they're read correctly. ... View more

Sure. This is my data: shape file with points excel table with some info, media names and their (relative to project mxd) paths. This table needs to be connected in a 1:n relationship with the points media in folders Goal: click on a point, read its attributes, read related attributes and open related media. Source files should be left as they are if possible in order to be easily editable and because they are used elsewhere. To accomplish that, this is what I have to do in ArcMap after loading the shp and xlsx: Create a 1:n relate on the point layer Now I can: click on a point in the map see all the fields in the point table and related table open any related media right from the identify pane in my default viewers (media link fields have a lightning symbol) change the display field for the related table in any way I want edit the excel table externally zip up the whole thing and send it to someone and they can use the mxd as intended Now we try the same thing in AGP. Since I can't open media links directly like in ArcMap AFAIK, I have to use attachments: use tool "excel to table", since sometimes table attribute fields aren't recognized when opening the xlsx directly copy the shp into a gdb for the next step use tool "enable attachments" use tool "add attachments", here I can only specify the match path field as attribute (plus working folder). This also needs to be done for every media field restart AGP because the attachments don't show up in the attributes of the points unless this is done Now I can do/see a fraction of what I can in ArcMap: click on a point in the map look at its attributes look at a list of media with not very helpful names, but at least I can open them Alternatively, I could do this: create a 1:n relate with the point layer and attachment table enable attachments for the attachment table attach it to itself multiple times, for every media field separately This more or less replicates what can be done in ArcMap, but you have to switch around between attributes and attachments. Since you can't open files directly from the attributes like in ArcMap, accidentally mixing up media is a problem because it doesn't show their corresponding attribute field (for example "before": image4r53653235465.jpg and "after": image4r53453235465.jpg, two files which would be easily distinguishable in ArcMap wouldn't be in AGP). Compared to the single step I have to do in ArcMap and the flexibility/security it gives me, I would indeed call this "horrible". Of course, I could be just overlooking something and file opening functionality from ArcMap is included in AGP. ... View more

Your table works. Mine's a xlsx file made with Excel 2010, German version. AGP version is 1.3. Specifying the encoding when saving the table doesn't do anything. ... View more