-
-
Notifications
You must be signed in to change notification settings - Fork 364
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
WMS KML generates incorrect output for MULTILINESTRING #4980
Comments
|
Mapfile is: |
|
SQL data is: Request is mapserv -v tells me, that |
|
@phopfgartner, has your patch been integrated into master? Would be nice to close this one... --Steve |
|
Hi @sdlime, looking at the code in master, it's not integrated, yet. Regards, Peter |
|
Do you have a patch ready? From: Peter Hopfgartner [mailto:notifications@github.com] Hi @sdlimehttps://github.com/sdlime, looking at the code in master, it's not integrated, yet. Regards, Peter — |
|
The code is in Regards, Peter On Fri, Dec 5, 2014 at 5:20 PM, Steve Lime notifications@github.com wrote:
|
This is an automated commentThis issue has been closed due to lack of activity. This doesn't mean the issue is invalid, it simply got no attention within the last year. Please reopen with missing/relevant information if still valid. Typically, issues fall in this state for one of the following reasons:
|
When exporting a MULTILINE, the generated KML is not valid.
Basically, starting with the second line in the ulti, all LineString Element are collected as childs in a LineString Element, like:
This is with MapServer 6.4.1 on CentOS 6.
Peter
The text was updated successfully, but these errors were encountered: