I assume it's been reconsidered as serving a sort of landmark purpose. Same as railroads — both were removed from the client a long time ago.kentsmith9 wrote:As for runways, I have always questioned the true purpose from Waze perspective, but assuming they want to market to pilots one day or we just want to see the airport as a landmark, we just need to be sure Waze will not include a runway as a routable segment once it appears in the client. Otherwise we will get routed to the back of the airport fence just because the runways are closer to the airport marker than the roadways in front of the terminal.
I believe the technical reason was that the client had no way of drawing a segment that wasn't also necessarily selectable and, at least in some way, navigable. A big change came to the livemap recently, and I believe it's safe to assume a similar big change will come to the client map in time — in fact, we were told as much by Waze staff. I assume with such a big change to the map will come a big change in the way the map is rendered, including the ability to render lines without having them also selectable and somehow navigable. Maybe I'm not as skeptical as others, but I don't believe Waze would be reintroducing railroads and runways into the client without ensuring that they are not navigable, considering how many complaints we used to get, forever ago.
Since railroads and runways are already displayed on the livemap, maybe we could build a rig and see what the routing server does. Although I'm not sure it's fair to assume that the routing server has been updated to meet the specifications of a client version that may still be months away.