<div dir="ltr"><div>Wasn't there also an ability to have multiple Mapbooks that the user could choose from a dropdown (to switch chapters)? I seem to remember this from 2.4, but haven't seen any examples in 2.6..<br>
<br></div>maybe this was in Bob's answer which I didn't see go to the list.<br><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Dec 6, 2013 at 11:03 AM, Dan Little <span dir="ltr"><<a href="mailto:theduckylittle@gmail.com" target="_blank">theduckylittle@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">There are a number of people implementing a large collection of layers using GeoMOOSE. I know Bob B with the City of Saint Paul likes to brag about 300+ layers in his GeoMOOSE catalog. 100 or so layers will not be difficult. GeoMOOSE has the ability to break up the display of layers into groups, those groups can be analogous to chapters.<div>
<br></div><div>Also, the Mapbook is only an XML file. If you want to create some better management tools then I'd suggest the following:</div><div>1. Create a small django (or Rails or PHP) app that manages the layers in your organizations native structure. You can then use a small web front end and database back end to manage the organization. Then simply write a "publish to mapbook" function that write the Mapbook out for the GeoMOOSE application.</div>
<div><br></div><div>2. Use your favorite text-template language. For larger projects I'll use Mako templates (python based) or a collection of Perl scripts to assemble separate files together to make one Mapbook.</div>
<div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Fri, Dec 6, 2013 at 4:01 AM, Josef Fürst <span dir="ltr"><<a href="mailto:josef.fuerst@boku.ac.at" target="_blank">josef.fuerst@boku.ac.at</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<div style="FONT:10pt Segoe UI;MARGIN:4px 4px 1px">
<div>I am exploring options to implement a hydrological atlas over the Web. The atlas contains more than 100 thematic maps, organised in 10 chapters. Each of the maps is composed of up to approx. 10 layers, generally shapefiles (and some images). Originally, this atlas was published on CD-ROM, together with a ESRI Mapobjects LT based viewer software.</div>
<div> </div>
<div>GeoMoose appears to be an attractive platform for implementing the atlas on the WWW at first sight, but I am not sure about the organisation of so many maps. I thought, multiple mapbooks could be a solution, but following the discussion on this list, this seems not to be a natural (and efficient) approach. </div>
<div> </div>
<div>I would be grateful for all recommendations based on GeoMoose, but also on alternative products. I am hesitating to go down to tools like OpenLayers.</div>
<div> </div>
<div>Regards,</div>
<div>Josef Fuerst</div>
<div> </div>
<div> </div></div>
<br></div></div>_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br></blockquote></div><br></div>
<br>_______________________________________________<br>
Geomoose-users mailing list<br>
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br></blockquote></div><br></div></div></div></div>