Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding run-time constants to common expression handling. #4208

Closed
mapserver-bot opened this issue Apr 4, 2012 · 4 comments
Closed

Adding run-time constants to common expression handling. #4208

mapserver-bot opened this issue Apr 4, 2012 · 4 comments

Comments

@mapserver-bot
Copy link

Reporter: sdlime
Date: 2012/02/22 - 16:54
Trac URL: http://trac.osgeo.org/mapserver/ticket/4208
Basically it would be nice to expose a few run-time constants to MapServer logical expressions. Things like computed extent, scale, image size, and cellsize. Syntax would be something like !name! following after the !bbox! hack in PostGIS. While I’m only interested in MapServer logical expressions it’s reasonable that certain drivers could support them as well within their DATA/FILTER statements.

I’m proposing !bbox! (as define in PostGIS code), !minx! (etc…), !scale!, !width!, !height!, and !cellsize!. One use for this would be triggering scaling on parameters passed to style GEOMTRANSFORMs (e.g a buffer).

Steve

@ghost ghost assigned sdlime Apr 5, 2012
@tbonfort
Copy link
Member

see #3827 for !bbox! substitutions. removing 6.2 milestone as I suspect it won't be ready in time

@sdlime
Copy link
Member

sdlime commented Jul 24, 2013

Might as well consider for 7.0/RFC 91. --Steve

@tbonfort
Copy link
Member

This won't happen for 7.0

@tbonfort tbonfort modified the milestones: 7.2 Release, 7.0 Release Feb 12, 2015
@mapserver-bot
Copy link
Author

This is an automated comment

This issue has been closed due to lack of activity. This doesn't mean the issue is invalid, it simply got no attention within the last year. Please reopen with missing/relevant information if still valid.

Typically, issues fall in this state for one of the following reasons:

  • Hard, impossible or not enough information to reproduce
  • Missing test case
  • Lack of a champion with interest and/or funding to address the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants