thank you Adam, Im afraid that it does not change anything by leaving out the fromstr and wkt. It is a really weird problem reversing the lat and lng like that...
cheers, On Feb 16, 2:58 pm, Adam Fast <adamf...@gmail.com> wrote: > GPolygon is "designed" to take the geometry natively - no fromstr() or > .wkt necessary. > > Try GPolygon(polycoords_from_database.geometry) > > Adam > > 2009/2/16 Adonis <achrysoch...@hotmail.com>: > > > > > Hello, > > > -being facing a non-givin-back-errors problem... > > > view.py > > > poly = GPolygon(fromstr > > (polycoords_from_database.geometry.wkt),"#f33f00",3,1,"#008000",1) > > > blah.html > > > map.addOverlay(new {%block poly%}{%endblock%}) > > > -the page source shows that the new GPolygon has a proper syntax BUT > > the new GLatLng arrays are given as if it was G-Lng-Lat ( the > > longtitude first and the latitude second ). I suppose this is critical > > because lat can only be between -90 and +90 etc. > > > Any suggestions? > > Thanks in advance. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---