Thanks for the help everyone. It ended up being duplicate Java environment variables in Windows causing conflict for Geoserver to serve out the data. I guess it was jumping the math around when calling upon Geoserver to feed the data? Who knows. I tried DBeaver, as suggested by a member. I was able to query a feature but couldn't figure out how to view it or export the coords in this utility. I then came across a release note for PostgreSQL's pgAdmin4 database management console. They came out with a new version in September that allows you to directly view geometric features through the PostGIS extension, displaying the queried feature in a map window (overlaid on OSM, too!). I jumped to a given jagged road or triangular building and they were fine! ![alt text][1] This is when we learned that Geoserver was likely the culprit. Looks like it was two conflicting Java path variables (not sure how that happened, but other people share the machine). Thanks for everyone's help! Cheers [1]: https://help.openstreetmap.org/upfiles/image_(1).png

Thanks for the help everyone. It ended up being duplicate Java environment variables in Windows causing conflict for Geoserver to serve out the data. I guess it was jumping the math around when calling upon Geoserver to feed the data? Who knows. I tried DBeaver and DBeaver, as suggested by a member. I was able to query a feature but couldn't figure out how to view it or export the coords. coords in this utility. I then came across a release note the for PostgreSQL's pgAdmin4 database management console console. They came out with a new version in September that allows you to directly view geometric features via through the PostGIS in a little extension, displaying the queried feature in a map window (overlaid on OSM, too!). I jumped to a given jagged road or triangular building and they were fine! ![alt text][1] This is when we learned that Geoserver was likely the culprit. Looks like it was two conflicting Java path variables (not sure how that happened, but other people share the machine). [1]: https://help.openstreetmap.org/upfiles/image_(1).png

Thanks for the help everyone. It ended up being duplicate Java environment variables in Windows causing conflict for Geoserver to serve out the data. I tried DBeaver and was able to query a feature but couldn't figure out how to view it or export the coords. I then came across a release note the PostgreSQL's pgAdmin4 database management console came out with a new version in September that allows you to directly view geometric features via PostGIS in a little map window (overlaid on OSM, too!). I jumped to a given jagged road or triangular building and they were fine! This is when we learned that Geoserver was likely the culprit. Looks like it was two conflicting Java path variables (not sure how that happened, but other people share the machine).