[GIS] Projecting OpenStreetMap data in PostGIS

openstreetmappostgispostgresql

I've loaded an extract of Openstreetmap data into a Postgresql database with PostGIS 1.5 using the following command withosm2pgsql.exe:

C:\Program Files (x86)\HOTOSM\bin>osm2pgsql.exe -c -s -H localhost -d osm_cloudmade -b -122.0,18.03,-64.85,46.05 -E EPSG:900913 -U postgres -P 5432 J:\DATA\OSM\usa.osm.bz2 -S J:\DATA\OSM\default.style

I understand that the Openstreetmap data is in Lat/Long WGS 84. If I inspect my table planet_osm_roads I see way geometry but no SRID.

Is there a way that I can project this to another system? Or do I first need to specify what the SRID is of this data?

Best Answer

Have you looked in the table "geometry_columns"? There should be an entry detailing the SRID for the "geometry" column in the planet_osm_roads table.

There is some background info here but that was an old thread and you haven't said you had any error messages, so assume that EPSG 900913 is present in your version of PostGIS and osmpgsql.

Assuming the co-ordinates in your geometry and your SRID are specified correctly, it is just a case of running ST_Transform on your geometry column (having created a new geometry column with the correct SRID first of course).

Related Solutions

[GIS] Accessing PostGIS raster data using Query Layer in ArcGIS Desktop

To do this, you'll want to create a separate table containing the vectorized raster or a view. If your raster table is big (lots of rows), you're better using a separate table instead of a view do to the computation occurring every time the view is accessed. The SQL for creating the view could be...

CREATE VIEW myview AS
SELECT
    rid,
    (ST_DumpAsPolygons(rast)).*
FROM ras_test1

You should be able to view that in ArcGIS. It might complain about lacking an primary key, which you could always add if needed.

[GIS] slow import via osm2pgsql to postgresql database

From the manual:

osm2pgsql relies much on its node cache during import. If the nodes do not fit into the cache it needs to do database lookups which slow down the process. Use enough cache so all nodes are cached. -C 12000 seems to do the job, even if that means you have to configure more swap space.

Try to use -C 'somethingbig'

See the wiki

If you want to try and build this executable yourself, just clone the github code and check the README file, it states somewhere:

On most Unix-like systems the program can be compiled by
running './autogen.sh && ./configure && make'.

So if you have all the libs/reqs fulfilled you'll be building an executable that works.

Best Answer

Related Solutions

[GIS] Accessing PostGIS raster data using Query Layer in ArcGIS Desktop

[GIS] slow import via osm2pgsql to postgresql database

Related Question