AlanOfTheBerg wrote:It sounds like the operation is mostly working as designed:
1. Segments incorrectly labeled with "Portolla Valley" were to be automatically updated to the correct city they are in, if that city could be identified
2. Segments were set to "no city" if the city could not be positively identified and a UR posted.
Only #2 was supposed to generate a UR, but perhaps, ALL of them generated a UR? That let's us verify them at least, to make sure the update process got it correct.
skbun wrote:Does this mean some or most of the PV smudge is supposed to be gone? I've got some up in Trinity county and near Mendocino, still. Maybe the script is still running?
shawndoc wrote:skbun wrote:Does this mean some or most of the PV smudge is supposed to be gone? I've got some up in Trinity county and near Mendocino, still. Maybe the script is still running?
I spent an hour today manually cleaning up PV segments in the SoCal desert today. So no, they haven't gone anywhere.
shawndoc wrote:Just an update, I went back to two of them and turned the city layer on. It looks like there's either a smudge, or just the way Waze handles city borders, doesn't like the curvy twisty borders that sometimes crop up where multiple cities merge together.
I'll need to poke around later, as well as try to figure out what the official border lines are.
If anyone has a resource for finding the exact city borders in California cities, I'd appreciate it. (Real borders, not mailing address/zip code borders, which often don't match the actual city limits)
Update: Here's a city zoning map from one of the cities, to give you an idea of how messy things are in this area.
Users browsing this forum: Baidu [Spider]