[georss] Database Schema

[Ron Lake]

Of course that depends on the database.  Some databases do provide
direct XML support (e.g. Oracle, X-Hive, SQL Server etc), but thus far
this is not integrated with their spatial support. Galdos provides
spatial support for XML encoded data (geometry) in an XML database
(X-Hive).  The problem with mapping to a relational (usually the most
common choice) is tha mismatch between XML Schema/XML and RDBMS.  This
is usually not a problem for simple schemas like GeoRSS though.

R

Ron Lake
CEO and Chairman
Galdos Systems Inc
+1-604-484-2751
Be there when GIS and the Web unite! Register now for GeoWeb 2007 at
www.geoweb.org

-----Original Message-----
From: georss-bounces at lists.eogeo.org
[mailto:georss-bounces at lists.eogeo.org] On Behalf Of Raj Singh
Sent: July 1, 2007 10:33 PM
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