Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Printing from a local tiled cache #39

Open
tchaddad opened this issue Apr 10, 2014 · 4 comments
Open

Printing from a local tiled cache #39

tchaddad opened this issue Apr 10, 2014 · 4 comments
Milestone

Comments

@tchaddad
Copy link
Contributor

Recently started thinking about this issue again: http://osgeo-org.1560.x6.nabble.com/Geomoose-users-Questions-about-printing-from-a-local-tiled-cache-td5080288.html.

It would be nice to be able to configure use of a local cache for fast viewing, and yet point to the source WMS for printing. I was thinking something like this would be how a mapbook entry could look (uses a real example cache and source wms):

 <map-source name="cz-poly@oca" type="xyz">
    <layer name="cz-poly@oca" status="on" />
    <url>http://www.coastalatlas.net/mapcache/gmaps/cz-poly/${z}/${x}/${y}.png</url>
    <param name="attribution" value="Oregon Coastal Management Program"/>
        <print-map-source name="cz-poly" type="wms" opacity="0.9">
            <url>http://www.coastalatlas.net/services/wms?</url>
            <layer name="cz-poly"/>
        </print-map-source>
</map-source>  

Just thought I would record it here as a future enhancement.

@tchaddad
Copy link
Contributor Author

A better title for this would be "Specifying Tile Layer fall-back WMS for printing purposes".

@tchaddad tchaddad added this to the 2.7.1 milestone Sep 13, 2014
@theduckylittle theduckylittle modified the milestones: 2.7.1, 2.8 Sep 13, 2014
@tchaddad
Copy link
Contributor Author

One work around to this problem is to run all WMS requests through MapCache. Doing this, MapCache will serve the tiles for viewing, but call the source WMS for printing.

A bit extreme, but it works.

@theduckylittle theduckylittle modified the milestones: Future, 2.8 Jul 10, 2015
@theduckylittle
Copy link
Member

Bumping this to future. :\ 2.8 has a lot of stuff in it already and we want to move to review.

@tchaddad
Copy link
Contributor Author

Understood!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants