views_handler_filter_geo does not support float targets, because it is inherited from views_handler_filter_numeric which treats targets as integers, and thus uses '%d' to generate SQL. This results in filters like "latitude >= 59.3 AND latitude <= 59.7" not working, because both values are truncated to 59.

Attached is a patch that changes parent class to views_handler_filter_float instead, this works fine.

CommentFileSizeAuthor
geo-filter-float.patch1.38 KBahtih

Comments

tmcw’s picture

tmcw commented
Status: Needs review » Reviewed & tested by the community

Works in my testing, albeit brief.

ahtih’s picture

ahtih commented

The Geo project had its last commit 17 weeks ago, and there are a number of patches waiting (such as this one) with AFAIK no attention from maintainers. I am fairly new to Drupal and do not really know what to do in this situation.

I could well contribute some more, as I am using Geo in a significant project myself. Since the project is pro-bono it would not be appropriate for me to pay maintainers for professional support either. I am not ready yet to propose myself as a maintainer though.

strk’s picture

strk commented

@ahtih : I feel your same frustration.
What I can suggest is to fork the codebase (possibly into a distributed CSV like git) and call for maintenance help on the mailing list
http://lists.osgeo.org/mailman/listinfo/drupal-geo

I'm sure you won't be alone.