Hi all, On Mon, Jul 2, 2012 at 9:20 AM, WanMil <[email protected]> wrote: >> Hi >> >> Am 29.06.2012 22:01, schrieb WanMil: >>> >>> I started an investigation to find the problem. It is currently unknown >>> if the problem is located on osmupdate or on osmosis site or if that's a >>> different understanding of the PBF format. >> >> >> Maybe this could be clarified by verifying the obf's with osmium. If >> osmium and osmupdate produces the same results, it's probably osmosis >> that get's it wrong. >> >>> The current status is that a planet file updated with osmupdate can be >>> read by osmsosis without any error message but osmosis reads different >>> longitude values than osmconvert/osmupdate. >> >> It would be very helpful if you could supply a minimal testcase (ha hand >> full of nodes) that have the same problem. >> >> Peter >> > > Hi Peter, > > as pointed out in http://forum.openstreetmap.org/viewtopic.php?id=17194 the > problem was caused and fixed by osmconvert.
Great. I believe this is the same problem I was having with osmconvert. Is the 'one-click' build (wget -O - http://m.m.i24.cc/osmconvert.c | cc -x c - -lz -O3 -o osmconvert) also updated? -- martijn van exel http://oegeo.wordpress.com _______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
