Upgrading to Vector Tiles
Whichever option you choose, we will continue to update all of our maps with the latest data designed specifically for commercial vehicles.
If you haven’t already, please use our test page to check that the browser you are using is compatible with vector maps. Most modern browsers are able to render vector graphics but older browsers, or browsers built for specific hardware, may not.
While both our raster and vector maps platforms support map rendering, routing, geocoding and many other features, they operate very differently. As a result some features may not be directly applicable in vector as they are in raster. We recommend:
- Create a checklist of the features you are currently using with raster maps.
- Compare how those features work in vector maps versus your current raster implementation. Our guides and examples cover the many of the most common use cases. If you don’t find what you are looking for please don’t hesitate to contact our support team. They are more than happy to help you. The table below may help get you started.
|Map Initialization||Raster/ Vector|
|Context Menu||Raster/ Vector|
|Change Map Style||Raster/ Vector|
|Custom Panel||Raster/ Vector|
|EU Toll Detail Report||Raster/ Vector|
|Feature Popup||Raster/ Vector|
|Feature Visibility||Raster/ Vector|
|Geocoding Results||Raster/ Vector|
|Layer Visibility||Raster/ Vector|
|POI Layer||Raster/ Vector|
|Road Surface Layer||Raster/ Vector|
|Route Report||Raster/ Vector|
Does your existing application with raster maps make direct calls to Trimble MAPS objects and functions throughout the code? If so, you may first want to consider creating your own mapping interface to provide a degree of separation between the map library and the rest of the application. That way, when switching from raster to vector, you will only have to update that mapping interface, not the entire application.
For raster users who already have this map abstraction in place, the switch to vector maps is more straight-forward.