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
Comments
@ahocevar do you have any ideas on this one? Could we add a metadata property on the feature which can contains all of these? |
My vote would be to have a metadata property on the source. This could get populated after parsing a feature collection. |
@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:
|
I think it would be better to create multiple layers for multiple feature |
Okay, as long as we understand the implications and eventually document the restrictions, I'm fine with this |
@bartvde, can this be closed? |
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?
The text was updated successfully, but these errors were encountered: