v2.37: "The operation 'createFeatureLayer' can now support segments of type COMBINED_TRANSPORT."

[Bernd Welter]

We improved the xServer v2.37 but unfortunately the following "impro release note" managed to escape from the official docs:

The operation 'createFeatureLayer' can now support segments of type COMBINED_TRANSPORT."

But trust me - the feature has been implemented!

Here's what that means:
Quite often users want to determine which explicit ferries they want to block in their "world" (or to be more precise: they want to restrict the ferries they want to see in routing results).

Let's look into this request:
The purpose:

• Create a custom feature layer scenario called "f1"
• ...based on the single segment "segmentIds": ["SEGM0002a453b15d...."], which is a COMBINED_TRANSPORT segment
• ...by blocking it
• ... in both directions
• ... anytime (no time domain given)

Code: Select all

{ "features": [
        {   "segmentIds": ["SEGM0002a453b15d...."], 
            "descriptions": 
            [   {   "attributes": [{"key": "opening","value": "0"}], "timeDomain": null  }   ],
            "direction": "BOTH"
        }
    ],
    "resultFields": { "binaryFeatureLayer": false  },
    "themeId": "PTV_RoadAttributes",
        "featureScenario": "f1",
            "requestProfile": {
        "featureLayerProfile": {
                "themes": 
                [   {   "featureScenarios": ["f1"], "id": "PTV_RoadAttributes", "enabled": true
                    }  ]
        }}}

• In xServer 2.36 and before a custom feature layer did not support to handle ferry segments:
  

  Code: Select all

  {
    "faultInfo": {
      "$type": "InvalidValueFault",
      "hint": "Please make sure that this string is a response from a PTV xServer of the same version using the same map. Do not modify this string.",
      "parameter": "/createFeatureLayerRequest/features[]/@segmentIds[]",
      "value": "SEGM0002a453..."
    },
    "message": "The encoded content is invalid."
  }
  

• With xServer 2.37 this request now returns a successful response:

  Code: Select all

  {
    "$type": "FeatureLayerResponse",
    "featureLayerDescription": {
      "themeId": "PTV_RoadAttributes",
      "featureScenario": "f1",
      "tenant": "globaltenant",
      "scope": "globalscope",
      "createdAt": "2025-05-30T12:46:54.000+02:00",
      "lastUsedAt": "2025-05-30T12:46:54.000+02:00",
      "size": 29366,
      "providerInformation": "HERE 241h0",
      "mapVersion": "6188119842897510564"
    }
  }

For those who are familiar with the xRouteToll2 Testclient:

• Creation of the layer was successful:

  

• Routing based on the scenario performs detour

  

Open questions:

• Visualization?
• How to maintain specific sets of ferries? (A single map contains thousands of COMBINED_TRANSPORT segments - often the clients want to block all but a few...
• When will this be availavble on PTV Developer?
• Provide your questions?

[Bernd Welter]

this is now also reflected in the PTV Developer Data API:

Check the changes