You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: katzlbt [Submitted to the original trac issue database at 12.35pm, Thursday, 3rd December 2009]
I have high resolution background ortho images and shape data that I can publish via a WMS Service or 256x256 tiles in Google Tiling System coordinates.
(1) I cannot figure out how to use the tiles, because I the background system coordinate system is not documented anywhere (or I cannot find it in http://wiki.openstreetmap.org/wiki/Potlatch/Primer).
(2) Would it be possible that the custom background field could be used to enter a WMS service URL?
Author: katzlbt [Added to the original trac issue at 9.11am, Friday, 4th December 2009]
So you say that my EPSG:4326 rendered ortho tiles are inaccurate when used as background for map making in potlatch? Is the expected inaccuracy >10m for central europe?
Why should you worry about the nonsperical aspect if the WMS Server eliminates that for you? Just use srs=EPSG:3785 (EPSG:900913) and the WMS service will supply sperical mercator image data, isn't it so?
Reporter: katzlbt
[Submitted to the original trac issue database at 12.35pm, Thursday, 3rd December 2009]
I have high resolution background ortho images and shape data that I can publish via a WMS Service or 256x256 tiles in Google Tiling System coordinates.
(1) I cannot figure out how to use the tiles, because I the background system coordinate system is not documented anywhere (or I cannot find it in http://wiki.openstreetmap.org/wiki/Potlatch/Primer).
(2) Would it be possible that the custom background field could be used to enter a WMS service URL?
Something like this (potlatch could append &width=256&height=256&BBOX=):
http://localhost:8080/geoserver/wms?service=WMS&version=1.1.0&request=GetMap&layers=cat:stanton&styles=&srs=EPSG:4326&
The text was updated successfully, but these errors were encountered: