Skip to content
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

Adding a rule-based layer in the qgis-server tutorial project #52

Open
pblottiere opened this issue Dec 15, 2021 · 2 comments
Open

Adding a rule-based layer in the qgis-server tutorial project #52

pblottiere opened this issue Dec 15, 2021 · 2 comments

Comments

@pblottiere
Copy link
Member

I'm using the QGIS-Training-Data repository to add some examples in the QGIS Server documentation and I think it'd be nice to have a rule-based layer in order to test the GetegendGraphics request with the RULE parameter.

I can take care of it if you tell me "what" kind of layer/data you'd be ready to add in the project.

@DelazJ
Copy link
Collaborator

DelazJ commented Dec 16, 2021

I can take care of it if you tell me "what" kind of layer/data you'd be ready to add in the project.

Response a la normande "whatever you think is worth it and address your need". What is unclear to me is the relation between the training data repo and the docs. Usually data in the TD are used for the training manual and the one in the qgis-sample-data repo are used in the user manual. Never paid attention to how the server docs respects or not these rules, though...

@pblottiere
Copy link
Member Author

Response a la normande "whatever you think is worth it and address your need".

ok :).

Usually data in the TD are used for the training manual and the one in the qgis-sample-data repo are used in the user manual. Never paid attention to how the server docs respects or not these rules, though...

Actually the Services chapter is a description of all requests/parameters supported by QGIS Server. But having a long list of bullet points is not very comprehensive nor user friendly.

I'd say that the training manual is like integration tests (we use all requests/parameters together to arrive at a complete/complex result) while a screenshot in the server documentation is like unit tests (what is the effect of this specific parameter).

Let me know what you think :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants