Road networks are not accurate

622
5
04-15-2019 04:53 AM
JasonPietka1
New Contributor III

How can I make this network accurate when getting map data?  Instead of having to manually fix it every time a road comes in like this.

0 Kudos
5 Replies
RobertBorchert
Frequent Contributor III

Sadly you need to fix it manually.  Bad data is bad data.

0 Kudos
JasonPietka1
New Contributor III

So ESRI cannot see if there is a median in a road?

0 Kudos
ChristianIten
Esri Contributor

Hi 

 

By default CityEngine uses OSM data and applies a set of heuristics to create street geometry. What you can do: After downloading OSM data you get a window that lets you turn off "Run generate bridges", "Run Simplify Graph.." and "Run Graph Clean Up..." this can result in a more satisfactory import. 

Hope this helps, Chris

JasonPietka1
New Contributor III

Thanks Chris I will try that.

0 Kudos
DavidWasserman
Regular Contributor

I am going to go against the grain and say I no longer do this in CityEngine. Christian Iten‌ has great suggestions for doing this work in CityEngine, but if you feel like GIS is your real pocket knife I would do the work there. 

The tools I typically use include: 

1. https://desktop.arcgis.com/en/arcmap/10.3/tools/cartography-toolbox/merge-divided-roads.htm

2. https://desktop.arcgis.com/en/arcmap/10.3/tools/cartography-toolbox/collapse-dual-lines-to-centerlin...

3. https://pro.arcgis.com/en/pro-app/tool-reference/data-management/feature-to-line.htm

4. Sometimes: https://github.com/d-wasserman/feature-line-split (Feature Line Whiskers to get width attributes from other datasets). 

Editing in GIS is just easier, and the tools to deal with attribute changes from dual carriage ways are just easier to manage there. If you go with a large enough study area, a cross-sectional database is just easier to maintain in GIS. Once imported, then I make sure everything is positioned with the tools mentioned here. 

David Wasserman, AICP
0 Kudos