wrt. "what to include in the url w.r.t ?, &..." that's easy to parse and fix. i am talking merely about not filtering any url parameters in the base url.
also, it's totally fine if the base url throws an error if the user made a mistake manually entering it! ..ede On 25.05.2021 14:01, Michaud Michael wrote: > Yes right. I think we tried in the past to use additional parameters passed > in the URL as query parameters rather than base url parameters but maybe I'm > wrong. > > Anyway, now that I added a field for additional query parameters in the query > panel, there is no reason to not use the url string of the first panel as is. > However, It may need a special care as the user not always now what to > include in the url w.r.t ?, &... > > Michaël > >> envoyé : 25 mai 2021 à 12:50 >> de : edgar.sol...@web.de >> à : jump-pilot-devel@lists.sourceforge.net >> objet : Re: [JPP-Devel] Regression in WMS with OJ 2 >> >> >> hey Jukka, Mike, >> >> as i recall initially a base was used as given and only the generated >> parameters (request etc.) were appended. did we run into issues that we >> limited the usage of url params in the base url? if not let's just suppose >> the users know's what they do and not over-engineer this. >> >> ..ede >> >> On 25.05.2021 12:36, Rahkonen Jukka (MML) wrote: >> >>> Hi Michaël. >>> >>> >>> >>> Most ”vendor options” in WMS affect GetMap, GetFeatureInfo etc. requests. >>> At service level, in addition to “map” with Mapservers, additional >>> parameters are at least used for identifying users. Unfortunately there is >>> no standard name for the parameter. I have seen “apikey”, “api-key”, >>> “apiKey”, and “token”. >>> >>> >>> >>> https://docs.nearmap.com/display/ND/Using+an+API+Key+in+Nearmap+Integrations >>> >>> https://enterprise.arcgis.com/en/server/latest/publish-services/linux/wms-services.htm >>> >>> https://openstream.edina.ac.uk/registration/help >>> >>> >>> >>> -Jukka- >>> >>> >>> >>> >>> >>> *Lähettäjä:* Michaud Michael <m.michael.mich...@orange.fr> >>> *Lähetetty:* maanantai 24. toukokuuta 2021 17.51 >>> *Vastaanottaja:* OpenJump develop and use >>> <jump-pilot-devel@lists.sourceforge.net>; Rahkonen Jukka (MML) >>> <jukka.rahko...@maanmittauslaitos.fi> >>> *Aihe:* Re: [JPP-Devel] Regression in WMS with OJ 2 >>> >>> >>> >>> Hi Jukka, >>> >>> Please, can you check if next snapshot solve the problem. >>> >>> By the way, I only added "map" as a possible parameter to be included in >>> the base URL. Do you know others ? >>> >>> We can also consider all parameters included in the connection dialog be >>> part of the base URL, >>> >>> but I'm not sure if is better as user not familiar with wms may include >>> some query parameters in the base URL. >>> >>> Michaël >>> >>> >>> >>> *envoyé :*20 mai 2021 à 12:47 >>> *de :* "Rahkonen Jukka (MML)" <jukka.rahko...@maanmittauslaitos.fi >>> <mailto:jukka.rahko...@maanmittauslaitos.fi>> >>> *à :* "jump-pilot-devel@lists.sourceforge.net >>> <mailto:jump-pilot-devel@lists.sourceforge.net>" >>> <jump-pilot-devel@lists.sourceforge.net >>> <mailto:jump-pilot-devel@lists.sourceforge.net>> >>> *objet :* [JPP-Devel] Regression in WMS with OJ 2 >>> >>> >>> >>> Hi, >>> >>> >>> >>> With Mapserver WMS it is common that the online resource is like >>> http://my.host.com/cgi-bin/mapserv?map=mywms.map&; >>> >>> https://www.mapserver.org/ogc/wms_server.html#changing-the-online-resource-url";. >>> It is not possible to use such services with OpenJUMP 2 because it cuts >>> the URL after the server part -> http://my.host.com/cgi-bin/mapserv? >>> >>> >>> >>> There is a new option to add custom WMS parameters with “more-parameters” >>> but it comes available too late, only after the initial connection has >>> been successful and user has selected the layers. >>> >>> >>> >>> The issue can be tested with this preconfigured server >>> http://wms.pcn.minambiente.it/ogc?map=/ms_ogc/WMS_v1.3/raster/ortofoto_colore_12.map&service=wms&request=getCapabilities&version=1.3.0&; >>> >>> >>> >>> -Jukka Rahkonen- >>> >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> <mailto:Jump-pilot-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >>> >>> >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >> >> >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
