[MapProxy] Improved granularity for seed refresh
moritz.kirmse at camptocamp.com
Tue Jun 1 01:05:27 PDT 2021
we would like to use the feature in development above in a production
Therefore it would be nice if the feature could make it into the next
release of mapproxy once it is finished and tested.
Is there already any release schedule or are there other features to be
released ? Would it be possible to be involved in the release planning ?
On Wed, May 19, 2021 at 12:10 PM Moritz Kirmse <moritz.kirmse at camptocamp.com>
> I started work on this topic.
> The basic functionality for refreshing existing tiles only is already
> implemented, but it cannot be configured.
> in the (draft) PR below, I chose to introduce a command-line parameter for
> mapproxy-seed, --skip-uncached
> This seems more logical to me than including this parameter in the
> configuration file (as I had initially imagined with the parameter
> existing_tiles_only: True)
> as for the second feature (keep_missing_files), everything already exists,
> it can be managed by the error handler in the mapproxy configuration with
> cache: False:
> response: '#ff0000'
> cache: False
> best regards,
> On Thu, May 6, 2021 at 5:11 PM Moritz Kirmse <moritz.kirmse at camptocamp.com>
>> I am starting to develop a new feature for Mapproxy which is needed to
>> get rid of some custom scripts, so that MapProxy can handle our whole tile
>> caching workflow by its own.
>> We would like to add the following two features to the mapproxy-seed
>> - restriction of reseeding to existing tiles only, once they have become
>> - conservation of old/stale tiles in case of missing replacement (source
>> not available, for ex. http error).
>> This might be two non-default options under the 'refresh_before' tree in
>> the seed.yaml file and look like in the example below:
>> weeks: 1
>> existing_tiles_only: True
>> keep_missing_files: True
>> I was about to create a Github issue for discussion on the topic, but it
>> said issues are reserved to bugs and the mailing list shall be used for
>> feature discussion.
>> So I will create a pull request and refine the feature there.
>> An existing PR will be useful for this feature, and I will be using it
>> for development:
>> https://github.com/mapproxy/mapproxy/pull/453 (Added max-repeat param
>> Do not hesitate to leave me any comments and suggestions, in case I
>> overlooked something.
>> Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MapProxy