Thanks for the survey,
Hopefully, the problem is fixed (r3508).
I now pass the InputStream (byte stream) to the DomParser instead of an
InputStreamReader.
This way, I let the DomParser read the appropriate encoding and parse
the xml file correctly.
At least I hope so (have tested on Uwe's url an
Hi,
Some quick tests:
- GeoWebCache 1.4 in WMS mode has "charset=UTF-8" in the headers and
"encoding="UTF-8"" in XML.
- GeoServer 2.2.x does not have charser in the headers but does have encoding
in XML.
- ArcGIS Server x.x does not have charser in the headers but does have encoding
in XML.
- M
Michaël Michaud wrote:
> In the adress given by Uwe, for example, last layer name is not parsed
> correctly, but I could not find a way
> to get a valid answer in the browser if I pass Uwe's url +
> "SERVICE=WMS&VERSION=1.1.1&REQUEST=GetCapabilities"
I see that you have not yet worked a lot with
On 15.04.2013 22:13, edgar.sol...@web.de wrote:
> On 15.04.2013 21:53, Michaël Michaud wrote:
> servers usually announce the character set they answer with.. do you
> check the response headers?
there is a nifty firefox plugin called "live http headers" btw.
Not sure if t
On 15.04.2013 21:53, Michaël Michaud wrote:
servers usually announce the character set they answer with.. do you check
the response headers?
>>> there is a nifty firefox plugin called "live http headers" btw.
>>> Not sure if the character set I need is in the http response head
Hi,
>>> servers usually announce the character set they answer with.. do you check
>>> the response headers?
>>> there is a nifty firefox plugin called "live http headers" btw.
>>> Not sure if the character set I need is in the http response header or
>>> in the xml declaration.
>>> I would have s
edgar soldin wrote:
>>>
>> servers usually announce the character set they answer with.. do you check
>> the response headers?
>> there is a nifty firefox plugin called "live http headers" btw.
>> Not sure if the character set I need is in the http response header or
>> in the xml declaration.
On 15.04.2013 20:23, Michaël Michaud wrote:
> Hi,
>>
>>> Hi,
I made some cross checks with combinations of
- WMS 1.1.1 or WMS 1.3.0
- Mapserver 6.0 or Geoserver 2.3.0
- EPSG:4326 (native latitude-longitude), EPSG:2393 (native
Nort
Hi,
>
>> Hi,
>>> I made some cross checks with combinations of
>>>
>>> - WMS 1.1.1 or WMS 1.3.0
>>>
>>> - Mapserver 6.0 or Geoserver 2.3.0
>>>
>>> - EPSG:4326 (native latitude-longitude), EPSG:2393 (native
>>> Northing-Easting), EPSG:3047 (native Northing-Easting) and E
On 15.04.2013 19:57, Michaël Michaud wrote:
> Hi,
>>
>> I made some cross checks with combinations of
>>
>> - WMS 1.1.1 or WMS 1.3.0
>>
>> - Mapserver 6.0 or Geoserver 2.3.0
>>
>> - EPSG:4326 (native latitude-longitude), EPSG:2393 (native
>> Northing-Easting), EPSG:3047
Hi,
I made some cross checks with combinations of
-WMS 1.1.1 or WMS 1.3.0
-Mapserver 6.0 or Geoserver 2.3.0
-EPSG:4326 (native latitude-longitude), EPSG:2393 (native
Northing-Easting), EPSG:3047 (native Northing-Easting) and EPSG:3067
(native Easting-Northing)
I did not find any malfunct
Hi,
I made some cross checks with combinations of
- WMS 1.1.1 or WMS 1.3.0
- Mapserver 6.0 or Geoserver 2.3.0
- EPSG:4326 (native latitude-longitude), EPSG:2393 (native
Northing-Easting), EPSG:3047 (native Northing-Easting) and EPSG:3067 (native
Easting-Northing)
Hi,
I have committed the modifications about WMS 1.3.0 (r3505)
Thanks to Jukka's server, I could test and compare WMS 1.1.1 / WMS 1.3.0
Tell me if lat/lon problems are fixed with all your use cases.
Michaël
Hi,
Thanks for the tests.
I still not master the lat/lon lon/lat problem, but with th
Hi,
Thanks for the tests.
I still not master the lat/lon lon/lat problem, but with the help of Jukka,
it should not be a problem to fix it...
Michaël
Hi,
Reason is simple, Lon-Lat is not turned into Lat-Lon in BBOX. But
Michaël has been doing some other not totally correct changes which
ar
Hi,
Reason is simple, Lon-Lat is not turned into Lat-Lon in BBOX. But Michaël has
been doing some other not totally correct changes which are causing troubles
too. But everything is correctable.
-Jukka-
Giuseppe Aruta wrote:
Hi Michael and Jukka
I tried with lat/lon server and I get no displa
Hi Michael and Jukka
I tried with lat/lon server and I get no display
Peppe
2013/4/10 Rahkonen Jukka
> Hi,
>
> May I aski f you have even tried to handle the BBOX axis order, and if
> yes, in which way? WFS 1.3.0 does not work well with Lat-Lon and
> Northing-Easting systems now.
>
> -Jukka-
>
Hi,
May I aski f you have even tried to handle the BBOX axis order, and if yes, in
which way? WFS 1.3.0 does not work well with Lat-Lon and Northing-Easting
systems now.
-Jukka-
Michaël Michaud wrote:
>
> Hi Jukka, WMS users,
>
> I added WMS 1.3.0 support but did not commit yet.
> code is ava
Hi,
WMS 1.3.0 works for me with EPSG:3067 which is Easting-Northing system.
However, there seems to be something odd with the reversed axis order in
systems like EPSG:4326 and EPSG:2393. I will collect some log info later
today. I did not see a regression with WMS 1.1.1, it is just that WMS 1
Hi Jukka, WMS users,
I added WMS 1.3.0 support but did not commit yet.
code is available here :
http://geo.michaelm.free.fr/OpenJUMP/
If it can be tested today to check I did not introduce a severe
regression, I can commit the code this evening.
Note : Beside 1.3.0, I've made a few changes to bou
19 matches
Mail list logo
