<p dir="ltr">I did a Rails app years back that did this too. Upload a shapefile and dynamically generated a mapbook and mapfile. The styling was all SLD and a default style was generated based on the shapefile type but had to be hand edited from there.</p>
<div class="gmail_quote">On Dec 16, 2015 12:15 PM, "Brent Fraser" <<a href="mailto:bfraser@geoanalytic.com">bfraser@geoanalytic.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Eli,<br>
I totally agree with your 90% approach to support.<br>
<br>
Not too sure about the QGIS extension option. I've used an existing plugin to generate map files and was not impressed. It had some trivial bugs, but the main problem was the level of coding needed to replicate a QGIS project in a map file with all the coordinate systems and styling options (and mapserver versions!).<br>
<br>
To some extent, I would have a similar problem with my Python code, but its main purpose is just to get the mapbook and template syntax right.<br>
<br>
Best Regards,<br>
Brent Fraser<br>
<br>
On 12/16/2015 10:28 AM, Eli Adam wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Dec 16, 2015 at 8:53 AM, Brent Fraser <<a href="mailto:bfraser@geoanalytic.com" target="_blank">bfraser@geoanalytic.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Dan,<br>
<br>
Some of their features are intriguing:<br>
View -> Timeline<br>
Project -> Save/Load<br>
About -> Game<br>
<br>
And<br>
Edit -> Upload Shapefile<br>
<br>
That last one is interesting as I had built some Python to take a<br>
shapefile and generate a GeoMoose-friendly Maperver .map file and snippets<br>
for Geomoose's mapbook.xml (when answering some support questions the person<br>
frequently sends me a shapefile and a plea for help). But shipping the<br>
Python to users would just generate more support questions. Maybe the<br>
answer is to host the Python (or the PHP equivalent) on the Geomoose.org<br>
site?<br>
</blockquote>
A QGIS extension that exports the same might be an option as well.<br>
<br>
For users I support, the goal is to take 90% of the users to what they<br>
need with GeoMoose. The remaining 10% getting the higher effort to do<br>
custom one-off projects for them, design some other process and<br>
system, or install and train them in QGIS or ArcMap. Trying to<br>
shoehorn the last 10% into your all purpose tool takes way more than<br>
10% of the effort and is not worth it. Or at least that is my<br>
approach.<br>
<br>
Eli<br>
<br>
<br>
</blockquote>
<br>
<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" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a></blockquote></div>