[GRASS-dev] [GRASS GIS] #125: quote around char attributes in ascii files may generate problems with v.in.ascii
#125: quote around char attributes in ascii files may generate problems with v.in.ascii --+ Reporter: ct529 | Owner: grass-dev@lists.osgeo.org Type: defect| Status: new Priority: major | Milestone: 6.3.0 Component: default | Version: 6.2.3 Keywords: quotes, inverted commas, v.in.ascii, text file, csv file, import | --+ Supposed you have an ASCII file (comma separated), where the first column is a character column, and is automatically generated by either R, openoffice calc, kspread, MS W Escle, or any gis package using text export. The data in each cell will be surrounded by quotes () aka inverted commas. If you try to load the file using the v.in.ascii command, it returns the error ERROR: x column is not of number type whatever the type of the x column. To fix the problem, you have to remove the quotes around the values in the first column. Quotes around values in other columns do not seem to be important. It should be fixed because all of the above packages correctly export character column with quotes around the values. -- Ticket URL: http://trac.osgeo.org/grass/ticket/125 GRASS GIS http://grass.osgeo.org GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Re: [GRASS GIS] #110: db/drivers/dbf fail to build due to undefined reference to 'SASetupDefaultHooks' (SHAPELIB)
#110: db/drivers/dbf fail to build due to undefined reference to
'SASetupDefaultHooks' (SHAPELIB)
---+
Reporter: marisn| Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: critical | Milestone: 6.4.0
Component: default | Version: svn-trunk
Resolution:|Keywords: dbf
---+
Comment (by neteler):
Maris, William, is the problem solved (for now)?
Question: Can we remove the Shapelib copy and use only GDAL/OGR for this?
The needed functions are
{{{
nm /home/neteler/grass63/dist.x86_64-unknown-linux-gnu/driver/db/dbf |
grep DBF
U DBFAddField
U DBFClose
U DBFCreate
U DBFGetFieldCount
U DBFGetFieldInfo
U DBFGetRecordCount
U DBFIsAttributeNULL
U DBFOpen
U DBFReadDoubleAttribute
U DBFReadIntegerAttribute
U DBFReadStringAttribute
U DBFWriteDoubleAttribute
U DBFWriteIntegerAttribute
U DBFWriteNULLAttribute
U DBFWriteStringAttribute
}}}
In GDAL/OGR, the AVC driver uses DBF bindings:
gdal/ogr/ogrsf_frmts/avc/
There is a local copy of dbfopen.h. Perhaps we can do the same?
Markus
--
Ticket URL: http://trac.osgeo.org/grass/ticket/110#comment:18
GRASS GIS http://grass.osgeo.org
GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS] #126: v.outlier sqlite
#126: v.outlier sqlite --+- Reporter: dadudeman | Owner: grass-dev@lists.osgeo.org Type: defect| Status: new Priority: major | Milestone: 6.4.0 Component: default | Version: 6.2.3 Keywords: v.outlier sqlite | --+- When running v.outlier with sqlite.db, I encounter the following error. DBMI-SQLite driver error: Error in sqlite3_prepare(): no such table: Auxiliar_outlier_table ERROR: Impossible to write in the database Google revealed a page that identified the same problem with a solution. http://lists.osgeo.org/pipermail/grass-user/2006-November/037304.html When I increased the spline step parameter, it worked (or at least it ran a while, I am unable to verify my results yet). I was unable to change my region resolution, so I kept increasing the spline step until it would run. -- Ticket URL: http://trac.osgeo.org/grass/ticket/126 GRASS GIS http://grass.osgeo.org GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS 6.3.0 to be released
2008/4/15, Markus Neteler [EMAIL PROTECTED]: After 6 release candidates, even tested on MS-Windows, I don't see any real blockers any more. I suggest to get out 6.3.0 this week and proceed with change to 6.4.release_branch/7.0.svn. We can have 6.3.1 if needed. Sounds ok? +1 Martin -- Martin Landa landa.martin gmail.com * http://gama.fsv.cvut.cz/~landa * ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
R: [GRASS-dev] GRASS 6.3.0 to be released
Hi all, It would be good also for me, even if it would better if we release it on next week tough (I'm very busy now). BTW, there are few thing to do for me, just some improvements for windows installer... Martin, do you think that we could add the needed python files into the 6.3.0 windows package, in order to let users start the pyGUI without the need to install python stuffs by themselves? Regards Marco -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Martin Landa Inviato: martedì 15 aprile 2008 19.04 A: Markus Neteler Cc: GRASS developers list Oggetto: Re: [GRASS-dev] GRASS 6.3.0 to be released 2008/4/15, Markus Neteler [EMAIL PROTECTED]: After 6 release candidates, even tested on MS-Windows, I don't see any real blockers any more. I suggest to get out 6.3.0 this week and proceed with change to 6.4.release_branch/7.0.svn. We can have 6.3.1 if needed. Sounds ok? +1 Martin -- Martin Landa landa.martin gmail.com * http://gama.fsv.cvut.cz/~landa * ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
