[MetaCRS] Quick and Dirty CSV File

[Landon Blake]

I'm about 4 shades of red right now. You are correct. When saving the
file with no value from Excel the empty cell was preserved.

My bad.

Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
 
 

-----Original Message-----
From: metacrs-bounces at lists.osgeo.org
[mailto:metacrs-bounces at lists.osgeo.org] On Behalf Of Martin Davis
Sent: Thursday, November 05, 2009 10:37 AM
Cc: metacrs at lists.osgeo.org
Subject: Re: [MetaCRS] Quick and Dirty CSV File



Landon Blake wrote:
>
> Martin wrote: "Instead of saying "None" or "Not Provided" just leave
the
> field empty (null)"
>
> Now this makes parsing harder! If we leave "none" or "not provided"
each
> row will always have the same number of values. If we don't include a
> value each row could have a different number of values or cells. This
> could make parsing a lot more difficult. For example, if I use the
> String.split function in Java I can get an array of Strings where the
> comma determines what goes in each element of the array. I can then
use
> the same index position to always access the desired array element
> without having to look at the other elements in the array. I hope this
> makes sense.
>
>   
This isn't a problem in CSV files.  An empty field still has a field 
delimiter, so the number of columns is unchanged. 

-- 
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022

_______________________________________________
MetaCRS mailing list
MetaCRS at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/metacrs


Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.