search

anushani / atlasmapper

Automatically exported from code.google.com/p/atlasmapper
0 stars 0 forks source link

Manual update of cached Capabilities Documents #54

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When a data source has a lot of data layers 
(http://spatial.ala.org.au/geoserver is one such example) the WMS service works 
but the capabilities document request fails (or takes an excessive amount of 
time). 

We need to be able to update from these sources manually as automatic updating 
when trying to update a client just causes the client update to fail. In effect 
the cache time out needs to be able to be set to infinite.

In effect this enhancement allows the AtlasMapper to bind against only partly 
operating services.

Original issue reported on code.google.com by eric.law...@gmail.com on 28 Mar 2013 at 1:05

GoogleCodeExporter commented 9 years ago 
Currently the only way to deal with a service that can not produce the 
capabilities document when it cache times out is to remove it from the client.

Original comment by eric.law...@gmail.com on 28 Mar 2013 at 1:07

GoogleCodeExporter commented 9 years ago 
I will add a upload field to manually associate the cap doc to a data source, 
which will never automatically expire.

Original comment by lafond.g...@gmail.com on 23 Apr 2013 at 3:58

GoogleCodeExporter commented 9 years ago 
I added / fixed support for the "file" protocol instead. Since this is not a 
common case, it would be too much works to add a file field just for that. I 
also added a note in the tooltip with an example on how to use the "file" 
protocol: file:///somepath/file.xml

Original comment by lafond.g...@gmail.com on 28 May 2013 at 5:05