[Antelope] lat,lon [SEC=UNCLASSIFIED]

[Rifat.Mohsin at ga.gov.au]

Hi David,

A colleague (Mathew Knafl)has asked me to forward this response in relation your query.

Hope this helps.

Regards,

Rifat

Hi Rifat,

If he wanted an example where the dnorth and deast is being used we can send him a dataless of the Alice Springs array.  These don't actually do exactly what he is after but in an array they give the distance in kilometres from a reference station i.e the central point.

E.g AS01 is 0.1111km north, 4.7915km east of reference station AS12.

There must be a way for the extra decimal places he is after be recognisable otherwise accuracy down to parts of a metre would be useless in this case.

Cheers

Matt

Matthew Knafl
Geospatial & Earth Monitoring Division
Geoscience Australia
Ph: +61 2 6249 9393
Mobile: 0416 302 798
Email: Matthew.Knafl at ga.gov.au
-----Original Message-----
From: Mohsin Rifat
Sent: Friday, 19 February 2010 9:37 AM
To: Knafl Matthew; Bugden Craig; Barton Tim
Subject: FW: [Antelope] lat,lon [SEC=UNCLASSIFIED]


FYI......

Cheers.

Rifat

> -----Original Message-----
> From: antelope-bounces at brtt.net [mailto:antelope-bounces at brtt.net] On
> Behalf Of Daniel Quinlan
> Sent: Thursday, 18 February 2010 1:53 AM
> To: David VonSeggern
> Cc: antelope-users at brtt.com
> Subject: Re: [Antelope] lat,lon
>
> 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
>
>
> _______________________________________________
> Antelope mailing list
> Antelope at brtt.net
> http://brtt.net/mailman/listinfo/antelope_brtt.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ASAR_dataless
Type: application/octet-stream
Size: 319488 bytes
Desc: ASAR_dataless
URL: <http://brtt.net/pipermail/antelope_brtt.net/attachments/20100219/082dbaca/attachment-0001.obj>