nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Does travel mode Walking have restriction on distance?

GKmieliauskas

When trying to solve route with travel mode "Walking" sometimes I get error message: "Distance between stops is too large to solve using the walking travel mode". The same routing service from web doesn't throw such error message. Is it native application library restriction? I can't say exactly but restriction distance could be about 50 km.

Environment: .Net8, Esri.ArcGISRuntime.Maui 200.4

Trouver plus de publications taguées avec

Maui

NET Framework

Accepted answers

FrankK

Yes, this is a limitation in the ArcGIS Runtime. When using walking mode, the total extent of all stops must be less than 50 miles. This limit exists because walking travel mode performs a non-hierarchical solve, which can be computationally intensive. Therefore, the code restricts the extent to reduce the load. We allow this on the server/pro version because they would be running on desktop/server machines with more resources, unlike the ArcGIS Runtime, which may operate on devices with fewer resources, such as phones.

All comments

GKmieliauskas

Hi,

After some investigation I have found that it couldn't be only distance issue. Sometimes it works on longer paths and doesn't on shorter. I noticed what it could be dependent on restricted paths for walking (highways and etc.) If it is possible to find a way that for example can cross highway but not goes along highway and distance is longer (but not so much) then it creates route. Otherwise, it returns exception. So, it depends on not only distance but and other network parameters.

OliverNoah

It seems like the error message you're encountering with the walking travel mode "Distance between stops is too large to solve using the walking travel mode" is likely due to a built-in restriction in the native application library. Many routing tools have limits on walking mode distances, typically around 50 kilometers or less, to balance the computational resources required for processing. These restrictions are common in native libraries, while web-based services might allow longer routes due to different handling mechanisms or optimized algorithms.

If your use case requires calculating longer walking routes, here are a few suggestions:

Break the Route into Segments: Split your intended route into smaller sections within the acceptable range and calculate them individually.
Explore Other Libraries or APIs: Consider using alternative APIs, like Google Maps or OpenRouteService, which might offer extended capabilities for walking mode.
Check Documentation: Refer to the specific routing library's documentation to confirm any distance limitations or find potential workarounds.
Optimization Options: Some libraries allow users to adjust parameters like granularity or approximation levels, which could help extend walking distances.

On a personal note, your question reminded me of my trip to Chandler, Arizona, last year. I stayed at my friend's home, and it was truly remarkable. The house itself was beautifully decorated, but what truly captivated me was the landscaping design. It was absolutely stunning and created a serene, welcoming atmosphere. When I asked my friend about it, they mentioned that the Chandler Landscaping design was crafted by a Chandler Landscaping Company. They seamlessly integrated lush greenery with modern aesthetics, creating a space that was both functional and visually appealing. If you're ever in Chandler, it’s worth checking out their work; they really brought the beauty of Arizona into their backyard!

OliverNoah

It looks like the error you're seeing may be due to a restriction in the native application library for the "Walking" travel mode. These modes typically have shorter distance limits, and a 50 km cap seems reasonable for pedestrian routes. The web service might handle longer routes differently, which is why you’re not encountering the same issue there.

As a frequent traveler, I'm always mindful of various rules and restrictions, especially when planning activities like foraging Hawaii, on Hawaii Island Kauai which offers unique opportunities to explore the island’s natural resources. Among my travels to countries like Japan, Australia, and the USA, my most unforgettable experience was on Kauai, where I delighted in observing its vibrant birdlife and lush landscapes. Understanding and navigating limitations in travel tools or apps ensures a seamless journey, whether it’s exploring urban areas or connecting with nature. My time on Hawaii Island remains a highlight, enriched by the beauty and adventure the island offers.

To solve your issue, consider breaking down the route into smaller segments or using a different travel mode for the longer parts. If you’re developing the app, it’s also worth checking the library for any configurable limits.

FrankK

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.