Latest Contributions by MelindaMorang

Hello, Tas.  I don't think that Hierarchy is really the right tool for the job you are trying to do.  Hierarchy is meant to help very quickly solve long-distance routes on large networks, routes that would take a really long time to solve with an exact solution.  The hope is that the route computed using Hierarchy is the same or very similar to the exact route computed with Hierarchy turned off, just much faster to compute.  Thus, it is not surprising that you got the same solution when you toggled your Hierarchy value.  Hierarchy is meant to decrease computation time, not to control which roads get used in your analysis. I think you might get closer to what you want by using restriction attributes based on road class (street, off-road cycle paths, and on-road cycle paths).  You can create "soft restrictions" that have a value of "Preferred -[high/medium/low]" which serves to make the route prefer to use those road segments over others.  So you could construct your restriction attribute so that off-street cycle paths are preferred a lot, and on-street cycle paths are preferred a little less (or whatever you think is appropriate) and regular streets are just normal.  Solve the analysis with the restriction turned off for a normal analysis and then turned on to mimic people's preferred behavior.  Here is some information about Restriction attributes: Understanding network attributes—Help | ArcGIS for Desktop Finally, instead of computing the route and then intersecting it with the underlying street features (which may be imperfect in the results returned), instead, use the Copy Traversed Source Features tool (Copy Traversed Source Features—ArcGIS Pro | ArcGIS for Desktop ).  This returns a feature class of the network edges that were used in the solved route, which is exactly what you're looking for. ... View more