CGI: Serve only the feature's properties not the entire feature as GeoJSON.

The Web Application doesn't need the original full/non-simplified
geometry.  After all, OpenLayers has fetched the tiles already and the
(visible part of) the geometry is already cached in the target SRS with
sensible simplification factors.

So there is really no need to transfer megabytes of high-precison data
to the client to highlight the feature.  This changes means that CGI
responses will remain small hence can be buffered.

To further speed up things one could store geometry area/perimeter/length
as generated columns (along with the list of municipality and county
codes) and serve row directly from PostgreSQL (bypassing PostGIS).  Also
since buffering is now an option the rows don't need be served in the
same order as the request, so one could batch queries using ANY[] or IN.

0 files changed, 0 insertions, 0 deletions