Hi,
As far as I can remember from reviewing the code, server side
simplification is enabled on a per-request basis. So it should be
possible to disable it when certain parameters (like $area required)
are met.
Matthias
___
Qgis-developer mailing li
Hi Marco,
I apologize,
my wrong.
I wrong to substitute the new master .
Now do it correctly and the crash is disappeared.
You patch is ok.
Andrea.
2014-06-22 17:50 GMT+02:00 Andrea Peri :
> I guess it is not a timeout question.
>
> To avoid the interference of the server web
> I test it runn
I guess it is not a timeout question.
To avoid the interference of the server web
I test it running into a shell (a cgi is always an executables)
I guess there is something else.
If I set the MAX_CACHE_LAYERS qgis server run and return the
getcapabilities (I ask it to test)
otherwise it crash.
Thanks for your answer Andreas,
I've one question though: If the data source is a Shapefile and
simplification is enabled, will the Field Calculator results be
dependent on the zoom? I expect they will be. Isn't that a big source
of potential confusion for the users?
And yes, I do understand that t
Hi Anita,
While I agree with you in general the difficulty is that if you do
serverside simplification QGIS does not even see the original geometry
anymore. So not easy to solve.
On the other hand you have several relatively easy workarounds. Either:
- disable simplification
- write the area to
Hi again Andre and Marco,
I've been investigating and the latest version of EPSG database (v8.4) already
incorporates a lot of changes compared to the datum_shift.csv from gdal.
>> tfm 1571 is a bug in the EPSG database. It should be "Amersfoort to
>> ETRS89 (1)", but somehow the source CRS
Just tried it with a project containing 111 layers here and the WMS
server works fine for me.
Could you check the apache error log if you are running into a server
timeout ( fcgid module kills process after some time ).
Marco
On 22.06.2014 14:22, Andrea Peri wrote:
No,
sorry , my wrong.
The
Hi,
I noticed this issue because I had a choropleth map showing population
density (calculated dynamically using "population"/$area). Some of the
polygons changed color when zooming. Simplify geometry, which is
active by default, caused minor changes to the value of $area when
zooming. I think $are
No,
sorry , my wrong.
The workaround MAX_CACHE_LAYERS still work.
A.
2014-06-22 14:01 GMT+02:00 Andrea Peri :
> Hi Marco, other information:
>
> The
> MAX_CACHE_LAYERS workarund
> Now seem do not work anymore.
>
>
> 2014-06-22 13:48 GMT+02:00 Andrea Peri :
>> Hi,
>> I tested it but don't seem w
Hi Marco, other information:
The
MAX_CACHE_LAYERS workarund
Now seem do not work anymore.
2014-06-22 13:48 GMT+02:00 Andrea Peri :
> Hi,
> I tested it but don't seem work.
>
> I'm using the master, is that ?
>
> A.
>
>
> 2014-06-22 13:04 GMT+02:00 Marco Hugentobler
> :
>> It should work now. Co
Hi,
I tested it but don't seem work.
I'm using the master, is that ?
A.
2014-06-22 13:04 GMT+02:00 Marco Hugentobler :
> It should work now. Could you test with the current git version? My test
> projects are not large enough.
>
> Regards,
> Marco
>
>
> On 22.06.2014 12:27, Andrea Peri wrote:
>
Hey everyone,
*Weekly Report 5*
*What was done this week?*
- Successfully added a basic unit test for checking whether the
algorithm is working by running it on the 'lines' data-set which is there
in the 'tests' folder of the processing toolbox and checking whether the
final feature
It should work now. Could you test with the current git version? My test
projects are not large enough.
Regards,
Marco
On 22.06.2014 12:27, Andrea Peri wrote:
you have right,
it is not a good solution. Too project depending and resource consuming.
thx for a better fixing
A.
2014-06-22 12:15
you have right,
it is not a good solution. Too project depending and resource consuming.
thx for a better fixing
A.
2014-06-22 12:15 GMT+02:00 Marco Hugentobler :
>> char* maxLayerEnv = getenv( "MAX_CACHE_LAYERS" )
>
>
> This is a short-time workaround for users.
>
> Regards,
> Marco
>
>
> On 22
char* maxLayerEnv = getenv( "MAX_CACHE_LAYERS" )
This is a short-time workaround for users.
Regards,
Marco
On 22.06.2014 12:12, Andrea Peri wrote:
Hi,
thx for response.
meanwhile,
I notice that the max allowed layers is exactly 101.
This mean (knowing C/C++) an array of 100 elements.
Search
Hi,
thx for response.
meanwhile,
I notice that the max allowed layers is exactly 101.
This mean (knowing C/C++) an array of 100 elements.
Searching for this particular value,
i find in the file "mapserver/qgsmslayercache.cpp"
is defined
mDefaultMaxLayers = 100;
if not defined the environ
It is a problem with the layer cache. Will provide a fix for that soon.
Regards,
Marco
On 22.06.2014 11:49, Andrea Peri wrote:
Hi,
I confirm.
There is a layer limit in QGIS-Server
I do a huge test removing one by one all the layers from my project.
And after the removing of every single laye
Hi,
I confirm.
There is a layer limit in QGIS-Server
I do a huge test removing one by one all the layers from my project.
And after the removing of every single layer I retest the working.
Aftr a while of time. I reach the limit.
And the project begin to run.
I do other test to exclude that w
Hi
On Fri, Jun 20, 2014 at 6:55 PM, Jürgen E. wrote:
>
> Please keep on testing for the coming week as I going to postpone until next
> friday.
Thanks for that!
> Maybe we should extent the testing phase to six weeks and use only 10 weeks
> for
> development for 2.6 (or 10+5 or 9+6 weeks, as w
19 matches
Mail list logo