RasterWeb!

HDR+

Post author By Pete Prodoehl
Post date 2009-05-15

If you’re familiar with HDR (High Dynamic Range) photography, you’ll know the results can look otherworldly (good) or cartoony (bad) or somewhere in between. Sure, sometimes you want cartoony, or an image that appears more like a painting or an illustration, but other times you really want a better photo, so that’s what this is about. (I’m calling it HDR+ for now…)

So HDR+ is the combining of an HDR image with the original non-HDR image to get the best of both worlds.

Original Photo(s) by John December.

I asked John December if I could combine this HDR photo with the original photo to see what it would look like… and he agreed.

I layered the two images in Photoshop, with the HDR on top at about 25% transparency, and I added some Gaussian blur to the sky to get rid of some of the pixelation. I also did a bit of dodging and burning here and there.

This shot of some water at Labelle Cemetery in Oconomowoc, Wisconsin is also a combination of an HDR and non-HDR image. I wanted to get rich, vibrant colors, but not have it look like an HDR image. I think it turned out quite well.

For this one, I processed one RAW file into 4 separate (different exposure) TIFF files and combined those into an HDR image, then layered two of the original TIFFs with the final HDR to get the final image.

If you’re doing HDR photography, consider playing around with this technique to get a new perspective on things… HDR plus a little more, if you will.

Tags hdr, johndecember, photos, photoshop, qtpfsgui

Uncategorized

Machine Tags for Bucketworks

Post author By Pete Prodoehl
Post date 2009-05-05
6 Comments on Machine Tags for Bucketworks

The following is a proposal for the use of machine tags for content related to Bucketworks. I’d love feedback from people familiar with machine tags, and people involved with Bucketworks.

The idea behind machine tags is adding a sort of namespace and hierarchy to a tagging system, and to assign it to a specific thing.

So for Yahoo’s Upcoming site (which lists events) PhotoCampMilwaukee had a tag like this:

  upcoming:event=1518729

These are used by Upcoming, which uses the Flickr API to gather photos for display on it’s site.

Now, we can assume that every event at Bucketworks would have a unique ID number, and use something like this:

  bucketworks:event=47264

This number could come from Drupal, CivicCRM, SalesForce, whatever… Just needs to be unique, and referenceable.

Now, we can see the same thing with users… on Flickr, if I see that Gabe is in a photo, I could use the tag:

  flickr:user=heygabe

where “flickr” represents Flickr, “user” is the thing we are specifying, and “heygabe” (his username on Flickr) is the value.

So… extended to Bucketworks, if Gabe’s username there is “gwollenburg” we might use:

  bucketworks:member=gwollenburg

Hmmm, maybe Gabe is not a member… and lots of people who come to events at Bucketworks might not be members (yet!) so maybe it is better to use “person” (but then, “user” could be the proper term as well, as the people are “users” of Bucketworks, right?)

  bucketworks:person=gwollenburg

Obviously every person needs a unique (to the Bucketworks network) username we can reference them with. (Note that I used Gabe’s Yammer username “gwollenburg” and not his bucketworks.org username: “heygabe”. (Is there also a username in SalesForce? It would be nice if there was a way to cross-reference all of them, though really, we want the most publically used one, so they are easy to determine.)

Jenn asked about tagging photos at Bucketworks with the room names, so we might use:

  bucketworks:space=greenhouse
  bucketworks:space=flowspace
  bucketworks:space=playspace
  bucketworks:space=cafe
  bucketworks:space=chromatarium
  bucketworks:space=parkinglot
  bucketworks:space=loadingdock
  bucketworks:space=sidewalk
  bucketworks:space=roof
  bucketworks:space=outside

Here are photos on Flickr with the tag bucketworks:space=playspace

(I went with “space” rather than “room” because I think it’s open to a wider interpretation, and luckily, Bucketworks seems to agree…)

(Are you thinking about geotags yet? They are another form of machine tags, and we should be using the coords for Bucketworks as well…)

The thing about machine tags is that you don’t so much just “come up with them” as they are defined by some entity, and then presented, and (hopefully) used.

So, if we did come up with a bunch of these, we would need to make them public, promote the use of them, show why you would use them (what cool things could be done, like, a slideshow with all photos from an event at Bucketworks) and having tools that make these things valuable would also be good…

What’s that? This reminds you of RDF, well, that’s okay :)

Thoughts?