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

Parse MultiGeometry in KML #829

Merged
merged 2 commits into from Jun 27, 2013
Merged

Parse MultiGeometry in KML #829

merged 2 commits into from Jun 27, 2013

Conversation

tschaub
Copy link
Member

@tschaub tschaub commented Jun 26, 2013

This fixes kml:MultiGeometry parsing for ol.geom.MultiPoint, ol.geom.MultiPolygon, and ol.geom.GeometryCollection. As mentioned in the commits, kml:MultiGeometry may be nested. We don't currently render heterogeneous collections, but this at least gets us parsing them.

The MultiLineString case was correct here.  The MultiPoint and MultiPolygon cases should be using the constructor instead of the `fromParts` factories.
As demonstrated in the tests, a MultiGeometry may contain other MultiGeometry nodes.  We can support this with heterogenous GeometryCollection instances - though these are not currently rendered.
This was referenced Jun 26, 2013
@bartvde
Copy link
Member

bartvde commented Jun 27, 2013

thanks for this @tschaub LGTM please merge

tschaub added a commit that referenced this pull request Jun 27, 2013
Parse MultiGeometry in KML
@tschaub tschaub merged commit fa4d2d4 into openlayers:master Jun 27, 2013
@tschaub tschaub deleted the kml branch June 27, 2013 13:36
afabiani pushed a commit to geosolutions-it/openlayers that referenced this pull request May 22, 2017
afabiani pushed a commit to geosolutions-it/openlayers that referenced this pull request May 22, 2017
afabiani pushed a commit to geosolutions-it/openlayers that referenced this pull request May 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants