> > I've just added a DATE_AS_STRING=YEs open option for such situations:
> > https://github.com/OSGeo/gdal/commit/3a7914cee018d5b65dc1639368edbd8faac2543d
After further thought, I'm wondering about the name of the new option.
This is just about reading GeoJSON, right? If so, then I think a name
Wow, that was fast! This looks great.
Many thanks,
Keith
On Tue, Jan 7, 2020 at 4:35 PM Even Rouault wrote:
>
> > ... ogr2ogr converts the identifiers to "3000\/02\/31" and "2000\/01\/01".
> >
> > Is there any way to preserve the original formatting of these strings?
>
> I've just added a DATE_
Hi,
Is there anyway to skip OGR's automatic detection of date types? When
using ogr2ogr, I'd like to avoid the inadvertent modification of
certain date-like strings. For example, if I have this GeoJSON...
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"pro
