Skip to main content
10 events
when toggle format what by license comment
Jul 18, 2019 at 17:51 comment added Interested_Programmer @ThingumaBob I am not in charge of the data and I am just uploading the data given. Thanks for your response though. I will pass it on.
Jul 18, 2019 at 17:49 vote accept Interested_Programmer
Jul 18, 2019 at 17:41 comment added geozelot @JGH aha! nice find, so you are absolutely right, it's the whitespaces rather than casting limtations. never thought someone would find this signature to be worth adding ,)
Jul 18, 2019 at 17:00 comment added JGH @ThingumaBob running \df++ st_asText show an (undocumented) version that gets a text input, cast it to geometry and call the common `st_asText(geometry)`` function. This cast should be valid on txt/bytea
Jul 18, 2019 at 16:55 answer added JGH timeline score: 2
Jul 18, 2019 at 16:15 comment added geozelot is the GPS column storing PostGIS' GEOMETRY bytea representation as TEXT?? That column really should be the appropriate GEOMETRY type. I guess the actual string literal of bytea can be cast implicitly when passed to ST_AsText, but not when passed as column reference...
Jul 18, 2019 at 16:10 comment added Inactivated Account Also I see you've tagged pgadmin4 - try using DBeaver - the new geometry viewer is super useful, as well as dbeaver generally being a much better interface for an analyst vs. a database administrator...
Jul 18, 2019 at 16:10 comment added Inactivated Account If you're trying to convert existing postgis geometry into lat and lon, could you try using the ST_X(GEOM), and ST_Y(geom) functions to see if those work instead? And, is the geometry valid on the point that is throwing the error?
Jul 18, 2019 at 16:05 review First posts
Jul 18, 2019 at 16:08
Jul 18, 2019 at 16:03 history asked Interested_Programmer CC BY-SA 4.0