PTV Logistics Product Forum

Hi there,

as you might know we provide PTV Developer clients for Microsoft.NET Core on GITHUB.
As of today we do NOT provide clients for MS.NET Framework / PTV Developer.

Though MS.NET Framweork is already replaced by MS.NET Core we are aware that not every player can easily switch to MS.NET core ...

Long story short: The new rate limits are now activated

If you are running into issues due to this get back to us!

Ah - I've just been told that there's already a ticket for this... we'll push this internally...

Hello Oliver,

as a user you are supposed (by law) to use the "best approach" you can provide the required input data:

Best case: You know the actual consumption on a specific trip (e.g. based on "started the trip full, had to fill up afterwards").
If not: check the vehicle's average consumption ...

I guess you are right : the relation Wörgl / Brenner is just the partial combined transport.
CT Wörgl.png
CT Wörgl2.png
I therefore recommend that you create a ticket through the helpdesk:
The data contains only 2 out of 4 relations
The labels are incorrect

Real name Name in 2025.2H
Wörgl ...

Api VarVersion Type Date Description

Route Optimization OptiFlow API 1.16.0 FEATURE 24.06.2025 Added the option to specify a vehicle's route duration preference. This replaces routeDurationBalancing, which is deprecated.

Route Optimization OptiFlow API 1.15.1 IMPROVEMENT 11.06.2025 ...

Hello Valdas,

Is it possible to create new custom segments of type COMBINED_TRANSPORT?

The answer is simple: not possible.

All the editor functions we ever offered - whether this was based on
xServer1 + Map&Guide RoadEditor
xServer2 / xData2
PTV Developer Custom Attributes
were designed to ...

The answer definetly depends on the API of your choice - and maybe I was a bit too optimistic / not sharp enough in my statement:

PTV Developer Route Optimization Optiflow :
check constraints=>tasks=>groups: SAME_ROUTE / CONSECUTIVE (Attention: max number of this constraint is 100 and can easily ...

Here's just a quick exmple of the impact of the PTV Developer Routing APIs property "polylineMapType":
polylineMapType.png
The purpose of the property is to align the returned polyline details to the rendering engine that is used afterwards:
Raster Maps API
Vector Maps API

polylineMapType2 ...

Unfortunately we had to fix a little bug in the formula...

The proper approach is based on "the sum of products":
co2-allocation.png

In the 1st version of my response and also in the concept "emission allocation" we used to refer "the product of sums...".

Has been updated by the colleages ...