changes for mapscript API updates in MapServer 8 #99
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kngai
pushed a commit
to kngai/geomet-climate
that referenced
this pull request
Dec 6, 2024
kngai
pushed a commit
to kngai/geomet-climate
that referenced
this pull request
Dec 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the address changes and depracations in MapServer 8.
LAYER.DUMPdirective from the mapfile template since it has been removed in MapServer 8. WMS GetFeatureInfo requests are identical following the removal.LAYER.METADATAandWEB.METADATAin favour of using the mapscript hashTableObject instead for accessing and setting metadata values.MAP.TRANSPARENTdirective since it has been removed in MapServer 8 and is now managed via the individualOUTPUTFORMATdeclarations.I have tested all changes via a local build of GeoMet-Climate.
CC @RousseauLambertLP