I think maps are one widget where having a browser-/platform-level implementation has definite advantages. To be sure, depending on the browser to arrange geocoding is hazardous (I’d expect you’d get better results if you had to specify lat/long and could merely give a label to that point), and for that reason a consistent geocoding implementation as seen in a web component is good; but for the actual map rendering at least, fitting in with the platform would be good. For example, my user agent may know where I live and thus show me this place relative to that place—the sort of thing that a web component can’t possibly do.

I’m cautiously in favour of making a standardised map canvas element, without any form of geocoding (thus reducing its usefulness, admittedly), leaving it to a web component to handle geocoding through any particular provider.