[RESOLVED] Location Query

[Shaggy Hiker]

That first question is one that I've been pondering for months. A single waypoint could be tied to multiple A or multiple B, but I believe that it should never be tied to an A and a B...except that I can't be certain that nobody would use one waypoint for both. I'm also not sure about the S1 or S2 fields. One of those could EASILY be associated with an A, and possibly with a B. In all cases, it would mean that somebody got lazy, but that could happen.

One thing I have determined since I posted the question is that none of this matters and I'm not quite sure why (though it's certain that I'm the reason, and that I made the change, I just don't remember when this change was made or why). Perhaps I did ask this very question back then, I'll have to go look.

So, now it doesn't matter so much, though I'm still interested in the question. Would it really matter to de-duplicate anything if all I will ever be doing is getting the Top (1) of the Min distance? If there are duplicates, they'd sort in whatever order, since they'd have the same minimum distance, and it wouldn't matter which was first, as either way I'd get the same answer.

EDIT: After looking at threads I have started, I found a couple that were asking about different aspects of this data, but were never this question. It's something that I have played around with over the last couple decades, so I'm not surprised I've had a couple questions about these queries. In fact, at one point, every waypoint was associated with a survey, which makes some searches easier. Once that connection was severed, that may be when I moved the key field into the waypoint table, though I don't remember.