Cheers!
Look at these two requests:
First gather a list of the available profiles with the
xRuntime2.ServerConfigurationRequest:
Code: Select all
{
"resultFields": {
"profiles": true
}
}
This will return a list of all given profiles (botrh routing and mapping, short version below):
Code: Select all
{
"$type": "ServerConfigurationResponse",
"profiles": [
{
"name": "blackmarble",
"description": "This profile contains the blackmarble rendering style.",
"useCases": [
"rendering"
],
"displayName": "Blackmarble"
},
{
"name": "4_box_truck",
"description": "A box truck with a driver delivering goods.",
"useCases": [
"routing"
],
"displayName": "Box Truck"
}
]
}
Filter the output list by the "useCases" to limit it to the routing profiles such as car, pedestarian, truck, ... I usually use this approach to create a list box with the profile names I'd like to use for the "xServe2.RequestBase.storedProfile" property.
In the next step you can request the detailed profile settings for each profile via the
xRuntime2.getConfigurationFileRequest, e.g.:
Code: Select all
{
"fileName": "profiles/routing/4_box_truck.xml"
}
to get a response such as
Code: Select all
{
"$type": "ConfigurationFileResponse",
"fileName": "profiles/routing/4_box_truck.xml",
"contents": "<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n<profile version=\"2\" dataCompatibilityVersion=\"2\" useCases=\"routing\" displayName=\"Box Truck\">\n <description>A box truck with a driver delivering goods.</description>\n <vehicleProfile>\n <engine cylinderCapacity=\"6700\" fuelConsumption=\"15.0\" emissionTechnology=\"NONE\"/>\n <weight emptyWeight=\"3905.0\" loadWeight=\"2448.0\" totalPermittedWeight=\"6353.0\"/>\n <dimensions height=\"345.0\" heightAboveFrontAxle=\"345.0\" length=\"665.0\" width=\"238.0\"/>\n <axle axleLoad=\"3775.0\" numberOfAxles=\"2\"/>\n\t\t<speeds maximumSpeed=\"115.0\">\n\t\t\t<speedRangesByNetworkClass>\n\t\t\t\t<maximumSpeeds>120.0</maximumSpeeds>\n\t\t\t\t<maximumSpeeds>112.0</maximumSpeeds>\n\t\t\t\t<maximumSpeeds>105.0</maximumSpeeds>\n\t\t\t\t<maximumSpeeds>100.0</maximumSpeeds>\n\t\t\t\t<maximumSpeeds>95.0</maximumSpeeds>\n\t\t\t\t<maximumSpeeds>50.0</maximumSpeeds>\n\t\t\t\t<maximumSpeeds>20.0</maximumSpeeds>\n\t\t\t\t<maximumSpeeds>9.0</maximumSpeeds>\n\t\t\t\t<minimumSpeeds>70.0</minimumSpeeds>\n\t\t\t\t<minimumSpeeds>38.0</minimumSpeeds>\n\t\t\t\t<minimumSpeeds>30.0</minimumSpeeds>\n\t\t\t\t<minimumSpeeds>25.0</minimumSpeeds>\n\t\t\t\t<minimumSpeeds>20.0</minimumSpeeds>\n\t\t\t\t<minimumSpeeds>10.0</minimumSpeeds>\n\t\t\t\t<minimumSpeeds>5.0</minimumSpeeds>\n\t\t\t\t<minimumSpeeds>4.0</minimumSpeeds>\n\t\t\t</speedRangesByNetworkClass>\n </speeds>\n </vehicleProfile>\n <featureLayerProfile>\n <parameters key=\"numberOfTires\" value=\"4\"/>\n </featureLayerProfile>\n <routingProfile>\n <searchSpace>\n <excludeByNetworkClass>\n <minimumDistancesFromWaypoint>UNBOUNDED</minimumDistancesFromWaypoint>\n <minimumDistancesFromWaypoint>UNBOUNDED</minimumDistancesFromWaypoint>\n <minimumDistancesFromWaypoint>UNBOUNDED</minimumDistancesFromWaypoint>\n <minimumDistancesFromWaypoint>200</minimumDistancesFromWaypoint>\n <minimumDistancesFromWaypoint>50</minimumDistancesFromWaypoint>\n <minimumDistancesFromWaypoint>20</minimumDistancesFromWaypoint>\n <minimumDistancesFromWaypoint>10</minimumDistancesFromWaypoint>\n <minimumDistancesFromWaypoint>10</minimumDistancesFromWaypoint>\n </excludeByNetworkClass>\n </searchSpace>\n <course>\n <network>\n <penaltiesByNetworkClass>\n <penalties>0</penalties>\n <penalties>10</penalties>\n <penalties>15</penalties>\n <penalties>35</penalties>\n <penalties>40</penalties>\n <penalties>90</penalties>\n <penalties>100</penalties>\n <penalties>100</penalties>\n </penaltiesByNetworkClass>\n </network>\n </course>\n </routingProfile>\n</profile>\n"
}
I guess that was the missing info, right?
Bernd
