> On Mar 6, 2023, at 3:37 PM, Bertil Chapuis wrote:
>
> Thank you for your answers and for the pointers.
>
>> PS Regarding which specification we choose to implement. The four principles
>> you outline sound good to me. It’s always better to follow the standard. If
>> leading implementation
Thank you for your answers and for the pointers.
> PS Regarding which specification we choose to implement. The four principles
> you outline sound good to me. It’s always better to follow the standard. If
> leading implementations (e.g. PostGIS and H2GIS) diverge from the standard,
> we can ma
PS Regarding which specification we choose to implement. The four principles
you outline sound good to me. It’s always better to follow the standard. If
leading implementations (e.g. PostGIS and H2GIS) diverge from the standard, we
can make a note, and possibly support them as secondary implemen
Similar issues have come up with non-GIS functions. For example, the DATEDIFF
function [1]. Snowflake and MSSQL have ‘DATEDIFF(timeUnit, datetime,
datetime2)’, whereas MySQL has ‘DATEDIFF(date, date2)’. We document which
specification we implement, and potentially we could implement both
specif
Hello Everyone,
I continue to make progress on the implementation of the Spatial Type (ST_)
extension for calcite [1] and wanted to exchange about the current design.
When implementing spatial functions, we usually refer to the OpenGIS Simple
Features Implementation Specification for SQL [2] or
