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

how to handle feature.type and feature.namespace #559

Closed
bartvde opened this issue Apr 16, 2013 · 6 comments
Closed

how to handle feature.type and feature.namespace #559

bartvde opened this issue Apr 16, 2013 · 6 comments

Comments

@bartvde
Copy link
Member

bartvde commented Apr 16, 2013

in OL2 we had these properties on a feature, which were set by the GML parser, what is the way to deal with this in OL3?

@bartvde
Copy link
Member Author

bartvde commented May 24, 2013

@ahocevar do you have any ideas on this one? Could we add a metadata property on the feature which can contains all of these?

@tschaub
Copy link
Member

tschaub commented May 25, 2013

My vote would be to have a metadata property on the source. This could get populated after parsing a feature collection.

@bartvde
Copy link
Member Author

bartvde commented May 25, 2013

@tschaub does this mean we could never combine multipe featureTypes in one source? Or you don't see a use case for that?

Sent from my iPhone

On May 25, 2013, at 6:26 PM, Tim Schaub notifications@github.com wrote:

My vote would be to have a metadata property on the source. This could get populated after parsing a feature collection.


Reply to this email directly or view it on GitHub.

@ahocevar
Copy link
Member

I think it would be better to create multiple layers for multiple feature
types. I agree with @tschaub.

@bartvde
Copy link
Member Author

bartvde commented May 27, 2013

Okay, as long as we understand the implications and eventually document the restrictions, I'm fine with this

@twpayne
Copy link
Contributor

twpayne commented Mar 23, 2014

@bartvde, can this be closed?

@bartvde bartvde closed this as completed Mar 24, 2014
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

No branches or pull requests

4 participants