[Featureserver] curl usage issue

Christopher Schmidt crschmidt at metacarta.com
Fri Dec 5 07:42:55 EST 2008


On Thu, Dec 04, 2008 at 02:26:49PM -0800, Josh Livni wrote:
> >
> > AFAICT, that's pretty much as per spec.  I guess I'm missing something
> > obvious.  I get the enoforce_srid_the_geom constraint violation.
> 
> 
> 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.
> 
> 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).
> 
> - we found it nice to be able to point to a PostGIS view that has a
> > geometry
> 
> 
> 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.
> 
> 
> >
> > - we did not find how to specify rang of values
> > like .../?somefield=[a,b]; is it possible ?
> 
> 
> 
> you can do less than/greater than type queries with postgis backend (eg
> &queryable=fieldname&fieldname__gte=5&fieldname_lte=8)
> 
> The action types currently supported for the postgis are  {'lt': '<', 'gt':
> '>',  'ilike': 'ilike', 'like':'like', 'gte': '>=', 'lte': '<='}

But you'll need to either:
 * Configure fields as 'queryable' in the datasource or
 * Pass a 'queryable=somefield' flag with your query.  

Regards,
-- 
Christopher Schmidt
MetaCarta



More information about the Featureserver mailing list