You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've read the discussion over in #1524 and while I fully agree that more complex geocalculations should be left to a dedicated gem, it would still be interesting to see PostGis support in geocoded_by.
Here's my current workaround:
classFoo < ApplicationRecord# has columns :address (string), :latitude (decimal), :longitude (decimal) and :coordinates (st_point)geocoded_by:addressafter_validation:geocode_postgisprivatedefgeocode_postgisgeocode# fills latitude and longitudeself.coordinates="POINT(#{longitude}#{latitude})"# fills postgisendend
While this is not too hard to accomplish, it would be even better to be able to have PostGIS support in geocoder, similar to support (geocoded_by: :coordinates)
The text was updated successfully, but these errors were encountered:
Thanks for this. In theory, I'm open to adding PostGIS support. However, two requirements:
It gets enabled manually, through configuration, and doesn't affect anyone who doesn't have the extension installed.
It doesn't make the existing SQL code significantly more complicated.
Number two is important, since the SQL part of the gem is already harder to understand and maintain than I'd like it to be. But I am open to this. If you want to write up a PR, go for it.
Hi Alex!
I've read the discussion over in #1524 and while I fully agree that more complex geocalculations should be left to a dedicated gem, it would still be interesting to see PostGis support in
geocoded_by
.Here's my current workaround:
While this is not too hard to accomplish, it would be even better to be able to have PostGIS support in geocoder, similar to support (
geocoded_by: :coordinates
)The text was updated successfully, but these errors were encountered: