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

Multiline strings are not rendered correctly due to typo in VectorLayer #802

Merged
merged 1 commit into from Jun 25, 2013
Merged

Multiline strings are not rendered correctly due to typo in VectorLayer #802

merged 1 commit into from Jun 25, 2013

Conversation

tschaub
Copy link
Member

@tschaub tschaub commented Jun 20, 2013

There is a typo in the parser lookup dictionary for feature types:

https://github.com/openlayers/ol3/blob/master/src/ol/layer/vectorlayer.js#L343

The line says:

'multilinstring': this.lineVertices_,

but it should say:

'multilinestring': this.lineVertices_,

Multilinestrings are still parsed but they do not use the shared vertex storage area and so when transforming to a different projection these features are skipped.

Previously read 'multilinstring' instead of 'multilinestring'.  Letting the compiler check for typos instead now.
@tschaub
Copy link
Member

tschaub commented Jun 21, 2013

Nice catch @jystic. I modified this to use the GeometryType enum.

@tschaub
Copy link
Member

tschaub commented Jun 25, 2013

Interested in an easy review @ahocevar?

@ahocevar
Copy link
Member

Looks solid. Please merge.

tschaub added a commit that referenced this pull request Jun 25, 2013
Multiline strings are not rendered correctly due to typo in VectorLayer
@tschaub tschaub merged commit 40b10c1 into openlayers:master Jun 25, 2013
@tschaub tschaub deleted the 802-multilinstring-typo branch June 25, 2013 14:33
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