[GRASS-dev] [GRASS GIS] #2185: Painfully Slow 'v.in.ogr' Vector Import

[GRASS GIS]

#2185: Painfully Slow 'v.in.ogr' Vector Import
-------------------------+------------------------------------------------
  Reporter:  justinzane  |      Owner:  grass-dev@…
      Type:  defect      |     Status:  new
  Priority:  normal      |  Milestone:  7.0.0
 Component:  Vector      |    Version:  svn-trunk
Resolution:              |   Keywords:  import, OGR, performance, v.in.ogr
       CPU:  x86-64      |   Platform:  Linux
-------------------------+------------------------------------------------

Comment (by wenzeslaus):

 Replying to [comment:20 martinl]:
 > Replying to [comment:18 imincik1]:
 > > TMPDIR, TEMP, TMP has no effect on temporary directory path created by
 vector library.
 >
 > Starting with r65348 when GRASS_TMPDIR_MAPSET is set to '0', the GRASS
 data TMPDIR is not `$LOCATION/$MAPSET/.tmp/$HOSTNAME`, but
 `$TMPDIR/.tmp/$HOSTNAME`.

 Sounds good. I'm curious how this will work for the mounted disc use case.

 Just few clarifications. I was trying to read the source code few days ago
 and I think that there is no actual usage of `HOSTNAME` variable but some
 C functions are used to retrieve this value (which probably is the value
 of `HOSTNAME` variable). Also you say "GRASS data TMPDIR" but the actual
 `TMPDIR` is a variable pointing to GRASS's directory in system temporary
 directory. Is this meant in symbolic way as $LOCATION and $MAPSET are
 meant or am I missing something?

 Do I understand correctly that you can change it anytime (inside GRASS
 session), so `grass.py` has to always clear both places? (Or it is even
 not worth attempting to care for this case in `grass.py`.)

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2185#comment:21>
GRASS GIS <http://grass.osgeo.org>