Hi Kingsley, I'm not really disagreeing with the decision to use this as one of the differentiators between the FOSS and closed source versions. I just wish that the list of features separating the two were a bit more clear, as I didn't see this specified on the Virtuoso OSS site. I'm sure thats just an oversight, though, since the spatial features are so new.
What I'm more interested in is actually getting the feature to work... the documentation is a bit premature imo. I was able to create the tables from the example at (9.34.8): http://docs.openlinksw.com/virtuoso/sqlrefgeospatial.html Inserting data into the geo table doesn't seem to result in any data insertions in the geo_inx table, and I don't see how the two are linked from an indexing standpoint. Also, I don't see how to expose a tranditional table with geospatial information as a geo-enabled RDF view. Are these things possible with the existing version of Virtuoso? Thanks, Jess On Wed, Feb 24, 2010 at 5:01 PM, Kingsley Idehen <[email protected]>wrote: > Nathan wrote: > >> Jesse Sightler wrote: >> >> >>> I'm attempting to enable geospatial support for a db that will support >>> both >>> SQL and RDF views. All the spatial apis appear to be missing, though: >>> SQL> select st_point (0, 52); >>> >>> *** Error 42001: [OpenLink][Virtuoso ODBC Driver][Virtuoso Server]SR185: >>> Undefined procedure db.DBA.st_point. >>> at line 16 of Top-Level: >>> select st_point (0, 52) >>> SQL> >>> >>> Is there some installation step that I'm missing in order to enable >>> support >>> for this? >>> >>> Thanks, >>> Jess >>> >>> >> >> AFAIK geospatial is only in the commercial edition. Which is a shame :( >> >> >> > Nathan, > > Shame? > > We do have to make a trade-off at some point between Open Source and Closed > Source. > > I know you don't imply our product is worth $0.00, but I would like to > discuss the matter for sure. > > Our point of view: > our product is provides huge value, and the work is extremely complex. How > do we sustain this behemoth of a project without some kind of monetary > compensation? > > Remember, not only is there an Open Source Edition of Virtuoso, it is also > used across the Linked Data from DBpedia, to DBpedia-Live, to a majority of > the bubbles in the Linked Data cloud. In all cases, OpenLink is doing the > heavy lifting (and incurring serious $ costs). > > > I am sure you agree, Virtuoso is very aggressively priced, as per our > pricing page [1] :-) > > Anyway, lets discuss as I am very open to thoughts from the community re. > this important matter. > > > Links: > > 1. http://www.openlinksw.com/virtuoso/sales/vpricing2.htm > > Kingsley > > > > > regards! >> >> nathan >> >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Virtuoso-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/virtuoso-users >> >> >> > > > -- > > Regards, > > Kingsley Idehen President & CEO OpenLink Software Web: > http://www.openlinksw.com > Weblog: > http://www.openlinksw.com/blog/~kidehen<http://www.openlinksw.com/blog/%7Ekidehen> > Twitter/Identi.ca: kidehen > > > > >
