Django GIS Measure refactor

[Riccardo Di Virgilio]

hi, the class MeasureBase in django.contrib.gis.measure is not subclassable.

i've write a new code, that allows the very same API, but it can be subclassed with no pain

the new code is one hundred line shorter, and is DRY.

in the old code the class Area and the class Distance write the same methods every time.

i've pushed a lot of base methods (like repr, init, sub, add, ...) in the base class, and i've defined just molt for the new Distance class and div for the new Area class.

Please consider to include this code in the django 1.4 version.

I've tested it and it works like the old version, but now you can create a new class for Weight with no method definition, just unit definition.

if you want i can write standard measure for every measure and we can put it inside localflavor...

[Riccardo Di Virgilio]

changed a bug with idiv

[xavierpencilline]

pretty cool stuff!

[Luke Plant]

At a first glance, this seems like a sensible improvement.

It won't get in to Django 1.4 now - we will be prioritising bug fixes at this stage.

Also, we need a patch in unified diff format to be able to review more easily.

Thanks!

[Riccardo Di Virgilio]

ok in that case i'll have the time to improve it.

what i'm doing is to create Measure, Area and Volume class and add mol and div method to switch from one class to another.

i'll also add a Weight class, so maybe it would be better to put this measure class in another package (like localflavor) and then just import it from gis.

[Riccardo Di Virgilio]

please wait that i'll post a new version. there are some algebric issue with this class.

with this class you can't divide Measure with Measure, but in math this is wrong...

3m * 3m = (3*3) * (m *m) = 9sq_m

3m / 3m = (3/3) * (m/m) = 1

i'll attach a new version that support div with other instance of the same class

[Riccardo Di Virgilio]

i've attached a new measure.py, with tests at the end.

just lunch python measure.2.py to test it

there is also the new diff file in unified format.

i've created also a Weight class to see how much it's easy to create a new measure class,

maybe it would be useful for developers to include a weight class somewhere in django

[Riccardo Di Virgilio]

Improvements are:

1: class names are printed in exceptions

2: div and mul with distance retruns correct instances of other classes (example 3m * 3m = 9sq_m

3: div with two instances of same class returns a number (example: 3m / 3m = 1)

feel free to choose the correct prefix for volume API, just change the string in the code.

todo: remove tests at the end.

[Riccardo Di Virgilio]

Measure py with TEST

[Riccardo Di Virgilio]

Measure diff unified format

[Riccardo Di Virgilio]

Measure py with TEST

[Riccardo Di Virgilio]

sorry i've done a mess with attachments...

[Riccardo Di Virgilio]

maybe it would be useful to use number_format when calling string, to easy use the class in django templates and i18n format number

def str(self):

return '%s %s' % (number_format(getattr(self, self._default_unit)), self._default_unit)

[Riccardo Di Virgilio]

full .py file

[Claude Paroz <claude@…>]

In [4d46106f8c233c5af283c903000ef8c6f1165393]:

Fixed #17754 -- Refactored gis.measure

This refactoring does allow much easier MeasureBase subclassing.
Many thanks to Ricardo di Virgilio for the initial patch.

[Claude Paroz]

Riccardo, thanks for this improvement. I've reworked your patch and committed only the refactoring part. The Weight and Volume classes are a nice proof of concept about how easy it is to subclass MeasureBase, but I did not include them because I don't see a real need for them in Django core.

Feel free to request further improvements in separate tickets.

[Riccardo Di Virgilio]

Hi, i'm migrating my code to django 1.5

there is a problem with the measure class, every time you mix decimal and float it raises a type error

so i've made a small diff to convert every numeric type to float automatically.

check the diff

[Claude Paroz]

Riccardo, I'd suggest opening a different ticket. Could you also provide tests for the issue (see django/contrib/gis/tests/test_measure.py)?