45.256 -71.92

     
We had a great time in
Auckland and
Hokitika.
     
          -38.333332,176.00
          -42.709,170.97
     

Responses

1. TomL says:
   

   February 27th, 2007 at 4:20 pm (#)

   I would use such functionality. My site has a feed of recent location events grouped by day. I initially wanted to use GeoRSS for the group of locations but could not as you explain above.

2. Allan Doyle says:
   

   February 27th, 2007 at 11:02 pm (#)

   Well, do you want to describe an “item”, which is what RSS consists of, or do you wan to describe “data” which is what a collection of NZ pics or location events seems to be? Why not post a GML or whatever file at the end of the day or at the end of the trip, and point a GeoRSS item at that? If you start trying to be able to stuff every imaginable construct inside, you will wind up with a complex beast that satisfies no one.

   That said, I’m all in favor of some kind of extensibility mechanism like the SMTP X- headers that let you toss in anything you want. Just don’t expect to have everyone be able to use/generate/parse them. As long as you could strip out the X- elements and still have a valid feed, go for it. But don’t try to crosss the 80/20 line unless you have 80% of the people with you. The recent GeoRSS vote of maybe 2% of people thinking they really wanted that feature was not very compelling.

3. Dave Brondsema says:
   

   February 27th, 2007 at 11:41 pm (#)

   Given an example like yours, where you’re trying to associate locations with specific parts of your content, microformats seem the way to go. However, you say that they don’t let you specify the association very well. How so? I think something like this would work (based on the example at http://microformats.org/wiki/geo):

   We went to foo bar (at
   N 37° 24.491
   W 122° 08.313)

   or if you don’t want to display the coordinate information visually:

   We went to foo bar
   37.386013-122.082932

   This is more general-purpose than georss: you can use it anywhere you have HTML content, not just Atom, RDF, or RSS.

4. Dave Brondsema says:
   

   February 27th, 2007 at 11:43 pm (#)

   It’d be nice if there were some formatting instructions by your comment box, so I know what’s allowed and how to get a code sample like this to work. Trying again, using curly braces:

   {div class=”geo”}
   We went to foo bar (at
   {abbr class=”latitude” title=”37.408183″}N 37° 24.491{/abbr}
   {abbr class=”longitude” title=”-122.13855″}W 122° 08.313{/abbr})
   {/div}

   or if you don’t want to display the coordinate information visually:

   {div class=”geo”}
   We went to foo bar
   {span class=”latitude” style=”display:none”}37.386013{/span}{span class=”longitude” style=”display:none”}-122.082932{/span}
   {/div}

5. Andrew says:
   

   February 27th, 2007 at 11:57 pm (#)

   Dave – I haven’t had it confirmed from the “powers that be” in Microformats that your suggestion is valid. However, I agree that it should be and handles the idea of adding the content to a location.

   Allan – I think for one that is raising the discussion too high a level for what people, in the end, want to do. This is typically the problem with people describing the “Semantic Web” and “ontologies” and then the actual person creating a blog or a mashup site.

   However, you do have a good point. But I believe that users want to create an “item” that has “data”. They are writing about a single item (news story) that has data (locations in the news). I actually don’t understand how your GML example works. But it also sounds complex and multifaceted, which slows/blocks adoption (see XFN/FOAF) whereas embedding rel=”coworker met” is very easy directly in the text (HTML or RSS) I am creating.

6. Allan Doyle says:
   

   February 28th, 2007 at 9:51 am (#)

   Forget the semantic distinction between “item” and “data”, and forget the bit about GML. What I really want to say is what Mikel said in the GeoRSS list – “Small pieces, loosely joined, of simple targeted vocabularies.” – i.e. don’t put so much into any one spec that it sinks under its own weight.

7. Andrew says:
   

   February 28th, 2007 at 11:20 am (#)

   True – but how to accomodate users who have actual, now, use cases that want to meet the standard if possible (so people can use their data), or do something that will be supported (or easily changed to) in the future?

   But you’re right, which is why Geonames is good, puts the entire spec/gazeteer into that spec, so someone that needs that functionality can dive into.

   So maybe the FAQ on GeoRSS would really turn into “recipes” based on use-cases. E.g. You want to do this, use these…

8. Scot says:
   

   March 7th, 2007 at 7:02 pm (#)

   I need exactly that functionality. I’m trying to turn traffic data (in tpegML format) into Atom with geoRSS embedded data. With tpegML, a single traffic message can contain 2 points (it might allow for more, I’m not sure though and I’ve only seen 2 points at once so far) – for example if there’s an accident between junctions 9 and 10 of a motorway, then there will be 2 points – one for each junction. So this is definitely a case of 1 item with multiple points.

   I even came across this post by searching Google, looking to see if multiple points was possible or not. My back up plan if it’s not possible (and it appears it’s not) is to use a line, but that certainly does feel wrong.

9. James says:
   

   March 26th, 2007 at 9:25 am (#)

   I’m came across this discussion today and it is something I have been thinking about for a while now.

   I use the geopress plugin on my blog and many times I have wished that I could associate multiple locations to a single entry. A simple example is I write a blog post on our weekend travels and we went to x, y and z. Currently, I am only limited to geotagging one location but wish, oh how I wish, I could tag multiple locations. It would increase the power of GeoRSS to me by more accurately locating posts.

Leave a Response