Latest Contributions by larryzhang1

Thanks for reply, peter, Looking forward to it. 10.2 will support both Pleiades 1A and 1B as well as SPOT6 products.... On Georeferencing tool (with RPCs) used to refine the accuracy with GCPs, do you referred to 10.1 SP2? Will the tool be integrated into (or work directly) inside MD? ... As with 10.1 RPCs are directly supported and georeferencing can be refined using the georeferencing tools in which control points can be used. Regards, ... View more

Thanks, Cody, The scripts like �??MDCS�?? (http://bit.ly/Owa2D6 ) under the ArcGIS Image Management Workflows (http://bit.ly/Z7kbNC) looks only available to the ArcGIS Online 'business' accounts. Is it correct? Do we have any other ways to get it? Regards, Larry @ Aramco ... View more

Matt, On CGA, the example of Philadelphia 2012 confuses me. Is it right example for this idea? Here, I have quick Q for consulting (sorry about those): Where are the GIS points for tree to �??grow�?? in the example CE? It looks there is no GIS points in this example. If used the attachment of SHP, how to organize the point SHP in new CE project and then make use of this example code? /** * File:    Vegetation.cga * Created: 12 Nov 2011 13:22:05 GMT */ version "2011.1" ############################################## # Attributes # # Driven by Object Attributes @Group("ATTRS",1) @Order(1) @Range("Trees","Shrub","Bush","Azalia","Iris","Fern","Rhododendron") attr type = "Trees" @Group("ATTRS",1) @Order(2) @Range(0,30) attr height = 20 @Group("ATTRS",1) @Order(3) @Range(360) attr ROTATION = rand(360) # User Attributes @Group("OPTIONS",2) @Order(1) @Range("low","high") @Description("High LOD only available for Trees yet") attr MODEL_LOD = "low" @Group("OPTIONS",2) @Order(2) attr MODEL_ASSET = case type == "Trees":   case MODEL_LOD=="high": fileRandom("assets/vegetation/trees-geometry/Tree*.obj")   else      : fileRandom("assets/vegetation/trees-billboards/alleyTree*.obj") else:   fileRandom("assets/vegetation/plants-billboards/"+type+"*.obj") @Group("OPTIONS",2) @Order(3) @Range("Meters","Feet") attr SIZE_UNIT = "Meters" @Group("OPTIONS",2) @Order(4) attr SIZE_RANDOMIZE = true @Group("OPTIONS",2) @Order(5) attr ROTATION_RANDOMIZE = true ############################################## # Constants # const unitScale = case SIZE_UNIT=="Feet": 0.3048 else: 1 const randomScale = case SIZE_RANDOMIZE: rand(0.7,1.3) else: 1 const randomRotation = case ROTATION_RANDOMIZE: rand(0,360) else: 0 ############################################## # Rules # @StartRule Point --> alignScopeToAxes(y) s(0,height*unitScale*randomScale,0) center(xz) r(0,-ROTATION+randomRotation,0) i(MODEL_ASSET) ... View more

Matt, For learning the powers of CE, can you pls instruct to implement the following idea? 1. Steps to import and organize the SHP (saying, Trees.shp) into CE project (the attachment) where there is a 'field' for different kinds of tree (1, 2, or 3), which individually represents �??pine, oak, or ash tree�??; 2.  Code trees�?? rule (with the field 'TreeHeight' & �??TreeType�??) Regards and many thanks, Here's a cool simple approach to create some variating building volumes, which can grow thinner from floor to floor. /** * File:    recursiveStepbacks.cga * Created: 5 Dec 2012 15:27:58 GMT * Author:  matt6767 */ version "2012.1" ############################################################ # GENERIC ATTRIBUTES ############################################################ @Group ("Building Volume",0)   @Order(0) attr Number_Of_Floors  = 8 @Group ("Building Volume")    @Order(1) attr Groundfloor_Height  = 6 @Group ("Building Volume")    @Order(2) attr Upperfloor_Height  = 3.5 @Group ("Recursive Detailing",1) @Order(0) attr Minimal_Stepback_Dimension  = 12 @Group ("Recursive Detailing") @Order(1) attr Stepback_Probability   = 0.25 @Group ("Recursive Detailing") @Order(2) attr Stepback_Dim     = rand(5,12) ############################################################ # FUNCTIONS ############################################################ Floorheight_Function(floorNumber) = case floorNumber == 0 :   Groundfloor_Height else :   Upperfloor_Height ############################################################ # GENERIC ATTRIBUTES ############################################################ @Hidden attr Current_Floor = 0 ############################################################ # START ############################################################ Lot --> alignScopeToAxes(y) LotAligned(scope.sy) LotAligned(yDim) --> # create a flat base extrude(world.y, 100) split(y) {yDim : BaseVolume | ~1 : NIL} BaseVolume --> comp(f) {bottom : NIL | side : BaseFacade | top : alignScopeToGeometry(yUp, 0, longest) BuildingRecursion} BuildingRecursion --> case Current_Floor > Number_Of_Floors :   NIL else :   extrude(world.y, Floorheight_Function(Current_Floor))   FloorVolume   set (Current_Floor, Current_Floor + 1)   comp(f) {top : FloorShape | all : NIL} FloorShape --> case p(Stepback_Probability) && scope.sx > Minimal_Stepback_Dimension :   alignScopeToGeometry(yUp, 0, longest)   split(x) {Stepback_Dim : BalconyShape | ~1 : BuildingRecursion} else :   alignScopeToGeometry(yUp, 0, longest)   BuildingRecursion ############################################################ # VOLUMES AND FACADES ############################################################ FloorVolume --> case Current_Floor == Number_Of_Floors :   # top floor   color(1,0,0) else :   Floor. BaseFacade --> color(.3,.3,.3) X. BalconyShape --> case Current_Floor > Number_Of_Floors :   NIL else :   extrude(1)   comp(f) {top : NIL | bottom : NIL | front : BalconyWall | back : BalconyWall | left : BalconyWall } BalconyWall --> color(.5,.7,.5) set (material.opacity, 0.7) [ATTACH=CONFIG]19717[/ATTACH] ... View more

Matt, ... http://forums.arcgis.com/threads/76669-Shapes-VS.-Models-VS.-MultiPatch It is helpful. Of course, my issue is reffered to '3D model' as multipatch (textured 3D model/shapes, if no distinction). From your post, I see the statement "MultiPatch IMPORT into CE : If a MultiPatch is imported into a CE scene via gdb, Shapes are created.". Does it mean that CE does not import 'textures' of 3D model/shapes into an 'existing' CE project or CE scene? If true, it could be an issue to CE, which should be improved in the new release of CE. Isn't it? ... View more

Many thanks for clarifications, Matt. .... CityEngine supports assets ( e.g. .dae ) which have 1 or multiple textures already assigned to it ( with correct UVs ). ... From our practice, when �??initially�?? importing 3D model with �??shape textures�?? (by photos) from geodatabase (or KMZ) into �??fresh�?? CE project and then importing others (image textures, SHP, etc.), those �??shape textures�?? can be kept 'AS IS' within 3D model. However, when importing 3D model with �??shape textures�?? into an 'existing' CE project, which already has many 3D shapes and imagery textures, those �??shape textures�?? (by photos) are lost.  Is this behavior normal? If not, any advices to avoid or fix in CE 2012.1? ... View more

Matt, ... http://forums.arcgis.com/threads/54072-textures-raster-files-concepts-in-CityEngine-ArcGIS ... The link is really helpful to clarify much confusion, especially, with recommendations and limitations when dealing with �??raster and DEM�?? in CE. Any more advices /steps to handle the issue 'Unknown Texture' partially on the image, after importing DEM? Thanks a lot, ++++++++ ... Oblique imagery is not directly supported for texturing (the images themselves of course, but not the oblique texture coordinate projection). ... What does 'not supporting the oblique texture coordinate projection in CE' mean? In fact, majority of features in 'imported' image looks fine in CE, but some parts (mainly located at areas with 'oblique' objects in the image) show the message 'Unknown Texture' after importing �??Terrain�?? data (see the attachment). Is it because of 'oblique' features in  the image? If not supporting �??oblique�?? objects of the image as texture in CE, are there any other effective ways to create those �??3D polygonal shapes�?? more accurately via using 'oblique objects' as reference? Does CE not support reverse engineering at all? ... View more

... the Identify tool still returns a pixel value of zero. ... From 'imagery processing' perspective, most likely, pixel values of zero inside the 'processed' raster imagery are not valid (except for DEM, and a few of cases for specific purposes). In other word, the pixel values in �??processed�?? panchromatic imagery should be ranged from 1 to 254 for 8-bit products. (Of course, 1-255 are widely acceptable). For RGB imagery, similarly, the pixel values (0, 0, 0) also should be avoided in the deliverables of 'processed' imagery. In fact, through this kind of inspection onto �??processed�?? imagery inside ArcGIS, it has been became one of the easiest practices as common QA/QC exercises in operation (such as, to avoid voids and black edge, etc.). ... View more

Hello. ... The circled areas in the attached image should not display as NoData as there is imagery here.  ... [ATTACH=CONFIG]20749[/ATTACH] Firstly, identify the DN (pixel values) inside the circled areas by �??Identity�?? tool and see if those are �??0�?? value. If yes, that indicates that both the background and circled areas in the MrSID imagery share same value (�??0�??) by default in ArcGIS, even though those are different from imagery perspective. So, use one of the following options, so that ArcGIS can properly differentiate those circled areas of the MrSID imagery against the background: 1. Under �??Symbology�?? of the Layer Properties in ArcGIS, check �??Display Background Value�?? and setup any color (saying, red); meanwhile, change default color in �??Display NoData�?? to other (saying, black). And then see if it works. If not, use the following solution to ensure that this issue will be solved permernently; 2. Import this MrSID into ERDAS (MrSID licensed) and then reprocess it via the Histogram/LUT. Make sure that the DN values inside those circled areas are over �??0�?? (saying, �??1�??) and then save as new image in IMG (or, export into MrSID again, if preferable) ... View more

Greeting, all, Thanks for above discussions. We need those *.DAE models georeferenced for sure. Does anyone have any practice on how effectively to georeference those DAE files in ArcGIS 10 or 10.1 (ArcGlobe or ArcScene), �??with�?? those assocciated KMZ files? Or can we spatially adjust those *.DAE models, 'with' those location-enabled footprints from geodatabase 'directly' in ArcGIS 10.1? I am wondering why one (KMZ) has georeferenced information and another (DAE) is not. (In fact, both of those *.DAE and KMZ files are saved/ exported from same SketchUp projects (7, 😎 at same time). In other word, do we have any 'efficient' way to ensure all having georeferenced information during Exporting in SketchUp? If not, what causes (standard Collada 1.4)? Regards, ... View more

It looks good. Also, do you know if the two issues in the attachment are solved or available in 2012? Here's what I found on their blog. Looks like a new version by June. Some highlights of the upcoming release include: Native 64-bit support Highly portable �?? no install needed, can run completely off a thumb drive Integrated ArcGIS Online and Portal for ArcGIS search capabilities Updated ArcGIS Online web map support Many presentation enhancements, including audio, new transition options, better slide handling, and more. Display attribute table for feature layers Built-in line and polygon buffering Custom address geocoding support (10.1 geocoding packages) More�?� ArcGIS Explorer Desktop 2012 will be released in conjunction with the final release of ArcGIS 10.1. ... View more