[fusion-users] MapServer + Fusion

[Jeff McKenna]

Excellent! Thanks very much Jay.

-jeff


On 29-Jul-08, at 9:38 PM, Jason Fournier wrote:

> Hey Jeff,
>
> I think you're right - this works for me in a MapFile:
>
> WEB
>  METADATA
>    "legend_title"  "CUSTOM MAP NAME"
>  END
> END
>
> That replaces the 'new node' label.  To replace the one above that I  
> think
> you can edit the strings file(s).
>
> Best regards,
> Jason
>
>
>
> -----Original Message-----
> From: fusion-users-bounces at lists.osgeo.org
> [mailto:fusion-users-bounces at lists.osgeo.org] On Behalf Of Jeff  
> McKenna
> Sent: Tuesday, July 29, 2008 6:57 PM
> To: fusion-users
> Subject: Re: [fusion-users] MapServer + Fusion
>
> Can someone refresh my memory for what metadata item is required to
> change the root folder name displayed in the legend?  (for example if
> you use the gmap mapfile you will see "new node" at the top of the
> legend tree by default, instead of a pretty map title)  For the life
> of me I could have sworn there was a special metadata item for
> this...but I can't remember!
>
> thanks.
>
> ---
> Jeff McKenna
> FOSS4G Consulting and Training Services
> http://www.gatewaygeomatics.com/
>
>
> On 11-Jul-08, at 2:04 PM, Paul Spencer wrote:
>
>> Tim,
>>
>> there is a little bit of layer metadata that you can use to control
>> how things appear in the legend.
>>
>> "displayInLegend" "true|false"
>>
>> By default, all layers are shown in the legend.  If set to false, it
>> will hide the layer in the legend
>>
>> "expandInLegend" "true|false"
>>
>> By default, all classified layers will show a sub-branch in the
>> legend with all the classes.  If set to false then the sub-branch is
>> initially collapsed
>>
>> "legendLabel" "string value"
>>
>> By default, the layer's NAME value is used in the legend.  If this
>> metadata is set, then the value will be used in the legend instead.
>>
>> "selectable" "true|false"
>>
>> By default, layers are not 'selectable' using the select widget.  If
>> this is set to 'true' then the layer will be considered 'selectable'
>> so the select widget will be enabled when this layer is selected in
>> the legend.
>>
>> The legend will create folders for each group and put the
>> appropriate layers in those groups.  The groups respond to the
>> following metadata in the first LAYER object in the group (first
>> layer to use the group name)
>>
>> "groupLegendLabel" "string value"
>>
>> By default, the group name is used as the legend label.  If this
>> metadata is set then the value will be used instead of the group  
>> name.
>>
>> "groupDisplayInLegend" "true|false"
>>
>> By default, all groups are displayed in the legend.  Setting this to
>> false will hide the group in the legend (and all layers that are
>> part of that group too).
>>
>> "groupExpandInLegend" "true|false"
>>
>> By default, groups initially start expanded to show the layers in
>> that group.  Setting this to false will start the group off
>> 'collapsed'.
>>
>> Cheers
>>
>> Paul
>>
>> On 11-Jul-08, at 12:37 PM, Nolte, Tim wrote:
>>
>>> One issue that I have, and I found out why, is that my separate
>>> layers
>>> end up getting stuck together. (those that are in the same group).
>>> What
>>> I found out was that those layers that I have named like "Johnson
>>> City"
>>> aren't accessed correctly and able to be independently turned off.
>>> However, if I name the layer "JohnsonCity" with no spaces in the  
>>> name
>>> then it works fine. The things about this is that what gets
>>> displayed in
>>> the Legend is that name and I don't want crapping looking layer
>>> titles.
>>> Also, something that I haven't figured out is how to completely hide
>>> certain layers from the legend that I use for dynamic purposes, that
>>> shouldn't be showing by default. Another problem I seem to have is
>>> that
>>> my legend icons don't all seem to be showing up correctly. Now this
>>> could be an issue with the version of UMN MapServer that I'm  
>>> using. I
>>> did have to do some custom things to get these working in my other
>>> mapping framework.
>>>
>>> - Tim
>>>
>>> ----
>>> Timothy J Nolte - tnolte at ilpcs.com
>>> Network Planning Engineer
>>>
>>> iPCS Wireless, Inc.
>>> 4717 Broadmoor Ave, Suite G
>>> Kentwood, MI 49512
>>>
>>> Office: 616-656-5163
>>> PCS:    616-706-2438
>>> Fax:    616-554-6484
>>> Web: www.ipcswirelessinc.com
>>>
>>>> -----Original Message-----
>>>> From: fusion-users-bounces at lists.osgeo.org
>>>> [mailto:fusion-users-bounces at lists.osgeo.org] On Behalf Of
>>>> Jason Fournier
>>>> Sent: Friday, July 11, 2008 10:08 AM
>>>> To: fusion-users at lists.osgeo.org
>>>> Subject: RE: [fusion-users] MapServer + Fusion
>>>>
>>>> Hi Tim,
>>>>
>>>>> From my understanding you should not have to do too much
>>>> tweaking of your
>>>> MapFile to get it to work properly with Fusion.  Certain widgets
>>>> will
>>>> require certain aspects of the MapFile to be present but you
>>>> should be able
>>>> to get a usable map without having to populate the MapFile
>>>> with extraneous
>>>> information.  What specifically are some of the issues you
>>>> are witnessing?
>>>>
>>>> Jason
>>>>
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: fusion-users-bounces at lists.osgeo.org
>>>> [mailto:fusion-users-bounces at lists.osgeo.org] On Behalf Of Nolte,
>>>> Tim
>>>> Sent: Thursday, July 10, 2008 3:29 PM
>>>> To: fusion-users at lists.osgeo.org
>>>> Subject: [fusion-users] MapServer + Fusion
>>>>
>>>> So was able to get something working by using files found under
>>>> fusion->templates->mapserver->standard for me use as samples.
>>>> I was able
>>>> to get the gmap demo data working and even my own current  
>>>> Production
>>>> MapServer .map file. There are a lot of strange issues that
>>>> make it seem
>>>> as though I'm going to need to make a new .map file that is tuned
>>>> for
>>>> Fusion. I'm going to have to do some reading. Off hand, does
>>>> anyone have
>>>> any pointers? I'm thinking that I'm going to have to add a
>>>> bunch of meta
>>>> data for this to work correctly. Is Fusion using my MapServer
>>>> install/mapfile as a WMS or WFS source?
>>>>
>>>> - Tim
>>>>
>>>> ----
>>>> Timothy J Nolte - tnolte at ilpcs.com
>>>>
>>>
>