Mike-1323 wrote:jasonh300 wrote:1. Having railroad on the map serves no purpose and adds no value to the map in most circumstances.
The best (possibly only) reason to have the railroad on the map is to prevent wazers on the train from contaminating the neighboring street speed data and generating a bunch of map problems as their track jumps from mapped road to mapped road. The best solution would be for wazers to turn off the app before getting on the train but barring that then having the tracks mapped is the next best solution. Of course, eliminating the "roads too far apart" map problem would be a considerable help as well.![]()
As mentioned the mapped railroad should not have junctions with navigable streets and should have its level set at one of the extremes (-5, 9) so no map problems are generated.
In the Netherlands we see railroads often running very close to streets and we see all the problems that can come from that. Adding railroads fixes almost all the problems coming from mismatching with nearby roads. Because railroads are invisible in the client we still see traces of paving during trainrides. To discourage paving in trains it would be good if railroads were visible in the client and as a fix we started using the "Walking Trail"-type. Works like a charm if enabled in both directions, and looks ok in the client.




