It is not a bug really, just a suggestion.
Most of GIS applications can display statistic of shapefile attribute data. In many cases it is useful to know the average value of the DBF filed column, most popular value/range etc…
This option is particular useful when we apply different colors to the shapes and if we don’t use linear color breaks.
It is not really difficult to add a code to an application, but if the attribute table is huge, let say there are about 10 000 records (shapes) in the table, then NET application needs a time to calculate values.
I suppose it would be more efficient to move this code to C++ app, in that case we would have embedded functionality and much faster implementation comparing with managed NET language.
This is a code which I use in my application (see below) and it allows to calculate following useful values:
1. Most popular value “Most Common Value”
2. Average value
3. Maximum value
4. Minimum value
5. Number of existing values in the dbf column
The question is: would it be useful to include this functionality to MapWinGis.Field class?
So we could use something like MapWinGis.Field.GetStat(StatEnum.MostPopular); MapWinGis.Field.GetStat(StatEnum. Average) or something similar ?
Comments: ** Comment from web user: sleschinski **
Most of GIS applications can display statistic of shapefile attribute data. In many cases it is useful to know the average value of the DBF filed column, most popular value/range etc…
This option is particular useful when we apply different colors to the shapes and if we don’t use linear color breaks.
It is not really difficult to add a code to an application, but if the attribute table is huge, let say there are about 10 000 records (shapes) in the table, then NET application needs a time to calculate values.
I suppose it would be more efficient to move this code to C++ app, in that case we would have embedded functionality and much faster implementation comparing with managed NET language.
This is a code which I use in my application (see below) and it allows to calculate following useful values:
1. Most popular value “Most Common Value”
2. Average value
3. Maximum value
4. Minimum value
5. Number of existing values in the dbf column
The question is: would it be useful to include this functionality to MapWinGis.Field class?
So we could use something like MapWinGis.Field.GetStat(StatEnum.MostPopular); MapWinGis.Field.GetStat(StatEnum. Average) or something similar ?
Comments: ** Comment from web user: sleschinski **
Reviewing it before 4.9.3 beta release: mode and unique values count can still be added. Perhaps should be done along with decoupling of existing methods (min, max std) from table class as we also need them for OGR layers. But there are too many other issues right now, so once again I'm leaving it for better times.