While looking through several of the routes near the San Francisco area, I've noticed that RideWithGPS occasionally has incorrect surface data and reports some unpaved distance even for routes that are completely paved. Sometimes RideWithGPS correctly reports some unintended unpaved data, and it's because the route incorrectly deviates onto a parallel unpaved path. This backfill process is the perfect time to do a quick spot check for such inconsistencies, and I would love it if we could smooth those out during this effort.
If you notice a route is incorrectly deviating onto a parallel unpaved path, please update the route and submit that to the perms team using the route update form.
Note that the perms team and the web team already have access to the unpaved distance reported by RideWithGPS. It's a good starting point, but it's far from perfect. Please don't blindly copy that value and report it as the official unpaved distance. If that number could be trusted, it would be a simple matter to backfill everything behind the scenes without this crowdsourcing effort. Instead, we're leaning heavily on folks who are familiar with these routes to provide accurate data.
Thanks,
Charlie