[Geoserver-users] TMS tiles not aligned with WMS requests

GeoServer GeoServer User
1

Hi,

I have been writing integration tests for Mapfish-print. For each type of protocol I have written a simple GeoExt based html page that prints layers.

I use a default Geoserver.

For each test page I display tiger-ny with the desired format (for example WMTS) and tiger:tiger_roads using WMS. The idea is to ensure that the two layers line up in the html display and the output mapfish-print pdf file.

WMTS, OSM, WMS and Vector all work correctly (both layers correctly align)

However when I used TMS the two layers do not align. The TMS layer is half way around the world to the west.

The projection is EPSG:900913.

The desired center is:
-8236566.427097, 4976131.070529

but to get the TMS layers to display I needed to put the center at:

3570451.1286428, 9077780.2262548

Code is at:

https://github.com/mapfish/mapfish-print-e2e-test/tree/master/src/main/webapp/data/www/geoext-print-examples/Print-TMS-Layers-Using-TMS-Version-1.0.0

Any ideas what is going on here?

Jesse

2

On Tue, Jan 21, 2014 at 10:05 AM, Jesse Eichar
<jesse.eichar@anonymised.com>wrote:

Hi,

I have been writing integration tests for Mapfish-print. For each type of
protocol I have written a simple GeoExt based html page that prints layers.

I use a default Geoserver.

For each test page I display tiger-ny with the desired format (for example
WMTS) and tiger:tiger_roads using WMS. The idea is to ensure that the two
layers line up in the html display and the output mapfish-print pdf file.

WMTS, OSM, WMS and Vector all work correctly (both layers correctly align)

However when I used TMS the two layers do not align. The TMS layer is
half way around the world to the west.

The projection is EPSG:900913.

The desired center is:
-8236566.427097, 4976131.070529

but to get the TMS layers to display I needed to put the center at:

3570451.1286428, 9077780.2262548

Code is at:

https://github.com/mapfish/mapfish-print-e2e-test/tree/master/src/main/webapp/data/www/geoext-print-examples/Print-TMS-Layers-Using-TMS-Version-1.0.0

Any ideas what is going on here?

I have not checked, but did you consider that TMS uses a different
row/column counting direction and origin point, compared to WMTS?

Cheers
Andrea

--
== Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information ==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

3

I am just using openlayer which should take that into account. I am not convinced that it is a problem with Geoserver. It could be a OpenLayers issue, but if it does then Mapfish-print has exactly the same issue and since they are different independent implementation that seems a little unlikely.

I suspect there is a configuration option or something that is not documented to align them up.

I did try tileOrigin and that didn’t help either.

Jesse

···

On Tue, Jan 21, 2014 at 10:23 AM, Andrea Aime <andrea.aime@anonymised.com…1107…> wrote:

On Tue, Jan 21, 2014 at 10:05 AM, Jesse Eichar <jesse.eichar@anonymised.com> wrote:

Hi,

I have been writing integration tests for Mapfish-print. For each type of protocol I have written a simple GeoExt based html page that prints layers.

I use a default Geoserver.

For each test page I display tiger-ny with the desired format (for example WMTS) and tiger:tiger_roads using WMS. The idea is to ensure that the two layers line up in the html display and the output mapfish-print pdf file.

WMTS, OSM, WMS and Vector all work correctly (both layers correctly align)

However when I used TMS the two layers do not align. The TMS layer is half way around the world to the west.

The projection is EPSG:900913.

The desired center is:
-8236566.427097, 4976131.070529

but to get the TMS layers to display I needed to put the center at:

3570451.1286428, 9077780.2262548

Code is at:

https://github.com/mapfish/mapfish-print-e2e-test/tree/master/src/main/webapp/data/www/geoext-print-examples/Print-TMS-Layers-Using-TMS-Version-1.0.0

Any ideas what is going on here?

I have not checked, but did you consider that TMS uses a different row/column counting direction and origin point, compared to WMTS?

Cheers
Andrea

–

== Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information ==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

4

Hi Jesse,
It wasn’t half the world away, but I did have issues aligning my TMS in OpenLayers and particularly MFP (that seemed to be a MFP/GeoExt thing). I think I resolved it by being sure to include proj4js in my project (even though everything is in the same projection).

There was also http://code.google.com/p/geoext-viewer/issues/detail?id=191

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

···

Cheers,
Jonathan

On 21 January 2014 09:41, Jesse Eichar <jesse.eichar@anonymised.com> wrote:

I am just using openlayer which should take that into account. I am not convinced that it is a problem with Geoserver. It could be a OpenLayers issue, but if it does then Mapfish-print has exactly the same issue and since they are different independent implementation that seems a little unlikely.

I suspect there is a configuration option or something that is not documented to align them up.

I did try tileOrigin and that didn’t help either.

Jesse

CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

On Tue, Jan 21, 2014 at 10:23 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Tue, Jan 21, 2014 at 10:05 AM, Jesse Eichar <jesse.eichar@anonymised.com> wrote:

Hi,

I have been writing integration tests for Mapfish-print. For each type of protocol I have written a simple GeoExt based html page that prints layers.

I use a default Geoserver.

For each test page I display tiger-ny with the desired format (for example WMTS) and tiger:tiger_roads using WMS. The idea is to ensure that the two layers line up in the html display and the output mapfish-print pdf file.

WMTS, OSM, WMS and Vector all work correctly (both layers correctly align)

However when I used TMS the two layers do not align. The TMS layer is half way around the world to the west.

The projection is EPSG:900913.

The desired center is:
-8236566.427097, 4976131.070529

but to get the TMS layers to display I needed to put the center at:

3570451.1286428, 9077780.2262548

Code is at:

https://github.com/mapfish/mapfish-print-e2e-test/tree/master/src/main/webapp/data/www/geoext-print-examples/Print-TMS-Layers-Using-TMS-Version-1.0.0

Any ideas what is going on here?

I have not checked, but did you consider that TMS uses a different row/column counting direction and origin point, compared to WMTS?

Cheers
Andrea

–

== Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information ==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

5

I did encounter that thread during my researching this issue, I will look deeper at the thread when I have time but I didn’t immediately see anything that should help.

Thanks for the link.
Jesse

···

On Tue, Jan 21, 2014 at 1:31 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:

Hi Jesse,
It wasn’t half the world away, but I did have issues aligning my TMS in OpenLayers and particularly MFP (that seemed to be a MFP/GeoExt thing). I think I resolved it by being sure to include proj4js in my project (even though everything is in the same projection).

There was also http://code.google.com/p/geoext-viewer/issues/detail?id=191

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

Cheers,
Jonathan

On 21 January 2014 09:41, Jesse Eichar <jesse.eichar@anonymised.com> wrote:

I am just using openlayer which should take that into account. I am not convinced that it is a problem with Geoserver. It could be a OpenLayers issue, but if it does then Mapfish-print has exactly the same issue and since they are different independent implementation that seems a little unlikely.

I suspect there is a configuration option or something that is not documented to align them up.

I did try tileOrigin and that didn’t help either.

Jesse

CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

On Tue, Jan 21, 2014 at 10:23 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Tue, Jan 21, 2014 at 10:05 AM, Jesse Eichar <jesse.eichar@anonymised.com> wrote:

Hi,

I have been writing integration tests for Mapfish-print. For each type of protocol I have written a simple GeoExt based html page that prints layers.

I use a default Geoserver.

For each test page I display tiger-ny with the desired format (for example WMTS) and tiger:tiger_roads using WMS. The idea is to ensure that the two layers line up in the html display and the output mapfish-print pdf file.

WMTS, OSM, WMS and Vector all work correctly (both layers correctly align)

However when I used TMS the two layers do not align. The TMS layer is half way around the world to the west.

The projection is EPSG:900913.

The desired center is:
-8236566.427097, 4976131.070529

but to get the TMS layers to display I needed to put the center at:

3570451.1286428, 9077780.2262548

Code is at:

https://github.com/mapfish/mapfish-print-e2e-test/tree/master/src/main/webapp/data/www/geoext-print-examples/Print-TMS-Layers-Using-TMS-Version-1.0.0

Any ideas what is going on here?

I have not checked, but did you consider that TMS uses a different row/column counting direction and origin point, compared to WMTS?

Cheers
Andrea

–

== Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information ==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it