<div dir="ltr">Thanks for the details Jim. That explains why things worked when they did and didn't when they didn't.<br><input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"enableNoauth":false,"persistentProtection":false,"expandedWatermarking":false,"expires":false,"isManaged":false},"attachments":{},"compose-id":"8","compose-window":{"secure":false}}"><br><div class="gmail_quote" style=""><div dir="ltr" class="gmail_attr">On Mon, Apr 18, 2022 at 1:07 PM Jim Klassen <<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</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>
That is expected behavior.<br>
<br>
GeoMoose treat separate map-sources as separate entities and will
make a separate request for each map-source. MapServer then doesn't
know the other layers were drawn and thus can't do label collision
detection between the layers in different map-sources. All the
layers within one map-source are drawn with one request to MapServer
and returned in one image.<br>
<br>
This is where the feature to include multiple map-source/layers in a
catalog layer src="" attribute came from. So people who really
wanted the labels perfect could put all their label drawing into one
mapfile at the top of the stack so MapServer could do optimal
conflict detection. There are also major downsides to this
regarding being able to treat layers independently which limits
GeoMoose functionality (changing z-order, generally incompatible
with the visible/active layers tab) and means all layers break (pink
screen) if one mapfile breaks. Depending on your use case this
tradeoff can be anywhere from no big deal to a show stopper. So we
support both options (but not both options, well, at the same time).<br>
<br>
<div>On 4/18/22 10:45, Christopher Hughes
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I'm encountering some odd issues when trying to
label multiple layers when they're
<div>in separate map-sources. All the labels work, but when
they're in separate map-sources,</div>
<div>they conflict with each other.</div>
<div><br>
</div>
<div>For example, when I set up a single map-source for a
basemap like this:</div>
<div><br>
</div>
<div> <map-source name="basemap" type="mapserver"><br>
<file>basemap.map</file><br>
<layer name="city" status="on"/><br>
<layer name="town" status="on"/><br>
<layer name="rivers" status="on"/><br>
<layer name="Contours_(40ft)" status="on"/><br>
<layer name="Contours_(10ft)" status="on"/><br>
<layer name="Streams" status="on"/><br>
<layer name="Streets" status="on"/></div>
<div> </map-source><br>
</div>
<div><br>
</div>
<div>Labels between different layers work seamlessly with each
other (label priority settings</div>
<div>are honored, auto positioning moves them to not overlap,
they automatically disappear</div>
<div>if a non-overlapping position can't be found).</div>
<div><br>
</div>
<div>If I break apart this map-source into individual
layers (i.e. you have layers in different mapfiles, </div>
<div>if you want a particular layer at the top of your map, or
you want to turn individual layers on or off), </div>
<div>the labels for these layers can overlap regardless of label
priority settings or auto positioning. </div>
<div>It's not a major problem, but it can make things look very
cluttered, and you have to spend a lot </div>
<div>more time considering how labels from different layers will
work with each other.</div>
<div><br>
</div>
<div>Has anyone run into this issue or found a workaround? I'm
not sure to what extent it's a MapServer</div>
<div>problem or a GeoMoose issue.</div>
<div><br>
</div>
<div>I appreciate any feedback,</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div><br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">
<div dir="ltr"><font size="4">Chris Hughes</font>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">GIS Analyst</div>
<div style="font-size:12.8px"><font size="1">Lincoln
County GIS Department </font></div>
<div><font size="1"><span style="font-family:Roboto,arial,sans-serif">880 NE
7th S</span><span style="font-family:Roboto,arial,sans-serif">t</span>.
l Newport, OR 97365</font></div>
<div style="font-size:12.8px"><font size="1">Tel: (541)
574 1283</font></div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Geomoose-users mailing list
<a href="mailto:Geomoose-users@lists.osgeo.org" target="_blank">Geomoose-users@lists.osgeo.org</a>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-users" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-users</a>
</pre>
</blockquote>
<br>
</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="https://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><font size="4">Chris Hughes</font><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">GIS Analyst</div><div style="font-size:12.8px"><font size="1">Lincoln County Surveyor Department </font></div><div><font size="1"><span style="font-family:Roboto,arial,sans-serif">880 NE 7th S</span><span style="font-family:Roboto,arial,sans-serif">t</span>. l Newport, OR 97365</font></div><div style="font-size:12.8px"><font size="1">Tel: (541) 574 1283</font></div></div></div></div>