Ticket #2331 (closed defect: fixed)

Opened 1 year ago

Last modified 7 months ago

Mapserver 5 doesn't appear to recognise WEB object's minscale (or maxscale) property on the fly

Reported by: gwatmuff1 Assigned to: sdlime
Priority: highest Milestone: 5.0.1 release
Component: MapServer C Library Version: 5.0
Severity: blocker Keywords: web minscale maxscale
Cc:

Description (Last modified by dmorissette)

Mapserver 5 doesn't appear to recognise WEB object's minscale (or maxscale) property on the fly? Mapserver 4x did.

URLs:

..&map_web_minscale=250000&...

MS 5 now gives following error:

loadWeb(): Unknown identifier. Parsing error near (250000):(line 1) (expected)

But:

..&map_web=MINSCALE+250000&... or ..&map.web=MINSCALE+250000&...

OR

..&map_web=MINSCALEDENOM+250000&... or ..&map.web=MINSCALEDENOM+250000&...

MS 5 also gives this error:

loadWeb(): Unknown identifier. Parsing error near (MINSCALE):(line 1)

OR

loadWeb(): Unknown identifier. Parsing error near (MINSCALEDENOM):(line 1)

And:

..&map.web=IMAGEPATH+/path/+MINSCALE+250000&...

MS 5 also gives same error:

loadWeb(): Unknown identifier. Parsing error near (MINSCALE):(line 1)

Has the map scale control been shifted to another object - can't find this in the docs?

Change History

09/28/07 17:22:09 changed by dmorissette

  • owner changed from steve lime to sdlime.
  • milestone set to 5.0.1 release.

11/02/07 14:12:06 changed by dmorissette

  • description changed.

Steve, it seems that MINSCALE/MINSCALEDENOM and MAXSCALE/MAXSCALEDENOM are not enabled for URL_STRING mode in maplexer.l.

Should they be added to URL_STRING mode or were they kept disabled intentionally to prevent clients from requesting layers/maps at scales at which the service provider do not want to offer them for performance or other reasons?

01/01/08 15:24:49 changed by sdlime

  • status changed from new to closed.
  • resolution set to fixed.

I was pretty conservative in what to allow via URL. That said, I don't think there is much, if any, risk with allowing access to that parameter. I've re-enabled in the 5.0 branch and in the trunk. I need someone to rebuild maplexer.c and commit though since anything I do on Mac OS seems to cause problems.

Steve

01/25/08 09:06:23 changed by dmorissette

Doh! I meant to generate a new maplexer.c for you and then I forgot. As a result, 5.0.1 has been released without an updated maplexer.c and that caused the build to break for some users.

I have committed a new maplexer.c generated with flex 2.5.31/Linux to branch-5-0 in r7312. Once I get confirmation from the users who reported the problem that the new file solves the issue then we may have to release 5.0.2.

01/25/08 10:39:56 changed by dmorissette

Users have confirmed that using the new maplexer.c solves the issue.