these days I've been told by a customer that he misses certain parameters in the PTV Developer MatrixRouting API. For example he would love to set
- allow / avoid ferries
- allow / avoid tolls
- fastest / shortest routes
- maybe multiple base profiles (40t truck, 12t truck...)
- Regular PTVDeveloper Routing API grants access to many parametzers at runtime. But...
- MatrixRouting is based on precalculated HighPerformanceGraphs (HPRs) and less flexible compared to the "at runtime parametrizable full flexible conventional routing". This is necessary to ensure the performance which is exremely important in usecases whcih depend on Matrix based data such as Sequencing, Fleet optimization... Well known topic for years.
- Therefore our Matrix operations are based on a defined set of pre-defined standard profiles
- cHPR: Technically spoken we have some technology in place which allows us to create custom profiles so a customer can define certain parameters whcih we will use to calculate special HPRs (including also the capability to consider your custom road attributes). But you have to be aware of:
- These custom HPRs occupy additional ressources (CPU, Memory, DiskSpace) and therefore they come with a price - ask your sales representative to get an offer.
- If a party needs multiple HPRs this will have an impact on the price.
As this approach does only require a user to know the profile name parameter we can also benefit from this through the HSS (SAP's Hana Spatial Services)Bernd
