That's odd.  I don't see anything wrong with the XML you posted.  Sure 'geo_co' is used twice, but that should be fine.  It means the same thing in both cases, simply with a different context.  I have little experience dealing with XML in SQL Server, but I'd have to say that if it can't parse this it is SQL Server's problem...

Actually, I take that back...I could see a problem with importing this directly in that this XML block is really several table joined together and then seperated structurally in the XML.  Still...SQL Server should be able to parse this!