Ian could we add a utility class to the gt-geojson jar for handling this
case (parsing geojson in isolation)? The GeoJSONWriter could make us of the
utility class to avoid duplication.
--
Jody Garnett
On Wed, 18 Mar 2020 at 10:42, Emilio Lahr-Vivaz wrote:
> Hi Ian,
>
> Do you mean using the Geo
Hi Ian,
Do you mean using the GeoJSONDataStore? I wasn't actually aware of it
until now, but I think it wouldn't work to use the feature writer
directly as that will write out to a file, correct? We (GeoMesa) have a
command line tool that abstracts around OutputStream for exporting data
in di
Emilio,
could you not just create a FeatureStore or FeatureWriter and write
features out that way as with any other datastore? But anyway glad that it
seems to work for you.
Ian
On Wed, 18 Mar 2020 at 14:00, Emilio Lahr-Vivaz wrote:
> Actually the GeoJSONWriter looks like it would work perfect
Actually the GeoJSONWriter looks like it would work perfectly. Our
workflow is: start writing the export (i.e. write the type
'FeatureCollection' and start the 'features' array); write 0-n features
as they come back from various asynchronous queries; finish writing the
export (i.e. write the cl
Yes, that is correct.
Ian
On Wed, 18 Mar 2020 at 13:13, Andrea Aime
wrote:
> On Wed, Mar 18, 2020 at 2:12 PM Ian Turton wrote:
>
>> I'm not quite sure what the use case for that would be, but if you would
>> like to propose modifications to GeoJSONWriter in gt-geojsondatastore I'm
>> happy to
On Wed, Mar 18, 2020 at 2:12 PM Ian Turton wrote:
> I'm not quite sure what the use case for that would be, but if you would
> like to propose modifications to GeoJSONWriter in gt-geojsondatastore I'm
> happy to consider them.
>
Just to match my previous answer and clarify... gt-geojsondatastore
I'm not quite sure what the use case for that would be, but if you would
like to propose modifications to GeoJSONWriter in gt-geojsondatastore I'm
happy to consider them.
Ian
On Wed, 18 Mar 2020 at 13:06, Emilio Lahr-Vivaz wrote:
> If that module is unsupported, are there any supported methods
On Wed, Mar 18, 2020 at 2:07 PM Emilio Lahr-Vivaz
wrote:
> If that module is unsupported, are there any supported methods for writing
> a feature as geojson? For our use case, we need to write each feature
> individually, and not as a feature collection.
>
None I'm afraid. GeoServer writes JSON
If that module is unsupported, are there any supported methods for
writing a feature as geojson? For our use case, we need to write each
feature individually, and not as a feature collection.
Thanks,
Emilio
On 3/18/20 4:00 AM, Andrea Aime wrote:
On Wed, Mar 18, 2020 at 12:03 AM Jody Garnett <
On Wed, Mar 18, 2020 at 12:03 AM Jody Garnett
wrote:
> Since this is an unsupported module should we just break the existing API
> contract in order to be clear about expectations?
>
Jody, since this is a unsupported module a quick band aid should do no?
Also consider the module is in bad shape,
10 matches
Mail list logo
