I'm surprised nobody has brought this up before :-) It's always been a limitation of the polygon task.
Osmosis uses the Java 2D libraries to do the polygon calculations. Please read the "Definition of insideness" in the following link which explains why you're seeing this issue. http://download.oracle.com/javase/6/docs/api/java/awt/Shape.html We have no way of changing the functionality of the inbuilt java libraries we're stuck with this one. I wonder if we should even have points existing on both 0 and 180 longitudes in the database given that they're the same location. Perhaps a number of tools rely on it though. Can you modify your polygon to extend to 181°? I don't think I've ever tried it, but it should work in theory. On Tue, Jun 14, 2011 at 7:04 AM, WanMil <wmgc...@web.de> wrote: > Hi, > > today I tried to cut out the data of asia from a planet file using the > attached asia.poly file. > Osmosis is doing fine with the exception that the points at +180° longitude > are missing. > > I created a little test osm file (180.osm) with one node at +180° and it's > removed by the asia.poly polygon. > > This is a real problem because there are (a few) points which really lie on > the +180° longitude, e.g. http://www.openstreetmap.org/** > browse/node/1113705746<http://www.openstreetmap.org/browse/node/1113705746> > > Without this node there are problems to calculate the multipolygon of the > russian country. So there is a specific need for that. > > Can you change the osmosis behaviour so that +180° longitude is supported? > > WanMil > > _______________________________________________ > osmosis-dev mailing list > osmosis-dev@openstreetmap.org > http://lists.openstreetmap.org/listinfo/osmosis-dev > >
_______________________________________________ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
