The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
It's 8:30 in Perth and Sydney is half an hour from New Year. My lady partner has busied herself this afternoon making a pavlova which looks spectacular. Meanwhile I've had a few sherbets and now we are dressed and ready to go out to celebrate with friends. She has also offered to drive which is a real bonus. See you in 2018 which I hope is going to bring good things for you all.
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
So here I am updating a list of a countries in a database I'm working on (fun stuff) to be all recent and fancy etc. I decided "hey, why not get all official and go with ISO standards." Cool right?
Well, therein makes one wonder. If you look at the list of ISO-3166-1[^] codes... UK is gone. So is Scotland, etc. You can search for ISO 3166-2:GB on the page to see the entry I'm referring to. Now it's GB for the whole darn mess. I know the UK isn't a country per sé, but when I show a list of countries as a selection on a form in a webpage and it doesn't say something like United Kingdom or Scotland and just a blanket "United Kingdom of Great Britain and Northern Ireland" in a select box that means everything and the kitchen sink, I can't help but think WTF.
So, let's say I want to store the address - including country - for a user in a database who lives in Scotland. Should I now be saying: John Doe, XYZ, in the friggin United Kingdom of Great Britain and Northern Ireland? Seems kinda silly to not just say Scotland, right?
More seriously…. if you think that’s bad enough, try adding a drop-down selector for UK counties – it’s next to impossible. Scotland and Wales both have two incompatible systems for defining counties/”administrative districts”, and while one may be “official”, try telling that to upset users because you used one and not the other…
And, going back to your original point and my reply, I once had a postcard addressed to me in “…. Wales, England”. The most astonishing thing was that it actually got delivered!
Yeah totally. It's way too verbose. Rather than re-key stuff, I just decided to add a shorthand column to the DB. So if for whatever reason I need to show the country at least it won't read like a paragraph or novel.
Thanks man, turns out I watched that same exact video. Totally wish I would've had your offer about a week ago. I just spent the entirety of this week cleaning up and tweaking my geo data (to the tune of 4million-ish cities) with all this new fancy ISO 3166 stuff. I have a about 3.5k off the wall places I have no real clue wtf their proper M49 code is though. I ended up using some private ones I found off of an XML feed on unicode.org.
Just out of curiosity, how are you naming your "regional" table that contains states, provinces, etc? I can't call mine State and I don't think Province will apply to every country in the world.
"State" or "State/region" seems to be in common use. As you say, there is no one word used by all countries - "county" in the UK, "department" in France, etc - but "state" is pretty much universally recognised, I think.
Likewise, "Zip code" seems also to be gaining universal acceptance, though many places still prefer "Post code", so maybe "Zip/Post code" is better for that.
Only thing you can be sure if is that no matter what you do, someone will be upset....
So, let's say I want to store the address - including country - for a user in a database who lives in Scotland. Should I now be saying: John Doe, XYZ, in the friggin United Kingdom of Great Britain and Northern Ireland? ...
The information that I have says that John Doe does not exist in the UKOGBANI. It is Joe Bloggs there...