Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Migration guide: DUMP shouldn't be needed in OGC request #3830

Closed
mapserver-bot opened this Issue · 12 comments

4 participants

@mapserver-bot
Collaborator

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.

@mapserver-bot
Collaborator

Author: aboudreault
Date: 2011/04/12 - 14:43
Fixed and committed in 21a1edc (r11544). The mapfile keyword still exists. Reopen the ticket if we decide to remove the mapfile keyword also.

@mapserver-bot
Collaborator

Author: dmorissette
Date: 2011/09/29 - 14:03
Reopening: this change needs to be mentioned in the 6.0 migration guide and all relevant docs need to be updated (all docs that used to refer to DUMP keyword)

@mapserver-bot
Collaborator

Author: dmorissette
Date: 2011/09/29 - 14:04
Moving to docs component. Any taker?

@mapserver-bot
Collaborator

Author: havatv
Date: 2011/09/29 - 14:24
I can start.

@mapserver-bot
Collaborator

Author: havatv
Date: 2011/09/29 - 17:52
The 6.0 and trunk documentation has been updated in mapserver/docs@4fe6fcb (r12604).

I have added deprecation notes in the layer and mapscript documents. In the rest of the documents I have removed
DUMP true
from the examples. I guess that for the examples to make sense, some metadata has to be added. I have included some, but please check and file bugs where more is needed.

@mapserver-bot
Collaborator

Author: havatv
Date: 2011/09/29 - 18:22
Added some more enable_request metadata in mapserver/docs@655e3a0 (r12605).

@mapserver-bot
Collaborator

Author: havatv
Date: 2011/09/30 - 08:33
I forgot the migration guide. I don't think I can edit the migration guide, so perhaps Daniel can do that?

@mapserver-bot
Collaborator

Author: havatv
Date: 2011/11/08 - 23:14
Since I don't think I can edit the migration guide, I reassign this one to Daniel.

@dmorissette dmorissette was assigned
@tbonfort
Owner

@havatv would you be willing to update the migration guide if you had commit rights ?

@havatv
Collaborator

@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.

@havatv havatv referenced this issue from a commit
Håvard Tveite Revert "Documentation of the removal of the DUMP parameter in the mig…
…ration guide (#3830)"

This reverts commit c50d7b1.

I have to apply to 6.0 first, so undoing this one!
b484454
@havatv havatv referenced this issue from a commit
Håvard Tveite Updated migration guide - removal of DUMP (#3830) c32e9a8
@tbonfort tbonfort referenced this issue from a commit
Håvard Tveite Updated migration guide - removal of DUMP (#3830) 3ef03d9
@tbonfort tbonfort referenced this issue from a commit
Håvard Tveite Updated migration guide - removal of DUMP (#3830) 0d0a240
@tbonfort
Owner

pushed to 6-0 (3ef03d9) and master (0d0a240)

@tbonfort tbonfort closed this
@tbonfort tbonfort reopened this
@tbonfort
Owner

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.

@havatv havatv referenced this issue from a commit in mapserver/docs
Håvard Tveite Modified the layer dump parameter description (mapserver/mapserver#3830
… )
d600239
@havatv havatv referenced this issue from a commit in mapserver/docs
Håvard Tveite Modified the layer dump parameter description (mapserver/mapserver#3830
… )
9c12392
@tbonfort tbonfort closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.