You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, in order to get the actual wkb representation of an object, one has to do:
bytes.fromhex(geo.wkb)
It would be both more efficient and more intuitive if geo.wkb contained directly the Well-Known Binary representation of the geometry. The string representation of the wkb could still be obtained with :
geo.wkb.hex()
What do you think about this change ? Would you be opened to a pull request ?
The text was updated successfully, but these errors were encountered:
Thank you for this useful library.
Currently, in order to get the actual wkb representation of an object, one has to do:
It would be both more efficient and more intuitive if
geo.wkb
contained directly the Well-Known Binary representation of the geometry. The string representation of the wkb could still be obtained with :What do you think about this change ? Would you be opened to a pull request ?
The text was updated successfully, but these errors were encountered: