Conflation was a big problem for us at MTC, as well. We built (heads-up digitized) the original bicycle route dataset as a stand-alone data package, traced on top of (or copied from) the street basemap or other data sources. When we started working on the bicycle trip planner, we quickly realized that we needed to conflate this data with our basemap, at least for Class 2 & 3 facilities (Class 1, being off-street paths, could just be added to the network as new links), so as to get the other attributes like one-way that we needed to support the routing engine. I don't quite remember what the outcome was, but I think that MTC should now have a conflated version of the regional bike route database that has already been conflated to their TeleAtlas North America (TANA) basemap. As mentioned at the meeting, this is both good and bad. Good, because that will allow for routing. Bad, because TANA began life as proprietary data, so it might be tough to convince MTC that they have created a new data product and thus have license to share it -- though I think this argument can be successfully and convincingly made, as there is past precedent for this at the agency.
I'll try and set up a meeting for this group with the relevant folks at MTC soon. I'll get back to you with potential dates.
O ...let's go do
O i n t e r e s t i n g
o o o o o o o o o o o o o o o o o o