You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sis.apache.org by "Martin Desruisseaux (Jira)" <ji...@apache.org> on 2022/11/29 10:56:00 UTC
[jira] [Updated] (SIS-515) CRS management for SQL/PostGIS filter
[ https://issues.apache.org/jira/browse/SIS-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Desruisseaux updated SIS-515:
------------------------------------
Fix Version/s: 1.4
(was: 1.3)
> CRS management for SQL/PostGIS filter
> -------------------------------------
>
> Key: SIS-515
> URL: https://issues.apache.org/jira/browse/SIS-515
> Project: Spatial Information Systems
> Issue Type: Bug
> Components: Storage
> Affects Versions: 1.1, 1.2
> Reporter: Alexís Manin
> Assignee: Alexís Manin
> Priority: Major
> Fix For: 1.4
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> When using the `sis-sqlstore` datastore upon a PostGIS table with a geometry column,
> if a bbox filter is applied on a FeatureSet, its conversion to an SQL clause for it ignore any CRS information. In this case, the resulting clause is wrong, apart for the case where the CRS is already aligned.
>
> We must at least try to write geometry SRID when possible (so, use [EWKT format|[https://postgis.net/docs/ST_GeomFromEWKT.html]).]
>
> Otherwise, when we can determine a common CRS in advance (most likely the one of the implied geometry column for optimisation purpose), we could try to reproject before-hand the literal filter (if any).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)