[Featureserver] GeoJSON, setting CRS in FeatureServer/OpenLayers
Tom Weir
tom.weir at safe.com
Mon Dec 17 12:17:08 EST 2007
On 17-Dec-07, at 8:40 AM, Christopher Schmidt wrote:
> On Mon, Dec 17, 2007 at 05:35:34PM +0100, David E. Reksten wrote:
>> On 17/12/2007, Josh Livni <mailing_lists at umbrellaconsulting.com>
>> wrote:
>>> The changelog for 1.09 notes 'Insert bogus CRS into GeoJSON' -
>>> line 35
>>> of GeoJSON.py does that.
>>
>> Thanks for the hint, knowing this it was easy to patch GeoJSON.py to
>> hardcode the (only) CRS we're using here. It seems that the beta
>> builds of FME 2008 is a bit picky about CRS values, it will only
>> accept "EPSG", not "OGN" values.
>>
>> FYI: I had to change the keyword "features" to "members" in line 35
>> as
>> well, for FME to accept the GeoJSON string. Very cool to insert
>> features in your browser using OpenLayers, then read them back with
>> FME directly from the web service!
>
> Note that both of these mean that FME is a rev behind in GeoJSON spec
> following. members -> features was a change we made in r5, I
> believe.
I've forwarded this thread to the developer responsible for our
GeoJSON support. Hopefully we can get this fixed prior to FME 2008
releasing.
Tom Weir
Developer
Safe Software
y tom.weir at safe.com
( +1 (604) 501-9985 x270
8 http://www.safe.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/featureserver/attachments/20071217/f061cdc3/attachment.html
More information about the Featureserver
mailing list