CBenson wrote:Sure. I'm assuming its not just TIGER data, but an approximation of other map data sorces as well. So the waze developers saw fit to include this data in the waze database. Its not like they included all the data in the TIGER database. It seems that simply saying non-routeable segments are not useful and deleting them is contrary to some initial waze decision. I'm willing to do this if the data are causing problems. But I'm not going to second guess the developers decision just because I don't see how the data fit into the mission of waze.
The TIGER (or any other initial source) data was only a starting point (over 2 years ago now). It's very likely that things have changes in the minds of Waze since then.
As it stands now, there are no plans to enable a pedestrian mode in Waze. So the best recommendation now is to delete non-drivable road types if there is no purpose for them to be on the map for commuters driving a vehicle. If they are needed to stay for some other function (such as to avoid jams on adjoining roads for people who are using Waze out of scope from it's intended function - trains, bicycles, etc) - keep them mapped and be sure they are not junctioned to the road network.
Sorry, but I feel that it is silly to leave mapped elements on the map that are serving no purpose for commuters driving a vehicle.
Are you also leaving roads in your area that are not even valid, don't exist, don't go anywhere just because they were imported from TIGER? Why?