Usecase: Map&Guide ROAD EDITOR
Posted: Wed Aug 31, 2016 9:04 am
Hello together,
these days several players asked us about the meaning of RoadEditor / how to deal with road blockings that are not part of the standard maps and the standard truck attributes (e.g. maximum weight for bridges or maximum height for tunnels).
This is why Lars and I decided to create a little thread dealing with the basics of the MAP&GUIDE RoadEditor.
Here we go:
RoadEditor is an approved technology used for more than 5 years now.
And we are already evaluating how to proceed with this usecase in the future.
Best regards Lars & Bernd
these days several players asked us about the meaning of RoadEditor / how to deal with road blockings that are not part of the standard maps and the standard truck attributes (e.g. maximum weight for bridges or maximum height for tunnels).
This is why Lars and I decided to create a little thread dealing with the basics of the MAP&GUIDE RoadEditor.
Here we go:
- MAP&GUIDE usecase which enables users to edit attributes of existing streets within an Access or SQL Server database
- closed for cars/trucks (boolean based)
- closed for specific values (e.g. exceeding 10t total weight, 3.5m height)
- incl. time dependencies
- No insertion or deletion of missing streets possible
- Only available OnPremise
- Data conditions are related to underlying map
- In case of a map update the database is also migrated within Map&Guide
- Segments which couldn't be matched by the update have to be manipulated manually
- xServer connection to data
-
approach #1: direct connection of xRoute to RE database
- supports time dependencies
- does not support map visualization
- restricted to xRoute win32
- approach #2: export of RE database into binary file
- does not support time dependencies
- content of binary file could be displayed as TruckAttributes layer
- possible with xRoute 32/64 // win/lin
-
approach #1: direct connection of xRoute to RE database
RoadEditor is an approved technology used for more than 5 years now.
And we are already evaluating how to proceed with this usecase in the future.
Best regards Lars & Bernd