Hi,
Motion: I move to adopt RFC 41 : Support for multiple geometry fields in
OGR
http://trac.osgeo.org/gdal/wiki/rfc41_multiple_geometry_fields
I've made a few changes in the last few days. See the history :
+1 Very nice addition!
Daniel
On 13-08-01 10:16 AM, Even Rouault wrote:
Hi,
Motion: I move to adopt RFC 41 : Support for multiple geometry fields in
OGR
http://trac.osgeo.org/gdal/wiki/rfc41_multiple_geometry_fields
I've made a few changes in the last few days. See the history :
Am 01.08.2013 16:16, schrieb Even Rouault:
Hi,
Motion: I move to adopt RFC 41 : Support for multiple geometry fields in
OGR
http://trac.osgeo.org/gdal/wiki/rfc41_multiple_geometry_fields
I've made a few changes in the last few days. See the history :
Selon Andre Joost andre+jo...@nurfuerspam.de:
Am 01.08.2013 16:16, schrieb Even Rouault:
Hi,
Motion: I move to adopt RFC 41 : Support for multiple geometry fields in
OGR
http://trac.osgeo.org/gdal/wiki/rfc41_multiple_geometry_fields
I've made a few changes in the last few
On Wed, Jul 31, 2013 at 3:23 PM, Carl Godkin cgod...@gmail.com wrote:
On Wed, Jul 31, 2013 at 2:35 PM, Even Rouault
even.roua...@mines-paris.org wrote:
I wonder if there is a way to determine if a .gdb is using a custom
coordinate system so we can make a sensible error message.
I find
I'm reading a geojson feed put out by the USGS
(http://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_day.geojson) but
the time/updated values are overflowing. Are there any settings to allow the
data to come across as bigint or strings?
For example:
On Thu, Aug 1, 2013 at 11:36 AM, Smith, Michael ERDC-RDE-CRREL-NH
michael.sm...@erdc.dren.mil wrote:
I'm reading a geojson feed put out by the USGS
(http://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_day.geojson)
but the time/updated values are overflowing. Are there any settings to
Unfortunately, that¹s after the data has been read and overflowed.
The time should be 1375291903959.
Updated should be 1375295733317.
Mike
On 8/1/13 2:21 PM, Kyle Shannon k...@pobox.com wrote:
On Thu, Aug 1, 2013 at 11:36 AM, Smith, Michael ERDC-RDE-CRREL-NH
michael.sm...@erdc.dren.mil wrote:
Hi,
GDAL GeoJSON driver use modified and outdated json-c. It seem to me that
this is the bug and ticket in track needed.
Best regards,
Dmitriy
01.08.2013 22:31, Smith, Michael ERDC-RDE-CRREL-NH пишет:
Unfortunately, that¹s after the data has been read and overflowed.
The time should be
Selon Dmitriy Baryshnikov bishop@gmail.com:
Hi,
GDAL GeoJSON driver use modified and outdated json-c. It seem to me that
this is the bug and ticket in track needed.
It would be a 2 step work. I indeed see that newer json-c supports int64, so a
first step would be to make the GeoJSON
On Thu, Aug 1, 2013 at 1:32 PM, Even Rouault
even.roua...@mines-paris.orgwrote:
Selon Dmitriy Baryshnikov bishop@gmail.com:
Hi,
GDAL GeoJSON driver use modified and outdated json-c. It seem to me that
this is the bug and ticket in track needed.
It would be a 2 step work. I indeed
I really like the RFC31!
Also it'll be great to have a chocie to build GDAL with internal and
external json-c, as libtif, libjpeg, etc. are. And drop patched version
of json-c.
Best regards,
Dmitriy
02.08.2013 0:36, Frank Warmerdam пишет:
On Thu, Aug 1, 2013 at 1:32 PM, Even Rouault
12 matches
Mail list logo