[georss] WAS: GeoRSS Validation Service? RETURNING TO: multiplelocations and time

[Peter Borissow]

Well I finally got a chance to knock out some code this morning - a java library to parse GeoRSS.

You can download it here:

http://www.kartographia.com/geoRSS/


Again, my hope is that we can start generating and sharing some reference software to parse GeoRSS.

I haven't had a lot of time to test this library. I can definately use some additional test data if you have any to share. I've created an atom feed to try to capture all of the variations of GML - even those not yet supported by GeoRSS.

http://www.kartographia.com/geoRSS/examples/Atom.xml

 
My hope is that once we have some reference software, we can start introducing more complex GML - like multipoint!


Thanks,
Peter





----- Original Message ----
From: Peter Borissow <peter.borissow at yahoo.com>
To: Raj Singh <raj at rajsingh.org>
Cc: Pat Cappelaere <pat at cappelaere.com>; Allan Doyle <adoyle at eogeo.org>; georss at lists.eogeo.org
Sent: Friday, March 2, 2007 5:13:53 PM
Subject: Re: [georss] WAS: GeoRSS Validation Service? RETURNING TO: multiplelocations and time


So that's a good point - the existing GeoRSS "spec" provides the option to specify coordinates in ANY reference frame! And you think multipoint geometries are going to scare users?

Just kidding. 

Anyway I'll try to get a partial implementation of a java-based GeoRSS parser out sometime this weekend or early next week for you to review. I already wrote one a while back - I just need to clean it up. It supports the following features:

- RSS, Atom, and RDF
- GeoRSS "Simple" Geometries
- A subset of GML Geometries (Point, Line, Polygon, MultiPoint, MultiLine, MultiPolygon, Envelope)
- Supports the 3 different GML coordinate formats
- It also happens to support DB2 and Sybase/SQS geometry types but I'll cut that code out

All the code does is "normalize" the geometries into a set of points and extracts the srs attribute. Coordinate transformation, rendering, mensuration, etc. are all higher level functions that should be handled by other classes. 

So why do I feel the need to do this? Because I'm still trying to convince you to adopt a wider range of gml geometries into the GeoRSS spec. 


Have a good weekend.

Peter



----- Original Message ----
From: Raj Singh <raj at rajsingh.org>
To: Peter Borissow <peter.borissow at yahoo.com>
Cc: Pat Cappelaere <pat at cappelaere.com>; Allan Doyle <adoyle at eogeo.org>; georss at lists.eogeo.org
Sent: Friday, March 2, 2007 3:57:55 PM
Subject: Re: [georss] WAS: GeoRSS Validation Service? RETURNING TO: multiplelocations and time


Parsing is one thing. Doing something smart with it is another. For  
example, if you get a GeoRSS GML geometry in, for example, a state  
plane coordinate system, can you either:
a. reproject it into lat/long to show on a Google/Yahoo/MS map or
b. reproject your map into the state plane system

That's just one example of the more general point that if you support  
GeoRSS GML, you should be able to manipulate coordinate reference  
systems in your application.
---
Raj


On Mar 2, 2007, at 2:53 PM, Peter Borissow wrote:

> Parsing RSS and Atom is a joke. Parsing GML geometries is not that  
> complicated either. In fact I wrote a limited GML parser that can  
> handle points, lines, and polygons + their "multi-" varients in  
> less than an hour. Adding the GeoRSS "simple" geometries took even  
> less time.



____________________________________________________________________________________
It's here! Your new message!  
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/


 
____________________________________________________________________________________
We won't tell. Get more on shows you hate to love 
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265