[georss] Database Schema

[Pat Cappelaere]

I agree with Raj.  Don't store the GeoRSS XML but simply the information you
are publishing.
We do use MySQL + spatial extensions to allow us to do spatial indexing and
support queries (WFS).  We are using Ruby on Rails (which makes it easier)
Pat.


> From: Raj Singh <raj at rajsingh.org>
> Date: Mon, 2 Jul 2007 01:33:20 -0400
> To: <georss at lists.eogeo.org>
> Subject: Re: [georss] Database Schema
> 
> No one has an opinion on this one? I think most people use PostGIS
> since its support for geometry is older, but the general principle is
> the same. I wouldn't store the GeoRSS GML text (XML) in the database.
> Instead, you should use the native spatial support in the database
> (http://www.mysql.org/doc/refman/5.1/en/spatial-extensions.html) to
> store the real coordinates. That allows you to do spatial indexing
> and queries. Then generate XML on the fly as needed.
> ---
> Raj
> 
> 
> On Jun 26, 2007, at 3:04 PM, rico.hauke at daimlerchrysler.com wrote:
> 
>> Hi list,
>> 
>> I need to store GeoRSS GML encoded data in a MySQL database, so I
>> was wondering if there already exists a database schema (tables,
>> keys and stuff) or if anyone has done this before?
>> 
>> Thanks,
>> Rico
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss