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 geospatial library (such as GEOS [1]--which I believe is what PostGIS relies on for much of its underlying functionality).
As for market interest, I would think there could be a lot of applicability in the energy space (where geometries are used to capture information about natural resources, transmission lines and other infrastructure, utility service areas, etc). --Jamey 1: http://trac.osgeo.org/geos/ On 12/2/10 12:47 PM, "Patrick van Kleef" <[email protected]> wrote: >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..: Bad >> geometry syntax LINESTRING(3 4,10 50,20 25), only formats like >> point(12 23) are allowed. >> >> Am I correct in interpreting this to mean that there is currently no >> support for lines, polygons, etc? And if so, are there any plans to >> add such capabilities? >> > > >There is currently only support for geo POINT data in Virtuoso >Commercial Edition. > >We have already drawn up some plans to add other types like LINES, >POLYGON etc, but we have not yet had sufficient feedback or commercial >incentive to move it more to the front of our development queue. > >However given the right signals from the marketplace we can certainly >re-prioritize this effort. > > >Best regards, > >Patrick >
