Add Legend to printable map (PDF output)

[tchaddad]

Place a legend showing layers turned on in the PDF output.

As mentioned here: http://lists.osgeo.org/pipermail/geomoose-users/2015-April/005601.html
and here: http://lists.osgeo.org/pipermail/geomoose-users/2015-July/005716.html

More to follow..

[theduckylittle]

So, apparently, we did not have legend rendering support. And now we do. Huzzah!

[tchaddad]

Tested successfully in 97b9ce2 by inserting:<param name="renderLegends">true</param> into the mapbook.xml parameters.

We should consider adding this to the demo mapbook so that users are aware that the option exists.

[elil]

The default mapbook.xml so far has been a balancing act of including the most common elements for example and reference and confusion with unnecessary information. We could also consider the approach of include all options.

I'll add this to the Mapbook Reference Guide. Suggestions on where?

[tchaddad]

Understand about the demo. I was thinking that this was a common enough need (it's highly requested) that adding it as <param name="renderLegends">false</param> so that it is turned off by default wouldn't be too intrusive.

As for the reference guide, the logical location is the configuration section at the top (since the guide is laid out like the Mapbook). But since that section mostly consists of copy-paste from the demo...

I assume it will also end up here?: http://docs.geomoose.org/master/docs/configuration.html#configuration

[elil]

Hmm, thinking about it, maybe it is better just in the configuration and not making the reference guide more crowded.

Assuming that our script that makes that page catches it, then yes, every config will be there.

@klassenjs should we update the release process with something about running doc_config_js.py? When does that get run?

[theduckylittle]

I set this as the default and fixed the code in master which had a regression that looked like I was testing some code.