ConOjosAjenos

Comes from About geolocation on Firefox (I)

So now, we know that our web app can get easily geographic info from the client, assuming of course the client uses Firefox 3.5 or newer. We won’t talk about code samples yet but go further into the theory of geolocation, now going to the second step mentioned on the first article and do it the other way… finding geolocation on web pages from the client.

There is a number of objects we can find geotagged on a webpage. Basically it will be HTML and jpeg images.

JPEGs
JPEG images are the easiest to get, due to only one existing standard. JPEG geotagging is written on what is called EXIF metadata. EXIF metadata is embedded on the headers of JPEG files, and includes, among other things, all the shooting data as: flash use, speed, ISO value, time and date, camera model and maker, position of the camera, color space… and geolocation data. Of course, all this data has to be supported by the camera to be included (i.e. having a camera with GPS) or you need to add all this info later with another software. Just to point an example, you can get all your photos that aren’t geotagged with a software as iTag, GPSED, HoudahGEO or GeoPhoto and embed the geolocation info on the EXIF data, either pointing on a map or using an autonomous gps waypoint file. Having on the JPEG file all the info about when, where and how all your photos where taken is a very precious value…

Wikipedia has some info on how the dump of the exact data of the EXIF headers would look like, but, we can get the full info without messing around with headers with any EXIF library or tool.

See the awesome console ExifTool software, available on most distros repositories or from source on its webpage, or the Exif Viewer Firefox AddOn if you wanna mess around with EXIF headers and info.

BTW, EXIF headers can contain a lot of interesting info that most people don’t know that even exists, and can lead to info leaks. Some day I’ll write something about it…

HTML
Geotagging doesn’t rely on a single standard when talking about HTML. Digging around we can see that most used formats are:

• ICBM Used by the GeoUrl project ( that has a blog that hasn’t been updated since 2008 ) consists on a ICBM META tag containing lat/long, in form of a decimal number. As GeoUrl is also a database of geotagged sites, they also index GeoTag style tags into their database.
• GeoRDF, defined by the W3, is based on the WGS84 datum (a datum is a standard used for having reference when locating points on the Earth surface) You can check the vocabulary, that is very easy and contains lat, long and alt.
• Microformats, a much hyped tagging system (not standard but “open”, if you really care, but it works), used for “machine tagging” sections and objects, so it can make individual ‘things’ parseable and recognizable by a parser/crawler/indexer. There is a Geo Microformat available, also based on WGS84, that has lat and long properties and it’s a clone of the geo property of the vCard standard.

i.e. Flickr allows you to say where a photo or an album has been taken, and it will geotag all your photos with that info, but it won’t do it inside the EXIF data of the image, but place a pair of tags on that Flickr photo page, one ICBM and one GeoTag.

So, there’s still more to come, in next article I’ll talk about the data we are extracting, the problems we can find, and what to do with it…

So we have to give context info related to the geolocation of what we are seeying on a webpage…

We have two things to geolocate here, that is:

• Finding where are YOU, the browser, the client…
• Finding where is located the info you are reading…

On this post, we’ll talk about that first one…
With Firefox, we have an easy way of dealing with it, it used to be called Geode, and now is embedded on Firefox since 3.5 with the motto “Location Aware Browsing” . It works, more or less, on the same way OS X and iPods work for geolocating you when you have no GPS available. A webpage request your position, you allow or disallow it, it gathers your current public IP address and the ESSIDS and MAC addresses of nearby wifi access points, sends it to Google Location Services, where, checking on a huge database of IPs and access points, find your approximate position and sends it back to the webpage it requested, so it can show you geographically related info or whatever.

Asking from your app to the client, and getting a lat/long reading, in just 3 javascript lines, it’s plain awesome, and you just have to take care of having a nice way of geo searching on your database.

This is kind of cool, and is a nice tool for all that webapps with data related to a place, like directories where you can find places to eat or drink, or tourist guides, or location related services. Think about entering Amazon to buy albums, and knowing the exact rate for shipping before even beggining your order, or arriving to a hotel in a strange place, opening your favourite ‘food and drink’ directory, and, since it knows your location, even without having a gps, recomending you the best places for having dinner, a good party or a show from your favourite artist…

Due to some personal issues, both Andrea and me have been a bit away of the project (I couldn’t use my hand due to a hard sprain on my wrist) but… We’re back again!

In case you don’t konw our project, is called GeoHermes, and we want it to read geo tags on the sits you visit, so you can get related info near geographically, getting info from different feeds from social sites, services sites, and so…

So we’ll put together all the ‘blueprints’ and make the specs ready for this week…

Our project page:

https://launchpad.net/geohermes

Paul pretty much summed everything we did, and we felt on the MMTC in Madrid:

http://blog.mozbox.org/post/2009/07/21/Madrid-Mozilla-Technologies-Course-on-site-courses-done

After a damn tiring (but very funny and interesting at the same time) week on Fuenlabrada, studying the bells and whistles of XUL, XBL, FUEL JS and so on, appears that we are ready to get released on the wild.

Almost everybody defined the basis of their future projects, and we’ve been provided with a good bunch of resources and help.

BTW, my project is going to be related to geolocalization and geotags, stay tuned here if you wanna get more info…

Finally, here you have, the course photo!

We are just about to begin the Madrid Mozilla Technologies Course, and, of course, that’s an exceptional excuse for reviving this blog, dead almost for two years.

Twenty people selected from more than two hundred from all around Europe, working on the technologies that drive the public face of the Internet, our browser. Our expandable, free, and open browser.

I’m very nervous and quite sure that we’re going to work in something worthy of offering to the Mozilla users and developers community…

Good luck to everybody!

All of you probably have seen all this photos of japanese people sleeping on weird places. Some peoples says that almost a third of the sleep hours a japanese salary man has is done on the public transport. I’ve spent a month with some japanese friends in Tokyo this summer, and is really impressive where can you find people sleeping…

Mi friend Coco Tsuji and Alessandro Tinelli, made up this short movie with images of people sleeping around, but I promise you that if you travel to Tokyo you will see really really weird places for sleeping.

Empezamos un mirror de Ubuntu…

root@maquina:~# apt-mirror
Downloading 9 index files using 9 threads…
Begin time: Thu Nov 15 02:29:33 2007
[9]… [8]… [7]… [6]… [5]… [4]… [3]… [2]… [1]… [0]…
End time: Thu Nov 15 02:29:41 2007

Proceed indexes: [P]

17.1 GiB will be downloaded into archive.
Downloading 22513 archive files using 20 threads…
Begin time: Thu Nov 15 02:29:47 2007
[20]…

Termina a las 03:22.
17 GiB en 1 hora.
una media de casi 5 MiB por segundo…

Así da gusto

Odaiba es una isla artificial, junto a Tokyo, llena de centros de ocio y similares…