[CON Devel] RE: importing point_cem data

[John Haasbeek]

Hi Steve - sorry I didn't get back to you right away.  Your fix will
work fine, but at some point I'll change the table definition and the
point_cem code to call the table nei_point_cem (just for consistency
with the other nei tables).

On the import_spatial_coverages command, yes it requires both arguments
(good catch).  I'll add the check for the FILENAME parameter to the
concept script also.

Finally, you are also correct that import_spatial_coverages.sql should
prepend the file path from the spatial_filenames table to the file name.
Specifying the full path is a good workaround for now, I will fix the
SQL code in the next release.

John H.

-----Original Message-----
From: Steve Knox [mailto:stevek at nrel.colostate.edu] 
Sent: Friday, May 05, 2006 11:29 AM
To: John Haasbeek
Subject: importing point_cem data

John,

This seems to fix the problem:
.../db/scenario_filenames.sql
I changed
nei_point_cem      VARCHAR(100) NOT NULL DEFAULT 'nei_point_cem.txt'
to
point_cem            VARCHAR(100) NOT NULL DEFAULT 'nei_point_cem.txt'
(default maybe should be "point_cem.txt" ??)

and
.../import/import_point_filenames.pl
I changed
$sql .= "nei_point_cem = '$point_cem', " if defined($point_cem);
to
$sql .= "point_cem = '$point_cem', " if defined($point_cem);

Steve

-- 

John,

 Since the "import_spatial_coverages" concept model function executes
import_spatial_filenames.pl and import_spatial_coverages.sh it needs
both $FILENAME and $DIRECTORY. Shouldn't both of these arguments be
passed to concept.sh function "import_spatial_coverages"?

import_spatial  -n PROJECTNAME -s SCENARIONAME -f FILENAME to
import_spatial  -n PROJECTNAME -s SCENARIONAME -f FILENAME -d DIRECTORY
[-t]

Also, should I provide the full path for surrfilename and surrdefiname
in "FILENAME" or should /spatial/processors/import_spatial_coverages.sql
prepend the spatial_dir to the names?


Steve

_________________________
Steve Knox
NREL
Room B256
Colorado State University
(970)491-1972




This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the Addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply to email at environcorp.com and immediately delete all copies of the message.