chelm
commented
9 years ago Hi @marks - Was out for a couple days so apologies on lack of attention.
Your requests make sense for koop. I assume the KML data from the open data portal that you speak of will be changing regularly and that's why you wouldn't just download it and convert it to GeoJSON with ogr2ogr or something.
So if you want to maintain the link to orginal data then Koop would make sense. I'd start by checking out one the "koop providers" like https://github.com/chelm/koop-geocommons. In short a provider wraps an API and connects to a dataset, pulls it down, converts it into geojson, stores the data locally in it's cache.
I'm working on better docs that show how the internal bits of Koop work, but this sounds like it'd be a good use case if the data are regularly changing.
I am still wrapping my head around the power and versatility of koop so apologies in advance if this is totally off topic
Based on the fact that the README mentions the ability to bring in data from any open data file/API, it would seem reasonable to me to support KMZ and KML files which I am encountering on a number of open data portals and am needing to convert to GeoJSON/etc for downstream projects.
In addition to confirmation that this is a reasonable request/idea, it'd be great to receive some pointers of where to look to start to implement this