Differences between TruckAttributes and PTV_TruckAttributes
Posted: Thu Sep 26, 2019 1:04 pm
Hi there,
in the recent months more and more players start to migrate their xRoute applications from binary file based TruckAttributes to the feature layer based PTV_TruckAttributes.
Some experience differences in the expected output: Therefore let me just mentions some basic statements
FeatureLayer is able to close this gap.
Best regards,
Bernd
in the recent months more and more players start to migrate their xRoute applications from binary file based TruckAttributes to the feature layer based PTV_TruckAttributes.
Some experience differences in the expected output: Therefore let me just mentions some basic statements
- To avoid misunderstandings: in the following statement TruckAttributes refers to a set of 3 binary files stored in the /RE subfolder of a map. The content of those files is provided as "STANDARD by PTV" or "result of an export process from Map&Guide". On the other hand PTV_TruckAttributes refers to a feature layer mechanism which uses a large number of files in the map folder (e.g. one file for each integration unit)
- In reality some restrictions are time dependent, e.g. transit rules.
- TruckAttributes do not contain any time dependent information. So a transit rule would have to be modelled either as a STATIC rule or be missing in the data.
- One big generic advantage of FeatureLayers is the capability to handle time dependent restrictions.
- The bad news for now: currently we do not provide an administration frontend or even an administration API for FeatureLayers. This topic is in development.
FeatureLayer is able to close this gap.
Best regards,
Bernd