[georss] Photographs

[Raj Singh]

This discussion got me thinking about photographs. Is anyone doing this in a
standard way? Of course it would be best to get the geographic information
closer to the source, e.g. in the EXIF info, but getting it in the RSS
entry/item is also a useful alternative.

Over the years I've seen a few research projects in this area and the best
way to describe this is to encode the point location of the camera, the
direction it was pointing, and the camera's field of view. Then you can
compute (if you know more math than I do) what the camera actually "saw".

...any flickr or mappr people on this list want to chime in???

refs: 
http://mappr.com/about/#how_it_works
http://www.flickr.com/groups/mappr/

--
Raj

On 5/19/06 11:33 AM, "Jeroen Ticheler" <Jeroen.Ticheler at fao.org> wrote:

> Hi,
> Not sure if I understand this, its Friday 5:30PM so my brain is
> shutting down for the weekend ;-)
> 
> Anyway, I just wanted to say I think Mike's idea is interesting. I
> see 1 problem and that is that in my GeoRSS the RSS contains an image
> that is just a thumbnail. I would be very interested in seeing the
> footprints of the related metadata be correctly displayed with a
> simple (non-filled) box and than see the thumbnail when selecting a
> BBOX. At the same time I could see another URL in the feed doing just
> what Mike mentioned (even a simple GetMap request URL could be part
> of the RSS and function as an image as mentioned by Mike :-) )
> 
> Ciao,
> Jeroen
> 
> On May 19, 2006, at 4:15 PM, Josh at oklieb wrote:
> 
>> Thinking about this, I can see cases for two alternatives:
>> 
>> 1) Allow / suggest optional rss:enclosure or atom:link element(s)
>> inside of georss:where so that the link to be associated with the
>> location is clear. This could also be used to reference a web map
>> context document or the map view most useful for interpreting the
>> located content of the item / entry. This makes sense where the
>> handler for the linked resource has to be geo-aware anyway. The
>> atom:link element is more useful here since it includes "rel"
>> attribute which can identify what the resource represents. It does
>> have the complication of requiring rss and atom schemas to be
>> referenced from georss (complicated in that normative XML Schema
>> for these does not exist).
>> 
>> 2) Allow / suggest georss:where or more likely georss:point /
>> georss:box as content for  rss:enclosure or atom:link elements.
>> This would more clearly provide an optional location for existing
>> media references, easier for a non-geo feed processor to deal with.
>> This does require a somewhat "non-standard" extension to rss or
>> atom, since content for the enclosure or ink elements is undefined
>> and extension points are only defined in atom for the feed, entry,
>> and person elements.
>> 
>> These are probably not exclusive alternatives, but are valuable for
>> different situations.
>> 
>> -Josh
>> 
>> On May 19, 2006, at 9:04 AM, Josh at oklieb wrote:
>> 
>>> Interesting idea. Could you provide an example of a feed using
>>> this? People are clearly using RSS to reference a variety of media
>>> resources (e.g. podcasts) and it would be important to support
>>> interoperable ways of clearly associating a location to the
>>> referenced resource so that a client can throw them on a map with
>>> both an interpretable style and the right links.
>>> 
>>> BTW, the tag in the georss schema is named "relationshipTag"...
>>> 
>>> Cheers,
>>> 
>>> Josh Lieberman
>>> 
>>> On May 19, 2006, at 6:26 AM, Mikel Maron wrote:
>>> 
>>>> 
>>>> Anselm Hook and I were talking here at XTech about rasters in
>>>> GeoRSS, and came up with a use for the "relationshiptype" tag, to
>>>> specify that a box geometry designates the bounding box of an
>>>> image refernced in a RSS item. For example..
>>>> 
>>>> <entry>
>>>>   <title>Georeferenced Image</title>
>>>>   <id>#1234</id>
>>>> 
>>>>   <georss:where relationshiptype="image-extent">
>>>>     <gml:Envelope>
>>>>        <gml:lowerCorner>42.943 -71-32</gml:lowerCorner>
>>>>        <gml:upperCorner>43.039 -69.856</gml:upperCorner>
>>>>     </gml:Envelope>
>>>>   </georss:where>
>>>>  </entry>
>>>> 
>>>> This seems like it could be pretty useful, but not something I've
>>>> thought of before. For example, many people were sharing aerial
>>>> images of New Orleans post-hurricane in KML. Imagine being able
>>>> to subscribe to a feed in a disaster zone, containing polygons
>>>> and points of affected areas, locations of aid delivery points,
>>>> and up to date imagery.
>>>> 
>>>> Thoughts?
>>>> 
>>>> -Mikel
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> georss mailing list
>>>> georss at lists.eogeo.org
>>>> http://lists.eogeo.org/mailman/listinfo/georss
>>> 
>>> _______________________________________________
>>> georss mailing list
>>> georss at lists.eogeo.org
>>> http://lists.eogeo.org/mailman/listinfo/georss
>> 
>> _______________________________________________
>> georss mailing list
>> georss at lists.eogeo.org
>> http://lists.eogeo.org/mailman/listinfo/georss
> 
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss