{"id":25851,"date":"2016-10-22T03:01:08","date_gmt":"2016-10-21T17:01:08","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=25851"},"modified":"2016-10-22T12:16:21","modified_gmt":"2016-10-22T02:16:21","slug":"geolocation-isp-ip-new-api-service-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/geolocation-isp-ip-new-api-service-tutorial\/","title":{"rendered":"Geolocation ISP IP New API Service Tutorial"},"content":{"rendered":"
\"Geolocation<\/a>

Geolocation ISP IP New API Service Tutorial<\/p><\/div>\n

The World Wide Web is one big “sharing” community, at least in the Open Source world, but most “Services” are subject to those “global economic headwinds” … you’ll forgive me, have just come from the news … and it is worth checking that a “Service” that used to be “gratis” is still that way. Revisiting Geolocation ISP IP Follow Up Tutorial<\/a> as shown below, today, resulted in that shock you get, as a programmer, when you don’t know how long something hasn’t been working according to plan. And when we say this, we’re discounting “bugs” in this assessment … totally “bug” free code is a very difficult thing to achieve from everybody’s point of view, looking at it … but, more, the prerequisite things that lean on the Open Source part of the World Wide Web, for “Service” help.<\/p>\n

So we needed a new “gratis” IP information “friend”, and, yes, we found one, so thanks, http:\/\/geoip.nekudo.com\/<\/a> for their free IP information API “Service”, and also for their associated GitHub repository<\/a> … though we made no use of its downloads today.<\/p>\n

So we’re piecing back together the functionality via the use of this new “Service” and feeding it into a table of information, off which you can visit other public websites of interest to research more. To recap, what today’s live run<\/a> (and you can download HTML programming source code you could call geoip.htm<\/a>, with changes described in this link<\/a>, and with this live run<\/a> link) does, is get Geolocation information off the IP address that the ISP providing access to the World Wide Web is using, and present that along with local Geolocation information, about where you, as the client, are positioned relative to that … sort of like wondering “where is the telecommunication tower for me getting access to the internet?”.<\/p>\n

We hope you enjoy trying it out yourself for the first time, or revisiting the web application to compare it to how it worked in days long ago … but how long ago?<\/font><\/p>\n

\n

Previous relevant Geolocation ISP IP Follow Up Tutorial<\/a> is shown below.<\/p>\n

\"Geolocation<\/a>

Geolocation ISP IP Follow Up Tutorial<\/p><\/div>\n

We discovered yesterday this great resource for data feeds (thanks to great link<\/a> for the great lead) at JSON IP and GeoIP REST API (IP Geolocation)<\/a> by Telize. In the course of discovering its usefulness we saw that it returned geolocation<\/a> data for what the ISP determined is the geographical location of your visitor IP address for your session with that ISP. So we did this at Newtown here, and went out and about and did the same execution logged into some Telstra free Wi-Fi public connection arrangement.<\/p>\n

So if this is the case, what do you think would improve the functionality of the software? You’ve probably guessed, and the scenario is awfully similar to the scenario of Yahoo YQL Nextbus JSON Primer Tutorial<\/a> … we compare “our” geographical position with the ISP’s one.<\/p>\n

Once you have two geographical positions and you wake up … well, once (a few moons ago) … as a Land Surveyor … you’d be obliged … well, you’d just have to … for all intents and purposes … in the fullness of time … calculate an Earth Great Circle Distance … or if you think we live in a wonderful worrrrrrld … we calculate an Earrrrrrth Great Circle Distance … believe it or not they calculate to be the same?! Here’s some JavaScript code …<\/p>\n


\nfunction great_circle_distance(talis, gnolis, latis, longis) {
\n var ourdist=0.0;
\n var rgnol=eval((gnolis) * Math.PI \/ 180.0);
\n var rtal=eval((talis) * Math.PI \/ 180.0);
\n var rlong=eval((longis) * Math.PI \/ 180.0);
\n var rlat=eval((latis) * Math.PI \/ 180.0);
\n var deltalong = Math.abs(eval(((gnolis)-(longis)) * Math.PI \/ 180.0));
\n var acof = eval(Math.sin(rtal) * Math.sin(rlat)) + (Math.cos(rtal) * Math.cos(rlat) * Math.cos(deltalong)); \/\/ via http:\/\/en.wikipedia.org\/wiki\/Great-circle_distance ... thanks
\n ourdist = eval(Math.round((Math.acos(acof) * 6371000.0) + 0.00001) * 100) \/ 100;
\n return ourdist;
\n}
\n<\/code><\/p>\n

So we calculate this in JavaScript and show you this along with three Google Chart Map Chart<\/a> scenarios …<\/p>\n

    \n
  1. ISP IP address position<\/li>\n
  2. Your position<\/li>\n
  3. ISP IP address position and Your position (to see how far apart they are on a map)<\/li>\n<\/ol>\n

    … if Magellan<\/a> had had Google Maps I’m sure he’d have done something similar.<\/p>\n

    Hopefully you will find something interesting with today’s live run<\/a>, and you can download HTML programming source code you could call geoip.html<\/a>, with changes to yesterday described in this link<\/a>.<\/p>\n

    \n

    Previous relevant Geolocation ISP IP Primer Tutorial<\/a> is shown below.<\/p>\n

    \"Geolocation<\/a>

    Geolocation ISP IP Primer Tutorial<\/p><\/div>\n

    It’s good every now and then to see what is new in the world of data feeds on the internet, so that is how, via this great link<\/a>, we got onto the wonderful Acronym lookup resource at NaCTeM<\/a> (The National Centre for Text Mining) which resulted in Acronyms Lookup Follow Up Tutorial<\/a> yesterday and the day before. Today we turn our attention to another great resource JSON IP and GeoIP REST API (IP Geolocation)<\/a> by Telize, whose functionality we have really enjoyed, and been intrigued by.<\/p>\n

    Geolocation<\/a> is about the “where” in life. Arguably the best looked after concept out of …<\/p>\n