Opened 11 years ago
Last modified 9 years ago
#501 closed enhancement
Multipoint request handling to be scalable for non 3D CRSs — at Version 1
Reported by: | Piero Campalani | Owned by: | Piero Campalani |
---|---|---|---|
Priority: | minor | Milestone: | Future |
Component: | petascope | Version: | 8.5 |
Keywords: | multipoint crs | Cc: | Alireza |
Complexity: | Hard |
Description (last modified by )
Currently the handling of WC*S requests on Multipoint coverages is working for fixed 3D XYZ CRSs.
Despite this maybe covers the majority of cases for Multipoint datasets, Petascope should deploy PostGIS queries and format the GML output according to the native CRS of the Multipoint coverage, including time series of multipoint.
For instance, petascope.wcps.server.core.XmlQuery
:
result = WcpsConstants.MSG_SELECT + " value, St_X(coordinate) AS x, " + "St_Y(coordinate) AS y, St_Z(coordinate) AS z " + WcpsConstants.MSG_FROM + " ps9_coverage c, ps9_multipoint_domain_set AS d, ps9_multipoint_range_set AS r " + WcpsConstants.MSG_WHERE + " c.name='" + coverageName + "' AND c.id = d.coverage_id AND d.id = r.point_id " ; ... xmin = trimParams[0].split(":")[0]; ymin = trimParams[1].split(":")[0]; zmin = trimParams[2].split(":")[0]; ...
Note:
See TracTickets
for help on using tickets.