text: 
  Dear HPGL developers
  As I asked in subject line it is clear that how can I use HPGL with
  c++. I am satisfied with HPGL performance.
  Now I need to bring the power of HPGL to web using Wt a C++ web toolkit. Is
  it possible?
  --
  Thanks && Regards
  Mohammed Rashad K.M
  +919642945690
  Hi,
  I am trying to interpolate weather data (temperature) to create contours.
  I tried to use ordinary kriging of HPGL. But the results are not
  satisfactory.
  Details of my codes is as follows :
  1. stn_lat.txt, stn_lon.txt, stn_temp.txt : consists of latitudes,
  longitudes and temperature value respectively. [Just for testing purpose i
  kept it separately.]
  2. one.txt consist of 1's and 0's for the masked value.
  3. The latitude,longitude values are basically non-gridded data. Latitude
  /longitudes are not equally-spaced. I have Temperature value for all. But
  just for testing purpose i replaced some values by 99. and corresponding
  mask in one.txt is made 0 instead of 1.
  4. the temperature values obtained by doing ordinary kriging is not matching
  the original values.What can be the possible reason??
  5. If i want to get temperature values for a grid. how do I do this??
  Please help.
  My codes are as follows:
  *import geo_bsd
  from geo_bsd import *
  grid = SugarboxGrid(3,1,659)
  cov1 = CovarianceModel(type=0, ranges = (5, 5, 5), sill = 1)
  import numpy as np
  import array
  li=[]
  inp = open ("input/stn_lat.txt","r")
  #read line into array
  for line in inp.readlines():
  for i in line.split():
  li.append(float(i))
  li2=[]
  inp2 = open ("input/stn_lon.txt","r")
  #read line into array
  for line in inp2.readlines():
  for i in line.split():
  li2.append(float(i))
  li4=[]
  inp4 = open ("input/stn_temp.txt","r")
  #read line into array
  for line in inp4.readlines():
  for i in line.split():
  li4.append(float(i))
  li3=[]
  inp3 = open ("input/one.txt","r")
  #read line into array
  for line in inp3.readlines():
  for i in line.split():
  li3.append(float(i))
  array_prop=np.array(([li2],[li],[li4]),dtype='float32')
  array_mask=np.array(([li2],[li],[li3]),dtype='float32')
  # define grid.
  cont_property = ContProperty(array_prop, array_mask)
  prop_result = ordinary_kriging(cont_property, grid, radiuses = (20, 20, 1),
  max_neighbours = 12, cov_model = cov1)
  write_property(prop_result, "R_OK_with.INC", "OK_RESULT", -99)
  *Thanks and Regards,
  sonal.
  Solved. This issue was the C++ Redistributable package.
  Here is the update link for XP SP3, Vista, 7, etc.
  -Aman
  On Mon, Jan 10, 2011 at 1:54 PM, Aman Thakral <aman.thakral@...>wrote:
  >
  Hello Hannes!
  First of all, thanks for the letter :) It's always nice to see feedback and
  questions about our software.
  Now, about Ordinary Kriging.
  Actually, it is known thing about Ordinary Kriging and we saw it on
  GSLIB/SGEMS tests as well.
  I think ArcGis adjust some parameters to make it more 'smooth', that's
  because the picture is nice.
  The reason for this behavior is the mean calculation process in OK.
  While Simple Kriging considered mean to be constant at all points, OK
  assumes that mean is varying from point to point (and the neighbors points
  around the interpolated one is used for mean calculation). So, if you have
  areas which has different mean values (calculated from initial data points
  in some radius), you will see this artifacts on the borders of the areas.
  Besides that, there are two strange things about your covariance model:
  1) Sill is too high, in most cases it is laying from 0 to 1 and it
  represents variance of the data. Why 3500? Is it from variogram you
  calculated before?
  2) Same thing about nugget.
  cov_krig = CovarianceModel(type=1, ranges=(150,150,1), sill=3500,
  nugget=600)
  try to use Sill = 1 and nugget = 0, if it helps, maybe you should consider
  more appropriate variogram model for your data.
  Also, you can use Simple Kriging with mean value calculated by the whole
  area.
  Another approach for varying mean data interpolation is to subtract mean
  trend from initial data after performing Kriging, and add it to the result
  later.
  Feel free to ask more questions and good luck!
  Arthur M.
  On Tue, Apr 13, 2010 at 10:08 AM, <
  hpgl-support-eng-request@...> wrote:
  > Send Hpgl-support-eng mailing list submissions to
  > hpgl-support-eng@...
  >
  > To subscribe or unsubscribe via the World Wide Web, visit
  >
  > or, via email, send a message with subject or body 'help' to
  > hpgl-support-eng-request@...
  >
  > You can reach the person managing the list at
  > hpgl-support-eng-owner@...
  >
  > When replying, please edit your Subject line so it is more specific
  > than "Re: Contents of Hpgl-support-eng digest..."
  >
  >
  > Today's Topics:
  >
  > 1. Errors in ordinary kriging ? (hannes)
  >
  >
  > ----------------------------------------------------------------------
  >
  > Message: 1
  > Date: Sun, 11 Apr 2010 16:03:19 +0200
  > From: hannes <hannes@...>
  > Subject: [Hpgl-support-eng] Errors in ordinary kriging ?
  > To: hpgl-support-eng@...
  > Message-ID: <1270994599.4762.61.camel@...>
  > Content-Type: text/plain;
  >)
  >
  > -------------- next part --------------
  > A non-text attachment was scrubbed...
  > Name: blankupload.tif.tar.gz
  > Type: application/x-compressed-tar
  > Size: 105576 bytes
  > Desc: not available
  > -------------- next part --------------
  > A non-text attachment was scrubbed...
  > Name: krigingfunny.png
  > Type: image/png
  > Size: 329471 bytes
  > Desc: not available
  >
  > ------------------------------
  >
  >
  > ------------------------------------------------------------------------------
  > Download Intel® Parallel Studio Eval
  > Try the new software tools for yourself. Speed compiling, find bugs
  > proactively, and fine-tune applications for parallel performance.
  > See why Intel Parallel Studio got high marks during beta.
  >
  >
  > ------------------------------
  >
  > _______________________________________________
  > Hpgl-support-eng mailing list
  > Hpgl-support-eng@...
  >
  >
  >
  > End of Hpgl-support-eng Digest, Vol 1, Issue 1
  > **********************************************
  >)