Calculate Route stored XML profile requirements
Posted: Tue Jul 28, 2020 8:45 am
Hello,
We've encountered a problem when trying to calculate a route with a stored profiled passed in as an url. As per the documentation, we've added the following key:
The profile is public and can be accessed via the browser and it has the following structure:
We've tried both with and without the parent propertie as we've seen in the documentation that parent profiles are not allowed for http urls.
The server responds with a 400 and the following hint:
"The profile must be available in the folder conf/profiles
Is there something we are missing? Are there any other criteria for accepting an xml profile?
As always your help is highly appreciated.
Thanks,
John
We've encountered a problem when trying to calculate a route with a stored profiled passed in as an url. As per the documentation, we've added the following key:
Code: Select all
{
...
"storedProfile": "{baseUrl}/publicFolder/carProfile.xml"
...
}
Code: Select all
<profile version="2" dataCompatibilityVersion="2" parent="truck40t.xml">
<vehicleProfile>
<engine/>
<weight/>
<dimensions height="244" length="1360" width="240"/>
<axle/>
<legalCondition/>
<load/>
<speeds/>
</vehicleProfile>
</profile>
The server responds with a 400 and the following hint:
"The profile must be available in the folder conf/profiles
Is there something we are missing? Are there any other criteria for accepting an xml profile?
As always your help is highly appreciated.
Thanks,
John