Looks like this is a known issue due to a misconfiguration of BART's transit feed.

(Source: I work at Google and located the relevant bug, but I don't work on maps.)