Hi, nice addition!
I've two observations:

• It doesn't appear to work on buffers
• The area and length measurements in the infowindow (numbers) could be localized (you've already localized the text)

Hi, nice addition! I've two observations:

• It doesn't appear to work on buffers
  That is because buffers are points with a radius style, hence got no area. We did something similar in the style window but I remember the figures being a bit off and needs some rework.

• The area and length measurements in the infowindow (numbers) could be localized (you've already localized the text)
  That formatting is not in the measure control but in the attribute handling. (It would also be nice if zero rows were omitted, eg area for lines.)

That formatting is not in the measure control but in the attribute handling. (It would also be nice if zero rows were omitted, eg area for lines.)

I see, the numeral and unit is returned via the @length and @area functions..wherever they are defined (I had a quick look and it seemed entirely cryptic) ..for yes those functions would need to be modified to return a localized numeral. Point me in a direction and I can have a look.

Edit. Right, utils/formatareastring.js and formatlengthstring.js need to be localized ...via getattributes.js, selecteditem.js, featureinfo.js and the viewer I think

That formatting is not in the measure control but in the attribute handling. (It would also be nice if zero rows were omitted, eg area for lines.)

I see, the numeral and unit is returned via the @length and @area functions..wherever they are defined (I had a quick look and it seemed entirely cryptic) ..for yes those functions would need to be modified to return a localized numeral. Point me in a direction and I can have a look.

Edit. Right, utils/formatareastring.js and formatlengthstring.js need to be localized ...via getattributes.js, selecteditem.js, featureinfo.js and the viewer I think

src/geometry/getarea and /getlength seems to be used by the replacer