I’ve got two important things to share. I solicit your valuable input:
1) a mapping problem and
2) a possible USATF/RRTC Data Sharing procedures shortcoming.
The mapping problem:
Google Earth and Google Maps provide an incorrect name for a key road that a new course is using – and, unfortunately, I relied upon it when creating the map.
If you want to follow along, the new course is NY09075JG, The Hilbert College 5K, located in Hamburg NY (5200 South Park Avenue, Hamburg NY 14075). You can see the map here if it’s not yet in the USATF database: http://BuffaloRunners.com/maps/NY09075JG.PDF
You can access Google Maps here: http://maps.google.com -- zoom in on Hilbert College in Hamburg NY.
Details: The physical road lacks any signage.
The town GIS lists the road as “unnamed road”.
Campus personnel drew a blank when I asked what the road’s name was but a few said they just referred to it as the ring road, since it rings the campus. Some, having seen some rendition of Google Maps, proclaimed the name to be "Twilight Lane".
Since Google Maps authoritatively labeled every component of the road with an unambiguous name, I went with that. I produced the map, using the name Google provided, “Twilight Lane”, and submitted the paper work. Subsequently, I learned that the name that Google Maps labeled the road with was very wrong. The name provided actually belongs to an entirely different nearby street.
Apparently, Google Maps and Google earth store the street names independently from the geographical locations and utilize an algorithm to attach the names to the streets when a map is produced. In this case, the larger unnamed street is “attracting” the name of a small dead end public street north of the campus. I have since discovered that the other road does in fact have signage indicating that it is “Twilight Lane”. Google Maps, however, leaves the other road unnamed and grants the name to our "ring road". Yikes!! Is this happening in other instances?
The procedures problem:
What I need now is a procedure to correct the map. The course measure is not affected in any way, therefore, I do not really want to pay $30 to re-certify. I just want to update the map so as to avoid confusing runners who may use the valuable USATF certified course database resource.
I’ve encountered this sort of problem before with existing maps (not my own), but the regional certifiers have not been particularly sympathetic to the need to update the maps when the certified distance was not affected.
I believe, in light of the broader availability and usage of the course maps, that it’s desirable to revisit this concept. Do we have, or can we create, a procedure to update course maps when problems are discovered that do not impact the certified distance but do impact the map’s usability and our credibility?
Original Post