![]() ![]() Reject the request by returning the value of requestContext.reject(.) (see Rejections).Complete the request by returning the value of plete(.).Generally when a route receives a request (or rather a RequestContext RequestContext for it) it can do one of these things: It also contains the current ExecutionContext and Materializer Materializer, so that these don’t have to be passed around manually. The RequestContext RequestContext is a data structure that contains the current request and auxiliary data like the so far unmatched path of the request URI that gets passed through the route structure. This is a cycling track example, so clearly is so more suited to the Cruiser app department However I think the purpose of this gpx file is clear and can therefore be useful for Kurviger app imports too.Ī gpx example file with the 3 alternative track (bicycle) routes in it.Įdiger_Eller to Cochem navtrack A_B_C_color_opacity_width.gpx (90.A Route Route itself is a function that operates on a RequestContext RequestContext and returns a RouteResult RouteResult. In the previous example, the multiple track import is an oddity, but mutliple tracks offer can also be usefully used.įind such an example with a gpx file where you so can choose from 3 different track sections at imports. (trk) track: Nice be used as overlay template.(wpt) waypoints with distance km tickmarks.The original track externally is converted to a usable gpx file for Kurviger import.ĥa85dc52b32a0279675289 wpt_rte_trk.gpx (291.5 KB) Wouldn’t it be eventually be useful if Kurviger would offer you the choice when an imported gpx file contains indeed different tracks ? Yes. So here you also have to edit that gpx file with an external program. The Kurviger1_Pro app however does not offer this option. The Kurviger app could also offer you to either calculate with track 1 called “route” or with track 2 called “track”. They do exceed the maximum number of 200, but Kurviger will limit this itself. The distance waypoints belonging to the track are then indeed usable. You could eventually use the distance waypoints as planner points but then you have to divide and select the correct waypoints set and bundle with an external program. You can import the tracks as an overlay but you have without an external operation no possibility to calculate with it. These distance km tickmark waypoints represent the distances to be driven. The other set belongs to the so correctly called “track”. The one set belongs to the so called “route”, and the sense of applying it like this escapes me completely. This is all put together in one big waypoints jar, and so you can’t do much with it. ![]() There are apparently 2 sets of extra added distance km tickmarks as (wpt) waypoints. ![]() Track 2 then has the name “track”, and this is exactly what you expect from a track. Track 1 has the misleading name “route” and although it has the characteristics of a route in terms of point density, it is definitely a track. This gpx file contains 2 tracks as well as multiple (2 bundles) km tickmarks waypoints In this form not usable for a direct import into the current Kurviger app. However, the composition of this file is very surprisingly weird. The gpx file technically complies with the gpx 1.1 standard. ![]()
0 Comments
Leave a Reply. |