I see from your data that location can be say "Western Australia, Australia"
Note there is also:
Strictly speaking asking for Australia would get you that and it would be correct (or not, depending on if you only wanted the country..).
[Australia is also a continent be I guess then for non-Australia-countries that text wouldn't be in your field..]
If you can control the table, you might want to have a separate field for country? If not:
lower(u.Location) LIKE '%australia'
or something better (in case you has a period afterwards or something..).
One more trivia: LIKE can use an index (depending on database and its cleverness = might be faster or not (by much)), except when starting with % that forces a (slower) sequential scan. This could also be an argument for having country in a separate field.
Even without % or if using a = instead of like, lower-function will also force a sequential scan. Databases with functional indexes allow you to make the right one avoiding that. Or the commonly used trick (but might just shift your work to the INSERT..):
where country = 'AU'