[Georuby-devel] post_gis_adapter's to_yaml function

Guilhem Vellut guilhem.vellut at gmail.com
Wed May 31 01:12:00 EDT 2006

Hello Doug,


I don't have all the elements to solve your problem. When you write "looking
through the yaml code it looks like there's an optional options hash", what
yaml code are you referring to? And how are you trying to use the method?


If you use it in fixtures, the to_yaml method for geometries is used the
following way:


  id: 1


  value: 3

geom: <%= Geometry.from_ewkt('POINT(1.4 5.67)').to_yaml %>

And it outputs the canonical representation of the geometry for the target
database (HexEWKB for PostGIS).






From: georuby-devel-bounces at rubyforge.org
[mailto:georuby-devel-bounces at rubyforge.org] On Behalf Of Doug Cole
Sent: 31 May 2006 03:26
To: georuby-devel at rubyforge.org
Subject: [Georuby-devel] post_gis_adapter's to_yaml function


  I just tried to use the to_yaml function in the post_gis_adapter and ran
across some problems:

-first I got an error related to the number of arguments (1 for 0), looking
through the yaml code it looks like there's an optional options hash so I
simply redefined the function as  "to_yaml( opts = {} )"  

-after fixing that I recieved the error "wrong argument type String
(expected Data) (TypeError)" which I haven't tackled.

anyone else run into these problems?  I was trying to dump some point data
from my postgres database to a fixture for testing.  Simply removing the
to_yaml definition fixed things, so that's how I've left it, but I thought
I'd report the problem. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/georuby-devel/attachments/20060531/8eb3e773/attachment.htm 

More information about the Georuby-devel mailing list