* [2010-12-05 00:29:05 +0600] Ivan Mikhailov écrit:
] 1. What types of spatial things should be supported?
]
] 2. What operations should be supported?
]
] 3. What sorts of geometry should be supported?
]
] The problem is that costs of features are not additive, the total cost
] of the imple
Hello William
> One challenge is that we still have no consensus on how to express
> this type of data and these operations in RDF, but that's a separate
> issue from support in the database itself.
IMHO, the lack of consensus of candidate users is a significant problem,
and the problem is "three
* [2010-12-02 13:23:30 -0700] Wood, Jamey écrit:
] Thanks for your response. I wonder if anyone could comment on how
] difficult the remaining work would be. Since the R-Tree indexing part has
] already been implemented, I wonder if the rest would largely just be a
] matter of integrating vario
Hi Patrick,
Thanks for your response. I wonder if anyone could comment on how
difficult the remaining work would be. Since the R-Tree indexing part has
already been implemented, I wonder if the rest would largely just be a
matter of integrating various higher-level functionality from an existing
Hi Jamey,
In playing with a trial copy of Virtuoso 6.2 (Commercial Edition),
I've noticed that it appears that its geospatial capabilities only
cover points. For example:
SQL> select st_geomfromtext('LINESTRING(3 4,10 50,20 25)');
*** Error 37000: [Virtuoso Driver][Virtuoso Server]GEO..
In playing with a trial copy of Virtuoso 6.2 (Commercial Edition), I've noticed
that it appears that its geospatial capabilities only cover points. For
example:
SQL> select st_geomfromtext('LINESTRING(3 4,10 50,20 25)');
*** Error 37000: [Virtuoso Driver][Virtuoso Server]GEO..: Bad geometry
