Re: [JPP-Devel] WMS layer problems
Rahkonen Jukka wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group_id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? Best regards, Andreas -- l a t / l o n GmbH Aennchenstrasse 19 53177 Bonn, Germany phone ++49 +228 18496-0 fax ++49 +228 1849629 http://www.lat-lon.dehttp://www.deegree.org Follow deegree on Twitter: http://twitter.com/deegree_org signature.asc Description: Digital signature -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] exploding GeometryCollections?
Hi, we don't have a standard-function to "explode" GeometryCollections to single Geometries in OpenJUMP, am I right? To have an option "don't allow GeometryCollections" in the main-menu-function ToolsAnalysisOne LayerUnion would be nice , too. Maybe I could try to implement something like that (I don't have as much time, so that could last a while...). Regards, Nils -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Hi, Rahkonen Jukka wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group_id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? No, this is an internal server. My last test's i've done with the standalone geoserver (http://downloads.sourceforge.net/geoserver/geoserver-2.0.2-bin.zip) and the included datasets. But why do not have other WMS clients problems? With QGIS 1.3.0 and an other propritary solution I've no problems with Geoserver 2.0.2. Matthias Best regards, Andreas -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Matthias Scholz wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group_id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? No, this is an internal server. My last test's i've done with the standalone geoserver (http://downloads.sourceforge.net/geoserver/geoserver-2.0.2-bin.zip) and the included datasets. But why do not have other WMS clients problems? With QGIS 1.3.0 and an other propritary solution I've no problems with Geoserver 2.0.2. I'm sure it's an OJ problem. What I'm not sure about is whether you use an outdated version or whether there is another bug in the way the encoding works in OJ. Best regards, Andreas -- l a t / l o n GmbH Aennchenstrasse 19 53177 Bonn, Germany phone ++49 +228 18496-0 fax ++49 +228 1849629 http://www.lat-lon.dehttp://www.deegree.org Follow deegree on Twitter: http://twitter.com/deegree_org signature.asc Description: Digital signature -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Hi! Matthias Scholz wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group_id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? No, this is an internal server. My last test's i've done with the standalone geoserver (http://downloads.sourceforge.net/geoserver/geoserver-2.0.2-bin.zip) and the included datasets. But why do not have other WMS clients problems? With QGIS 1.3.0 and an other propritary solution I've no problems with Geoserver 2.0.2. I'm sure it's an OJ problem. What I'm not sure about is whether you use an outdated version or whether there is another bug in the way the We use the released OJ 1.3.1 version and yesterday I've tested with the SVN version. With both the same problems. encoding works in OJ. Best regards, Andreas -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Matthias Scholz wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group_id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? No, this is an internal server. My last test's i've done with the standalone geoserver (http://downloads.sourceforge.net/geoserver/geoserver-2.0.2-bin.zip) and the included datasets. But why do not have other WMS clients problems? With QGIS 1.3.0 and an other propritary solution I've no problems with Geoserver 2.0.2. I'm sure it's an OJ problem. What I'm not sure about is whether you use an outdated version or whether there is another bug in the way the We use the released OJ 1.3.1 version and yesterday I've tested with the SVN version. With both the same problems. can you post/send the GetCapabilities-response document? With that, I can also make some tests. Best regards, Andreas -- l a t / l o n GmbH Aennchenstrasse 19 53177 Bonn, Germany phone ++49 +228 18496-0 fax ++49 +228 1849629 http://www.lat-lon.dehttp://www.deegree.org Follow deegree on Twitter: http://twitter.com/deegree_org signature.asc Description: Digital signature -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Andreas Schmitz wrote: Rahkonen Jukka wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group _id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? We do not use Geoserver WMS services but I installed Geoserver on my laptop for testing with the Windows installer http://downloads.sourceforge.net/geoserver/geoserver-2.0.2.exe After installation Geoserver WFS is at http://localhost:8080/geoserver/wms I used the sf:archsites demo layer for testing, and checked the incoming GetMap requests from the request log that is located at geoserver2.0.2\logs directory. Now I do not have my laptop with me and I made another trial with an OJ 1.3 and Geoserver 2.0.1. This time Geoserver WMS works OK. I can see WMS layers, and if I save the project, close and reopen it and do right click - zoom to WMS layer then everything works just perfectly. I need to do some further tests in a more controlled way so I can see if my problems yesterday were due to Geoserver 2.0.2 or some old OJ version. I thought I was using 1.3 but I am not totally sure. It is possible to check the WMS url that OJ is using by using the nice Beanshell script from http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Beanshe ll:Get_the_WMS_URL_that_JUMP_is_using Running that from the Beanshell window should show immediately if OJ is having troubles with URL-encoding. -Jukka Rahkonen- -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Rahkonen Jukka wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group _id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? We do not use Geoserver WMS services but I installed Geoserver on my laptop for testing with the Windows installer http://downloads.sourceforge.net/geoserver/geoserver-2.0.2.exe After installation Geoserver WFS is at http://localhost:8080/geoserver/wms I used the sf:archsites demo layer for testing, and checked the incoming GetMap requests from the request log that is located at geoserver2.0.2\logs directory. Now I do not have my laptop with me and I made another trial with an OJ 1.3 and Geoserver 2.0.1. This time Geoserver WMS works OK. I can see WMS layers, and if I save the project, close and reopen it and do right click - zoom to WMS layer then everything works just perfectly. I need to do some further tests in a more controlled way so I can see if my problems yesterday were due to Geoserver 2.0.2 or some old OJ version. I thought I was using 1.3 but I am not totally sure. It is possible to check the WMS url that OJ is using by using the nice Beanshell script from http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Beanshe ll:Get_the_WMS_URL_that_JUMP_is_using Running that from the Beanshell window should show immediately if OJ is having troubles with URL-encoding. if you have the cmd shell enabled (change the script to start OJ with 'java ' instead of 'start javaw '), you should also see the GetMap requests logged on the command line (or if you configured OJ to use log4j to log into a file). Best regards, Andreas -- l a t / l o n GmbH Aennchenstrasse 19 53177 Bonn, Germany phone ++49 +228 18496-0 fax ++49 +228 1849629 http://www.lat-lon.dehttp://www.deegree.org Follow deegree on Twitter: http://twitter.com/deegree_org signature.asc Description: Digital signature -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Rahkonen Jukka schrieb: Andreas Schmitz wrote: Rahkonen Jukka wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group _id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? We do not use Geoserver WMS services but I installed Geoserver on my laptop for testing with the Windows installer http://downloads.sourceforge.net/geoserver/geoserver-2.0.2.exe After installation Geoserver WFS is at http://localhost:8080/geoserver/wms I used the sf:archsites demo layer for testing, and checked the incoming GetMap requests from the request log that is located at geoserver2.0.2\logs directory. Now I do not have my laptop with me and I made another trial with an OJ 1.3 and Geoserver 2.0.1. This time Geoserver WMS works OK. I can see WMS layers, and if I save the project, close and reopen it and do right click - zoom to WMS layer then everything works just perfectly. I need to do some further tests in a more controlled way so I can see if my problems yesterday were due to Geoserver 2.0.2 or some old OJ version. I thought I was using 1.3 but I am not totally sure. It is possible to check the WMS url that OJ is using by using the nice Beanshell script from http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Beanshe ll:Get_the_WMS_URL_that_JUMP_is_using Running that from the Beanshell window should show immediately if OJ is having troubles with URL-encoding. Here is my result: bsh % print(wc.getLayerManager().getLayerables( com.vividsolutions.jump.workbench.model.WMSLayer.class).iterator().next().createRequest(wc.getLayerViewPanel()).getURL()); http://localhost:8080/geoserver/ows?service=wmsversion=1.1.1request=GetCapabilitiesREQUEST=GetMapSERVICE=WMSVERSION=1.1.1WIDTH=672HEIGHT=530LAYERS=sf%3AarchsitesTRANSPARENT=TRUEFORMAT=image%2FpngBBOX=591480.7610900033,4914595.597562009,606276.7792053049,4926265.076135089SRS=EPSG:26713STYLES= Matthias -Jukka Rahkonen- -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Matthias Scholz wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group _id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? We do not use Geoserver WMS services but I installed Geoserver on my laptop for testing with the Windows installer http://downloads.sourceforge.net/geoserver/geoserver-2.0.2.exe After installation Geoserver WFS is at http://localhost:8080/geoserver/wms I used the sf:archsites demo layer for testing, and checked the incoming GetMap requests from the request log that is located at geoserver2.0.2\logs directory. Now I do not have my laptop with me and I made another trial with an OJ 1.3 and Geoserver 2.0.1. This time Geoserver WMS works OK. I can see WMS layers, and if I save the project, close and reopen it and do right click - zoom to WMS layer then everything works just perfectly. I need to do some further tests in a more controlled way so I can see if my problems yesterday were due to Geoserver 2.0.2 or some old OJ version. I thought I was using 1.3 but I am not totally sure. It is possible to check the WMS url that OJ is using by using the nice Beanshell script from http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Beanshe ll:Get_the_WMS_URL_that_JUMP_is_using Running that from the Beanshell window should show immediately if OJ is having troubles with URL-encoding. Here is my result: bsh % print(wc.getLayerManager().getLayerables( com.vividsolutions.jump.workbench.model.WMSLayer.class).iterator().next().createRequest(wc.getLayerViewPanel()).getURL()); http://localhost:8080/geoserver/ows?service=wmsversion=1.1.1request=GetCapabilitiesREQUEST=GetMapSERVICE=WMSVERSION=1.1.1WIDTH=672HEIGHT=530LAYERS=sf%3AarchsitesTRANSPARENT=TRUEFORMAT=image%2FpngBBOX=591480.7610900033,4914595.597562009,606276.7792053049,4926265.076135089SRS=EPSG:26713STYLES= this looks almost good. Did you enter the complete GetCapabilities request when trying to load the layer? You should leave the GetCapabilities parameters off, since they're added automatically. Example: load the layer using http://localhost:8080/geoserver/ows The URL encoding actually looks good (: is encoded as %3A). Best regards, Andreas -- l a t / l o n GmbH Aennchenstrasse 19 53177 Bonn, Germany phone ++49 +228 18496-0 fax ++49 +228 1849629 http://www.lat-lon.dehttp://www.deegree.org Follow deegree on Twitter: http://twitter.com/deegree_org signature.asc Description: Digital signature -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Andreas Schmitz schrieb: Matthias Scholz wrote: Hi, I checked that WMS layer name is stored OK in the OJ project file wms-layer-namesf:archsites/wms-layer-name Let's hope that question is only about url-encoding error. I discussed with a Geoserver developer and he considered that both ways would be correct, to leave it unaltered sf:archsites or to url-encode it to sf%3Aarchsites. I think this is rather critical bug that effectively prevents all use of Geoserver WMS services. Therefore I filed a new ticket https://sourceforge.net/tracker/?func=detailaid=3023366group _id=118054atid=679906 I agree. But checking the code I only see it being encoded once. I vaguely remember fixing such a double encoding problem (deegree WMS also often has a colon separated prefix for layer names, eg. for the CITE instances), but I think it had to do with GetFeatureInfo. Are you sure you're using an up to date version? Well, probably you are... Maybe it's a problem with how it's encoded in the GetCapabilities response. Is there an online server against which I could test? We do not use Geoserver WMS services but I installed Geoserver on my laptop for testing with the Windows installer http://downloads.sourceforge.net/geoserver/geoserver-2.0.2.exe After installation Geoserver WFS is at http://localhost:8080/geoserver/wms I used the sf:archsites demo layer for testing, and checked the incoming GetMap requests from the request log that is located at geoserver2.0.2\logs directory. Now I do not have my laptop with me and I made another trial with an OJ 1.3 and Geoserver 2.0.1. This time Geoserver WMS works OK. I can see WMS layers, and if I save the project, close and reopen it and do right click - zoom to WMS layer then everything works just perfectly. I need to do some further tests in a more controlled way so I can see if my problems yesterday were due to Geoserver 2.0.2 or some old OJ version. I thought I was using 1.3 but I am not totally sure. It is possible to check the WMS url that OJ is using by using the nice Beanshell script from http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=Beanshe ll:Get_the_WMS_URL_that_JUMP_is_using Running that from the Beanshell window should show immediately if OJ is having troubles with URL-encoding. Here is my result: bsh % print(wc.getLayerManager().getLayerables( com.vividsolutions.jump.workbench.model.WMSLayer.class).iterator().next().createRequest(wc.getLayerViewPanel()).getURL()); http://localhost:8080/geoserver/ows?service=wmsversion=1.1.1request=GetCapabilitiesREQUEST=GetMapSERVICE=WMSVERSION=1.1.1WIDTH=672HEIGHT=530LAYERS=sf%3AarchsitesTRANSPARENT=TRUEFORMAT=image%2FpngBBOX=591480.7610900033,4914595.597562009,606276.7792053049,4926265.076135089SRS=EPSG:26713STYLES= this looks almost good. Did you enter the complete GetCapabilities request when trying to load the layer? You should leave the GetCapabilities parameters off, since they're added automatically. Example: load the layer using http://localhost:8080/geoserver/ows This is the solution :-) I've allways used the complete GetCapabilities request as a copy from the link in the geoserver webinterface. From the view as a normal user OJ should support both possibilities and build internal the correct URL or the user should see a hint in the dialog. Can you patch this? Thank you, Matthias The URL encoding actually looks good (: is encoded as %3A). Best regards, Andreas -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Matthias Scholz wrote: this looks almost good. Did you enter the complete GetCapabilities request when trying to load the layer? You should leave the GetCapabilities parameters off, since they're added automatically. Example: load the layer using http://localhost:8080/geoserver/ows This is the solution :-) I've allways used the complete GetCapabilities request as a copy from the link in the geoserver webinterface. Hi, Now I believe that we have finally enough information about what went wrong with the save and open project. My URL-encoding problems had to be a false alarm because of using an outdated OJ version. I will check that againg later and if a fresh OpenJUMP works right on my laptop I will comment my bug report as already solved. But the real issue is in saving the GetMap URL into OpenJUMP project file. When connecting Geoserver with URL http://localhost:8080/geoserver/ows?request=getcapabilities; OpenJUMP is reading the GetMap URL from GetCapabilities and asks user if it should be used instead. That url is http://localhost:8080/geoserver/wms?SERVICE=WMS If user is pressing Yes then this GetMap URL will be used for further communication and it works. SERVICE=WMS will now be included twise it the requests but is does not matter. I suppose that Geoserver folks have meant that the GetMap URL is http://localhost:8080/geoserver/ows?SERVICE=WMS, in that case adding service parameter makes sense. Now what is going wrong is that OpenJUMP is saving the original connection URL into the project file as server-urlhttp://localhost:8080/geoserver/ows?request=getcapabilities; amp;/server-url If the project is reopened OpenJUMP does not ask again if the GetMap url from the GetCapabilities should be used. I don't know what to do. The most proper solution might be to save both the GetCapabilities url and GetMap url into the project file. With deegree plugin which supports GetFeatureInfo even GetFeatureInfo url might be saved. A light weight solution is to write some Known issue thing that informs users that project file keeps only the GetCapabilities url and there will be problems with WMS services which are using a different base url for GetMaps. -Jukka Rahkonen- -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] how to refresh a layer in run time
Hi there,
I would like to refresh a layer after changing attribute of each feature in the
layer based on an event table. The event table records attribute assigned to
each feature at specified stage. Following is the schema of the event table:
Event(
StageID int, // StageID defines sequence of the event
Feature01 int, // value to be assigned to feature 01
Feature02 int, // value to be assigned to feature 02
...
Feature10 int)
Based on the StageID sequence, values for each feature would be retrieved and
updated to corresponding feature. Finally, update value would be visualized by
unique colortheming. However, it seems the layer refreshing can only be
effective outside the ResultSet loop of the event table.
The following is the program codes:
Inside execute(PlugInContext context)
// get a layer
lyr = context.getLayerManager().getLayer(postgis);
//create a Resultset RS
ResultSet RS stat.executeQuery(select * from Event);
while (RS.next())
{
updatePostgisLayer(lyr, RS);//This function updates feature in the layer
}
layer refreshes after the looping all the resultset.
My question is how to refresh the layer once attribute values are updated for
each each row of the RecordSet, i.e. immediately after the updatePostgisLayer
function.
If I change the query to retrieve specify row (i.e. single row only), layer can
be refreshed. But it requires to activate it manually for each update.
I tried to add lyr.fireLayerChanged(LayerEventType.APPEARANCE_CHANGED);
or lyr.fireAppearanceChanged() after the updatePostgisLayer function but it
didn't work.
Anyone can help?
thanks,
Elton
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Update and refresh layer in run time
You might try: context.getLayerManager().fireFeaturesChanged( features, FeatureEventType.ATTRIBUTES_MODIFIED, layer); Also look into: context.getLayerManager().setFiringEvents(false); //before loop context.getLayerManager().setFiringEvents(true); //after loop Larry On Wed, Jun 30, 2010 at 10:21 PM, Elton Chan elton.c...@yahoo.com wrote: Hi Larry, Thank for your reply. I've tested that view panel can update automatically when attribute is updated. However, if I continue to update an attribute in a for loop, it seems it cannot refresh. I wonder if the auto update would be activated immediately after the setAttribute function, or after completion of the for loop or I need to add a later between each update. BTW, how can I fire the update event mannually. thanks, Elton -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] exploding GeometryCollections?
Hi Nils, If you mean an explode utility method you are correct - I don't think there is one. There is code in the ExplodeSelectedFeaturesPlugIn. Also, there is support for recursive parsing of GeometryCollections when using an EditTransaction. If you do add a utility function, it should probably go in org.openjump.core.geomutils. Larry On Thu, Jul 1, 2010 at 2:54 AM, Nils Kuhn nils.k...@bws-gmbh.de wrote: Hi, we don't have a standard-function to explode GeometryCollections to single Geometries in OpenJUMP, am I right? To have an option don't allow GeometryCollections in the main-menu-function ToolsAnalysisOne LayerUnion would be nice , too. Maybe I could try to implement something like that (I don't have as much time, so that could last a while...). Regards, Nils -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] how to refresh a layer in run time
Hi Nils,
I believe you might be running into problems updating because your loop is
blocking the GUI thread. You might try a LayerViewPanel.repaint() using
invokeAndWait().
Larry
On Thu, Jul 1, 2010 at 6:42 AM, Elton Chan elton.c...@yahoo.com wrote:
Hi there,
I would like to refresh a layer after changing attribute of each feature in
the layer based on an event table. The event table records attribute
assigned to each feature at specified stage. Following is the schema of the
event table:
Event(
StageID int, // StageID defines sequence of the event
Feature01 int, // value to be assigned to feature 01
Feature02 int, // value to be assigned to feature 02
...
Feature10 int)
Based on the StageID sequence, values for each feature would be retrieved
and updated to corresponding feature. Finally, update value would be
visualized by unique colortheming. However, it seems the layer refreshing
can only be effective outside the ResultSet loop of the event table.
The following is the program codes:
Inside execute(PlugInContext context)
// get a layer
lyr = context.getLayerManager().getLayer(postgis);
//create a Resultset RS
ResultSet RS stat.executeQuery(select * from Event);
while (RS.next())
{
updatePostgisLayer(lyr, RS);//This function updates feature in the layer
}
layer refreshes after the looping all the resultset.
My question is how to refresh the layer once attribute values are updated
for each each row of the RecordSet, i.e. immediately after the
updatePostgisLayer function.
If I change the query to retrieve specify row (i.e. single row only), layer
can be refreshed. But it requires to activate it manually for each update.
I tried to add lyr.fireLayerChanged(LayerEventType.APPEARANCE_CHANGED);
or lyr.fireAppearanceChanged() after the updatePostgisLayer function but it
didn't work.
Anyone can help?
thanks,
Elton
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] how to refresh a layer in run time
Sorry, Elton, not NIls. I answered so many questions that I got confused
about who I was answering. :-)
On Thu, Jul 1, 2010 at 8:24 AM, Larry Becker becker.la...@gmail.com wrote:
Hi Nils,
I believe you might be running into problems updating because your loop
is blocking the GUI thread. You might try a LayerViewPanel.repaint() using
invokeAndWait().
Larry
On Thu, Jul 1, 2010 at 6:42 AM, Elton Chan elton.c...@yahoo.com wrote:
Hi there,
I would like to refresh a layer after changing attribute of each feature
in the layer based on an event table. The event table records attribute
assigned to each feature at specified stage. Following is the schema of the
event table:
Event(
StageID int, // StageID defines sequence of the event
Feature01 int, // value to be assigned to feature 01
Feature02 int, // value to be assigned to feature 02
...
Feature10 int)
Based on the StageID sequence, values for each feature would be retrieved
and updated to corresponding feature. Finally, update value would be
visualized by unique colortheming. However, it seems the layer refreshing
can only be effective outside the ResultSet loop of the event table.
The following is the program codes:
Inside execute(PlugInContext context)
// get a layer
lyr = context.getLayerManager().getLayer(postgis);
//create a Resultset RS
ResultSet RS stat.executeQuery(select * from Event);
while (RS.next())
{
updatePostgisLayer(lyr, RS);//This function updates feature in the layer
}
layer refreshes after the looping all the resultset.
My question is how to refresh the layer once attribute values are updated
for each each row of the RecordSet, i.e. immediately after the
updatePostgisLayer function.
If I change the query to retrieve specify row (i.e. single row only),
layer can be refreshed. But it requires to activate it manually for each
update.
I tried to add lyr.fireLayerChanged(LayerEventType.APPEARANCE_CHANGED);
or lyr.fireAppearanceChanged() after the updatePostgisLayer function but
it didn't work.
Anyone can help?
thanks,
Elton
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] SextanteRasterLayer, pixel values and visualization
Larry and Steven, sorry for bothering you, I know you're both busy... I had a deeper look at the RasterImageLayer class. Apparently there is a scaling function there (as Stefan pointed out), but for what I can understand, the image is read, then rescaled, then added to a Layerable. This means that the Layerable stores the already scaled cell values and, if the actual cell values are needed, the image needs to be reloaded. I don't see how this model can be tweaked to have on one side the cell values stored in memory and on the other a Layerable that can be rendered properly. What do you reckon? Please tell me I'm wrong. Thanks Alberto On 29/06/2010 16:32, Larry Becker wrote: Hi Alberto, I did take a look at the render architecture to see how it might be done, but unfortunately I don't have a lot of time right now to help with this effort so any advice I have is only a guess, but I think it might have to happen in the image layer's paint method. Larry On Tue, Jun 29, 2010 at 2:01 AM, Alberto De Luca i...@geomaticaeambiente.it mailto:i...@geomaticaeambiente.it wrote: Stefan and Larry, thank you for your help. Unfortunately I'm not an expert either, so I'm really not sure about what to do. I kind of like Larry's approach (but I need to think about it to see if I can work something out of it). I'll have a deeper look at the pirol classes too... Alberto On 28/06/2010 21:49, Stefan Steiniger wrote: actually.. wasn't there a scaling function somewehere in the pirol classes? so the place to correct is in those? Alberto De Luca schrieb: Dear OJ developers, I was working on the Sextante classes, trying to enhance raster support and visualization capabilities. Having a powerful raster management is important so we can port to OJ all the raster plugins we developed for the OJ-derived AdB-ToolBox (we exchanged some emails on the topic a while ago). So, as a first attempt, I tried to add ESRI FLT raster support, adding some lines of code to the RasterImageLayer class. I am here facing a dilemma though. The loadImage method returns a planarimage, which is then displayed on the screen. If I read the FLT file into a TiledImage whose SampleModel is DataBuffer.TYPE_FLOAT (to match the data model of the FLT file) and return it to be displayed, OJ loads it ok, but the raster displayed is completely blank. I know it's there because I can export its envelope and I can read cell values (using the OpenJUMPSextanteRasterLayer class), values that exactly match the values stored in the FLT file. If after creating the TiledImage I rescale it into a 0-255 range PlanarImage, I can display it ok (as a grayscale for example) but then when I read the cell values from the raster layer, they're clearly different from the original FLT values. My question is: is there a way to have a correct visualization while maintaining access to the actual cell values? In www.lac.inpe.br/JIPCookbook/2200-display-surrogate.jsp http://www.lac.inpe.br/JIPCookbook/2200-display-surrogate.jsp http://www.lac.inpe.br/JIPCookbook/2200-display-surrogate.jsp they suggest the use of the javax.media.jai.iterator.RandomIter class to access cell values after the image has been rescaled. Would this be appropriate in OJ? In the attached GridFloat.java you can find the code used to read the FLT grid (see the readGrid and the getPlanarImage methods). Also attached you can find my modified RasterImageLayer class (see in particular the loadImage method). Please consider I'm not a good programmer, so I might just be on a completely wrong track... Thanks Alberto -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first http://sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ 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 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first http://sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
Re: [JPP-Devel] Exposing JUMP as an RMI service?
Hi Martin, I'm still thinking about your RMI idea. In SkyJUMP, there is a communications module that allows other programs to control it remotely. It doesn't use RMI, but it could be ported to OJ and changed to do so. It includes two bidirectional channels for command and data. The protocol is XML and the module allows arbitrary execution of plugins. An example is: ?xml version=1.0 encoding=UTF-8? command-data commandSendDatasetPlugIn/command parameters properties mapping key class=java.lang.Stringinput-filename/key value class=java.lang.StringC:\JUMP\tmp\test.jml/value /mapping /properties /parameters /command-data This example causes the current selection to be written to the designated file. Just thought I would keep the ball rolling on this idea. regards, Larry On Thu, Jun 3, 2010 at 2:39 PM, Martin Davis mbda...@refractions.netwrote: It occurred to me recently that it might be useful to have a spatial viewer acting as an RMI service for out-of-process or remote clients. A possible use case would be as a spatial logger - a client process could log spatial data generated during the course of execution which would be immediately viewable in the spatial viewer. The neat thing is that this would work during a debug session, so the developer could get a good view of data being processed during the run. For those not familiar with it, RMI makes it almost trivially easy to expose a service endpoint and communicate with it from other Java processes. It would be fairly simple to expose a service that allowed clients to create layers, add features to layers, etc. Really the service could expose almost anything that can be manipulated in JUMP). It would thus enable a sort of remote plugin facility. I also envision a very simple client API that hid the (fairly trivial) aspects of connecting to an RMI service. This may be a solution in search of a problem - but RMI is so powerful it seems like there must be some applications for it. Has anyone played around with exposing an RMI service from JUMP? -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] WMS layer problems
Hi, I repeated my tests with Geoserver 2.0.2, this time with the latest OpenJUMP nightly build. WMS layers are working fine. The URL-encoding problems I had were with the OJ 1.3 version (April 19, 2009). -Jukka Rahkonen- -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] exploding GeometryCollections?
Hi, When I have to achieve such a think I do it that way : - Union - Make the new layer editable - Edition Selection Select by geometry type... - choose MultiPolygon, GeometryColletion types - right click on the layer view - Explode selected features Is that what you want to get ? OK, I agree an option in the union (and union by attributes) plugins or a generic function available in Tools Edit geometry Geometry functions would be nice. Michaël Larry Becker a écrit : Hi Nils, If you mean an explode utility method you are correct - I don't think there is one. There is code in the ExplodeSelectedFeaturesPlugIn. Also, there is support for recursive parsing of GeometryCollections when using an EditTransaction. If you do add a utility function, it should probably go in org.openjump.core.geomutils. Larry On Thu, Jul 1, 2010 at 2:54 AM, Nils Kuhn nils.k...@bws-gmbh.de mailto:nils.k...@bws-gmbh.de wrote: Hi, we don't have a standard-function to explode GeometryCollections to single Geometries in OpenJUMP, am I right? To have an option don't allow GeometryCollections in the main-menu-function ToolsAnalysisOne LayerUnion would be nice , too. Maybe I could try to implement something like that (I don't have as much time, so that could last a while...). Regards, Nils -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first http://sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ 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 -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
