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-
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
Andreas Schmitz schrieb:
> Matthias Scholz wrote:
>
> Hi,
>
>
> I checked that WMS layer name is stored OK in the OJ project file
> sf:archsites
> Let's hope that question is only about url-encoding error.
>
>
I discussed with a Geoserver developer and
Matthias Scholz wrote:
Hi,
> >>> I checked that WMS layer name is stored OK in the OJ project file
> >>> sf:archsites
> >>> 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,
Rahkonen Jukka schrieb:
> Andreas Schmitz wrote:
>
>
>> Rahkonen Jukka wrote:
>>
>> Hi,
>>
>>
>>> I checked that WMS layer name is stored OK in the OJ project file
>>> sf:archsites
>>> Let's hope that question is only about url-encoding error.
>>>
>> I discussed with a Geoserver d
Rahkonen Jukka wrote:
Hi,
> > > I checked that WMS layer name is stored OK in the OJ project file
> > > sf:archsites
> > > 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 una
Andreas Schmitz wrote:
> Rahkonen Jukka wrote:
>
> Hi,
>
> > I checked that WMS layer name is stored OK in the OJ project file
> > sf:archsites
> > 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 c
Matthias Scholz wrote:
Hi,
> I checked that WMS layer name is stored OK in the OJ project file
> sf:archsites
> 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 le
Hi!
> Matthias Scholz wrote:
>
> Hi,
>
>
I checked that WMS layer name is stored OK in the OJ project file
sf:archsites
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,
Matthias Scholz wrote:
Hi,
> >> I checked that WMS layer name is stored OK in the OJ project file
> >> sf:archsites
> >> 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 una
Hi,
> Rahkonen Jukka wrote:
>
> Hi,
>
>
>> I checked that WMS layer name is stored OK in the OJ project file
>> sf:archsites
>> 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
Rahkonen Jukka wrote:
Hi,
> I checked that WMS layer name is stored OK in the OJ project file
> sf:archsites
> 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:archsi
gt; Lähettäjä: Rahkonen Jukka [mailto:jukka.rahko...@mmmtike.fi]
> Lähetetty: 30. kesäkuuta 2010 14:34
> Vastaanottaja: OpenJump develop and use
> Aihe: Re: [JPP-Devel] WMS layer problems
>
> Hi,
>
> I can't say anything about your save and reload problem
> because I
Hi,
I can't say anything about your save and reload problem because I can't
see Geoserver WMS layers at all!
I had a try with Geoserver v.2.0.2 and found something that looks like
an OpenJUMP bug. Geoserver is sending the layer names in a not so common
way so that they include also the namespace
Hi,
now I have testet with a new local GeoServer 2.0.2 installation(without
any changes) and OJ from SVN. I do not see a WMS layer after save and
reload a project. Please can anybody validate this?
With other WMS, such as http://wms.jpl.nasa.gov/wms.cgi you can save and
load projects without any
Hi Jukka!
> Hi,
>
> Slow loading is because Geoserver by default advertises all the possible SRSs
> it supports, it is couple of thousands I suppose. You can configure Geoserver
> to send just those projections you will need with GetCapabilities. It is
> controlled by the Geoserver admin utilit
Hi,
Slow loading is because Geoserver by default advertises all the possible SRSs
it supports, it is couple of thousands I suppose. You can configure Geoserver
to send just those projections you will need with GetCapabilities. It is
controlled by the Geoserver admin utility, in the WMS part "L
Hi Uwe!
> Hi Matthias,
>
> you can solve your second problem with
> a right mouseclick at the WMS-layer and then
> "Zoom to WMS layer" from the kontextmenu.
Sorry this solves my problem not :-(
Matthias
>
> Regards
>
> Uwe
>
>
> Uwe Dalluege
>
---
Hi Matthias,
you can solve your second problem with
a right mouseclick at the WMS-layer and then
"Zoom to WMS layer" from the kontextmenu.
Regards
Uwe
Uwe Dalluege
--
--
Dipl.-Ing. Uwe Dalluege
Labor fuer Geoinformatik und Geovisualisierung
Haf
19 matches
Mail list logo
