Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Exception: ParseException: Unknown WKB type 79 in GEOSWKBReader->readHEX() (line 318 of geofield/geofield.module)
this is on my startup screen and I cannot do anything else.
Comment | File | Size | Author |
---|---|---|---|
#11 | geofield-wkb-exception-1924206-11.patch | 890 bytes | Jan van Diepen |
Comments
Comment #1
deggertsen CreditAttribution: deggertsen commentedI've run into the same issue. Did you ever find a solution?
Comment #2
deggertsen CreditAttribution: deggertsen commentedFor 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.
Comment #3
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedI agree with you, @deggersten
Comment #4
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedQuick fix:
Don't know what happens if $items[$id][$delta]['geom'] is not defined or NULL.
Comment #5
mtoscano CreditAttribution: mtoscano commentedI 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.
Comment #6
mtoscano CreditAttribution: mtoscano commentedBTW, 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.
Comment #7
mtoscano CreditAttribution: mtoscano commentedIf 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
Comment #8
mtoscano CreditAttribution: mtoscano commentedAdditional 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.
Comment #9
mtoscano CreditAttribution: mtoscano commentedGEOS 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
Comment #10
jjchinquist CreditAttribution: jjchinquist commentedIn 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?
Comment #11
Jan van Diepen CreditAttribution: Jan van Diepen commentedI have the same issue.
I am not using PostGIS however.
The quick fix works for me and I am creating an install profile.
That means I need the patch to be available as a patch file.
So here's that patch file.
Comment #12
dobe CreditAttribution: dobe commented#11 patch worked for me.
Comment #13
hvalentim CreditAttribution: hvalentim commented+ 1 for working patch 11.
Using PostGIS 2.1
Comment #14
guillaumev CreditAttribution: guillaumev commentedSame issue here, with geofield_postgis, and patch 11 fixed it. RTBC ?
Comment #16
Brandonian CreditAttribution: Brandonian commentedThanks for the patch, @Jan van Diepen! Committed to 7.x-2.x
http://drupalcode.org/project/geofield.git/commit/18076ae
Comment #17
Brandonian CreditAttribution: Brandonian commentedMarking as fixed.