# GeoSparql queries not working

**URL:** <https://community.stardog.com/t/geosparql-queries-not-working/129>\
**Category:** Support\
**Created:** [February 20, 2017, 9:34pm UTC](https://community.stardog.com/t/geosparql-queries-not-working/129 "2017-02-20T21:34:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![NielsHoffmann](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/nielshoffmann/32/41_2.png) [@NielsHoffmann](https://community.stardog.com/u/NielsHoffmann)\
**Post date:** [February 20, 2017, 9:34pm UTC](https://community.stardog.com/t/geosparql-queries-not-working/129/1 "2017-02-20T21:34:54Z")

</div>

I’m trying to do some GeoSparql queries. I enabled spatial functionality when creating the repo.  
If I do "stardog-admin metdata get " I get:  
| spatial.enabled | true  
| spatial.index.version | 1  
| spatial.precision | 11

But in the stardog.log the following appears:  
SELECT ?m ?p  
WHERE {  
?m a ex:Monument ;  
geo:hasGeometry ?mgeo .  
?p a ex:Park ;  
geo:hasGeometry ?pgeo .  
?mgeo geof:within ?pgeo .  
} limit 50 offset 0  
org.openrdf.query.QueryEvaluationException: com.complexible.stardog.plan.eval.ExecutionException: The database has geospatial functionality disabled, cannot perform spatial queries.

Any clue what the problem could be?  
I’m using Stardog Community 4.2.3 on windows 7 with jre1.8.0\_111

Cheers,  
Niels

---

<div class="post-metadata">

**Author:** ![kendall](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/kendall/32/9_2.png) [@kendall](https://community.stardog.com/u/kendall)\
**Post date:** [February 20, 2017, 10:06pm UTC](https://community.stardog.com/t/geosparql-queries-not-working/129/2 "2017-02-20T22:06:16Z")

</div>

Niels,

Geospatial, HA Cluster, JMX, and Virtual Graphs aren’t available in Community. You can try them in the Stardog Enterprise eval.

Cheers,  
Kendall

---

<div class="post-metadata">

**Author:** ![NielsHoffmann](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/nielshoffmann/32/41_2.png) [@NielsHoffmann](https://community.stardog.com/u/NielsHoffmann)\
**Post date:** [February 21, 2017, 6:58am UTC](https://community.stardog.com/t/geosparql-queries-not-working/129/3 "2017-02-21T06:58:30Z")

</div>

Hi,

I was suspecting something like that…

There’s nothing in the documentation about those differences though is there? Or did I overlook that section?

It would be good to have those limitations clearly documented.

Cheers, Niels

---

<div class="post-metadata">

**Author:** ![kendall](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/kendall/32/9_2.png) [@kendall](https://community.stardog.com/u/kendall)\
**Post date:** [February 21, 2017, 1:25pm UTC](https://community.stardog.com/t/geosparql-queries-not-working/129/4 "2017-02-21T13:25:10Z")

</div>

There isn’t enough in the documentation about this to be sure. We will fix this for the upcoming 5.0 release. Thanks for bringing it to our attention.

Cheers,  
Kendall

---

<div class="post-metadata">

**Author:** ![kendall](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/kendall/32/9_2.png) [@kendall](https://community.stardog.com/u/kendall)\
**Post date:** [February 21, 2017, 1:25pm UTC](https://community.stardog.com/t/geosparql-queries-not-working/129/5 "2017-02-21T13:25:17Z")

</div>