<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">AFAICT, that's pretty much as per spec. I guess I'm missing something<br>
obvious. I get the enoforce_srid_the_geom constraint violation.</blockquote><div><br>Ok - so it sounds like now you're uploading valid geojson to the latest FS, and you're getting a different traceback than your last post. I would guess, based on your email saying you don't know what epsg your table has, and the fact you say it does have an enforce constraint, that it's not epsg:4326 as your config says, and that this is causing your error.<br>
<br>Try find out what srid you have, and ensure your FS layer definition matches that (SELECT st_srid(the_geom) should return the srid for stuff already in there).<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
- we found it nice to be able to point to a PostGIS view that has a<br>
geometry</blockquote><div><br>Yes, it is nice. But you can't [easily] update data directly to a view - so its really only good for looking at existing data unless you build some triggers. <br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
- we did not find how to specify rang of values<br>
like .../?somefield=[a,b]; is it possible ?</blockquote><div><br><br>you can do less than/greater than type queries with postgis backend (eg &queryable=fieldname&fieldname__gte=5&fieldname_lte=8) <br><br>The action types currently supported for the postgis are {'lt': '<', 'gt': '>', 'ilike': 'ilike', 'like':'like', 'gte': '>=', 'lte': '<='}<br>
<br></div><div> -Josh<br><br></div></div><br>