Select to view content in your preferred language

Limitations Importing Streets

770
6
05-12-2022 04:47 AM
MattOlsen
New Contributor III

Hi all. 

We are using the import DXF function to create a street network for our project. We need to be quite precise about how the street network is generated and so can't draw this directly in CityEngine.

There are some limitations to how this works that are making this workflow difficult. Hoping I'm missing something and you can help me. 

This is the street network, drawn in AutoCAD:

MattOlsen_0-1652350504293.png

All lines are flattened (Z=0), and trimmed (ends of lines meet exactly). I'm using DXF version 2007 (also 2004, with the same results).

I've played around with various import options (including different settings for 'Cleanup Graph'), and have found the following issues:

1 - Streets don't join other streets at acute angles. 

MattOlsen_1-1652351391168.png

2 - Not possible to join more than 2 lines together at a node. See below - a corner is formed from 2 of the lines in the CAD file, but not the other line running through it. 

MattOlsen_2-1652355138254.png

3 - Lines drawn perpendicular to one another - some join, some don't.

No join - not possible to fix this by dragging the node of the left road away and then rejoining with the street running up and down the image.

MattOlsen_3-1652355303854.png

Join - drawn exactly the same way in CAD!

MattOlsen_4-1652355321258.png

4 - Some streets intersect and create a node, some don't:

Correct intersection shown top left - incorrect bottom right. Again, these are drawn exactly the same way in CAD.

MattOlsen_6-1652355500143.png

 

5 - Strange joins when lines meet arcs (shown in CAD vs. CityEngine)

MattOlsen_11-1652355889959.png

MattOlsen_8-1652355821951.png

 

MattOlsen_10-1652355861853.png

MattOlsen_9-1652355844545.png

--

This is really fundamental stuff that may end up making it impossible to work in CityEngine for this project, which would be a real shame!

Does anyone have any pointers on how to address the issues above?

Any help much appreciated.

0 Kudos
6 Replies
plfontes
Occasional Contributor

Hi Matt,

I have also experienced some of these issues in the past, even though my workflow was to import from GIS.

I learned that you must have nodes/vertex in every line intersection and in all lines intersecting on your original drawing before importing. So if nodes don't exist you would need to create them artificially.

Hope this helps.

0 Kudos
MattOlsen
New Contributor III

Thanks @plfontes - 

That does make sense - I've tried doing some similar in AutoCAD, separating all lines that join at a node. I've also tried adding a 'point' in AutoCAD at the intersection.

MattOlsen_0-1652362605215.png

 

Unfortunately in CityEngine I still get two overlapping streets - each with their own node, where I would want one node with 4 streets connected - 

MattOlsen_1-1652362691349.png

It doesn't seem possible to join the two nodes together - result below when I drag one of the nodes away from the other:

MattOlsen_2-1652362787743.png

Any tips for this?

 

 

 

 

 

0 Kudos
JonasObertuefer
Esri Contributor

Hi Matt,

If you can send me the DWG/DXF via PM i can have a look.

Best,
Jonas

0 Kudos
Clover4
New Contributor II

Matt,   I think you have identified several of the issues with intersections currently. 

I look at this intersection you provided and I think of the manual interventions its going to take, and even then I don't know what to expect with the inside median or the diagonal connection on the right, until I start messing with it.  So I've accepted that I might have some loss of precision for speed of modeling in these cases, and usually the city scale of the models helps to hide some of this depending on project context.   And even if these streets were joined at import of the CAD, I would still expect a lot of tinkering with the nodes and arc directions to get this to look right, so sometimes it is just easier to draw these complex intersections incrementally controlling each node and arc.

Brian_Wamsley_1-1652442385141.png

I would certainly love to see some improvements to intersections in future updates!

In your last question/example though,  you should be able to click on the orange dot and pull that to the connection location on to the other street (with a small loss in precision because it was done by hand).  It might show a weird result before you let go of the mouse click but it usually works as expected, and sometimes it crashes the program.  So I save very frequently during street edits.

 

JonasObertuefer
Esri Contributor

thanks for providing me the file, I had a look:

Issue 1-4:

As @plfontes pointed out:


you must have nodes/vertex in every line intersection and in all lines intersecting on your original drawing before importing


In AutoCAD you either have to do this manually or you have to write/find a LISP script that does this automatically for you.

Additionally, all lines that you want to be connected should be on the same layer, otherwise there will be a graph network created for each layer (you can't connect nodes from different graph networks together)

Issue 5:

Arcs are converted to multiple segments (and not curves) on import. If you want have the street curved again you need to manually edit it.

I suggest to convert the arcs to polylines using the mpedit (Express Tools) command

Issue in 2nd post joining nodes together:

pretty sure this did not work for you because they where not part of the same graph network

To achieve best results/control on import:

  • Don't drag & drop the dxf into the scene use File -> Import
    • Uncheck all options in the dialog
      dxfImportSettings2.jpg
  • Select graph network -> Cleanup Graph.../Streets...
    • Check only "Merge Nodes"
    • Set "Horizontal Merge Distance" to 1m*
    • Set "Vertical Merge Distance" to 1m*
      CleanupGraphSettings.jpg
  • In the Inspector:
    • Enalbe shapeCreation for Blocks/Nodes/Segments
    • Nodes:
      • change "type" from "smart" to "junction" or "crossing"*
      • change "angleThreshold" from "35" to "10"*
  • Resolve remaining conflicts manually:
    • Move nodes slightly into one direction
    • Merge nodes (if that’s ok)
    • Change shape parameters or completely turn off the shapeCreation for individual nodes/segments
      • e.g. sidewalkWith can be set to 0 if not needed

As @Clover4 mentioned you will loose some precison in the manual cleanup process. Unfortuantely we don't have an intersection type that generates shapes which would work well with nodes close to each other, that's a current limitation for sure but its also not very trivial what geometry to generate in such cases.

*This applies to the example street layout from this thread, for other street layouts you might want to set other values

 

 

DavidWasserman
Regular Contributor

This is generally my experience with working with close up intersection nodes as well. Often the problem can be adjusted for by buffering draw lines in some GIS/CAD platform before import to see where those problem areas will likely occur before hand. It can often be accommodated by optimizing the data for import. 

David Wasserman, AICP