Exception: ParseException: Unknown WKB type [#1924206]

Comment	File	Size	Author
#11	geofield-wkb-exception-1924206-11.patch	890 bytes	Jan van Diepen

Comment #1

deggertsen commented 6 November 2013 at 23:45

I've run into the same issue. Did you ever find a solution?

Log in or register to post comments

Comment #2

deggertsen commented 7 November 2013 at 06:00

For me this had something to do with a few incomplete Canadian addresses that were put into Address fields. Geofield threw this error instead of ignoring those addresses. It would be nice if there was a way to make Geofield simply ignore a bad address.

Log in or register to post comments

Comment #3

socialnicheguru commented 30 December 2013 at 20:21

I agree with you, @deggersten

Log in or register to post comments

Comment #4

socialnicheguru commented 3 January 2014 at 14:54

Quick fix:

 //sng
 try {
          $geom = $reader->readHEX($raw_geom[1]);
          $items[$id][$delta]['geom'] = $writer->write($geom);
 } catch (Exception $e) {
    echo 'Caught exception: ',  $e->getMessage(), "\n";
 }

//          $geom = $reader->readHEX($raw_geom[1]);
//          $items[$id][$delta]['geom'] = $writer->write($geom);
        }

Don't know what happens if $items[$id][$delta]['geom'] is not defined or NULL.

Log in or register to post comments

Comment #5

mtoscano commented 17 January 2014 at 10:11

I have had this issue twice (Exception: ParseException: Unknown WKB type 49 in GEOSWKBReader->readHEX() (line 319...) and disabling GEOS solved the issue.
The error occur on node save and if I change the display format; if I disable GEOS and then unable it again I have no errors on node view.
I am using
PHP 5.5.7
PostgreSQL 9.1.11
PostGIS 1.5
GEOS 3.3.8

Geofield uses PostGIS as spatial backend.

Log in or register to post comments

Comment #6

mtoscano commented 17 January 2014 at 11:00

BTW, in my case nothing to do with addresses at all, just two simple lines on an Openlayers map.
I wasn't able to apply the "quick fix" above.

Log in or register to post comments

Comment #7

mtoscano commented 17 January 2014 at 11:11

If I switch the backend to Default Storage Backend I have no errors with GEOS enabled, so the problem seems to be related to WKT/WKB conversion with GEOS enabled and PostGIS backend.
This happened also on another machine with PostGIS 2.0.3

Log in or register to post comments

Comment #8

mtoscano commented 17 January 2014 at 12:16

Additional information: during Feeds import nodes are created correctly with PostGIS backend and GEOS enabled, but the error occurs on first node view. Disabling/enabling GEOS and the following node view are fine.

Log in or register to post comments

Comment #9

mtoscano commented 27 January 2014 at 15:22

GEOS incompatibility with PostGIS backend it is a big issue, as if you go with PostGIS it is also for performance but if you loose GEOS support performance decline, someone willing to have a look at this?
Thanks

Log in or register to post comments

Comment #10

jjchinquist

Vienna, Austria

commented 2 February 2014 at 21:44

In regards to comment #8, that sounds like a caching error if you are disabling and enabling something. Mato, can you try a view + cache clear + view again?