-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Canadian Postal Codes #38
Comments
I don't have a postcode/zipcode db available for the UK - so what use is it? Does it provide distance matching for candidates? |
sourcing a UK dB of postal codes is pretty easy. need one? On June 2, 2015 7:17:10 PM EDT, RussH notifications@github.com wrote:
|
Sure - just trying to find the value - as I've not used a postal code db On Wed, 3 Jun 2015 at 00:29 Alain Maisonneuve notifications@github.com
|
Hi, thinking about this - if you have the full postalcode db AND it's under a license so that it can be shared then it'd be very useful to include. |
OK excellent i will add it. On Fri, Sep 4, 2015 at 10:56 AM, RussH notifications@github.com wrote:
|
Alain, looking forward - I suspect we can bin the whole zipcode db and move ot a Such as this? Russ On 4 September 2015 at 16:28, Alain Maisonneuve notifications@github.com
|
Actually - can you drop me an email describing where in the app you use this functionality? Just trying to see if the zipcode.php replacement works with google maps lookup. But as I've never used this functionality, I can't see where you "enter a zipcode and find near candidates?" or is the functionality slightly different? |
The functionality is on the 'Edit' Candidates page. there are a few In terms of the candidate 'Search' thats actually not a bad idea. and On Mon, Sep 7, 2015 at 8:19 AM, RussH notifications@github.com wrote:
|
I only asked on 'distance from jobs to candidates' as I see there is Russ On 9 September 2015 at 21:24, Alain Maisonneuve notifications@github.com
|
I have the code added for worldwide zipcode (postcode) lookup via Google, i.e.; However it returns the information in XML. I'm just working through the SimpleXML elements that're required to extract the useful info and replace the 'zipcode database' for USA only. |
Oh fantastic, much better solution
…On November 24, 2016 8:00:24 AM EST, RussH ***@***.***> wrote:
I have the code added for worldwide zipcode (postcode) lookup via
Google, i.e.;
http://maps.googleapis.com/maps/api/geocode/xml?sensor=false&address=G612RW
However it returns the information in XML. I'm just working through the
SimpleXML elements that're required to extract the useful info and
replace the 'zipcode database' for USA only.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#38 (comment)
|
Okay, so if you go to http://demo.opencats.org/index.php?m=candidates&a=add
and use a zipcode / postcode it should now populate the address, city &
state.
Will assemble into a pull request.
…----
Russ
On 24 November 2016 at 13:03, Alain Maisonneuve <notifications@github.com>
wrote:
Oh fantastic, much better solution
On November 24, 2016 8:00:24 AM EST, RussH ***@***.***>
wrote:
>I have the code added for worldwide zipcode (postcode) lookup via
>Google, i.e.;
>http://maps.googleapis.com/maps/api/geocode/xml?sensor=
false&address=G612RW
>
>However it returns the information in XML. I'm just working through the
>SimpleXML elements that're required to extract the useful info and
>replace the 'zipcode database' for USA only.
>
>--
>You are receiving this because you authored the thread.
>Reply to this email directly or view it on GitHub:
>#38 (comment)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARQfP-fZ9rFI7DGKrrtm2sLY_Ucy6tiks5rBYsJgaJpZM4EQYdU>
.
|
upon checking - it looks like Google uses different labels in its XML
response for Address / City/State in different countries.
My test (for the UK) http://maps.googleapis.com/maps/api/geocode/xml?sensor=
false&address=G612RW
The lookup functions to return the '*route*' as street address, the '
*postal_town*' as the City, and '*administrative_area_level_2*' for state.
For USA it's slightly different. If I try http://maps.googleapis.com/
maps/api/geocode/xml?sensor=false&address=37403
The '*locality*' field is Chattanooga, and * administrative_area_level_2*
is Hamilton County. There's also '*administrative_area_level_1*' which is
Tennessee - therefore unless we have a separate lookup table based upon the
returned country from the Google XML response it may be simpler to
document that folks may need to make manual amendments to the lookup to
return the different field appropriate for their country.
A lookup table based upon the XML country to decide which fields to return
would be the ideal solution & would also accommodate opencats installations
which are recruiting in foreign countries - but that can be an enhancement
for the future. It's beyond my scope!
…----
Russ
On 24 November 2016 at 16:45, Russell Hay ***@***.***> wrote:
Okay, so if you go to http://demo.opencats.org/
index.php?m=candidates&a=add and use a zipcode / postcode it should now
populate the address, city & state.
Will assemble into a pull request.
----
Russ
On 24 November 2016 at 13:03, Alain Maisonneuve ***@***.***>
wrote:
> Oh fantastic, much better solution
>
> On November 24, 2016 8:00:24 AM EST, RussH ***@***.***>
> wrote:
> >I have the code added for worldwide zipcode (postcode) lookup via
> >Google, i.e.;
> >http://maps.googleapis.com/maps/api/geocode/xml?sensor=fals
> e&address=G612RW
> >
> >However it returns the information in XML. I'm just working through the
> >SimpleXML elements that're required to extract the useful info and
> >replace the 'zipcode database' for USA only.
> >
> >--
> >You are receiving this because you authored the thread.
> >Reply to this email directly or view it on GitHub:
> >#38 (comment)
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#38 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AARQfP-fZ9rFI7DGKrrtm2sLY_Ucy6tiks5rBYsJgaJpZM4EQYdU>
> .
>
|
I'm not sure I follow, why would you want to read the <type>? The only address components that should be considered would be the <long_name> for each component, no?
…On November 24, 2016 12:56:54 PM EST, RussH ***@***.***> wrote:
upon checking - it looks like Google uses different labels in its XML
response for Address / City/State in different countries.
My test (for the UK)
http://maps.googleapis.com/maps/api/geocode/xml?sensor=
false&address=G612RW
The lookup functions to return the '*route*' as street address, the '
*postal_town*' as the City, and '*administrative_area_level_2*' for
state.
For USA it's slightly different. If I try http://maps.googleapis.com/
maps/api/geocode/xml?sensor=false&address=37403
The '*locality*' field is Chattanooga, and *
administrative_area_level_2*
is Hamilton County. There's also '*administrative_area_level_1*' which
is
Tennessee - therefore unless we have a separate lookup table based upon
the
returned country from the Google XML response it may be simpler to
document that folks may need to make manual amendments to the lookup to
return the different field appropriate for their country.
A lookup table based upon the XML country to decide which fields to
return
would be the ideal solution & would also accommodate opencats
installations
which are recruiting in foreign countries - but that can be an
enhancement
for the future. It's beyond my scope!
----
Russ
On 24 November 2016 at 16:45, Russell Hay ***@***.***> wrote:
> Okay, so if you go to http://demo.opencats.org/
> index.php?m=candidates&a=add and use a zipcode / postcode it should
now
> populate the address, city & state.
>
> Will assemble into a pull request.
>
>
>
> ----
> Russ
>
> On 24 November 2016 at 13:03, Alain Maisonneuve
***@***.***>
> wrote:
>
>> Oh fantastic, much better solution
>>
>> On November 24, 2016 8:00:24 AM EST, RussH
***@***.***>
>> wrote:
>> >I have the code added for worldwide zipcode (postcode) lookup via
>> >Google, i.e.;
>> >http://maps.googleapis.com/maps/api/geocode/xml?sensor=fals
>> e&address=G612RW
>> >
>> >However it returns the information in XML. I'm just working through
the
>> >SimpleXML elements that're required to extract the useful info and
>> >replace the 'zipcode database' for USA only.
>> >
>> >--
>> >You are receiving this because you authored the thread.
>> >Reply to this email directly or view it on GitHub:
>>
>#38 (comment)
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>>
<#38 (comment)>,
>> or mute the thread
>>
<https://github.com/notifications/unsubscribe-auth/AARQfP-fZ9rFI7DGKrrtm2sLY_Ucy6tiks5rBYsJgaJpZM4EQYdU>
>> .
>>
>
>
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#38 (comment)
|
Hi Alain, yes we have to select on type and return the associated long_name. The issue appears to be that for different countries, we may want to return different type fields for city & state; |
Is there value in adding canadian postal codes to the zipcode table?
I have the full list.
The text was updated successfully, but these errors were encountered: