MapServer 4.6.0-beta3 released
Ken Lord
kenlord at GMAIL.COM
Tue May 31 14:57:20 PDT 2005
>
> Hi Daniel,
> I think my case was unusual because I absolutely had to use jpeg output
> (with interlace off), so that our flash interface could use the map image,
> and I had to have transparent set to on so that my map symbolizations would
> work.
> My map has polygon features that are symbolized using three styles, a
> solid fill style on the bottom, a style with an ellipse/vector symbol to
> create a 'hatch' effect, and a cartoline style on top to give a nice
> anti-aliased outline to the polygon. The background colour and hatch
> pattern/colour are different in each class within the layer to reflect
> dozens of combinations of primary, secondary, and tertiary surficial geology
> types within that layer's dataset.
> Previously without transparent set to on, you couldnt see through the
> 'blank' parts of the hatch styles to see the solid fill underneath.
> 'Transparent' may not be relevant or allowable for jpeg's, but before
> 4.6b3, the setting had to be within outputformat to turn transparent on
> for my symbolizations. Perhaps two unrelated systems were using the same
> parameter.
> Perhaps the documentation just needs a note that transparent is not
> allowable for jpeg's.
> It was definately working in 4.6beta2. I have beta2 and beta3 (and older
> versions) installed in separate folders on our webserver, each with all
> their associated dll's. To switch a website between the versions I just have
> to point a virtual folder in the website directory to the appropriate
> mapserver software folder.
> Thanks,
> Ken
>
>
> On 5/31/05, Daniel Morissette <dmorissette at dmsolutions.ca> wrote:
> >
> > Sending this reply to mapserver-dev instead of -users...
> >
> > Ken Lord wrote:
> > >
> > > If TRANSPARENT is within the outputformat, mapserver fails and returns
> >
> > > the following error message:
> > >
> > > "GD/JPEG OUTPUTFORMAT jpeg has TRANSPARENT set ON, but this is not
> > > supported. It has been disabled."
> > >
> >
> > Ah! That makes more sense now. Due to the nature of the format, JPEG
> > does not and cannot support transparency. This is not new to MapServer
> > 4.6, only the more explicit error message may be new.
> >
> >
> > >
> > > If this was the intended effect, then just the 4.6 documentation needs
> >
> > > to be updated for the syntax change.
> >
> > Since this is just an error message to prevent users from requesting an
> > impossible combination, I don't think there is much to document. I mean
> > I'm not convinced that it would make sense to document all the
> > impossible combinations of mapfile parameters.
> >
> >
> > > I brought this up because the
> > > change was not listed in the revision history in history.txt, and the
> > > mapserver log and our flash interface don't show this error message,
> > > leaving me to try it out in an HTML template when our flash site
> > failed.
> > >
> >
> > Unfortunately the HISTORY.TXT is only as accurate as what the developers
> > make of it. It is possible that some items are missing if some
> > developers fail to update it, and there is not much I can do about this.
> >
> > However I did find a note from Frank in the 4.4.0 HISTORY.TXT about this
> > new validation:
> >
> > - Force GD/JPEG outputFormatObjects to IMAGEMODE RGB and TRANSPARENT OFF
> >
> > if they are RGBA or ON. Makes user error such as in bug 1703 less
> > likely.
> >
> > Are you sure that this was working in 4.6beta2?
> >
> > Daniel
> > --
> > ------------------------------------------------------------
> > Daniel Morissette dmorissette at dmsolutions.ca
> > DM Solutions Group http://www.dmsolutions.ca/
> > ------------------------------------------------------------
> >
>
--
==============================
Ken Lord B.Sc <http://B.Sc>., A.Dipl.T.H.
7488 Magnolia Terrace
Burnaby BC, V5E 4L1
604-777-2171
kenlord at gmail.com
kenlord at email.com
klord at bgcengineering.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20050531/257499ab/attachment.htm>
More information about the MapServer-users
mailing list