Joe Hildreth schrieb: > Ric, > > I am really new at this, but I had a similar problem when I imported OSM > data into my postgres server. When using the osm2pgsql tool I omitted > the -m flag resulting in a shift of about 10-15 km in my projection. The > solution for me was to wipe the db and re-import the data using the -m > switch. Actually, the default behavior of osm2pgsql is to replace data > so you would not have to remove it before hand. (If I recall correctly) >
Okay I read a couple of ressources and they all mention that a missing -m switch is causing such a behaviour. Since it wouldn't harm to update my db with the latest osm data I will double check that I have the latest osm2pgsql and that I use -m switch, which I'm sure I used the last time to import the data. I've checked the spatial_ref_sys and all the proj4text entries look fine, so basically this is the only explanation. Thanks, Ric > Hope that helps. > > Regards, > > Joe > > > On Thu, 2009-02-26 at 14:07 +0100, Ric S wrote: > >> Hi Folks, >> >> this is a little bit offtopic, but I think someone here might know the >> solution. >> I'm trying to transform osm data from my postgis db to lat lon values. >> >> SELECT name, place, asText(transform(way,4326)) from planet_osm_point >> WHERE name = 'Ingolstadt' AND place = 'city' ORDER BY name; >> >> The result is: >> >> 11.4333 48.9570163662354 >> >> If I use the values for example with google maps the resulting point is >> off by about 20km. The expected result would be rather around 11.41 48.76. >> >> Any clue what's wrong? >> >> Thanks Ric >> >> >> >> >> >> >> _______________________________________________ >> Mapnik-users mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/mapnik-users >> > > _______________________________________________ Mapnik-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-users
