#2499: v.in.ogr in does not handle "nan" in attribute tables properly
--------------------------+-----------------------------------------
Reporter: sbl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.8.3
Component: Vector | Version: unspecified
Resolution: | Keywords: v.in.ogr, DBMI, SQLite, nan
CPU: Unspecified | Platform: Unspecified
--------------------------+-----------------------------------------
Comment (by mmetz):
This is not a problem of v.in.ogr, but of SQLite, and possibly other GRASS
db drivers.
A solution would be to change all GRASS modules that update attribute
tables and replace nan/-nan with NULL.
Another solution would be to replace nan/-nan with NULL in
db_execute_immediate() which is probably easier than changing all modules
but might have unexpected side effects because SQL statements passed to
the db drivers can be quite complex.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2499#comment:9>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
