-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KML : Issues with Line overlap behavior #251
Comments
Folow up issue: Scaling placemark size using the 'scale' tag in KML also doesn't render as expected, the placemark size appears unchanged. However, opening in the KML in GE shows correct behavior.
|
Scaling is not handled, and may be not, see #197 |
Ok, I will handle this another way. Could you let me know about my original question, if there is a possible solution from your end. (Pls say yes!) |
Hello brunob. Thank you very much for sharing this plugin with the community. I've been reviewing it especially for kml files but apparently what is done is a flea is on an image several times, place my kml in Google Earth and the result is different. I hope that soon you can solve the problem, for the moment it has been useful, thank you. |
@zaratedev you are welcome :) Can you describe your bug in a specific issue please ? |
Hi
I have a kml with multiple lines, with different colours. However, I'd like a particular line (green) to be always drawn on top of all the others, incase of line overlap.
Your plugin seems to draw the lines in random order. I've tried several things like giving the top line an altitude, using gx:drawOrder1/gx:drawOrder, etc but I still dont seem to be able to get the line I want to be drawn on top. Btw all these fixes seem to work fin on GE, the green line is being drawn on top. Can't seem to replicate the same result using this plugin. Is there anything I can do in code or in kml to force draw the line on top?
I'm attaching a sample KML,, I'll really appreciate your assistance on this.
126697_mod1.zip
Thanks
Nori
The text was updated successfully, but these errors were encountered: