[Geoserver-users] MapFish extension & YAML layouts

GeoServer GeoServer User
1

Hi List,
Has anyone who’s been using the MapFish printing extension got any config.yaml files they’re willing to share with the community? These seem like the sort of thing that would benefit from being shared as they’re generally going to be fairly generic while they also seem to be a royal pain to create.

I’ve found the samples here, but that seems to be it.
https://trac.mapfish.org/trac/mapfish/browser/print/trunk/samples

Also, does anyone have any suggestions for how to actually debug them? The config files seem incredibly touchy about formatting etc and the exceptions I’m using to debug via GeoServer console are generic and not useful for this sort of thing (i.e.: 25 Jan 18:22:07 ERROR [org.mapfish.print.servlet.BaseMapServlet] - Error while generating PDF java.lang.IllegalStateException: unsupported protocol: ‘d’ ).

Cheers,
Jonathan

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.

2

http://sig.cmparks.net/cmp-ms-90x122.pngStephen V. Mather
GIS Manager
(216) 635-3243 (Work)
clevelandmetroparks.com

config.yaml (59.8 KB)

3

My application uses GeoServer 2.2.2 and SQL server 2008 for now. But the database might be upgraded to SQL server 2012.

I did some search. It seems that GeoServer extension supports SQL Server 2008 only and does not support 2012. Any knows?

Thanks!
Maggie

4

On Fri, Jan 25, 2013 at 8:08 PM, Meichun Li <pcloudy2005@anonymised.com> wrote:

My application uses GeoServer 2.2.2 and SQL server 2008 for now. But the database might be upgraded to SQL server 2012.

I did some search. It seems that GeoServer extension supports SQL Server 2008 only and does not support 2012. Any knows?

The development happened against SQL Server 2008, don’t think any developer tried it against
SQL Server 2012. It may work… or not.
Let us know how it goes

Cheers
Andre

–

==
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

Hi Steve,
Thanks for this, its quite a long file, and after about 30 minutes of bashing my head against what appears to be a Geoserver/Mapfish bug, I’ve finally got them to render. They’re very good.

I’d be interested to hear how you debugged them.
Cheers,
Jonathan

On 25 January 2013 18:51, Stephen V. Mather <svm@anonymised.com> wrote:

Here’s one.

Best,
Steve

Stephen V. Mather
GIS Manager
(216) 635-3243 (Work)
clevelandmetroparks.com

From: Jonathan Moules [jonathanmoules@anonymised.com]
Sent: Friday, January 25, 2013 1:30 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] MapFish extension & YAML layouts

Hi List,
Has anyone who’s been using the MapFish printing extension got any config.yaml files they’re willing to share with the community? These seem like the sort of thing that would benefit from being shared as they’re generally going to be fairly generic while they also seem to be a royal pain to create.

I’ve found the samples here, but that seems to be it.
https://trac.mapfish.org/trac/mapfish/browser/print/trunk/samples

Also, does anyone have any suggestions for how to actually debug them? The config files seem incredibly touchy about formatting etc and the exceptions I’m using to debug via GeoServer console are generic and not useful for this sort of thing (i.e.: 25 Jan 18:22:07 ERROR [org.mapfish.print.servlet.BaseMapServlet] - Error while generating PDF java.lang.IllegalStateException: unsupported protocol: ‘d’ ).

Cheers,
Jonathan

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.

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.

6

http://sig.cmparks.net/cmp-ms-90x122.pngStephen V. Mather
GIS Manager
(216) 635-3243 (Work)
clevelandmetroparks.com

7

Yep, that was the plan but YAML is hurting my brain. :slight_smile:
Cheers again,
Jonathan

On 28 January 2013 12:50, Stephen V. Mather <svm@anonymised.com> wrote:

Ah, in perfect fairness, GeoSolutions built the first version. Once that was in place, it was pretty simple to modify and go. Hopefully it will work similarly for you.

Best,
Steve

Stephen V. Mather
GIS Manager
(216) 635-3243 (Work)
clevelandmetroparks.com

From: Jonathan Moules [jonathanmoules@anonymised.com]
Sent: Monday, January 28, 2013 7:38 AM
To: Stephen V. Mather
Cc: geoserver-users@anonymised.come.net
Subject: Re: [Geoserver-users] MapFish extension & YAML layouts

Hi Steve,
Thanks for this, its quite a long file, and after about 30 minutes of bashing my head against what appears to be a Geoserver/Mapfish bug, I’ve finally got them to render. They’re very good.

I’d be interested to hear how you debugged them.
Cheers,
Jonathan

On 25 January 2013 18:51, Stephen V. Mather <svm@anonymised.com> wrote:

Here’s one.

Best,
Steve

Stephen V. Mather
GIS Manager
(216) 635-3243 (Work)
clevelandmetroparks.com

From: Jonathan Moules [jonathanmoules@anonymised.com]
Sent: Friday, January 25, 2013 1:30 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] MapFish extension & YAML layouts

Hi List,
Has anyone who’s been using the MapFish printing extension got any config.yaml files they’re willing to share with the community? These seem like the sort of thing that would benefit from being shared as they’re generally going to be fairly generic while they also seem to be a royal pain to create.

I’ve found the samples here, but that seems to be it.
https://trac.mapfish.org/trac/mapfish/browser/print/trunk/samples

Also, does anyone have any suggestions for how to actually debug them? The config files seem incredibly touchy about formatting etc and the exceptions I’m using to debug via GeoServer console are generic and not useful for this sort of thing (i.e.: 25 Jan 18:22:07 ERROR [org.mapfish.print.servlet.BaseMapServlet] - Error while generating PDF java.lang.IllegalStateException: unsupported protocol: ‘d’ ).

Cheers,
Jonathan

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.

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.

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.