[mapguide-users] WMS layer name problem

[Jackie Ng]

Responses inline [JN] below.

- Jackie

You wrote:

Hi Jackie,

Thank you very much for the help. What you did is exactly what i did to
load the wms as a layer definition.


The layer names that create problems are the following:


- [TI-028b.1] Gambarogno Lalpt - Piano zone Magadino (ti 028b_1
zp100064_pz_ma)
- [TI-028b.1] Gambarogno Lalpt - Piano zone S. Nazzaro (ti 028b_1
zp100064_pz_sn)
- [TI-028b.1] Gambarogno Lalpt - Piano zone S. Abbondio (ti 028b_1
zp100064_pz_sa)
- [TI-028b.1] Gambarogno Lalpt - Piano zone Gerra G. (ti 028b_1
zp100064_pz_ge_)
- [TI-028b.1] Gambarogno Lalpt - Piano zone Vira G. (ti 028b_1
zp100064_pz_vi)
- [TI-028b.1] Gambarogno Lalpt - Piano zone Indemini (ti 028b_1
zp100064_pz_in)
- [TI-028b.1] Gambarogno Lalpt - Piano zone Piazzogna (ti 028b_1
zp100064_pz_pi)
- [TI-028b.1] Gambarogno Lalpt - Piano zone Caviano (ti 028b_1
zp100064_pz_ca)


JN: Thanks for the specific list. I'll dig further.

The improvements that you did to the advanced options of the WMS feture
source are avaliable on the next release of Maestro?


JN: Yes this change will be in the next release. No specific date on a next
release of Maestro. But if you want to try Maestro with this change, you
can grab the latest CI build from AppVeyor

https://ci.appveyor.com/project/jumpinjackie/mapguide-maestro/builds/50521030/artifacts

Another question the query to wms in ajax viewer are possible only  with
implementation of an external programm right or there is another solution?


JN: The AJAX viewer is pretty much our "legacy" viewer offering that can
only view layers served from MapGuide. It does not support external base
layers or WFS/WMS layers unless those services are consumed via their
respective FDO providers (which is what you're currently doing)

I try to compose the getfetureinfo and create a link on a tooltip but i
dont know how to find the width, hight, i and j paramters of wms to
complete the url.


Have you some idea or advise?


JN: Sorry, the AJAX viewer only lets you *view* any WMS layers consumed
through the FDO provider. There is no interaction support and trying to add
such support is a fruitless endeavor. Neither does fusion without some
significant work.

However my mapguide-react-layout offering does let you overlay/underlay WMS
layers against your MG layers and the default select tool does automatic
WMS GetFeatureInfo queries against any WMS layers you click on and can
present its result as either a feature popup or client-side vector feature
"selection".

It also comes built-in with an External Layer Manager widget to easily add
WFS/WMS and file-based plaintext vector data (GeoJSON/KML/etc) layers. If
you need a viewer solution that needs to do more than view WMS layers
out-of-the-box then mapguide-react-layout is probably your best choice.

mapguide-react-layout is on my github:
https://github.com/jumpinjackie/mapguide-react-layout
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20240905/fbe5ecb3/attachment.htm>