Solved! Go to Solution.
Still fighting with the same problem. I could get rid of the warning message mentioned in my previous post by changing the oneway attribute type to boolean (with "1" being an a active oneway and "0" both ways).
But whatever I do my problem remains: After applying "Dissolve Network" the directions of the lines go wild - even those that are restriced to oneway. They simply don't comply with the directions given in the source network that was created based on the initially uploaded shapefile. Can anyone recreate this problem or even better: Give a hint what I could have done wrong? 🙂
Shape file based networks are not supported.
But it is easy to create a new file geodatabase, then a feature dataset using the spatial reference of the shape file, copying the shapefile into that feature dataset and then creating/building a network dataset.
In a geodatabase, networks can be made with more than one feature source. So Feature Datasets (think of it like another folder on your hard disk to organize your data) are used to ensemble all the network sources in one place with the same spatial reference so that network connectivity is easy to create.
Still fighting with the same problem. I could get rid of the warning message mentioned in my previous post by changing the oneway attribute type to boolean (with "1" being an a active oneway and "0" both ways).
But whatever I do my problem remains: After applying "Dissolve Network" the directions of the lines go wild - even those that are restriced to oneway. They simply don't comply with the directions given in the source network that was created based on the initially uploaded shapefile. Can anyone recreate this problem or even better: Give a hint what I could have done wrong? 🙂
The resulting network looks just fine at first (after rebuilding) but the oneway roads have lost their directions and are often going into the wrong direction.