Routing configuration should be reworked to avoid parameter order hardcoding about viking HOT 3 CLOSED

Agreed, the format should be more flexible.

ATM I think the most likely (least effort to implement & therefore get done) approach will be to add an extra property along the lines of:

<property name="ll-order-lat-first">FALSE</property>

To switch the order to be lon, lat.

Thus this would keep any backwards compatibly as the default would be TRUE to use lat, lon.

Ultimately a more flexible tokenizer approach would be nice and/or a smarter way to select sub-items (e.g. being able to list/select the routing profile type [cycle/car/foot/etc...] - without having to specify the whole object class common properties each time), but unlikely to get done in the near future.

from viking.

The values in the xml files get passed to sprintf, iirc. I've gotten away with using

lonlats=%2$s,%1$s

for example to make it swith the lat/lon order from what it expects.

from viking.

Addressed with #39

Add since you can also change the default ordering via the "printf positional arguments" technique '%n$' for the Nth argument - there is no need for an additional parameter reordering methods.

from viking.