Updates core to 1.0-pre33. MapMatching is now taking a PMap that must contain a profile string matching one of the (now required) routing profiles. MapMatchingResource is still (only) using the vehicle/weighting parameters which are mapped to one of the available profiles using ProfileResolver. So starting with this version map matching config requires a profile section (not only when CH is used), but the web-api should still be working as before. The profile parameter for the web API will be added afterwards.
Updates core to 1.0-pre33.
MapMatching
is now taking aPMap
that must contain aprofile
string matching one of the (now required) routing profiles.MapMatchingResource
is still (only) using thevehicle/weighting
parameters which are mapped to one of the available profiles usingProfileResolver
. So starting with this version map matching config requires aprofile
section (not only when CH is used), but the web-api should still be working as before. Theprofile
parameter for the web API will be added afterwards.