To our knowledge no Python package is available for conversion between cartesian and polar coordinates, so we made one for convenience.

The package converts numpy arrays where the last dimension contains x, y or magnitude, orientation coordinates.

When working with cupy arrays, the package performs calculations on the GPU automatically.

Raw and compiled data. LRMSD and delta_COM values, Cartesian coordinates of all structures, and complete Psi4 output files

Real and simulated lidar data of indoor and outdoor scenes, before and after geometric scene changes have occurred. Data include lidar scans from multiple viewpoints with provided coordinate transforms, and manually annotated ground-truth regarding which parts of the scene have changed between subsequent scans.

The house coordinates, also called georeferenced building addresses, assign each building in Bremerhaven, provided it has a house number and is assigned exactly one coordinate in the country coordinate system. Like the official house rings, they are a product of the real estate cadastre. Because they are based on an individual survey on site, they have a high geometric accuracy and can be ideally combined with the official house circles, but also with other georeferenced data from the official surveying system.

• Data Set Overview

• =================

• Version 1.1

• ===========

This Version 1.1 Data Set replaces the Version 1.0 Data Set (DATA_SET_ID=VG2-J-MAG-4-1.92SEC) previously archived with the PDS. Changes to this Version include the Addition of Data Columns not included in Version 1.0, the Modification of Time Format and Flag Values, and Upgrade of associated Labels and Catalog Templates to PDS Version 3.4.

• Data Set Description
• ====================

This Data Set includes Voyager 2 Jupiter Encounter Magnetometer Data from the Low Field Magnetometer (LFM) resampled at a 1.92 s Sample Rate from the 60 ms Instrument Sampling Rate. The Data are given in Jovicentric System III (1965) right-handed Coordinates, S3RH. Data Coverage begins in the Solar Wind and continues until at least the first Magnetopause Crossing.

The Data Set consists of the following Columns:

• 1) Time - Universal Time of the Sample in the Format YYYY-MM-DDTHH:MM:SS.SSSZ
• 2) Spacecraft Clock Values - m65536:mod60:fds_line
• 3) mag_id - Magnetometer ID: 1=LFM, 2=HFM
• 4) Br - Radial Magnetic Field Component, Jupiter to Spacecraft
• 5) Btheta - North/South Magnetic Field Component, positive southward, System III (1965), S3RH
• 6) Bphi - Azimuthal Magnetic Field Component, positive eastward, System III (1965), S3RH
• 7) Bmag - Magnitude of the averaged Magnetic Field Components
• 8) avg_Bmag - Average of the Magnetic Field Magnitudes
• 9) delta - Magnetic Latitude, delta=asin(Btheta/Bmag)
• 10) lambda - Magnetic Longitude, lambda=180.0-atan(Bphi/-Br)
• 11) rms_br - Br RMS Value
• 12) rms_bt - Bt RMS Value
• 13) rms_bn - Bn RMS Value
• 14) npts - Number of Points in the Average

All Magnetic Field Observations are measured in nT. All of the Magnetic Field Data are calibrated (see the Instrument Calibration Description for more Details). The Coordinate System for this Data Set is System III (1965), S3RH. The Jupiter S3RH Coordinate System is defined in (Dessler, 1983) and the Reference Documents for this Data Set are: (Ness et al., 1981), (Lepping et al., 1981), (Connerney et al., 1981), (Behannon et al., 1981).

These Data are provided in a conventional, right-handed, Spherical Coordinate System with Vectors R, Theta, and Phi. The the Magnetic Field Components are:

• Br - Radial Magnetic Field Component, along the Jupiter to Spacecraft Line, positive away from Jupiter
• Btheta - North/South (S3RH) Magnetic Field Component, positive southward
• Bphi - Azimuthal (S3RH) Magnetic Field Component, positive eastward

+-----------------------------------------+

| Processing Characteristics | Value |

| Processing Level ID | 4 | | Software Flag | Y | | Processing Start Time | 1988-09-21 | +-----------------------------------------+

• Parameters
• ==========

+--------------------------------------------------------+

| Parameter Characteristics | Value |

| Sampling Parameter Name | TIME | | Data Set Parameter Name | MAGNETIC FIELD VECTOR | | Sampling Parameter Resolution | 1.920000 | | Minimum Sampling Parameter | 19770820120000.000000 | | Maximum Sampling Parameter | UNK | | Sampling Parameter Interval | 1.920000 | | Minimum Available Sampling Int | 0.060000 | | Data Set Parameter Unit | NANOTESLA | | Noise Level | 0.006000 | | Sampling Parameter Unit | SECOND | +--------------------------------------------------------+

+-------------------------------------------------------------------------------------------------------------------------------------------------+

| Parameter Name | Resolution (Units) | Description |

| Time | 1.92 s | Time of the Sample (UT) in the Format YYYY-MM-DDTHH:MM:SS.SSSZ. The full Sampling Rate for | | | | the Instrument is 0.06±0.006s. | | | | | | m65536, mod60, and fds_line | Counts | Spacecraft Clock mod 65536, mod 60, and fds line | | | | | | mag_id | N/A | Magnetometer ID | | | | | | Magnetic Field Components | nT | Measured Parameters equaling the Magnetic Field Strength along a particular Axis Direction. | | (Br, Btheta, Bphi) | | Usually the three orthogonal Axis Components are measured by three different Sensors. | | | | | | Magnetic Field Vector | nT | Derived Parameter which combines the three orthogonal Magnetic Field Component Measurements. | | (Bmag, avg_Bmag) | | | | | | | | delta | degrees | Magnetic Latitude: delta=asin(Btheta/Bmag) | | | | | | lambda | degrees | Magnetic Longitude: lambda=180.0-atan(Bphi/-Br) | | | | | | rms_Br, rms_Bt, and rms_Bn | nT | Pythagorean Root Mean Square Deviation of the Component Averages | | | | | | npts | Counts | The Number of Data Points in the Current Average | +-------------------------------------------------------------------------------------------------------------------------------------------------+

Official house coordinates (PLC, town, postal district, street, house number, Coordinate) Landkreis Diepholz; Up-to-date: 01.04.2016

The house coordinates, also called georeferenced building addresses, assign each building of the district Diepholz, provided it has a house number and is assigned exactly one coordinate in the country coordinate system. Because they are based on an individual survey on site, they have a high geometric accuracy.

• Data Set Overview
• =================

This Data Set consists of Voyager 2 Neptune Encounter Ephemeris Data relative to the Planet in Minus NLS Coordinates.

The NLS or Neptune West Longitude System Coordinate System is a Planetocentric System fixed to Neptune, which is rotating with a 16.11 h Period.

• Cartesian Coordinates

• =====================

• NLS Cartesian Coordinates

• =========================

• X lies in the Equatorial Plane of Neptune, positive away from the Planet, and through the Prime Meridian at the Reference Epoch

• Y completes the left-handed Set, Y = Z ⨯ X

• Z points along the Spin Axis of Neptune

The Prime Meridian of this System is defined such that at 1989-08-25T03:56:00.000 the Voyager 2 Spacecraft was at 167.7° West Longitude.

For the PDS Archive Data Set, the original Data Archive has been converted to an East Longitude (right-handed) Coordinate System Minus NLS (-NLS). This is achieved by reversing the Direction of the Y Axis, or in Spherical Coordinates, by subtracting the NLS Longitude from 360°. The Data are provided in Units of Neptunian Radii, which was taken to be equal to 24,765 km by the Voyager Project. Angles are given in Degrees. Both Cartesian and Spherical Coordinates are provided.

+-----------------------------------+

| Parameter Characteristics | Value |

| Processing Level ID | 4 | | Software Flag | Y | | Processing Start Time | UNK | | Processing Stop Time | UNK | +-----------------------------------+

• Parameters

• ==========

• Data Set Parameter POSITION VECTOR

• ==================================

A Position Vector is a Triad that describes the Location of a Point in three dimensional Space relative to some Origin.

+-----------------------------------------------------------------------+

| Parameter Characteristics | Value |

| Data Set Parameter Name | POSITION VECTOR | | Data Set Parameter Unit | NEPTUNE RADII (24,765 KM) OR DEGREES | | Sampling Parameter Name | TIME | | Sampling Parameter Unit | SECONDS | | Sampling Parameter Resolution | 12 | | Sampling Parameter Interval | 12 | | Minimum Available Sampling Int | 12 | +-----------------------------------------------------------------------+

• Source Instrument Parameters
• ============================

N/A

• Measurement Information
• =======================

N/A

• Processing

• ==========

• Processing History

• ==================

+-------------------------------------------------------------------+

| Parameter Characteristics | Value |

| Source Data Set ID | N/A | | Software | UNK | | Product Data Set ID | VG2-N-POS-5-SUMM-NLSCOORDS-12SEC-V1.0 | +-------------------------------------------------------------------+

This data set includes Voyager 2 Jupiter encounter magnetometer data from the Low Field Magnetometer (LFM) resampled at a 48 second sample rate. The data are given in Jovicentric System III right handed coordinates and have been averaged from the 60 ms instrument sample rate to a 48 second resampled rate. Ephemeris data, provided in 96 second sampled System III (1965) coordinates, have been merged into the data files for this data set. The ephemeris data, generated from Voyager 2 SEDR and provided by the Voyager MAG Team, are part of the data set VG2-J-POS-6-SUMM-S3COORDS-V1.1. The position vectors for times at which ephemeris is not provided have been flagged.

• Data Set Overview

• =================

• Version 1.1

• ===========

The SEDR based Data provided as Part of this Data Set were originally reviewed and archived with the NSSDC and PDS as Version 1.0 (DATA_SET_ID=VG2-J-POS-4-48.0SEC). Version 1.1 includes additional Columns not present in the previous Version, 96 s Time Samples rather than 48 s Time Samples, Times converted to "PDS Style" or "Zulu Time", and upgrading of PDS Labels and Templates to Version 3.4. The SPICE based Data that are also Part of this Data Set were not previously archived with the PDS. This Version 1.1 Data Set replaces previously archived Versions.

• Data Set Description
• ====================

This Data Set consists of Voyager 2 Jupiter Encounter Ephemeris Data in System III (1965) left-handed Coordinates covering the Period from 1979-07-05 to 1979-08-12.

Two Versions, both covering the same Time Period, but containing slightly different Data, are provided. One Version was generated by the Voyager Magnetometer (MAG) Team from the Voyager 2 SEDR, the other by the PDS/PPI Node using the VG2_JUP.BSP and PCK00003.TCP SPICE Kernels.

Due to Inaccuracies in Voyager SEDR, as well as Changes in the Values of some Key Parameters (e.g., the Radius of Jupiter) the Timing is improved for the SPICE generated Data. However, since much of the original Analysis was based upon the SEDR generated Ephemeris, these Data have been included as well.

• SEDR Generated Ephemeris
• ========================

+------------------------------------------------------+

| Parameter Characteristics | Value |

| Instrument P.I. | N/A | | Data Supplier | NSSDC | | Data Sampling Rate | 96 SECONDS | | Data Set Start Time | 1979-07-05T00:00:47.269Z | | Data Set Stop Time | 1979-08-12T16:54:20.608Z | +------------------------------------------------------+

• SPICE Generated Ephemeris
• =========================

+------------------------------------------------------+

| Parameter Characteristics | Value |

| Instrument P.I. | N/A | | Data Supplier | S. JOY | | Data Sampling Rate | 48 SECONDS | | Data Set Start Time | 1979-07-05T00:00:47.269Z | | Data Set Stop Time | 1979-08-12T16:55:08.608Z | +------------------------------------------------------+

• Parameters

• ==========

• SEDR Generated Ephemeris

• ========================

+----------------------------------------------------------------------------------------------------------------------------------------------------+

| Parameter Name | Resolution/Units | Description |

| time | 96 s | Time of the Sample (UT) in the Format YYYY-MM-DDTHH:MM:SS.SSSZ | | m65536 | counts | Spacecraft Clock Counts, mod 65536 | | mod60 | counts | Spacecraft Clock Counts, mod 60 | | fds_line | counts | Spacecraft Clock Counts, fds_line | | sc_x | R[J] | Jovicentric (System III) Spacecraft Position, Cartesian Coordinates, X Component | | sc_y | R[J] | Jovicentric (System III) Spacecraft Position, Cartesian Coordinates, Y Component | | sc_z | R[J] | Jovicentric (System III) Spacecraft Position, Cartesian Coordinates, Z Component | | vel_x | km/s | Jovicentric (System III) Spacecraft Velocity, Cartesian Coordinates, X Component | | vel_y | km/s | Jovicentric (System III) Spacecraft Velocity, Cartesian Coordinates, Y Component | | vel_z | km/s | Jovicentric (System III) Spacecraft Velocity, Cartesian Coordinates, Z Component | | sc_r | AU | Jovicentric (System III) Spacecraft Position, Spherical Coordinates, Radial Distance (Range) | | sc_lat | degrees | Jovicentric (System III) Spacecraft Position, Spherical Coordinates, Latitude | | sc_lon | degrees | Jovicentric (System III) Spacecraft Position, Spherical Coordinates, Longitude | | CartSys3_to_SphSys3 | | Cartesian System III to Spherical System III Coordinates Rotation Matrix containing nine 1PE15.8 Elements | | SC_to_CartSys3 | | Payload (Spacecraft) to Cartesian System III Coordinates Rotation Matrix containing nine 1PE15.8 Elements | | SC_to_SphSys3 | | Payload (Spacecraft) to Spherical System III Coordinates Rotation Matrix containing nine 1PE15.8 Elements | +----------------------------------------------------------------------------------------------------------------------------------------------------+

• SPICE Generated Ephemeris
• =========================

+-----------------------------------------------------------------------------------------------------------------------------------------------------+

| Parameter Name | Resolution/Units | Description |

| time | 48 s | Time of the Sample (UT) in the Format YYYY-MM-DDTHH:MM:SS.SSSZ | | R | AU | Jovicentric (System III 1965) Spacecraft Position, Spherical Coordinates, Radial Distance (Range) | | LAT | degrees | Jovicentric (System III 1965) Spacecraft Position, Spherical Coordinates, Latitude | | LON | degrees | Jovicentric (System III 1965) Spacecraft Position, Spherical Coordinates, Longitude | | LocTime | hours | Angular Separation between the Meridian containing the Sun and the one containing the Spacecraft converted | | | | converted to a Time. The Sun Meridian is defined to be Noon (12.000), with Midnight (0.000) opposite it. | | | | Dawn (6.000) and Dusk (18.000) are where the Sun rises and sets according to the Rotation of the Planet. | +-----------------------------------------------------------------------------------------------------------------------------------------------------+

• Coordinate System
• =================

The System III (1965) is a Jovicentric left-handed Coordinate System defined such that Longitude increases with Time as viewed by a stationary Remote Observer.

• Jovicentric (Jupiter Fixed) Cartesian Coordinates

• =================================================

• X points along the Jupiter-Sun Line in the Solar Equatorial Plane, positive towards the Sun

• Y completes the right-handed Set, Y = X ⨯ Z

• Z points along the Spin Axis of Jupiter

• Jovicentric System III (1965) Spherical Coordinates

• ===================================================

• R gives the Jupiter to Spacecraft Range, positive away from Jupiter

• LAT completes the left-handed, Orthogonal Set

• LON gives the System III (1965) East Longitude with Longitude increasing eastward from a specific Jovian Prime Meridian

SPICE Ephemeris were generated using the current Definition of the Jovian Radius, 71,492 km. The Spin Rate used in generating these Data is the same as that used for System III (1965), 870.536° per Day.

• Data Coverage
• =============

+------------------------------------------------------------------------------------+

| Filename | Records | Start Date and Time | Stop Date and Time |

| Volume ID: VG_1502 | | | | | SEDR_S3_96S.TAB | 31288 | 1979-07-05T00:00:47.269Z | 1979-08-12T16:54:20.608Z | | SPICE_S3_48S.TAB | 62578 | 1979-07-05T00:00:47.269Z | 1979-08-12T16:55:08.608Z | +------------------------------------------------------------------------------------+

House coordinates assign an exact position to each unique building address. The Bavarian Survey Administration has more than 3.3 million current house coordinates available. House coordinates can be selected by administrative units (country, district, county, municipality), postal code areas or spatial delimitation. Optionally, complete data (all HK of the selected area) or differential data (only the newly created, modified or cancelled HK since the last update) are provided. A selection according to quality levels (A, R or A+R) is possible. In addition to the specified reference systems, a delivery in the system DHDN (geographic 2D) (EPSG:4314) is also possible.

These sites are those reported as visited or pending/onoing ('to visit' in the status column) as of end 28 April 2015. The 'visited' coordinates come from the international Urban Search and Rescue (USAR) team reports as provided to the Virtual OSOCC and to the USAR coordination centre and are from GPS. The 'to visit' sites come from the government of Nepal as a list of names to which we have attempted to assign coordinates. The site names are often ambiguous so these coordinates are approximate. The list of visited sites is incomplete because there are international USAR teams that have not reported their visited sites. Also, this list DOES NOT INCLUDE NEPALI USAR TEAM SITES VISITED. This list was compiled by MapAction (www.mapaction.org)

This data set includes data from the Low Field Magnetometer (LFM) in the solar wind the near the Uranus encounter. The actual encounter data (1986-01-24T07:00:00 -> 1986-01-25T04:00:00) are provided in the Uranus Longitude coordinate system. The magnetometer data in the solar wind are given in Heliographic coordinates and the data have been averaged from the 9.6 second resampled data to a 48.0 second sampled rate.

This data set contains data acquired by the Galileo Magnetometer during the Interplanetary Cruise to Jupiter. The data are at varying resolution depending on the averaging constant applied by the instrument. These data have been fully processed to remove instrument response function characteristics. The data are provided in physical units (nanoTesla) and in 2 coordinate systems. This set of data files contains data in Inertial Rotor Coordinates (IRC= despun spacecraft).

This data set consists of Voyager 2 Jupiter encounter ephemeris data in Heliographic coordinates covering the period 1979-06-20 to 1979-08-18. Two versions, both covering the same time period, but containing slightly different data, are provided. One version was generated by the Voyager MAG team from Voyager 2 SEDR, the other by the PDS/PPI node using the VG2_JUP.BSP and PCK00003.TPC SPICE kernels.

Aim: Species occurrence records are essential to understanding Earth’s biodiversity and addressing global environmental issues, but do not always reflect actual locations of occurrence. Certain geographic coordinates are assigned repeatedly to thousands of observation/collection records. This may result from imperfect data management and georeferencing practices, and can greatly bias the inferred distribution of biodiversity and associated environmental conditions. Nonetheless, these ‘biodiverse’ coordinates are often overlooked in taxon-centric studies, as they are identifiable only in aggregate across taxa and datasets, and it is difficult to determine their true circumstance without in-depth, focused investigation. Here we assess highly recurring coordinates in biodiversity data to determine artificial hotspots of occurrences. Location: Global Taxon: Land plants, birds, mammals, insects Methods: We identified highly recurring coordinates across plant, bird, insect, and mammal records in the Global Biodiversity Information Facility, the largest aggregator of biodiversity data. We determined which are likely artificial hotspots by examining metadata from over 40 million records; assessing spatial distributions of associated datasets; contacting data managers; and reviewing literature. These results were compiled into the Artificial Hotspot Occurrence Inventory (AHOI). Results: Artificial biodiversity hotspots generally comprised geopolitical and grid centroids. The associated uncertainty ranged from several square kilometers to millions. Such artificial biodiversity hotspots were most prevalent in plant records. For instance, over 100,000 plant occurrence records were assigned the centroid coordinates of Brazil, and points that have at least 1,000 associated occurrences comprised over 9 million records. In contrast, highly recurring coordinates in animal data more often reflected actual sites of observation. Main Conclusions: AHOI can be used to i) improve accuracy of biodiversity assessments; ii) estimate uncertainty associated with records from artificial hotspots and make informed decisions on whether to include them in scientific studies; and iii) identify problems in biodiversity informatics workflows and priorities for improvement. Methods Primary biodiversity records were queried from the Global Biodiversity Information Facility on January 30 and May 10, 2021 for plants (Plantae; https://doi.org/10.15468/dl.th5tn8; https://doi.org/10.15468/dl.76jc24), June 3, 2022 for birds (Aves; https://doi.org/10.15468/dl.jh3u2u), and August 23, 2021 for insects (Insecta; https://doi.org/10.15468/dl.4q2972), and mammals (Mammalia; https://doi.org/10.15468/dl.cujmgz). We then assessed the frequency of the geographic coordinates and identified the most frequently recurring sets of coordinates across each taxonomic group. Coordinates were assessed as provided in the “decimalLatitude” and “decimalLongitude” columns of the downloaded data without any rounding to be conservative. Rounding coordinates before assessing their frequency would increase the overall number of records associated with each set of coordinates and increase the risk of associating true points with georeferenced ones. Only exact matches were counted to calculate the frequency of each unique set of coordinates. We determined which of the highly-recurrent coordinates are likely artificial by examining metadata and images from datasets comprising over 40 million records to date; assessing spatial distributions of associated datasets; contacting data managers; and reviewing literature (Fig. 2). We used QGIS software to validate grid centroid coordinates by plotting the grid systems over the reported occurrence coordinates to confirm the grid centroid, grid size and the coordinate reference system. Countries represented in our dataset that utilized such grids were identified through occurrence record metadata, visual inspection of associated datasets, literature review, and data managers, and included France, the United Kingdom, Germany, the Netherlands, Belgium, Switzerland, and Spain. For each group, we started by evaluating the most recurrent set of coordinates and proceeded in order of decreasing frequency. We initially examined the top 100 recurring coordinates for plants and the top 50 recurring coordinates for each animal group. These coordinates were manually curated into the following categories when possible: grid centroid, geopolitical centroid, georeferenced location, and true observation or collection site. Some coordinates could be associated with multiple categories. It is possible that the determinations we made for highly-recurrent coordinates could also be extended to additional, less recurrent, coordinates that were assigned to other records in the datasets they belonged to (but not included in our initial survey). These data were compiled into AHOI, an inventory of highly-recurrent GBIF coordinates, with their descriptions and determinations. To validate our approach and assess whether artificial biodiversity hotspots are the result of systemic practices or errors, we additionally evaluated data from the Field Museum of Natural History, as some of the top 100 most recurring coordinates were associated with the institution. We downloaded all plant records from this dataset and evaluated all coordinates that were assigned to at least 1000 records. We found that the coordinates from this dataset represented artificial aggregates of specimens around geopolitical centroids. These verifications were also included in AHOI. Further, we listed the rationale for each individual coordinate determination and provides examples of relevant information from occurrence record metadata in the “example_description” and “reasoning” fields respectively.

ISEE-3 Weimer propagated solar wind data and linearly interpolated to have the measurements on the minute at 60 s resolution solar wind plasma data in GSE coordinates. This data set consists of propagated solar wind data that has first been propagated to a position just outside of the nominal bow shock (about 17, 0, 0 Re) and then linearly interpolated to 1 min resolution using the interp1.m function in MATLAB. The input data for this data set is a 1 min resolution processed solar wind data constructed by Dr. J.M. Weygand. The method of propagation is similar to the minimum variance technique and is outlined in Dan Weimer et al. [2003; 2004]. The basic method is to find the minimum variance direction of the magnetic field in the plane orthogonal to the mean magnetic field direction. This minimum variance direction is then dotted with the difference between final position vector minus the original position vector and the quantity is divided by the minimum variance dotted with the solar wind velocity vector, which gives the propagation time. This method does not work well for shocks and minimum variance directions with tilts greater than 70 degrees of the sun-earth line. This data set was originally constructed by Dr. J.M. Weygand for Prof. R.L. McPherron, who was the principle investigator of two National Science Foundation studies: GEM Grant ATM 02-1798 and a Space Weather Grant ATM 02-08501. These data were primarily used in superposed epoch studies References: Weimer, D. R. (2004), Correction to ‘‘Predicting interplanetary magnetic field (IMF) propagation delay times using the minimum variance technique,’’ J. Geophys. Res., 109, A12104, doi:10.1029/2004JA010691. Weimer, D.R., D.M. Ober, N.C. Maynard, M.R. Collier, D.J. McComas, N.F. Ness, C. W. Smith, and J. Watermann (2003), Predicting interplanetary magnetic field (IMF) propagation delay times using the minimum variance technique, J. Geophys. Res., 108, 1026, doi:10.1029/2002JA009405.

The Thuringian Marking Coordinates Catalogue (GKK Th) contains all Thuringian areas, as they are managed in the cadastral areas, with their assignment to the municipalities and their focus coordinates in different coordinate systems. The coordinates were recorded with an accuracy of 500 m to 1 000 m. It is an addition to the Thuringian Marking Key Catalogue, which includes important keys to the ALB, such as the booking districts of the parcels and the land registers, as well as the assignment to the cadastral areas.

This data set includes calibrated magnetic field data acquired by the Voyager 1 Low Field Magnetometer (LFM) during the Saturn encounter. Coverage begins in the solar wind inbound to Saturn and continues past the last outbound bowshock crossing. The data are in Kronographic (L1) coordinates and have been averaged from the 9.6 second summary rate to a 48 second sample rate. All magnetic field measurements are given in nanoTesla (nT). The magnetic field data are calibrated (see the calibration description included in the Voyager 1 Magnetometer instrument catalog file for details). This data set supersedes VG1-S-MAG-4-48.0SEC.

One-minute Carter Coordinate Grid. The Carter coordinate system is a grid, based on latitude and longitude, used to locate oil and gas wells in Kentucky. The system was developed by the Carter Oil Company to mimic the township and range location system in areas that had not been surveyed. The State is divided into a regular grid with each cell (or quad) being five minutes of latitude by five minutes of longitude. These quads are assigned letters (equivalent of the township) beginning with A in the south and increasing through Z and AA to GG northward. The quads are assigned numbers (equivalent of the range) beginning with zero (0) in the west and increasing to 92 in the east. Each five-minute by five-minute quad is further subdivided into 25 one-minute by one-minute sections. Within the one-minute section, the location is pinpointed by specifying the distance from an adacent pair of one-minute section boundaries to the well. The Carter coordinate is written by specifying a pair of footages from the one-minute section boundaries and the reference boundary (north, south, east, or west) for each, the one-minute section number, the five-minutes quad letter, and the five-minute quad number. A Carter coordinate and topographic index map of Kentucky is available from Publication Sales at the Kentucky Geological Survey.Data Download: https://kgs.uky.edu/kgsweb/download/state/CARTER1.ZIP

This data set includes calibrated magnetic field data acquired by the Voyager 1 Low Field Magnetometer (LFM) during the Saturn encounter. Coverage begins in the solar wind inbound to Saturn and continues past the last outbound bowshock crossing. The data are in Kronographic (L1) coordinates and have been averaged from the 1.92 second summary rate to a 9.6 second sample rate. All magnetic field measurements are given in nanoTesla (nT). The magnetic field data are calibrated (see the calibration description included in the Voyager 1 Magnetometer instrument catalog file for details).