[0] If I take the listed xml as shown in 3:29:44 post at its face value, I would be surprised the weather forecast site's service would serve the document without a doctype defining the entity &_deg; (no underscore) and with blanks before the root element aws:weather. But, suppose it really happen. In that case, the way to salvage it is to supply your own entity definition to it.
[1] And then, the SAXParserFactory should set NamespaceAware to true so that the content handler could popular correctly local name, in case the handler makes specific use of it.
[2] I would suggest something of this kind so that you can
test it out properly. (It seems the site cannot post entity literally, so I put a underscore after & which should not be there---watch out.)