Consider the term 'geospatial' instead of 'spatial'
Description
Activity
Show:

Sanne Grinovero November 11, 2014 at 11:03 PM

Hardy Ferentschik November 11, 2014 at 12:38 PM
Clearly true neutral
thanks for the clarification.
I on the other hand, after using the spatial API a bit more and reviewing the documentation, feel my proposal is actually making things easier. However, instead of againstField
I prefer usingField
now.

Nicolas Helleringer November 10, 2014 at 1:45 PM
Clearly true neutral

Hardy Ferentschik November 10, 2014 at 1:43 PM
the goal was to lower the entry cost for new commer on the spatial feature : I do not see Hardy Ferentschik commit changing that.
, so does this mean you are pro or con this change or just neutral?

Nicolas Helleringer November 7, 2014 at 9:16 AM
the goal was to lower the entry cost for new commer on the spatial feature : I do not see commit changing that.
Fixed
Details
Details
Assignee

Reporter
Components
Fix versions
Priority
Created December 19, 2013 at 3:18 PM
Updated November 13, 2014 at 6:56 PM
Resolved November 11, 2014 at 11:03 PM
We use @Spatial and qBuilder.spatial()
should we move to Geospatial to make things clearer?
WDYT Nicolas?