<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Stephen, do you mind sharing what the source of the traffic disruption feed is? Mainly curious if it's one of the ones we use (email direct if needed). I had tried to do something similar a while ago but honestly did not make good progress (this was before I found st_HausdorffDistance and need to give that a try too). But I found that problems with both the input data being inaccurate and the Navteq data not always being complete caused all kinds of problems getting the matches accurate. If the input data isn't accurate or you don't have proper direction info it's very easy to pick the wrong lane or side of the street. Express lanes, upper/lower levels, and complex geometries at intersections all contributed to making the matching hard.<div><br></div><div>Nicolas, I had to do something similar with a navteq version update. In my case we'd stored the link ids from the old data set for various reasons and needed to figure out what the new link ids were for ones that had changed. As you know Navteq "retires" the ids for any change, including geometry changes. I found a combination of st_HausdorffDistance and things like making sure the direction matched got me a large portion of them matched in an automated fashion, and did the remainder semi-manually.</div><div><br></div><div>Matej, when you asked before I didn't understand everything you were trying to do, but to answer your question about the data being in the same table, you just need to do a self join to compare each row to all the others.</div><div><br></div><div>select <whatever that operation was>(t1.the_geom, t2.the_geom) from </div><div>table1 t1, table2 t2</div><div>where t1.id != t2.id</div><div>and <some operation to determine if they are close></div><div>etc.</div><div><br></div><div>charles</div><div><br><div><div>On Jan 26, 2012, at 1:56 PM, Stephen Woodbridge wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Nicolas,<br><br>I am still waiting on the actual data. The input is a traffic disruption feed with ids to one dataset and I need to map the identified segments to the equivalent segments in a Navteq data set. I suspect that I will have a combination of connected segments that form a sub-network and not a single path. But some of the sample feed data I do have references a single segment, like the location of an accident. In other cases, like a major construction project that affects multiple segments on multiple streets it will be a sub-net.<br><br>-Steve</span></blockquote></div><br></div></body></html>