Joe Nelson

Nothing yet, but sounds like a good idea. Tell me more about how you would like to do spatial queries. What kind of interface would be convenient for you?

You can make a view which uses these functions and the view will be accessible to the client just like a table would be.

We could add some of the [geospatial operators](http://www.postgis.us/downloads/postgis21_cheatsheet.pdf) as valid filters in the URL, although there are a few problems. One is that many of the operators use an ampersand...

For now try making and calling a stored procedure to do what you need. http://postgrest.com/api/reading/#stored-procedures

One option to add a geojson column in the output is by using a computed column as described in https://postgrest.com/en/v0.4/api.html#computed-columns I think it would output just what you want, but...

@gorbypark want to give the computed column approach a try and let me know how it works for you?

@palmerj fair point, I'll re-open the issue. Maybe the best way to focus the issue is to post SQL for creating a table with columns of the desired postgis types,...

Ruslan is right in that creating a computed column for a table is really easy -- you just make a function. Then the table gets a new column that you...

I can see how it's annoying to replace a big json object entirely just to change one part of it. We can think of ways to allow such a patch,...

Both #488 and this issue are special cases of the general ability to manipulate JSONB in a patch request. If we're going to extend the behavior of PATCH it probably...