Closed pka closed 1 year ago
I'm hoping this is related to https://github.com/georust/geozero/pull/22#issuecomment-1115135463
I'm eager to see how it shakes out - let me know if you'd like me to test something.
It's slowly getting serious! Chaining like in #22 now supported.
It's slowly getting serious! Chaining like in #22 now supported.
Nice! I've just taken a quick look at it, and it seems promising!
Do you think it's ready to attempt something like #36 (comment)? I can give it a try if you think so.
Will have to support the event API in a format writer first. What's your favorite output format you want apply reprojection? geo-types?
Will have to support the event API in a format writer first. What's your favorite output format you want apply reprojection? geo-types?
geo-types would be great!
Testing the event API by implementing it for the FlatGeoBuf writer resulted in some major changes (e.g. bd3f1dd) and the following open points:
processor
type in GeomVisitor
shouldn't be defined at compile time to support user flags like promote-to-multi yes/noIdeas to investigate:
Experimental branch is kept in https://github.com/pka/geozero/tree/event-api
This PR adds an event API, which should eventually replace the direct method call API. Main advandages are:
PromoteToMulti
andLonLatToMercator
)GeomVisitor
struct tracks main geometry type and collection flag, which can be used in format writersNext steps:
FeatureProcessor
API. Should it be also event based?