Hi Jackie,
Thank you for all the information and the test that you did.
There is something strange: i load your package but, during the test connection appears the following error:
FDO Connection Status:
The remote server returned an error: (559) MgFdoException.: The custom error module does not recognize this error.
The remote server returned an error: (559) MgFdoException.
I compared the 2 config file and two main difference are the following:
- MM config: <xs:maxLength value="0" /> / JK config: <xs:maxLength value="256" />
- where you put x20 the maestro by me put x2e
But in both case the connection doesn't work, or by loading your package or by creating the feature source new by me.
Do you have some idea?
Here a link to my actual package
https://www.swisstransfer.com/d/0500602d-5285-4071-b49e-b66c0bf74137
Do you have some idea about this issue
Thank you
-----Messaggio originale-----
Da: mapguide-users <[email protected]> Per conto di [email protected]
Inviato: giovedì, 5 settembre 2024 21:00
A: [email protected]
Oggetto: mapguide-users Digest, Vol 212, Issue 4
Send mapguide-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osgeo.org/mailman/listinfo/mapguide-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific than "Re: Contents of mapguide-users digest..."
Today's Topics:
1. Re: WMS layer name problem (Jackie Ng)
2. Re: WMS layer name problem (Jackie Ng)
----------------------------------------------------------------------
Message: 1
Date: Thu, 5 Sep 2024 20:24:33 +1000
From: Jackie Ng <[email protected]>
To: MapGuide Users Mail List <[email protected]>
Subject: Re: [mapguide-users] WMS layer name problem
Message-ID:
<CAAC2fNR88fAuzStjvg57AQLyDcsZeA+1rqzqqgeLjs54JWZE+[email protected]>
Content-Type: text/plain; charset="utf-8"
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-0001.htm>
------------------------------
Message: 2
Date: Thu, 5 Sep 2024 23:24:54 +1000
From: Jackie Ng <[email protected]>
To: MapGuide Users Mail List <[email protected]>
Subject: Re: [mapguide-users] WMS layer name problem
Message-ID:
<CAAC2fNT5S_SthVUxQjc3pHU1ZnYM3j2eO1PhsLR=-goTKb+[email protected]>
Content-Type: text/plain; charset="utf-8"
An update on the example layers.
I could not reproduce the problems you described. I set up a WMS feature source in Maestro (git master) with a slimmed down configuration doc focused only on the layers you specified and I was able to create and preview all the layers specified.
To see for yourself, I've uploaded a package containing this WMS feature source and all the layers you mentioned here:
https://download.osgeo.org/mapguide/testing/data/WMS.mgp
This package loads into Library://WMS/ so make sure nothing else is there already or it may get overwritten by this package when loaded.
So as far as I'm concerned, the displaying of these WMS layers is fine on any viewer as MapGuide layers using the WMS FDO Provider. However if you desire GetFeatureInfo-based interaction, then my mapguide-react-layout viewer recommendation still stands.
- Jackie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20240905/42030e1e/attachment-0001.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
mapguide-users mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/mapguide-users
------------------------------
End of mapguide-users Digest, Vol 212, Issue 4
**********************************************
Thank you for all the information and the test that you did.
There is something strange: i load your package but, during the test connection appears the following error:
FDO Connection Status:
The remote server returned an error: (559) MgFdoException.: The custom error module does not recognize this error.
The remote server returned an error: (559) MgFdoException.
I compared the 2 config file and two main difference are the following:
- MM config: <xs:maxLength value="0" /> / JK config: <xs:maxLength value="256" />
- where you put x20 the maestro by me put x2e
But in both case the connection doesn't work, or by loading your package or by creating the feature source new by me.
Do you have some idea?
Here a link to my actual package
https://www.swisstransfer.com/d/0500602d-5285-4071-b49e-b66c0bf74137
Do you have some idea about this issue
Thank you
| MAURIZIO MASELLI | ||
| Geografo dipl. Bsc UZH, Ingegnere geologo dipl. MSc ETHZ Caposettore Geoinformazione | ||
| +41 58 580 01 49 | ||
| Locarno • Bellinzona • Biasca • Mendrisio | ||
| www.andreotti.ch | ||
-----Messaggio originale-----
Da: mapguide-users <[email protected]> Per conto di [email protected]
Inviato: giovedì, 5 settembre 2024 21:00
A: [email protected]
Oggetto: mapguide-users Digest, Vol 212, Issue 4
Send mapguide-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osgeo.org/mailman/listinfo/mapguide-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific than "Re: Contents of mapguide-users digest..."
Today's Topics:
1. Re: WMS layer name problem (Jackie Ng)
2. Re: WMS layer name problem (Jackie Ng)
----------------------------------------------------------------------
Message: 1
Date: Thu, 5 Sep 2024 20:24:33 +1000
From: Jackie Ng <[email protected]>
To: MapGuide Users Mail List <[email protected]>
Subject: Re: [mapguide-users] WMS layer name problem
Message-ID:
<CAAC2fNR88fAuzStjvg57AQLyDcsZeA+1rqzqqgeLjs54JWZE+[email protected]>
Content-Type: text/plain; charset="utf-8"
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-0001.htm>
------------------------------
Message: 2
Date: Thu, 5 Sep 2024 23:24:54 +1000
From: Jackie Ng <[email protected]>
To: MapGuide Users Mail List <[email protected]>
Subject: Re: [mapguide-users] WMS layer name problem
Message-ID:
<CAAC2fNT5S_SthVUxQjc3pHU1ZnYM3j2eO1PhsLR=-goTKb+[email protected]>
Content-Type: text/plain; charset="utf-8"
An update on the example layers.
I could not reproduce the problems you described. I set up a WMS feature source in Maestro (git master) with a slimmed down configuration doc focused only on the layers you specified and I was able to create and preview all the layers specified.
To see for yourself, I've uploaded a package containing this WMS feature source and all the layers you mentioned here:
https://download.osgeo.org/mapguide/testing/data/WMS.mgp
This package loads into Library://WMS/ so make sure nothing else is there already or it may get overwritten by this package when loaded.
So as far as I'm concerned, the displaying of these WMS layers is fine on any viewer as MapGuide layers using the WMS FDO Provider. However if you desire GetFeatureInfo-based interaction, then my mapguide-react-layout viewer recommendation still stands.
- Jackie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapguide-users/attachments/20240905/42030e1e/attachment-0001.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
mapguide-users mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/mapguide-users
------------------------------
End of mapguide-users Digest, Vol 212, Issue 4
**********************************************
_______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
