<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 26, 2013, at 8:07 AM, Robert R. Raiz wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hello,<br><br>The idea is to create an environment which should allow the use of a specific map file based on user input (useful if one has several projects which are not connected). My goal is to use GeoMoose in an environment which will have a mapfile for each project. These mapfiles will be in local projection and will have all the data 'to be' added in the mapbook.xml file.<br>
<br>So, let's say I have my map files city-based (each using its own local projection, the epsg code of the county):<br><br>data/testing/dakota/dakota.map<br>data/testing/commerce/commerce.map<br>data/testing/chicago/chicago.map<br clear="all">
<div style=""><br>My goal is to populate (on the fly, using a script) the mapbook based on what I enter in the navigation bar.<br><br>Two questions:<br>1. Do I have to create a .js file of all the epsg codes I use and add them in the geomoose.html file?<br>
I noticed that it also works without doing this. What am I gaining by creating these .js files?<br></div></div></blockquote><div>I think Proj4JS checks <a href="http://spatialreference.org">spatialreference.org</a> if it can't find the projection locally. If it didn't work the lat/lon at the bottom of the window would be wrong and anything else requiring re-projection would fail.</div><div><br></div><blockquote type="cite"><div dir="ltr"><div style=""><br>2. Can I "read" the status of a layer (on, off) from the .map file instead of declaring the layer status in the mapbook?<br>
I already have the status of every layer stated in the corresponding map file. The ones I do not want to load (to have them checked) by default are set to OFF. It would be great if I could keep the status without having to specify them for each layer in the mapbook.<br></div></div></blockquote><div>In the current form this would require GetMapbook.php be customized to use MapScript to parse the mapfiles. There is a provision to support different mapbooks based on the URL (...geomoose.html?mapbook=). If you didn't mind writing the mapbooks, you could use that. Traditionally, we use a mapfile per layer to try and isolate faults (it is assumed that different layers are maintained by different people).</div><br><blockquote type="cite"><div dir="ltr"><div style="">
<br>Furthermore, I will be digging into GeoMoose 24/7 so if I can help the community with something, I will, gladly. The setback is that I am not a programmer so probably my options are limited. <br></div></div></blockquote><div>Thanks. We can always use help with docs and testing too.</div><div><br></div><br><blockquote type="cite"><div dir="ltr"><div style=""><br>It would be great to meet some of the developers at FOSS4G Nottingham, at the Code Sprint or GeoHack days, although I did not see any presentation about GeoMoose in the schedule.</div></div></blockquote>The GeoMoose community in Minnesota was rather swamped this spring with helping put together the FOSS4G-NA conference in Minneapolis. It looks like we missed the deadlines for abstract submission.<br><br><blockquote type="cite"><div dir="ltr"><div style="">
<br>Many thanks,</div>-- <br><b><i>Raiz Roland Robert</i></b><br><br><br>
</div>
_______________________________________________<br>Geomoose-users mailing list<br><a href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br>http://lists.osgeo.org/mailman/listinfo/geomoose-users<br></blockquote></div><br></body></html>