[patch] bbox/bounds memory optimizations

[shinigami]

Hi,

bbox/bounds allowed access to coordinates through creation LatLon objects only, which led to creation of looots of useless instances. Example:

return lat() < b.getMin().lat()

lat() > b.getMax().lat()

lon() < b.getMin().lon()

lon() > b.getMax().lon();

creates 4 objects just to find if point is outside of box.

So I made shortcuts getMinLat() for getMin().lat() etc...
Added few methods consuming (double lat, double lon) instead of (LatLon) to avoid m(new LatLon(lat,lon)) usages.
Changed some implementations. (counting center of rectangle really need not create two objects;)

[Don-vip]

Thanks, there is room for improvements with these classes :)

Can you please first finish javadoc for all new public methods (methods without javadoc + empty javadoc statements such as "@return") ? Thanks.

[shinigami]

javadoc added

[Don-vip]

In 6203/josm:

fix #9024 - bbox/bounds memory optimizations (modified patch by shinigami) + javadoc

[Don-vip]

There's something very, very wrong in r6203 that broke rendering of many ways. I set back generated latest jar release of today to r6201 to fix this (I have no idea right now what happened).

[Don-vip]

In 6204/josm:

fix #9024 - fix problems introduced in r6203

[shinigami]

Ee, ugly NaNs, sorry:(

I made few more changes there. First I tried to speed up QuadTiling.tile2LatLon(long quad), but it seems to we do not need it at all.
Look at it, if I understand it well the same can be easily computed from QBLevel parent's bbox and quadrant index.
I removed quad from QBLevel too, it is used nowhere now.