I implented a small collection of stored procedures to emulate spatial
operations, but more from a graphics perspective:
PointInViewport (returns all points in a viewport)
PolyInViewport ( returns all polys in a viewport)
PointInPoly (Returns all polygons that cover a point(never quite got it
going))
getFlatPoly (returns all poly points in a 2d (z=0) recordset)
getPoly (returns all poly points recordset with all 3d coordinates)

The project has since died, and I don't think the company would release the
sources.
How complicated a system are you looking for?

(All of a sudden, this is off-topic for this list. We'd better make it
private, direct emails)

Nige.


-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]On Behalf Of Kendall Sears
Sent: Monday, 23 October 2006 5:09 PM
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] Spatial extensions for Firebird


Please don't tease... If you know of an active Firebird Spatial Project
PLEASE forward that info on to me. I've been involved with GIS for over
10 years and have been drooling at the prospect of getting a Spatial
Interbase (nee Firebird) since before the OpenGIS spec was created.
Unfortunately, I didn't have the time to start such a project on my own.

Kendall

> You didn't expect me to give the whole game away, did you?
>
> ;-)
>
> N.
>
>
> -----Original Message-----
> From: firebird-support@yahoogroups.com
> [mailto:firebird-support@yahoogroups.com]On Behalf Of Kendall Sears
> Sent: Monday, 23 October 2006 2:11 PM
> To: firebird-support@yahoogroups.com
> Subject: RE: [firebird-support] Spatial extensions for Firebird
>
>
> Spatial Extensions are far more than just the data storage. The OpenGIS
> standard specifies a plethora of spatial operators that operate on the
> data storage and return specific data. These AND the data storage are
> what make up a spatial database.
>
> Now, it *IS* possible to store spatial data and spatially operate on it
> in
> a non spatial database. This is done by ESRI's ArcINFO/ArcDesktop suite
> of GIS applications to allow MS SQL Server to store spatial data in an
> otherwise spatially incompetent database.
>
> Kendall
>
> > It's easy to build, and far more flexible than implementing it in the
> > engine.
> > Imagine needing to store something the engine didn't support:
> >
> > Here's a quick sample of some tables:
>
> [Nice set of example tables deleted]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>

[Non-text portions of this message have been removed]