-
-
Notifications
You must be signed in to change notification settings - Fork 364
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
Migration guide: DUMP shouldn't be needed in OGC request #3830
Comments
|
Author: aboudreault |
|
Author: dmorissette |
|
Author: dmorissette |
|
Author: havatv |
|
Author: havatv I have added deprecation notes in the layer and mapscript documents. In the rest of the documents I have removed |
|
Author: havatv |
|
Author: havatv |
|
Author: havatv |
|
@havatv would you be willing to update the migration guide if you had commit rights ? |
|
@tbonfort, I have not yet had the time to get used to working with git. I still feel quite unsure when I sporadically work with git on the documentation, and I would not be comfortable with having the possibility to cause damage to the Mapserver code due to lack of git competence. I will need to allocate some time for familiarising myself with git before I can continue to contribute to Mapserver documentation the way I used to do when we were on svn/trac. |
|
DUMP is not just deprecated, it is completely unused. This should be made clear in the docs, and the layerObj->dump property should be removed from the code. |
Reporter: aboudreault
Date: 2011/04/12 - 14:03
Trac URL: http://trac.osgeo.org/mapserver/ticket/3830
The dump keyword was used to determine what layers was queryable or could be displayed in a few OGC requests. With the implementation of the RFC 67, we don't need it anymore.
The text was updated successfully, but these errors were encountered: