Skip to content
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 : Support For NetworkLink #213

Open
ismail44 opened this issue Mar 16, 2016 · 8 comments
Open

KML : Support For NetworkLink #213

ismail44 opened this issue Mar 16, 2016 · 8 comments

Comments

@ismail44
Copy link

Is there, or will there in the future be support for the NetworkLink element type?

@brunob
Copy link
Collaborator

brunob commented Mar 17, 2016

I don't get it, what script are you talking about ?

@ismail44
Copy link
Author

Sorry, I was a bit tired when I posted that issue... it's in the KML script... as it turns out there's a NetworkLink element that is relatively unused, except by the people from whom I am consuming KML.

I actually modified the code locally to handle it, but I am not 100% sure it is the best implementation.

On Mar 17, 2016, at 2:34 PM, b_b notifications@github.com wrote:

I don't get it, what script are you talking about ?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

@brunob
Copy link
Collaborator

brunob commented Mar 18, 2016

Ok, feel free to post a pull request when you think your patch is ok.

@brunob brunob changed the title Support For NetworkLink KML : Support For NetworkLink Mar 18, 2016
@deeg
Copy link

deeg commented Jul 4, 2017

@ismail44, were you able to end up sharing the code?

@ismail44
Copy link
Author

ismail44 commented Jul 4, 2017

Sadly I didn't... and the code is on a computer on a closed network at my old job. It was relatively easy to implement, if I remember correctly it only took about 20 minutes.

@ismail44 ismail44 closed this as completed Jul 4, 2017
@bomberblue07
Copy link

I'd REALLY like support for this feature, please! I don't know why this issue was closed if the problem wasn't solved

@ismail44
Copy link
Author

I'll certainly reopen it... I just cannot be the one to solve it.

@ismail44 ismail44 reopened this Feb 26, 2019
@brunob
Copy link
Collaborator

brunob commented Feb 26, 2019

As i've said 3 years ago :

Ok, feel free to post a pull request when you think your patch is ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants