Our remote access service accepts requests in the form of a URL. We have chosen to use HTTP as the transport protocol as it passes easily through proxies and firewalls.

The information returned by a request is user configurable using a template file, so you can organize the data anyway that you like. We have a standard template available, or alternatively you can create your own template.

The service is accessed via http by sending a request like

Which returns a html page formatted according to your template. More information is provided on Templates below.

Once your access has been configured, you can access the service from within your cgi script with a HTTP request like –

This request uses our default template, which is designed for parsing by a perl script.

The format of the response is totally user configurable – all it is, is a text file containing tags like <geobytes city> where you would want the city name to appear. Accordingly, the tags can appear anywhere in the page, and can appear more than once. In the above standard template they appear in meta tags so that they can easily be read by a perl script.

Clients are welcome to create their own template.

Note: The template need not be HTML, it can be plain text, or coma delimited text like

"<geobytes countryid>",<geobytes country>,<geobytes latitude>,<geobytes longitude>etc

Click here for the supported tags.

Here is what the results look like when using our default template.

<meta http-equiv="countryid" content="254">
<meta http-equiv="country" content="United States">
<meta http-equiv="regionid" content="126">
<meta http-equiv="region" content="California">
<meta http-equiv="cityid" content="7433">
<meta http-equiv="city" content="Santa Barbara">
<meta http-equiv="latitude" content="34.4119">
<meta http-equiv="longitude" content="-119.72">
<meta http-equiv="timezone" content="pst">
<meta http-equiv="weighting" content="10">
<meta http-equiv="certainty" content="87">
<title>glrs Template</title>


How to get setup.
Access can be setup immediately. All we need is the IP Address of the host(s) that will be sending the resolution request to our server. We use the IP Address of the requesting host to identify authorized requests.

You can nominate as many addresses as you require. Optionally, you may also like to provide us with a ‘template’ file which will be used by our server to format the response. If you elect not to supply a custom template then our default template will be used. The template will be used to format the data that is returned by each request. We are happy to meet any special requirement that you may have regarding the format of the data. We are also happy to update the template as frequently as you may require.

The supported geobytes tags:
Our remote access service is powered by GeoSelect, so all of the geoselect tags including the control tags – <geoselect>, <geoif>, and <geobytes> are all supported.

<geobytes countryid>
<geobytes country>
<geobytes fips104>
<geobytes iso2>
<geobytes iso3>
<geobytes ison>
<geobytes internet>
<geobytes comment>

<geobytes regionid>
<geobytes region>
<geobytes code>
<geobytes adm1code>

<geobytes cityid>
<geobytes city>
<geobytes latitude>
<geobytes longitude>
<geobytes timezone>

DMA (US only)
<geobytes dmaid>
<geobytes dma>
<geobytes market>

<geobytes certainty>
<geobytes isproxyforwarderfor>
<geobytes isproxynetwork>

Note: All tags must appear in lowercase.

Further information on the supported tags is available here.

– because everybody's somewhere