Content-Type: |
multipart/alternative;
boundary="_000_60F8C3E3D5FED64EA86AF77EEAF4648443237391daguerre1nglond_" |
Date: |
Wed, 23 Aug 2017 14:42:07 +0000 |
Reply-To: |
|
Subject: |
|
From: |
|
Message-ID: |
|
In-Reply-To: |
|
MIME-Version: |
1.0 |
Sender: |
|
Parts/Attachments: |
|
|
Brad, thanks – useful to know. So any occurrence of geographic coordinates in TMS should ideally be accompanied by a field in which to specify the Geodetic Datum used? Would I be right in thinking that, if the Geodetic Datum is known, coordinates could be recalculated to match other Geodetic Data?
Best wishes
Rupert
Rupert Shepherd, PhD FSA
Collection Information Manager
[log in to unmask]<mailto:[log in to unmask]>
Tel: +44 (0)20 7747 5921
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Brad Millen
Sent: 23 August 2017 15:26
To: [log in to unmask]
Subject: Re: Adding VIAF and other linked data references to Constituents
Hi:
Be aware of limitations using Geographic coordinates for locations. All coordinates must have a Geodetic Datum. If not, you get what is called “Datum Shift”. A NAD27 Decimal Latitude is slightly different than a NAD83 or even a WGS84. You can correct this but a lat and long may not plot properly for an address if a NAD83 is used on Google Maps, which is WGS84. A street address may be a block away and the distance from the equator will make that shift worse.
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of David Lowe
Sent: 2017-08-23 10:14 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: Adding VIAF and other linked data references to Constituents
I think that sounds great. And while we're at it, every table describing a physical location should have a field for geo coordinates. I've had to commandeer the Remarks field for over 200,000 constituent addresses<http://pic.nypl.org/map/?address.AddressTypeID=*&address.CountryID=*&bbox=*&Nationality=*&gender.TermID=*&process.TermID=*&role.TermID=*&format.TermID=*&biography.TermID=*&collection.TermID=*&DisplayName=*&Date=*&mode=2>.
To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
|
|
|