|
|
Niels Charlier created an issue |
|
App-schema: support for multiple geometries with different CRS |
|
Issue Type: |
|
|---|---|
|
Assignee: |
|
|
Components: |
Application schema |
|
Created: |
14/Jul/21 10:50 AM |
|
Priority: |
|
|
Reporter: |
Medium|
Geotools in general and app-schema specifically has unpredictable and buggy behaviour when you use multiple geometries in features, particularly if they have different CRS. There are various assumptions in the code that a feature type only has one single CRS. App-schema will use the first CRS it finds in the source type and list this for any geometry. On reprojection, there will be an attempt to reproject all geometries, which will fail if they are not all in the same CRS. Expected behaviour is that the different CRS can be in a complex type, and that reprojection only reproject the default geometry. One remark: it is necessary that the default geometry in your complex type is also the first geometry in your source table column list. It is unlikely to avoid this curiosity because it would require far too many core changes to avoid it (the first geometry is assumed to be the default in a simple type). But at least if this is done, it should work. |
|
|
|
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100168-sha1:61fd6a1) |
|
|
|
