You can clone with
HTTPS or Subversion.
Following vector reduction work of #1136 this ticket is to provide pixel resolution tokens to users willing to do custom simplifications based on that. px_gw and px_gh were proposed by Dane in that ticket. That'd be fine with me.
I'm not convinced those are the best names - would be good to consider some alternatives.
I see there are two version of the postgis_datasource::populate_tokens method. One takes no token values, the other takes each of the token values. Why the duplication ?
one is used when the replacement tokens are not known (but the subquery still needs to be executed to be able to grab metadata).
Provide !pixel_width! and !pixel_height! tokens (#1181)
closing, this was handled by #1192
There seems to be a bug in the implementation of this. Too bad it lacked an automated testcase.
The width of a pixel in geographical units seem to be augmenting rather than diminishing as the output size augments!