{"id":47779,"date":"2020-01-26T03:01:26","date_gmt":"2020-01-25T17:01:26","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=47779"},"modified":"2020-01-26T06:35:14","modified_gmt":"2020-01-25T20:35:14","slug":"integrating-timezone-places-with-geographicals-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/integrating-timezone-places-with-geographicals-tutorial\/","title":{"rendered":"Integrating Timezone Places with Geographicals Tutorial"},"content":{"rendered":"
\"Integrating<\/a>

Integrating Timezone Places with Geographicals Tutorial<\/p><\/div>\n

Revisiting our Geographicals suite of Web Applications recently, specifically Great Circle Distance<\/a> calculations we ended up hankering for a wider choice of Placename choices in the dropdowns presented. Examining the PHP code last changed around about the time of Integrating a Google Map Chart with Geographicals Tutorial<\/a> their first relevant PHP codeline goes …<\/p>\n

<?php
\n
\nrequire_once<\/a>('..\/Geographicals\/place_latlong.php');
\n<\/code>
\n?><\/p>\n

… was a reminder to us regarding the software design, where this (called) place_latlong.php code is shared around several web applications, helping out populating those Placename dropdowns we talked about above, to the extent that no changes were made to the Great Circle Distance PHP code files in order to complete our software task today.<\/p>\n

So that covers “intervention points”, always of interest to us. Knowing where<\/i> to intervene is often the most arduous part of a software integration task. Now, how about how<\/i>? Well, we could have called on PHP TimeZone<\/a> functionalities, but we think perhaps we should avoid a solution that is (totally) PHP (reliant) because we think …<\/p>\n