What the fuck, Goog?

[NE2]

http://www.google.com/search?q=Kingston+and+Dallas+Turnpike

[corco]

Wait what the fuck

[Brandon]

That's why I Bing.

http://www.bing.com/search?q=Kingston+and+Dallas+Turnpike&pc=ZUGO&form=ZGAFDF

[Alps]

... no matter how many locations these places have in Kingston and Dallas, that cannot possibly override more relevant results

[J N Winkler]

You do get the relevant results within the first five hits if you group:  {"Kingston and Dallas" turnpike} instead of {Kingston and Dallas turnpike}.  I suspect NE2's initial search produced the results it did because Google has added Google Maps' intersection-parsing logic to the main search.

[NE2]

You do get the relevant results within the first five hits if you group:  {"Kingston and Dallas" turnpike} instead of {Kingston and Dallas turnpike}.

Actually one would need to do "Kingston and|& Dallas Turnpike" because turnpike (and railroad) names can be written either way. (Though this one seems to be all 'and'.)

[J N Winkler]

Actually one would need to do "Kingston and|& Dallas Turnpike" because turnpike (and railroad) names can be written either way. (Though this one seems to be all 'and'.)

Thanks for this tip--I wouldn't have tried this since I distrust Google's parsing of pipe syntax within double quotes, but I tried it just now and it seems it produces actual results instead of complaining that there is nothing out there containing the string "&|and".