Tutorial 4: Import streets

Transcription

1 Copyright Esri. All rights reserved.

2 Table of Contents Tutorial 4: Import streets Copyright Esri. All rights reserved. 2

3 Tutorial 4: Import streets Download items Tutorial data Tutorial PDF Import DXF street data CityEngine street networks CityEngine street networks are attributed graphs, consisting of graph nodes (crossings) and graph edges (street segments). They can be generated with the street grow feature, created in CityEngine, or imported via an external file, such as DXF. Prepare street data for CityEngine In this example, the main road structure for a seaside city has been sketched in Illustrator using its path and geometry tools. Export a DXF file from external CAD applications When exporting the street network, make sure the units fit the CityEngine unit system, which always interprets numbers in imported files as meters. You can open the.dxf in a text editor and look for the vertex data to see what dimensions are written out. In this example, an export scale of 1 pixel equals 10 units is set to get the needed dimensions (see the export options screen shot below). The following is vertex data generated by the DXF export operation: Vertex data... AcDb2dVertex VERTEX... The following screen shot shows suggested options in the Illustrator DXF/DWG Options dialog box: Copyright Esri. All rights reserved. 3

4 Import a DXF file into CityEngine 1. Open the sesame_01.cej scene file. 2. Locate the sesame_streetsketch.dxf file in the data folder. 3. Right-click the file, and choose Import. The Layer 2 data layer is already added as a graph layer to be imported. Copyright Esri. All rights reserved. 4

5 4. Make sure Run Graph Cleanup Tool after Import is checked, and click Next. 5. Enable Intersect Segments, Snap Nodes to Segments, and Merge Nodes. 6. Set the snapping distance to 1 and the merging distance to Click Finish. A new graph layer called sesame_streetsketch appears in the Scene Editor. Alternatively, you can open the sesame_02.cej scene file to get the scene with the imported data. Grow minor streets Once the major streets are imported, you can start to refine the street network and grow the minor streets in between. The Street Grow Algorithm in CityEngine tries to fill existing closed blocks, so you can iteratively fill the street blocks with streets. 1. Focus the street block you want to create minor streets. 2. Create two single small streets using the graph edit tool. This a) specifies the general orientation of the streets in the block, and b) defines a starting node for the Street Grow Algorithm. 3. Manually create some street segments. 4. Select the segments (q key), and fill in the blank areas using the Grow Streets dialog box. Copyright Esri. All rights reserved. 5

6 The sesame_03.cej scene file contains the finished street network. Final result The sesame_12.cej scene file contains a finished street network with extracted and subdivided lots. The following screen shot shows Sesame City with generated minor streets and extracted building footprints: Copyright Esri. All rights reserved. 6

7 The following screen shot shows Sesame City with simple buildings and vegetation models: Import OSM street data "OpenStreetMap is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them." openstreetmap.org OpenStreetMap OSM is an XML-based format used to describe vector data in a map. It defines three basic data types nodes, ways, and closed ways which are used to describe all the other elements: Nodes Points between which segments are drawn. Ways Ordered list of nodes, displayed as connected by line segments in the editor. Closed Ways Ways that go in a complete loop. They are used to describe areas such as parks, lakes, or islands. Copyright Esri. All rights reserved. 7

8 Export an OSM file from OpenStreetMap The OSM data for this tutorial (area of historical Pompeii) was downloaded from api.openstreetmap.org/api/0.6/ map?bbox= , , , Find the.osm file in the data folder of your current CityEngine project. Import an OSM file into CityEngine 1. Open a new scene file by clicking File > New > CityEngine > CityEngine scene. 2. Drag the file into the 3D viewport. 3. In the OSM import dialog box, choose the layers to import. Typically, all streets are in the highway layer and buildings are in the building layer. Use the Select/deselect all check box to deselect all layers if necessary. 4. Set the additional options as shown in the following screen shot: Copyright Esri. All rights reserved. 8

9 5. Click Finish. 6. Accept the suggested coordinate system WGS 1984 UTM Zone 33N. 7. Click OK. Two new layers (street network and shapes) appear in the Scene Editor, and the OSM data is visible in the 3D viewport, with automatically created street shapes on the imported street centerlines. 8. Rename the graph network layer to OSM_Streets. 9. Rename the shape layer to OSM_Shapes. Street widths If you look closely at the generated street shapes, you'll notice that they differ in width. When importing OSM data with the Map OSM tags option enabled, CityEngine creates layer attributes that define street widths from OSM street types. Select a street segment and note its parameters in the Inspector. In the following screen shot, a street with highway type primary has assigned street and sidewalk width parameters according to the layer attribute mapping from the imported OSM Layer OSM_Streets: Copyright Esri. All rights reserved. 9

10 You can manually modify the street width by setting a new width value to the streetwidth parameter (the value will change to a userset value) or by using the Street Edit tool on the toolbar. OSM attribute mapping 1. Select the new graph network layer in the Scene Editor, and look at the layer attribute code in the Inspector. The street segment in the previous image is of type tertiary and is mapped to 6 meters in the function streetwidthbyclass. You can change the mapping here as desired. # // // Example OSM Tag Mapping streetscale = 1 // street width scale factor width = getobjectattr("width") lanes = getobjectattr("lanes") attr streetwidth = // street width depending on available attributes case width > 0 : width * streetscale case lanes > 0 : lanes * 3 * streetscale else : streetwidthbyclass * streetscale * one-way class = getobjectattr("highway") streetwidthbyclass = case class == "primary" : 8 case class == "secondary" : 7 case class == "tertiary" : 6 case class == "motorway" : 12 case class == "trunk" : 11 case class == "road" : 6 case class == "residential" : 5 case class == "footway" : 2 case class == "cycleway" : 2 case class == "steps" : 2 else : 4 one-way = // one-way width correction case getobjectattr("one-way") == "yes" : 0.5 else : 1 sidewalkscale = 1 // sidewalk width scale factor sidewalkwidth = case class == "primary" : 2 case class == "secondary" : 2 case class == "tertiary" : 2 case class == "residential" : 2 else : 0 attr sidewalkwidthleft = sidewalkwidth * sidewalkscale attr sidewalkwidthright = sidewalkwidth * sidewalkscale Data conflicts Imported OSM data often is not very clean and leads to conflicts (for example, overlapping streets). Open blocks or red dotted lines are indications of unconnected segments or overlapping streets, which can lead to invalid blocks. There are a number of ways to deal with such conflicts: Use the Cleanup Graph tool with different parameters. Select fewer streets from the highway layer in the import dialog box. Set street and sidewalk widths to lower values (resulting in less overlapping streets). Manually clean up the street network after import by combining or removing nearby crossings or parallel streets. Copyright Esri. All rights reserved. 10

11 The following screen shots show an example of unconnected graph nodes before and after cleaning: Note: OSM street data usually contains elevation data (attribute level), but it may be faulty. If you activate the Run Generate Bridges Tool option, CityEngine automatically works out a possible solution to deal with this. Add a map layer with georeferenced satellite imagery 1. Click File > Import > CityEngine Layers > Texture Import. 2. Browse to the pompeii_satellite.tif file in the maps folder. The pompeii_satellite.tfw world file accompanies the pompeii_satellite.tif file and stores the georeference information for the image. Therefore, the Size (bounds) and Offset (location) parameters are automatically set. See world file raster datasets for more information. 3. Click Finish to create the new texture map layer. Copyright Esri. All rights reserved. 11

12 Note: CityEngine does not reproject images on import. Choosing the coordinate system on image import is only used to calculate the correct location information. It is therefore crucial to have image data prepared in the projection used in the CityEngine scene. (In the previous example, the Pompeii satellite image has been reprojected in ArcMap to WGS 1984 UTM Zone 33N (the Scene Coordinate System used for this tutorial scene). The following screen shot show the satellite map added to OSM street data: Generate models 1. Select all shapes in the OSM_Shapes layer in the Scene Editor.. 2. Assign the osm_generic.cga rule file. Because some shapes already have a valid start rule set, the Set Start Rule dialog box appears. 3. Click Skip. 4. Click Generate. As you may have noticed, only the streets have been generated. The building shapes were not generated. Select one of them and note in the Inspector that there is no start rule assigned. Copyright Esri. All rights reserved. 12

13 5. To fix it, right-click the selected shape in the viewport and choose Select > Select Objects with Same Start Rule from the context menu. This selects all shapes with no start rule set. 6. In the Inspector, click the Select button next to the Start Rule field. 7. In the Set Start Rule dialog box, choose Lot. 8. Click Generate again. The following screen shot shows simple generic models generated on OSM data: Import shapefile (and geodatabase) street data Because the operation of importing streets from shapefiles and geodatabase files is almost identical, a specific example for geodatabases is not shown here. Shapefile data 1. Locate the streets.shp file in the data folder of the tutorial project. The shapefile also has a.prj file, which ensures correct georeferencing on import. The data consists of polylines that import as street segments in CityEngine. The data also contains a width attribute, which controls street width in CityEngine. Attribute table of the shapefile as displayed in ArcMap: Copyright Esri. All rights reserved. 13

14 Import data 1. Create a new empty CityEngine scene. 2. Drag and drop the streets.shp file from the Navigator into the 3D viewport. 3. During import, CityEngine prompts you to choose a scene coordinate system. The projection defined for the shapefile is suggested as default; use that here. Note: The.shp data in this example contains the width attribute to control the street width. Data with no such attribute results in default street widths. Street widths can also be set manually after import. Mappings to other attribute names are possible as well using attribute mapping. See the CityEngine manual for details. Cleanup The imported street shapes show some conflicting street shapes, marked with red dotted lines. Use the Cleanup Graph operation with Resolve Conflicting Shapes enabled to fix those automatically. You can also use the Simplify Graph tool to reduce unneeded complex graph segments by approximating the graph by deleting unneeded graph settings and setting the tangents. See the Street Network section of the CityEngine manual for details. Assign rule file 1. Select all street shapes. 2. From the File Navigator, drag the sesame_01.cga rule file from the projects rule folder onto the selected shapes in the 3D viewport. Simple street models are generated. Copyright Esri. All rights reserved. 14

15 Copyright Esri. All rights reserved. 15