Ignore the information about scaled integers, it is not relevant to your use case. If you have imported with osm2pgsql then observe the following: * planet_osm_nodes `planet_osm_nodes` is almost certainly not what you are interested in as it has raw coordinates for nodes but no *other* information (is this node a tree? a shop? a city? etc) * Instead, use the tables `planet_osm_point`, `planet_osm_polygon`, and `planet_osm_line`, where the coordinates are stored in the "way" column. Read up on PostGIS functions. You can use st_astext to display the "way" column in a human readable format. * Your database is in "spherical Mercator" coordinates, not lat/lon degrees. Hence the confusion. Use the PostGIS function `st_transform(way,4326)` to convert these coordinates to lat/lon degrees, or alternatively use the `-l` command line option when importing with osm2pgsql.

Ignore the information about scaled integers, it is not relevant to your use case. If you have imported with osm2pgsql then observe the following: 1. * planet_osm_nodes is almost certainly not what you are interested in as it has raw coordinates for nodes but no *other* information (is this node a tree? a shop? a city? etc) 2. * Instead, use the tables `planet_osm_point`, `planet_osm_polygon`, and `planet_osm_line`, where the coordinates are stored in the "way" column. Read up on PostGIS functions. You can use st_astext to display the "way" column in a human readable format. 3. * Your database is in "spherical Mercator" coordinates, not lat/lon degrees. Hence the confusion. Use the PostGIS function `st_transform(way,4326)` to convert these coordinates to lat/lon degrees, or alternatively use the `-l` command line option when importing with osm2pgsql.

Ignore the information about scaled integers, it is not relevant to your use case. If you have imported with osm2pgsql then observe the following: 1. planet_osm_nodes is almost certainly not what you are interested in as it has raw coordinates for nodes but no *other* information (is this node a tree? a shop? a city? etc) 2. Instead, use the tables `planet_osm_point`, `planet_osm_polygon`, and `planet_osm_line`, where the coordinates are stored in the "way" column. Read up on PostGIS functions. You can use st_astext to display the "way" column in a human readable format. 3. Your database is in "spherical Mercator" coordinates, not lat/lon degrees. Hence the confusion. Use the PostGIS function `st_transform(way,4326)` to convert these coordinates to lat/lon degrees, or alternatively use the `-l` command line option when importing with osm2pgsql.

Ignore the information about scaled integers, it is not relevant to your use case. If you have imported with osm2pgsql then observe the following: 1. planet_osm_nodes is almost certainly not what you are interested in as it has raw coordinates for nodes but no *other* information (is this node a tree? a shop? a city? etc) 2. Instead, use the tables `planet_osm_point`, `planet_osm_polygon`, and `planet_osm_line`, where the coordinates are stored in the "way" column. Read up on PostGIS functions. You can use st_astext to display the "way" column in a human readable format. 3. Your database is in "spherical Mercator" coordinates, not lat/lon degrees. Hence the confusion. Use the PostGIS function `st_transform(way,4326)` to convert these coordinates to lat/lon degrees, or alternatively use the `-l` command line option when importing with osm2pgsql.