[Featureserver] GeoJSON, setting CRS in FeatureServer/OpenLayers

[Josh Livni]

I'd expect a patch to read an additional crs or (srid or whatever)
>>> parameter in the cfg file would be easy, but I'm not sure if that's the
>>> appropriate place to put that sort of info (What happens your datasource
>>> has multiple srids, but your query result only displays one?  No idea...)
>>>       
>> Why not store (and return) an individual CRS for each feature?
>>     
>
> Store where? Keep in mind that with the exception of the DBM and sqlite
> datasources, we don't have any way to add columns to store additional
> attributes: we simply represent the data as it is.  
>
> Regards,
>   

And PostGIS.  While many folks set a constraint on their geometry column 
so that only one SRID is allowed, there's certainly nothing stopping you 
from having each row be in a different projection -- I've even seen it 
done - on purpose!   This example is what led me to my first comment 
about being unsure.

But now I feel more sure that the most reasonable place this info should 
be stored, to deal with the most use cases, is definitely with the 
featureserver layer configuration. 

Of course, I have no use-case where I need this attribute, and perhaps 
those who actually do need it might have a more informed opinion on the 
matter than me....

  -Josh