Is there data that suggests the geographiclib calculation is taking
longer than some other code might?  There's a lot going on in postgis,
and without a benchmark showing it's an issue, it feels like it could be
premature optimization.

Reply via email to