Latest Contributions by AndreasUlmer

Currently only geometry objects (3D models) can be displayed in CityEngine Web Scenes, so no labels or symbols. The only option now would be to prepare textures with the street labels, assign them to the features with cga and object attributes, and export as geometry objects along with the real geometry. This however will be displayed as every other geometry (e.g. will not have a constant screen size). By putting the "label geometries" on a separate layer you could mimick a labels on/off behaviour. So this is clearly a makeshift solution. You might be able to automatize the label-texture-generation process using an image library (e.g. imagemagick)  together with the CityEngine Python api. e.g. a possible workflow: 1. run a CE py script to collect street name attributes from or features, and prepare an imagemagick bat script 2. running the bat script generates per-feature label textures 3. adapt the cga script so that each feature references its label texture. Let me know if this scenario is of interest, I think I can find some scripts along these lines in the attic. FYI: We are working on a follow-up application to the CE Web Scene viewer that will support point/line/polygon geometries along with symbolisation and labels. So improvements are on the way. best Andreas ... View more

Hi Jeff thanks for the additional files, great help to reproduce the issue. I don't have a full explanation yet, but hopefully a workaround for you. 0. from the data you provided 1. open the (empty) cej. 2. import the raster 3. select terrain layer, fire up the 3ws exporter, open the Misc options tab: in the global offset field, I see the infinity values (see img) 4. get rid of those by clicking center. this will reevaluate the offset coordinates correctly 5. export -> 3ws loads fine ### I did encounter a follow up issue however on the resulting web scene: when I export the terrain on its own, I see strange holes in the resulting Web Scene. I could avoid this by adding a single shape that I manually created below the terrain (just roughly in that area). When exporting the terrain with the shape in the scene, the exported terrain looks fine (even if the shape is not included in the web scene). It looks like there is some flaw in calculating the bounding box of this terrain, causing a) the inf offset error and b) incorrectly merged (dropped) faces on export due to precision issues originating from this incorrect bounding box. and some good news: I tested the same thing in soon-to-be-released CityEngine 2013, and it works fine with none of the above issues. best Andreas ... View more

Hi Jeff thanks for the file. I looked into it and found invalid values in the 3ws (infinity values and huge coordinates), which cause the parser to break. (FYI: a 3ws is just a gzipped json file that's human readable. You can unzip a 3ws to look into it, modify and rezip it if desired. Make sure to use gzip as archive format. 7-zip works fine for this). I tried to track down where these invalid values come from. So far it seems to be a bug in the CityEngine coordinate conversion happening during 3ws export. I still need to investigate further, but it might be that it is related to that specific spatial reference you are using. As a possible woraround, can you try to prepare the raster in a different projection, and recreate the CityEngine scene with that new projection? e.g. UTM zone of Canada. For further investigation: * in what area is the raster data located? what size/extent does it span? * can you share the raster file (or a smaller extent) so we can better reproduce the problem? thanks Andreas ... View more

hi hard to say what the problem is from the distance. We'd need the 3ws file to track the problem down. Is it possible for you to share it somehow? If you don't want to share it publicly, please PM me. Andreas ... View more

andreas.ulmer, I am really sorry for asking you again... but how can I figure out what am i to type in instead of RANDOMPORTNUMBER? If new port number is randomly generated every time, waht is the way to find th current one? Start CityEngine Preview a 3ws (double-click on 3ws) Browser opens, the url shows the random port number Note: While CityEngine is running, the random port does not change. CityEngine selects one random port when it's started, and this random port is used until CityEngine is closed. When CityEngine is restarted, a new random port is generated. ... View more

Hi Matt There are not many built-in options into the information display. 1. At the moment the only option to do this is to delete the attribute. 2. CityEngine exports the attributes in reverse order to the 3ws. This is going to be fixed with the upcoming CityEngine version. 3. Not possible so far (except using iframe) 4. Not possible so far (except using iframe or CE python export script) 5. The easiest way to do this is to rename the objects in CityEngine using attribute info (with Python script) There are two possible approaches to do such things, however both include a bit of knowledge and work. a). use a python export script in CityEngine to prepocess the data before export write a python script that 1. loops over all shapes, and rewrites the attributes / the name to fit your requirements 2. triggers the 3ws export 3. (if desired) undoes the attributes to state before export b). use iframe attributes that link to your externally hosted page an attribute containing iframe code in value will embed the iframed html page in the information display. This way you can basically create your own customized information display by processing the iframe url with a server-side script (e.g. php, ashx) e.g. * prepare all shapes in CE to have an attribute of the form <iframe src="http://MYSERVER/MYPAGE.php?attr1=a&attr2=b&..."> (e.g. with Python, or already from the src data) * prepare MYPAGE.php to interprete the url params and render to html as desired does that help you further? best Andreas ... View more

1. with a custom web server (e.g. IIS, apache) CityEngine Web Viewer requires a web server to be able to tun. The 2nd part of the description text "Use CityEngine Web Viewer application on custom web server" explains how to set up CityEngine Web Viewer on an already installed web server. 2. Use CityEngine built-in web server CityEngine contains a small web server that is started when CityEngine launches. This is required for the 3ws preview application to be able to run. The url for this needs to start with http://, not with file:// (file:// bypasses the web server). Note that * the internal CityEngine web server is started with a random port number that is different everytime CityEngine is started. To load 3ws files with the CityEngine preview application, place the 3ws in a CityEngine project in your current workspace, and load it with ?3dWebScene=/PROJECT/FOLDER/WEBSCENE.3ws the complete url looks like http://localhost:RANDOMPORTNUMBER/ceviewer.html?3dWebScene=/PROJECT/FOLDER/WEBSCENE.3ws ... View more

Hi! (I saw it in one of your online tutorials) which tutorial are you referring to? ... View more

I did find an updated version of that script. same general behaviour, but slightly update UI. [ATTACH=CONFIG]23543[/ATTACH] ... View more

Hi Jussi I'm sure you checked that, but just in case: these dialogs might appear "behind" the open CE window. Might it be the fact that my workspace is in c:\users folder and im running on finnish windows 7 which autotranslates "users" to the finnish equivalent in some manner which might then result in the scripts in that folder not working? could be. can you try the following: * create a new folder C:\addscripts\ * copy measureStreetLength.py into that folder * in your CE project, File -> New... General - Folder * folder name : addscripts * choose advanced - link to alternate folder, browse to C:\addscripts * open the new linked folder, open measureStreetLength.py, Python -> Run Script ... View more

Hi Matt, Thanks for your pointer, after switching off Street Network layer the model successfully exported. But now I need to figure out whats the problem in the shape geometry. Thanks. Hi Vipulsoni can you try to limit the problem to a small area (one to several blocks)? (select a small extent of the street network layer, export, verify the problem is still present) and if so, could you post that 3ws here so we can track the problem down? ... View more

Hi Carl I there a setting that I need to change to include the bookmarks? no setting required, this should work out of the box. Can you try the following: in the problematic scene * create a new shape layer "test" with a single shape * hide all other layers * start 3ws exporter, and set exported content to "export shapes only" * exclude all layers from being exported (uncheck in second export page) except "test" * does the problem still occur? * if so, can you post the problematic 3ws here so we can track the problem down? ... View more

Hi H, modifying data within the export callbacks is tricky, or to put it frank, not working reliably. Reason is that the exporter runs in a different thread, and the shape references you get in the callbacks are not reliable references to the shapes in the scene's data structure. For your case I suggest to do the required modifications in a "preflight" method before the exporter is started. #1 set shape attributes #2 start the export process (scripted-export) #3 (restore shape attributes) Your script with these modifications is attached. (Note: Run this script directly via Python -> Run script (or f9), instead of starting the exporter) Does this help you further? best Andreas ... View more