GeoJSON Object Errors about ogr2ogr HOT 7 CLOSED

from ogr2ogr.

@danielrasmuson I'm unable to duplicate using latest Node v6 or v7. I get the following response:

{ type: 'FeatureCollection',
  crs:
   { type: 'name',
     properties: { name: 'urn:ogc:def:crs:EPSG::3857' } },
  features: [ { type: 'Feature', properties: [Object], geometry: [Object] } ] }

What version of ogr2ogr are you running? ogr2ogr --version

from ogr2ogr.

I had the very same problem. It appears that the generation of the GeoJSON FeatureCollection does NOT buffer the way you might expect. I was expecting that I could grab each feature by stripping off the beginning lines (denoting the FC) and get line-by-line features with a trailing comma. Most of the time that works but occasionally a line does not contain a complete feature for conversion to an object.

As a test, I have been converting Census.gov Zip code geometry files (ZCTA5 500K). These are large enough that every 2 or three attempts the error occurs.

My solution was to stream the output of ogr2ogr to a file. Then I read in the file line-by-line, stripping off the beginning and commas at the end of lines (except for the last feature). It's inelegant that I need to write and then read a file, but it seems to be a reliable solution.

ogr2ogr --version
GDAL 1.11.4, released 2016/01/25

I'd love to hear of a better solution.

from ogr2ogr.

I am getting this now. But it's not consistent. Sometimes it just works, and sometimes it throws this exception.

from ogr2ogr.

Closing due to age, reopen if issue persists.

from ogr2ogr.

from ogr2ogr.

Is this still an issue for you @Peter-Gabel? Feel free to reopen if so. Providing sample code that fails would help for me to address it. And if you have an insight into a fix from your testing, a PR would also be welcome.

As the sole maintainer of this project, closing old, possibly irrelevant, issues helps me keep my task list organized but I want to leave the option open for the asker to reopen if it indeed is still relevant and should be attended to. Other maintainers automate this with bots, which I may consider in the future so it's not personal. Feel free to let me know if you have other ideas.

from ogr2ogr.