I have been planning a trip for next June to Utah from Toronto, and back again via a different route, for sightseeing purposes. One stretch of road I want to travel on is the Old Folsom Trail, and I find there is a geocoding error in Streets and Trips 2005 which is also found in the Delorme product, so it likely comes from the state where the Old Folsom Road [same route, new name] is found. At exactly 44° north latitude the stretch of the road coming south from the north and the stretch of the road comiing north from the south do not meet, with the southern portion offset west by about 6 meters or 7 yards. Since Streets and Trips does not permit me to link the road across the gap, I cannot plan my trip successfully for this part of the road using Streets and Trips, since it insists on taking me to the meeting point from the north, then looping back and around via other roads to take me to the meeting point from the south, before resuming the trip. This distorts the travel time and milage figures for the day, screws up the place for stopping for the night, and so on, because of the number of miles added for this loop around to correct for the deficient data.
Streets and Trips does NOT permit me to fix up for the error. Is there any way to get around all of the problems this sort of geocoding error creates for me? I do not want to split my 7000 kilometer trip into a day by day mapping to make it possible for me to ignore the errors on the one day caused by this error in the database. I do not want to split the day into three parts, the first being to the southern end of the north part of the road, the middle part being the loop around and the last being the part from the northern end of the southern part of the road, so that I can use the first and last parts to figure out things. That is an awful 'compromise' as it still leaves the total milage for the trip out by that amount, the estimated gas usage wrong, and that one day completely screwed up. Is there any way to get the TRIP correct when the underlying data is incorrect?
As a side note, does anyone know how long it will take for this error in the Old Folsom Road/Trail to be corrected in the database that is used to produce Streets and Trips and MapPoint? Clearly the data is purchased, likely from an intermediary between the state in question and Microsoft. Even the state itself may be getting the data from a county in the state or from a municipality in the state. So the chain of data flow from source to the product is long and it could take years to move from the source to the final product if manpower is lacking or budgets are tight. Clearly it will not be fixed in the product I am now using before I take my trip in June, since Streets and Trips 2005 just recently came out and the 2006 version will likely not be released before September 2005.
FWIW, email me directly at the username if responding as I am not likely to visit this forum very often. It is off my daily route, as it were...