[mkgmap-dev] [PATCH] Splitter area rounding seems wrong

Hi list I am debugging a coastline/sea generation issue and in the process of this, discovered what I believe to be a splitter bug. There is a method in RoundingUtils.java that rounds the boundaries of an area to multiples of Garmin units. The minimum and maximum longitude are both rounded down while the minimum and maximum latitude are both rounded up. The resulting rounded area is therefore shifted relative to the original area and does not necessarily bound all the data. This looks like a bug to me. The attached patch rounds the minimum longitude/latitude down and the maximum longitude/latitude up, making sure that the rounded area always fully contains the original area. - Bartosz