New input and output format defined in GeoJson as Feature sets.

[jodymarca]

You can use both input and output or just one of those. You can also select dynamically output using tag "format":"geojsonfeatures" in the request.
You can select at startup --geojsonfeature and --geojsonfeaturesinput (if you use server mode) or use them in a spark program in Hadoop ecosystem (I tried and used them in both versions)

[smattheis]

Please keep this pull request open for a while. I will merge (and revise) it as soon as possible. I just don't have the capacity to do it now. Thanks a lot for this pull request.

[jodymarca]

Ok no problem
Regards
Jody

On Sat, Oct 29, 2016 at 12:41 PM, Sebastian Mattheis <
[email protected]> wrote:

Please keep this pull request open for a while. I will merge (and revise)
it as soon as possible. I just don't have the capacity to do it now. Thanks
a lot for this pull request.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#34 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AS1GJsgiDriobyOrOZuUyLUieYOGh5ypks5q4yLKgaJpZM4KVKNz
.

[smattheis]

I will check this pull request togehter with #39 once I have a strategy for #39. - ... to give a ping that it's not forgotten or ignored. ;)
I'm trying to keep a good test coverage in the project and I know that it's a little bit tricky with the output formats. To be able to do a "by-hand and look-with-eyes" test, can you briefly tell me what the output format must look like? - I also thought about a simple test that reads the output as GeoJSON with some library to at least test if it's valid GeoJSON. I would also adapt this kind of test strategy to the other output format(s) based on GeoJSON. Do you think that this could work and check the basic of your suggested output formatter?