search

itamair / geoxml3

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

Points moved in new egeoxml.js version #106

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Load kml
2. First and last point are moved in other coordenates.

What is the expected output? What do you see instead?
With an old version of egeoxml.js it's right, but with the last version that 
points are wrong. The KML file is identical using old or new version, but with 
new version the first and the last point are moved "sincronized" in another 
position. Virtually, you could move both of them together to the right position.

What version of the product are you using? On what operating system?
The last version of egeoxml.js (r123), over W7, with Firefox 35.0 or Chrome 
39.0.2171.95 m

Original issue reported on code.google.com by andyned...@gmail.com on 15 Jan 2015 at 12:41

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I've found the "error". I use <hotSpot x='125' y='225' xunits='pixels' 
yunits='pixels'/> to make the KML file. If I delete that tag, the points are 
right, but I don't know why with old version it works (I suppose that tag was 
ignored in old version).

Original comment by andyned...@gmail.com on 15 Jan 2015 at 1:33

GoogleCodeExporter commented 9 years ago 
egeoxml and geoxml3 are different libraries

Original comment by geocodezip on 15 Jan 2015 at 1:46