[MapProxy] Extending/creating new client and source

G. Allegri giohappy at gmail.com
Wed Nov 6 08:39:52 PST 2013

Thanks Oliver,
I see, I have to define a SourceConfiguration subcalss and append it
to source_configuration_types.
One API is something internal with a custom tile indexing, which requires
some preprocessing on the base of the bbox we're requesting. I won't go
into the details, but I've seen that the I need to subclass tile source
The other API is the Google Maps Static API. Don't worry, we're licensed to
do that :)


2013/11/6 Oliver Tonnhofer <olt at omniscale.de>

> On 06.11.2013, at 16:46, G. Allegri wrote:
> > I'm new to MapProxy development, forgive me if I'm asking a trivial
> question.
> > I need to access a tailored map server API and the best way to achive
> this, AFAICS, is creating my own client and source type.
> > config.py loads and instantiate sources on the base of the config file
> parsing. Does this mean that putting my new classes inside mapproxy/client
> and mapproxy/source is enough?
> Yes, you need to implement your own client/source and load that one in the
> loader.py.
> Can you tell what API it is? The tile source should be able to handle most
> use-cases already.
> Regards,
> Oliver
> --
> Oliver Tonnhofer    | Omniscale GmbH & Co KG    | http://omniscale.com
> http://mapproxy.org | https://github.com/olt    | @oltonn

Giovanni Allegri
blog: http://blog.spaziogis.it
GEO+ geomatica in Italia http://bit.ly/GEOplus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20131106/bfc5ef9b/attachment.html>

More information about the MapProxy mailing list