[Gvsig_english] determining length of lines in a polyline layer

[Sal Garfi]

Dear Juan,

Yes, you are right to correct me. The gvSIG distance is ca 5% less than the Google Earth distance, so I'm attaching the the original kml file and the shape file which includes two 'length' fields. The first length field was created using Sextante, while the 'Length 2' field was created by the length determination facility in gvSIG.

You'll also notice that the kml file shows a very small part of the infamous complex of berms that have been created by Morocco in Western Sahara. I've already digitised, in Google Earth, the entirety of the berms and I now want to calculate their lengths and input them into gvSIG for further analysis. This is part of my PhD research on the war in Western Sahara.

Best wishes,
Sal
  ----- Original Message ----- 
  From: Juan Lucas Dominguez Rubio 
  To: Users and Developers mailing list ; Users and Developers mailing list 
  Sent: Monday, November 08, 2010 12:18 PM
  Subject: Re: [Gvsig_english] determining length of lines in a polyline layer


  Hello, Sal.

  "95% less than" means "20 times less than", actually.

  Do you mean "5% less than"? (you expected 100 and got 95)

  I have made a test with the attached shapefile and:

  gvSIG says it's length is 50.12 m 
  Google Earth says it's length is 50.06 m

  The difference is about 0.12 %.

  Can you send your example?


  Regards,

  Juan Lucas Domínguez Rubio
  ---
  Prodevelop SL, Valencia (España)
  Tlf.: 96.351.06.12 -- Fax: 96.351.09.68
  http://www.prodevelop.es
  ---


------------------------------------------------------------------------------
  De: gvsig_internacional-bounces at listserv.gva.es en nombre de Sal Garfi
  Enviado el: lun 08/11/2010 12:31
  Para: Users and Developers mailing list
  Asunto: [Gvsig_english] determining length of lines in a polyline layer


  Dear All,

  I have recently digitised linear features in Google earth that I have converted from kml format to shape files. I wanted to tabulate the total distances of these lines in gvSIG so I used the available facility in vector line tools in Sextante. However, the distances were on average 95% less than the distances noted in the features' properties in Google Earth. I then used gvSig's own facility for determining lengths of polylines and these were the same as those determined in Sextante. I'm working in WGS84 - so what could be causing the differences? And which system is correct, Google Earth or gvSIG? 

  All the best,
  Sal Garfi


------------------------------------------------------------------------------


  _______________________________________________
  Gvsig_internacional mailing list
  Gvsig_internacional at listserv.gva.es
  http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserv.gva.es/pipermail/gvsig_internacional/attachments/20101108/bec1ea0d/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dakhla lengths test 2.shp
Type: application/octet-stream
Size: 6908 bytes
Desc: not available
Url : http://listserv.gva.es/pipermail/gvsig_internacional/attachments/20101108/bec1ea0d/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Dakhla.kml
Type: application/vnd.google-earth.kml+xml
Size: 18191 bytes
Desc: not available
Url : http://listserv.gva.es/pipermail/gvsig_internacional/attachments/20101108/bec1ea0d/attachment.kml 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dakhla lengths test 2.shx
Type: application/octet-stream
Size: 124 bytes
Desc: not available
Url : http://listserv.gva.es/pipermail/gvsig_internacional/attachments/20101108/bec1ea0d/attachment-0001.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dakhla lengths test 2.dbf
Type: application/octet-stream
Size: 2125 bytes
Desc: not available
Url : http://listserv.gva.es/pipermail/gvsig_internacional/attachments/20101108/bec1ea0d/attachment-0002.obj