[Antelope] lat,lon

[Daniel Quinlan]

As I think you're suggesting, the easiest way to deal with this is to make 
a copy of css3.0 (named something a little different) and alter the lat and 
lon attributes to have more resolution.  Then you can have a database which
is effectively css3.0 and everything in Antelope should 
continue to work on the new schema without any other changes.  

The program dbconvert could be helpful in converting an original site table
to the new version, but you would have to edit in any increased resolution by
hand.

I think the dnorth and deast fields were supposed to deal with this to some extent.

The more general problem of fixing the various issues in the schema is a lot
harder.

-- danq

On Feb 16, 2010, at 4:33 PM, David VonSeggern wrote:

> One of the defects of the CSS3.0 schema is that latitude and longitude are only stored
> to 4 decimal places (roughly 10-m accuracy).  Some of us may wish to use Antelope for
> sensors that are more closely spaced than what the CSS3.0 site table can accurately
> describe.   I am currently setting up to handle a seismic exploration receiver line with 15-m
> geophone spacing.
> 
> Has anyone out there dealt with this and devised a new schema relation to basically
> make an alternate site table which would store lat-lon to 5 or 6 decimal places?  I just
> thought I would not redefine this until I saw what had been done elsewhere.
> 
> David von Seggern
> 
> _______________________________________________
> Antelope mailing list
> Antelope at brtt.net
> http://brtt.net/mailman/listinfo/antelope_brtt.net