Amon Caldas
Amon Caldas
Hey @pilian Thanks for your feedback. The ORS maps client is a tool for many types of usage and one of them is to plan a route. But it can...
Which file types?
Every new route generated via user interaction made triggers an URL change. So the URL is expected to be always synchronized with the app state. The avoid polygons are also...
Hi @noerw The input itself is the simplest part. The app flow to keep applying the restrictions related to the avoid polygons once you upload a file is the key...
Hey @noerw Thanks for the comments. Yes, upload was not the proper term. I should have used `load` instead. The thing is that every change in the app inputs lead...
Hey @thibaultmol . Could you please give us more details about the optimization feature you would like see in the app? thanks
Hey @stefanocudini! Thanks for the input. How do you imagine this implemented on the map client, regarding the interface? I noticed that the response to a optimization request brings no...
May I consider that this feature is only feasible when the back-end is returning geometries? If that is the case, I will close this issue and then we could reopen...
If I follow the steps you described, right after clicking on the [>] button, the interface will have already two slots (one for starting place and another one for destination)....
The interface, at start, has only one input. But, if as described in the steps above the [>] is clicked, then it will present two inputs: one for starting point...