{"id":5403,"date":"2013-11-30T05:02:36","date_gmt":"2013-11-29T18:02:36","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=5403"},"modified":"2013-11-30T05:02:36","modified_gmt":"2013-11-29T18:02:36","slug":"phpjavascripthtml-geographicals-by-placename-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/phpjavascripthtml-geographicals-by-placename-tutorial\/","title":{"rendered":"PHP\/Javascript\/HTML Geographicals By Placename Tutorial"},"content":{"rendered":"
\"PHP\/Javascript\/HTML<\/a>

PHP\/Javascript\/HTML Geographicals By Placename Tutorial<\/p><\/div>\n

Here is a tutorial that presents various functionality via placename lookups of Latitude and Longitude. The inhouse functionality called on include Sun Angles<\/a>, Moon Angles<\/a> and Great Circle Distances<\/a>. Am hoping it can give some pointers to ideas to do with supervision and automation, in that you can have an idea that works well (which is very important) but is not so user-friendly. Sometimes in this scenario a supervisory layer can improve things and make the application easier to use. Asking the question “What would make this easier to use?”<\/i> is a good thing to step back and ask after you have created an application. And, of course, with all things, there is the “why”<\/a><\/i>? Doing that here made me realise what was needed to improve the application was a data source that linked geographicals to placenames. This led to the creation of the new supervisor and the existing applications were modified to accept improved and more functional calling arrangements. This resulted in a central more functional central application. Not everybody likes this centralization of functionality and for a future tutorial soon we may integrate those “child”<\/i> applications in another way that doesn’t need a supervisory layer.<\/span><\/p>\n

The Javascript embellishments in this tutorial mainly revolve around:<\/p>\n