Bug #43331 for Locale-Geocode: Missing FIPS codes

Mon Feb 16 10:00:41 2009 olaf [...] wundersolutions.com - Ticket created

Subject:

Missing FIPS codes

First off, great stuff! I just found your module this morning, but I plan to use it on some production machines very soon. I noticed that some of the FIPS codes which are missing in the source of Locale::Geocode can be found here: http://www.maxmind.com/app/fips_include If you like, I could look into providing you with a patch after running the data against this list. Thanks! Olaf

Wed Mar 11 19:56:08 2009 diz [...] cpan.org - Correspondence added

hi olaf. thank you for the support! i'm afraid the issue of FIPS may be somewhat muddier than either you or i initially anticipated... first of all, i never intended Locale::Geocode to be a fully compliant FIPS source. in fact, the FIPS codes are only present in Locale::Geocode because they happened to be attached to the data i began with. in retrospect, that was likely a poor decision on my part. Locale::Geocode adheres primarily to ISO 3166. this distinction is important due to a number of things i've discovered after reading up on FIPS. * many of the FIPS country codes are incompatible with ISO 3166-2 * FIPS codes are issued for some administrative divisions that do not exist in ISO 3166 * FIPS 10-4, the contents of which are referenced in the URI you provided, was withdrawn by the NIST as a standard on 2008-09-02 i see only one of two solutions for proper reconciliation: * removing the FIPS data entirely. this is certainly the easier option for me, but less likely to be endorsed by you. ;) * modularize the data to allow segregation of the FIPS data from the ISO 3166 data, since the territory and administrative divisions differ between the two. this would entail creating a namespace Locale::Geocode::Source under which Locale::Geocode::Source::FIPS and Locale::Geocode::Source::ISO3166 may live in harmony. selection of the source may be given during instantiation. i like the second option primarily since it more accurately fulfills the description implied by the name of the package. it is, after all, Locale::Geocode, not Locale::ISO3166. your thoughts?

Wed Mar 11 19:56:09 2009 The RT System itself - Status changed from 'new' to 'open'

Wed Mar 11 19:57:38 2009 diz [...] cpan.org - Taken

Thu Mar 19 11:40:02 2009 olaf [...] wundersolutions.com - Correspondence added

On Wed Mar 11 19:56:08 2009, DIZ wrote: Show quoted text

> i like the second option primarily since it more accurately fulfills the > description implied by the name of the package. it is, after all, > Locale::Geocode, not Locale::ISO3166. > > your thoughts?

That sounds reasonable to me as well. I think it makes more sense than mixing it all together and it's probably more helpful than removing that data entirely. :) If you need any help with this, let me know! Olaf

Sat May 02 19:40:22 2009 diz [...] cpan.org - Correspondence added

On Thu Mar 19 11:40:02 2009, OALDERS wrote: Show quoted text

> That sounds reasonable to me as well. I think it makes more sense

than Show quoted text

> mixing it all together and it's probably more helpful than removing

that Show quoted text

> data entirely. :) If you need any help with this, let me know!

hi olaf, i had begun work on this when my machine suffered a drive failure. :( i was able to save bits and pieces, but the event derailed my progress and it's taken me some time to gather the chutzpah to start back on it. in any event, i'm now dedicating some time to Locale::Geocode 2.0 and i could certainly use your help. right now i'm running the complete ISO 3166-2 database through some processes in order to glean the most amount of data from it, but i don't want to have to think about FIPS codes while i'm doing it. if you can provide me with a complete list of FIPS codes in a structured format (say, a CSV file or a eval()able hash referencing the ISO alpha2 codes), that would be excellent. i'll likely be moving my work to github very soon, so you will be able to follow my progress. thanks! -mike

Sat May 16 12:28:51 2009 olaf [...] wundersolutions.com - Correspondence added

Subject:	Re: [rt.cpan.org #43331] Missing FIPS codes
Date:	Sat, 16 May 2009 12:28:04 -0400
To:	bug-Locale-Geocode [...] rt.cpan.org
From:	Olaf Alders <olaf [...] wundersolutions.com>

On 2-May-09, at 7:40 PM, Mike Eldridge via RT wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=43331 >

>> hi olaf,

> > i had begun work on this when my machine suffered a drive failure. :( > i was able to save bits and pieces, but the event derailed my progress > and it's taken me some time to gather the chutzpah to start back on > it. > > in any event, i'm now dedicating some time to Locale::Geocode 2.0 > and i > could certainly use your help. > > right now i'm running the complete ISO 3166-2 database through some > processes in order to glean the most amount of data from it, but i > don't > want to have to think about FIPS codes while i'm doing it. if you can > provide me with a complete list of FIPS codes in a structured format > (say, a CSV file or a eval()able hash referencing the ISO alpha2 > codes), > that would be excellent. > > i'll likely be moving my work to github very soon, so you will be able > to follow my progress. > > thanks! > > -mike

Hi Mike, I'll put something together for you. Apologies for my response time. I've got a newborn on my hands right now, which is cutting down on a lot of my free time. :) I'll send you something as soon as I can. Please do let me know when you're set up on github. That would be helpful. Best, Olaf -- Olaf Alders olaf@wundersolutions.com http://www.wundersolutions.com

Fri Jun 05 00:31:38 2009 olaf [...] wundersolutions.com - Correspondence added

On Sat May 16 12:28:51 2009, OALDERS wrote: Show quoted text

> > On 2-May-09, at 7:40 PM, Mike Eldridge via RT wrote: >

> > <URL: https://rt.cpan.org/Ticket/Display.html?id=43331 >

> >> hi olaf,

> > > > i had begun work on this when my machine suffered a drive failure. :( > > i was able to save bits and pieces, but the event derailed my progress > > and it's taken me some time to gather the chutzpah to start back on > > it. > > > > in any event, i'm now dedicating some time to Locale::Geocode 2.0 > > and i > > could certainly use your help. > > > > right now i'm running the complete ISO 3166-2 database through some > > processes in order to glean the most amount of data from it, but i > > don't > > want to have to think about FIPS codes while i'm doing it. if you can > > provide me with a complete list of FIPS codes in a structured format > > (say, a CSV file or a eval()able hash referencing the ISO alpha2 > > codes), > > that would be excellent. > > > > i'll likely be moving my work to github very soon, so you will be able > > to follow my progress. > > > > thanks! > > > > -mike

Hi Mike, I've put something together mashing up the FIPS codes at maxmind http://www.maxmind.com/app/fips_include and the ISO codes provided by Locale::SubCountry It's in YAML format. Let me know if this is what you had in mind or if you need me to rework this. Best, Olaf

Message body is not shown because it is too large.