[EMAIL PROTECTED] wrote:

Does anyone have a recommendation as to which solution would be more optimal, both for space and processing time?

Perhaps you should consider using Postgres. It has builtin support for polygons. It can index polygon columns. And it includes some builtin functions to work with them.
http://www.postgresql.org/docs/7.4/static/datatype-geometric.html#AEN4852
http://www.postgresql.org/docs/7.4/static/functions-geometry.html


Good luck,
Bob

Reply via email to