<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
That looks promising.<br>
<br>
<div class="moz-cite-prefix">On 12/27/23 16:23, TC Haddad via
geomoose-psc wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFVrPyg93r-11aatFaa9qtxacL=D8Eaw5su9tEvaEmKKweHSiA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div><br>
</div>
<div>Yesterday I edited the wiki page that Brent linked to, to
add the GeoCat Bridge QGIS plugin, which was recently
referenced on the MapServer list as another mapfile syntax
generator. Mentioning it here because I had been testing their
"StyleViewer" this last week, and it's pretty uncomplicated to
use, and the tabbed interface allows flipping from MapServer
to GeoStyler syntax pretty easily, so that's potentially a
single (well-supported?) UI that helps with both raster and
vector styling. Screen grab here for the curious: <a
href="https://imgur.com/a/VM4XRbH" moz-do-not-send="true"
class="moz-txt-link-freetext">https://imgur.com/a/VM4XRbH</a></div>
<div><br>
</div>
<div>I think having users do their styling in QGIS is the way to
go if at all possible, and there are other QGIS plugins (e.g.
SLYR: <a href="https://github.com/north-road/slyr"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/north-road/slyr</a>)
out there that are already tailored to enticing migration from
the E**I ecosystem of styling (LYR files) to QGIS. So that
means with some documentation glue, users could be coached on
how to bring existing cartography into QGIS from the
proprietary world, and then transfer it to MapServer or
GeoStyler cartography for use in GeoMoose, without too many
steps. <br>
</div>
<div><br>
</div>
<div>At least, this is what comes to mind on the cartography
side from my "GIS in the trenches" experience with users in
small communities.</div>
<div><br>
</div>
<div>Tanya</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Dec 14, 2023 at
8:14 AM Dan Little via geomoose-psc <<a
href="mailto:geomoose-psc@lists.osgeo.org"
moz-do-not-send="true" class="moz-txt-link-freetext">geomoose-psc@lists.osgeo.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>- <a
href="https://github.com/openlayers/ol-mapbox-style/pull/940#issuecomment-1855415159"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/openlayers/ol-mapbox-style/pull/940#issuecomment-1855415159</a></div>
<div><br>
</div>
<div>We use a "vendored" version of the ol-mapbox-style-spec
to power GeoMoose's styling right now. This may have an
effect on us over the next few months that motivate moving
some of the styling engine over to something like
GeoStyler's. </div>
<div><br>
</div>
<div>This does force me to shine light on a few GeoMoose
things that I've been struggling with in the last two
years:</div>
<div>1. How can we keep being the "plug-in-data-and-go"
solution? How do we become the best at that? MapServer can
feel very difficult to work with despite its performance.
I think MapServer 8 is a great piece of software and I
understand many of the design decisions but if I've grown
up on E**I stuff, at this point, it'll be difficult to
approach.</div>
<div>2. How can we get better at vector styling? This may be
Ahab's Whale but is definitely something I think about.
Styling in the app, styling data, how do we serve data
that is easy to style? Etc. etc. <br>
</div>
<div><br>
</div>
<div>Things I know we can't make a part of our standard
install and expect easy uptake:<br>
</div>
<div>- Cloud</div>
<div>- Docker</div>
<div>- "Compile."</div>
<div><br>
</div>
<div>There are solutions I would love to think about but
have left off the table:</div>
<div>- Create a mapfile editor. It's been tried but with
narrow constraints it might work.</div>
<div>- Jump to QGIS server and/or piggy back on it to allow
publishing whole apps. Keeping up with these changes are
likely a full time job.</div>
<div>- "F**k it, we're the mapserver now!" Collaborate with
or upon a solution written in rust or go that support
cross platform compilation. Double click a binary, it
starts the server, go through the wizard to tell it where
some data is, and you're off to the races. Want it as a
service? Sure here's the 10-step guide to making it work
with pm2 or on Debian.</div>
<div><br>
</div>
<div>Thank you for taking the space for this. 😆 I genuinely
want us to have a product that people can use, use easily,
and provide some real benefit to the ecosystem in ways
other projects aren't. I love that this team has always
focused on what it takes to do GIS in the trenches and
what that user profile looks like.</div>
<div><br>
</div>
</div>
_______________________________________________<br>
geomoose-psc mailing list<br>
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">geomoose-psc@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
geomoose-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a>
</pre>
</blockquote>
<br>
</body>
</html>