Kris and Betsy Smith http://www.croncast.com This is the keyword feed for Flickr API. Once cool, Kris and Betsy are now living on a cul de sac and breeding. Betsy really should be on the road making mad cash but that would interfere with breastfeeding. Podcasting for Download every M-W-F by 3:00 P.M. CST. en-us Palegroove Studios 2004-2013 No Croncast, Kris, Betsy, Comedy, Parenting, Funny, Palegroove, Croncast, eBay, Goodwill This is the keyword feed for Flickr API. Once cool, Kris and Betsy are now living on a cul de sac and breeding. Betsy really should be on the road making mad cash but that would interfere with breastfeeding. Podcasting for Download every M-W-F by 3:00 P.M. CST. This is the keyword feed for Flickr API. Once cool, Kris and Betsy are now living on a cul de sac and breeding. Betsy really should be on the road making mad cash but that would interfere with breastfeeding. Podcasting for Download every M-W-F by 3:00 P.M. CST. http://www.croncast.com/images/croncast_itunes.jpg http://www.croncast.com This is the keyword feed for Flickr API. Once cool, Kris and Betsy are now living on a cul de sac and breeding. Betsy really should be on the road making mad cash but that would interfere with breastfeeding. Podcasting for Download every M-W-F by 3:00 P.M. CST. Croncast - Kris and Betsy Smith info@palegroove.com http://www.croncast.com Palegroove http://www.croncast.com/rssk/1329/Make-the-Flickr-PHP-API-not-so-ugly-and-easier-to-use_photo-frame_digital.php Blog Flickr API and using RSS 2.0 feeds instead. The reason? They come with all the photo stream data that you need in a nice little package. Things like title, description, tags, date taken, date uploaded, image dimensions, etc.

What is missing from the RSS feed the ability to load comments with a photo and choose how many items are returned in the feed. The API, however, will let you load hundreds of images and load comments for each photo.

There is a catch though. The API is broken up into about a 75 different calls. Not one single call to the server can match the data that is returned in the RSS feed. To get the same data I need to make approximately 8 different calls to Flickr. Not good.

What use is the API?

It gives me the ability to create a historical back up of my photos in their most basic form with urls, date, descriptions (with html stripped) and tags. It also gives someone building an application a rich data source to do some of the things that Flickr isn't already doing - the purpose of an API.

After working with it for a few hours I became frustrated. PHP is my poison of choice and the PHP examples that Flickr uses all return serialized data. Which is great and easy to work with if you already know what the XML namespaces are but without them it is hard to access the data. And in some cases impossible without printing out the serialized array and looking at it because the returned serialized array's keys don't match the XML namespaces. Not to mention children are buried in deeper arrays that aren't as easy to access as say $title = $item->photo['title'].

Here's how I cleaned up the mess. If you are PHP guru then I am sure you could get this down to one script.

An 'include' script, sort of. View this script by URL on your server to see all name spaces:

1) Create a new PHP file declaring xml as file type - header("Content-Type: text/xml")
2) Use the url that Flickr supplies to return content in REST format
3) Comment out the line for serialization
4) Use PHP's file_get_contents() function
5) echo the returned XML

<?php header("Content-Type: text/xml"); # call the API $flickr_url = file_get_contents("http://api.flickr.com/services/rest/?api_key=YOUR-API-KEY&method=DATA-TO-RETURN); echo $flickr_url; ?>

A loader script:

1) Create a loader script
2) Call the include script - $resp = simplexml_load_file("YOUR INCLUDE SCRIPT URL");
3) Get the data out by name space, the same ones that Flickr documents

<?php $resp = simplexml_load_file("INCLUDE-SCRIPT-URL"); // Check to see if the response was loaded, else print an error if ($resp) { $results = ''; // If the response was loaded, parse it foreach($resp->photo as $photo) { $title = $photo->title; echo $title; } } ?>

To view the name spaces that you will want to access simply open up the include script by url in your browser.

For now I will stick with the RSS 2.0 feeds for blog submissions but once I have some free time I will be using the API code above to create a cached archive for my own safe keeping.

Tags: photo frame digital Flickr API PHP simple simplexml_load_file ]]>Flickr API and using RSS 2.0 feeds instead. The reason? They come with all the photo stream data that you need in a nice little package. Things like title, description, tags, date taken, date uploaded, image dimensions, etc.

What is missing from the RSS feed the ability to load comments with a photo and choose how many items are returned in the feed. The API, however, will let you load hundreds of images and load comments for each photo.

There is a catch though. The API is broken up into about a 75 different calls. Not one single call to the server can match the data that is returned in the RSS feed. To get the same data I need to make approximately 8 different calls to Flickr. Not good.

What use is the API?

It gives me the ability to create a historical back up of my photos in their most basic form with urls, date, descriptions (with html stripped) and tags. It also gives someone building an application a rich data source to do some of the things that Flickr isn't already doing - the purpose of an API.

After working with it for a few hours I became frustrated. PHP is my poison of choice and the PHP examples that Flickr uses all return serialized data. Which is great and easy to work with if you already know what the XML namespaces are but without them it is hard to access the data. And in some cases impossible without printing out the serialized array and looking at it because the returned serialized array's keys don't match the XML namespaces. Not to mention children are buried in deeper arrays that aren't as easy to access as say $title = $item->photo['title'].

Here's how I cleaned up the mess. If you are PHP guru then I am sure you could get this down to one script.

An 'include' script, sort of. View this script by URL on your server to see all name spaces:

1) Create a new PHP file declaring xml as file type - header("Content-Type: text/xml")
2) Use the url that Flickr supplies to return content in REST format
3) Comment out the line for serialization
4) Use PHP's file_get_contents() function
5) echo the returned XML

<?php header("Content-Type: text/xml"); # call the API $flickr_url = file_get_contents("http://api.flickr.com/services/rest/?api_key=YOUR-API-KEY&method=DATA-TO-RETURN); echo $flickr_url; ?>

A loader script:

1) Create a loader script
2) Call the include script - $resp = simplexml_load_file("YOUR INCLUDE SCRIPT URL");
3) Get the data out by name space, the same ones that Flickr documents

<?php $resp = simplexml_load_file("INCLUDE-SCRIPT-URL"); // Check to see if the response was loaded, else print an error if ($resp) { $results = ''; // If the response was loaded, parse it foreach($resp->photo as $photo) { $title = $photo->title; echo $title; } } ?>

To view the name spaces that you will want to access simply open up the include script by url in your browser.

For now I will stick with the RSS 2.0 feeds for blog submissions but once I have some free time I will be using the API code above to create a cached archive for my own safe keeping.

Tags: photo frame digital Flickr API PHP simple simplexml_load_file ]]> Tue, 29 Jan 2008 10:11:15 -0600 tag:croncast.com,1329 For months I have been bypassing the A loader script: 1) Create a loader script 2) Call the include script - $resp = simplexml_load_file("YOUR INCLUDE SCRIPT URL"); 3) Get the data out by name space, the same ones that Flickr documents photo as $photo) { $title = $photo->title; echo $title; } } ?> To no photo frame, digital, Flickr API, PHP, simple