Let's keep photography and mapping mashable

Many people have suggested that I submit some of my many aerial photos to Google Earth. I'd love to do that, but after looking at the instructions for adding photos, especially the "acceptance policy", I have to wonder if it's worth the effort, or even the Right Thing To Do.

First, I have to upload photos into Paroramio, which was bought by Google earlier this year.. Since I've already uploaded 17,310 photos into my Flickr account, I'm not in the mood to do that again, least of all into a silo'd service — which Panoramio appears to be, while Flickr is not... at least not as much as Panoramio.

For an idea of the difference, compare Flikr's many APIs with the single one offered by Panoramio.

Thanks to Flickr's openness, every one of my many photo sets on Flickr is also usable in a complementary service provided by Tabblo. That's why every one of my tabblos (montages) are composed of shots I've already uploaded to my Flickr account.

I love that Tabblo and Flickr both recognize that the online photo marketplace is bigger than both of them, that the photos in their archives are the property of their contributors, and that those photos should be under those contributors' control. Open APIs such as Flickr's allow users (or customers) to move photos form one service to another, on an as-needed basis. In the argot of the Identity Gang, the customer gets to federate his or her own photographs between different photo services. (Federation is a kind of sharing with the user's or customer's permission.)

But Google Earth appears to be forcing me to upload to Panoramio, if I'd like my photos to appear in Google Earth.

Now, in an ideal world — that is, one where the Net is truly symmetrical, peer-to-peer and end-to-end — I would rather do the federating myself, from my own photo archive, with my own APIs. That way I could federate selected photos to Flickr, Tabblo, Panoramio and whomever else I please. In fact, that would probably make things easier for everybody. But that's a VRM (vendor relationship management) grace we don't enjoy yet. In the absence of that, we need more open APIs between services such as these, so customers' photos can be shared at the vendor-to-vendor level.

Then there's the "acceptable use" business. Panoramio says "not selected" photos include thirteen bulleted items, including "Underwater or aerial photos similar to the satellite images from Google Maps". Well, most of the images I'd like to submit are taken from airplanes, at heights ranging from runway level to 40,000 feet. None are from the heights enjoyed by satellites, and very few are shot straight down, in the manner of satellite photos, since they're shot looking out the windows of passenger planes. Still, the rule says similar to. What is that?

I could go to the trouble of setting up a Panoramio account and try my luck after a few uploads, but I don't want to waste what little time I have. That's one thing I love about Flickr. The labor and time involved in posting and commenting on photos is very low. Tabblo has also made it very easy to assemble montages of photos, and to print them out in various ways. I'd like to see Panoramio and Google Earth operate in the same market-friendly mash-em-up way.

Maybe they do and I don't know it. Ya'll can help me with that.

Meanwhile, the photo/mapping market is a (literally) moving one for me. Specifically, I'd like to geotag every photo I take that's within sight of GPS satellites. I have two Garmin handheld GPSes and two little portable bluetooth GPS receivers that can transmit raw data to devices that know what to do with it. Far as I can tell, those do not include my Canon 30D digital SLR. They do include some Sony Cybershot cameras, however. I know that because somebody loaned me a Sony GPS-CS1, which is built to use only where Windows and Sony proprietary silos intersect, so it's useless to me. But still, its existence points the way toward geotagging of everything that might require it.

The politics of APIs are are not easy or uncomplicated. (Follow that last link to visit one example.) But I would think that services built on Linux and other open components — as are Flickr and Tabblo (haven't checked on Panoramio yet) — would veer strategically toward making photography and mapping as mashable as possible. I'd like to encourage that.

So I'll stop there and let the rest of you fill me in on what's open, what's not and where you think the whole photo/mapping market needs to go as the technologies of both increasingly intersect and overlap.


Doc Searls is the Editor in Chief of Linux Journal


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.


carlcan's picture

I have a extra gps tracking devise. it says legent and garmin on it. it locates way points and stuff like that. i was wondering if you could put it on someones car and track were they're going without you there and without them knowing. can anyone give me specific instructions on how to do this??

gps tracking devices

Visual Travel Guide

Fab...'s picture

You should try the VisualTravelGuide instead of Panoramio. It's published in google earth and the way to browse the pictures is much better and faster.

GPS logger cross-platform compatibility

Richard Akerman's picture

I don't think your comment on photo geocoding: "Sony GPS-CS1, which is built to use only where Windows and Sony proprietary silos intersect" is entirely fair. There are couple "degrees" of automation in photo geocoding: 1) automatic in-camera - almost no cameras support this. If cameras would accept Bluetooth NMEA streams, that would be the best and most open solution. Eventually though I expect cameras will just have built-in GPS. 2) External file matching. For this all you need are images files, a GPS track, and software to match up the two (by matching time stamps). While it's true that Sony's device is Windows and Sony-camera friendly, it does work with any photos that comply to EXIF 2.1, and its GPS track can be used with any standard software, whether it's RoboGEO or GPS Visualizer. The software and data files are not a big problem, there are applications for geocoding that are web-based as well as ones that run on Windows, Mac and Linux. The main barrier is device communication. Almost without exception the current GPS loggers only support "control" communication using serial-over-USB, with custom serial drivers and software that are Windows-only. That means a) you need their Windows software in order to change the GPS settings and b) you need their Windows software in order to download the files. There are two ways they could solve this: first, they could offer file browsing over Bluetooth - it's very frustrating to have a GPS logger that can communicate fine with Mac Google Earth using a NMEA serial stream over Bluetooth, but it doesn't support the Mac over USB. Second, it is a bit artificial that they don't support their drivers on the Mac - the underlying hardware architecture of a Mac is the same as a PC these days, someone commented "serial drivers should be so standardized, it's almost like they have to put extra effort into not supporting the Mac". For Mac, you can also of course insert "Linux". One good way to try to address things right now is by working with gpsbabel - they are trying to support devices cross-platform. For more info see GPS loggers and Macs: why can't we all get along?