id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
12010	Add `ewkb` and `hexewkb` properties and document the GEOS IO Classes	James	jbronn	"The documentation states that the hex member returns the HEXEWKB of a geometry.  This isn't true, it is only returning the hex value without the SRID embeded into it as the HEXEWKB should.  
Example of issue:
{{{
(FROM PYTHON)
> p = django.contrib.gis.geos.GEOSGeometry('POINT(2 3)',4326)
> p.ewkt
 'SRID=4326;POINT (2.0000000000000000 3.0000000000000000)'
> p.hex
 '010100000000000000000000400000000000000840'
 
 (FROM PostGres with PostGIS)
 postgres=# SELECT GeometryFromText('POINT(2 3)', 0);
                   geometryfromtext
 ----------------------------------------------------
  01010000200000000000000000000000400000000000000840
 (1 row)
 
 postgres=# SELECT GeometryFromText('POINT(2 3)', 4326);
                   geometryfromtext
 ----------------------------------------------------
  0101000020E610000000000000000000400000000000000840
 (1 row)
}}}
The output above verifys that the SRID information isn't being returned as part of the hex result of the geometry.  Either the documentation is incorrect and a method should be provided that does return the HEXEWKB or there is a bug where the srid isn't being considered when calculating the HEXEWKB value.

The documentation I am looking at:
http://geodjango.org/docs/geos.html#hex "		closed	GIS	1.1		fixed			Accepted	0	1	0	0	0	0