In a GIS, the answer starts with a geographic coordinate system. Learn the fundamental concepts of geographic coordinate systems.Exercises can be completed with either ArcGIS Pro or ArcMap.

USGS is assessing the feasibility of map projections and grid systems for lunar surface operations. We propose developing a new Lunar Transverse Mercator (LTM), the Lunar Polar Stereographic (LPS), and the Lunar Grid Reference Systems (LGRS). We have also designed additional grids designed to NASA requirements for astronaut navigation, referred to as LGRS in Artemis Condensed Coordinates (ACC), but this is not released here. LTM, LPS, and LGRS are similar in design and use to the Universal Transverse Mercator (UTM), Universal Polar Stereographic (LPS), and Military Grid Reference System (MGRS), but adhere to NASA requirements. LGRS ACC format is similar in design and structure to historic Army Mapping Service Apollo orthotopophoto charts for navigation. The Lunar Transverse Mercator (LTM) projection system is a globalized set of lunar map projections that divides the Moon into zones to provide a uniform coordinate system for accurate spatial representation. It uses a transverse Mercator projection, which maps the Moon into 45 transverse Mercator strips, each 8°, longitude, wide. These transverse Mercator strips are subdivided at the lunar equator for a total of 90 zones. Forty-five in the northern hemisphere and forty-five in the south. LTM specifies a topocentric, rectangular, coordinate system (easting and northing coordinates) for spatial referencing. This projection is commonly used in GIS and surveying for its ability to represent large areas with high positional accuracy while maintaining consistent scale. The Lunar Polar Stereographic (LPS) projection system contains projection specifications for the Moon’s polar regions. It uses a polar stereographic projection, which maps the polar regions onto an azimuthal plane. The LPS system contains 2 zones, each zone is located at the northern and southern poles and is referred to as the LPS northern or LPS southern zone. LPS, like is equatorial counterpart LTM, specifies a topocentric, rectangular, coordinate system (easting and northing coordinates) for spatial referencing. This projection is commonly used in GIS and surveying for its ability to represent large polar areas with high positional accuracy, while maintaining consistent scale across the map region. LGRS is a globalized grid system for lunar navigation supported by the LTM and LPS projections. LGRS provides an alphanumeric grid coordinate structure for both the LTM and LPS systems. This labeling structure is utilized in a similar manner to MGRS. LGRS defines a global area grid based on latitude and longitude and a 25×25 km grid based on LTM and LPS coordinate values. Two implementations of LGRS are used as polar areas require a LPS projection and equatorial areas a transverse Mercator. We describe the difference in the techniques and methods report associated with this data release. Request McClernan et. al. (in-press) for more information. ACC is a method of simplifying LGRS coordinates and is similar in use to the Army Mapping Service Apollo orthotopophoto charts for navigation. These data will be released at a later date. Two versions of the shape files are provided in this data release, PCRS and Display only. See LTM_LPS_LGRS_Shapefiles.zip file. PCRS are limited to a single zone and are projected in either LTM or LPS with topocentric coordinates formatted in Eastings and Northings. Display only shapefiles are formatted in lunar planetocentric latitude and longitude, a Mercator or Equirectangular projection is best for these grids. A description of each grid is provided below: Equatorial (Display Only) Grids: Lunar Transverse Mercator (LTM) Grids: LTM zone borders for each LTM zone Merged LTM zone borders Lunar Polar Stereographic (LPS) Grids: North LPS zone border South LPS zone border Lunar Grid Reference System (LGRS) Grids: Global Areas for North and South LPS zones Merged Global Areas (8°×8° and 8°×10° extended area) for all LTM zones Merged 25km grid for all LTM zones PCRS Shapefiles:` Lunar Transverse Mercator (LTM) Grids: LTM zone borders for each LTM zone Lunar Polar Stereographic (LPS) Grids: North LPS zone border South LPS zone border Lunar Grid Reference System (LGRS) Grids: Global Areas for North and South LPS zones 25km Gird for North and South LPS zones Global Areas (8°×8° and 8°×10° extended area) for each LTM zone 25km grid for each LTM zone The rasters in this data release detail the linear distortions associated with the LTM and LPS system projections. For these products, we utilize the same definitions of distortion as the U.S. State Plane Coordinate System. Scale Factor, k - The scale factor is a ratio that communicates the difference in distances when measured on a map and the distance reported on the reference surface. Symbolically this is the ratio between the maps grid distance and distance on the lunar reference sphere. This value can be precisely calculated and is provided in their defining publication. See Snyder (1987) for derivation of the LPS scale factor. This scale factor is unitless and typically increases from the central scale factor k_0, a projection-defining parameter. For each LPS projection. Request McClernan et. al., (in-press) for more information. Scale Error, (k-1) - Scale-Error, is simply the scale factor differenced from 1. Is a unitless positive or negative value from 0 that is used to express the scale factor’s impact on position values on a map. Distance on the reference surface are expended when (k-1) is positive and contracted when (k-1) is negative. Height Factor, h_F - The Height Factor is used to correct for the difference in distance caused between the lunar surface curvature expressed at different elevations. It is expressed as a ratio between the radius of the lunar reference sphere and elevations measured from the center of the reference sphere. For this work, we utilized a radial distance of 1,737,400 m as recommended by the IAU working group of Rotational Elements (Archinal et. al., 2008). For this calculation, height factor values were derived from a LOLA DEM 118 m v1, Digital Elevation Model (LOLA Science Team, 2021). Combined Factor, C_F – The combined factor is utilized to “Scale-To-Ground” and is used to adjust the distance expressed on the map surface and convert to the position on the actual ground surface. This value is the product of the map scale factor and the height factor, ensuring the positioning measurements can be correctly placed on a map and on the ground. The combined factor is similar to linear distortion in that it is evaluated at the ground, but, as discussed in the next section, differs numerically. Often C_F is scrutinized for map projection optimization. Linear distortion, δ - In keeping with the design definitions of SPCS2022 (Dennis 2023), we refer to scale error when discussing the lunar reference sphere and linear distortion, δ, when discussing the topographic surface. Linear distortion is calculated using C_F simply by subtracting 1. Distances are expended on the topographic surface when δ is positive and compressed when δ is negative. The relevant files associated with the expressed LTM distortion are as follows. The scale factor for the 90 LTM projections: LUNAR_LTM_GLOBAL_PLOT_HEMISPHERES_distortion_K_grid_scale_factor.tif Height Factor for the LTM portion of the Moon: LUNAR_LTM_GLOBAL_PLOT_HEMISPHERES_distortion_EF_elevation_factor.tif Combined Factor in LTM portion of the Moon LUNAR_LTM_GLOBAL_PLOT_HEMISPHERES_distortion_CF_combined_factor.tif The relevant files associated with the expressed LPS distortion are as follows. Lunar North Pole The scale factor for the northern LPS zone: LUNAR_LGRS_NP_PLOT_LPS_K_grid_scale_factor.tif Height Factor for the north pole of the Moon: LUNAR_LGRS_NP_PLOT_LPS_EF_elevation_factor.tif Combined Factor for northern LPS zone: LUNAR_LGRS_NP_PLOT_LPS_CF_combined_factor.tif Lunar South Pole Scale factor for the northern LPS zone: LUNAR_LGRS_SP_PLOT_LPS_K_grid_scale_factor.tif Height Factor for the south pole of the Moon: LUNAR_LGRS_SP_PLOT_LPS_EF_elevation_factor.tif Combined Factor for northern LPS zone: LUNAR_LGRS_SP_PLOT_LPS_CF_combined_factor.tif For GIS utilization of grid shapefiles projected in Lunar Latitude and Longitude, referred to as “Display Only”, please utilize a registered lunar geographic coordinate system (GCS) such as IAU_2015:30100 or ESRI:104903. LTM, LPS, and LGRS PCRS shapefiles utilize either a custom transverse Mercator or polar Stereographic projection. For PCRS grids the LTM and LPS projections are recommended for all LTM, LPS, and LGRS grid sizes. See McClernan et. al. (in-press) for such projections. Raster data was calculated using planetocentric latitude and longitude. A LTM and LPS projection or a registered lunar GCS may be utilized to display this data. Note: All data, shapefiles and rasters, require a specific projection and datum. The projection is recommended as LTM and LPS or, when needed, IAU_2015:30100 or ESRI:104903. The datum utilized must be the Jet Propulsion Laboratory (JPL) Development Ephemeris (DE) 421 in the Mean Earth (ME) Principal Axis Orientation as recommended by the International Astronomy Union (IAU) (Archinal et. al., 2008).

Contains NY State Plane Coordinate System Zones. For use to see what State Plane Zone in New York of an area you are working in is.Please contact NYS ITS Geospatial Services at nysgis@its.ny.gov if you have any questions

The purpose of creating and utilizing a road spatial data standard is to consolidate road spatial data and integrate the existing feature attribute information into a national database for reporting, planning, analysis and sharing purposes.

The primary benefit of using the road spatial data standard remains the organization and documentation of road data to allow users to share spatial data between parks, regions, programs, other federal agencies, and the public, at the national level.

This dataset contains a variety of spatial data layers compiled in support of research activities associated with the NAME research program. With a few exception the data layers have each been imported and projected to a common geographic coordinate system into the ESRI ArcGIS geographical information system. This dataset is one large (550 MB) gzipped tar file.

The National Park Service Building Spatial Data Standard is intended to provide a framework for organizing our building point and polygon spatial data, documenting its lineage, and facilitating data integration as well as data sharing. The standards will help ensure spatial data consistency, quality, and accuracy and will assist in program direction, reporting, and information requests.

This feature class contains lines representing formal and informal trails as well as routes within and across National Park Units. This dataset uses a set of core attributes designed by the NPS enterprise geospatial committee.

New Parking Citations dataset here: https://data.lacity.org/Transportation/Parking-Citations/4f5p-udkv/about_data ---Archived as of September 2023--- Parking citations with latitude / longitude (XY) in US Feet coordinates according to the California State Plane Coordinate System - Zone 5 (https://www.conservation.ca.gov/cgs/rgm/state-plane-coordinate-system). For more information on Geographic vs Projected coordinate systems, read here: https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/gcs_vs_pcs/ For information on how to change map projections, read here: https://learn.arcgis.com/en/projects/make-a-web-map-without-web-mercator/

Discover the booming Vertical Coordinate System market! Learn about its $500 million (2025 est.) size, 7% CAGR, key drivers, restraints, and top players like Esri. Explore market trends and projections to 2033 in this comprehensive analysis.

Tacoma 1990 - USGS 1 meter Aerials for ArcGIS Online/Bing Maps/Google Maps, etc. This layer includes UP, Fircrest, Fife, and some of Federal Way.Contact Info: Name: GIS Team Email: GISteam@cityoftacoma.orgCompany: U.S. Geological SurveyFlight Time: July, 1990Metadata (Internal use only)Earth Explorer Full Display of Record 1 (Internal use only)Original ArcGIS coordinate system: Type: Projected Geographic coordinate reference: GCS_North_American_1983_HARN Projection: NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet Well-known identifier: 2927Geographic extent - Bounding rectangle: West longitude: -122.632392 East longitude: -122.304303 North latitude: 47.380453 South latitude: 47.118196Extent in the item's coordinate system: West longitude: 1112120.835383 East longitude: 1191291.333557 South latitude: 658000.509741 North latitude: 751710.870268

Puyallup River 1940 - 3 foot Aerials for ArcGIS Online/Bing Maps/Google Maps, etc.Contact Info: Name: GIS Team Email: GISteam@cityoftacoma.orgCompany: Army Corps of EngineersScale: Approx. 1:15,000Puget Sound River History Project - Version 1Puget Sound River History Project - Version 2MetadataOriginal ArcGIS coordinate system: Type: Projected Geographic coordinate reference: GCS_North_American_1983_HARN Projection: NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet Well-known identifier: 2927Geographic extent - Bounding rectangle: West longitude: -122.508957 East longitude: -122.305211 North latitude: 47.377456 South latitude: 47.121285Extent in the item's coordinate system: West longitude: 1142687.587301 East longitude: 1191072.715539 South latitude: 658328.705521 North latitude: 750622.583189

Question Paper Solutions of chapter Database and Coordinate System of GIS & Remote Sensing, 8th Semester , Civil Engineering

Summary

Rail Crossings is a spatial file maintained by the Federal Railroad Administration (FRA) for use by States and railroads.

Description

FRA Grade Crossings is a spatial file that originates from the National Highway-Rail Crossing, Inventory Program. The program is to provide information to Federal, State, and local governments, as well as the railroad industry for the improvements of safety at highway-rail crossing.

Credits

Federal Railroad Administration (FRA)

Use limitations

There are no access and use limitations for this item.

Extent

West -79.491008 East -75.178954 North 39.733500 South 38.051719

Scale Range Maximum (zoomed in) 1:5,000 Minimum (zoomed out) 1:150,000,000

ArcGIS Metadata ▼►Topics and Keywords ▼►Themes or categories of the resource  transportation

* Content type  Downloadable Data Export to FGDC CSDGM XML format as Resource Description No

Temporal keywords  2013

Theme keywords  Rail

Theme keywords  Grade Crossing

Theme keywords  Rail Crossings

Citation ▼►Title rr_crossings Creation date 2013-03-15 00:00:00

Presentation formats  * digital map

Citation Contacts ▼►Responsible party  Individual's name Raquel Hunt Organization's name Federal Railroad Administration (FRA) Contact's position GIS Program Manager Contact's role  custodian

Responsible party  Organization's name Research and Innovative Technology Administration/Bureau of Transportation Statistics Individual's name National Transportation Atlas Database (NTAD) 2013 Contact's position Geospatial Information Systems Contact's role  distributor

Contact information  ▼►Phone  Voice 202-366-DATA

Address  Type  Delivery point 1200 New Jersey Ave. SE City Washington Administrative area DC Postal code 20590 e-mail address answers@BTS.gov

Resource Details ▼►Dataset languages  * English (UNITED STATES) Dataset character set  utf8 - 8 bit UCS Transfer Format

Spatial representation type  * vector

* Processing environment Microsoft Windows 7 Version 6.1 (Build 7600) ; Esri ArcGIS 10.2.0.3348

Credits Federal Railroad Administration (FRA)

ArcGIS item properties  * Name USDOT_RRCROSSINGS_MD * Size 0.047 Location withheld * Access protocol Local Area Network

Extents ▼►Extent  Geographic extent  Bounding rectangle  Extent type  Extent used for searching * West longitude -79.491008 * East longitude -75.178954 * North latitude 39.733500 * South latitude 38.051719 * Extent contains the resource Yes

Extent in the item's coordinate system  * West longitude 611522.170675 * East longitude 1824600.445629 * South latitude 149575.449134 * North latitude 752756.624659 * Extent contains the resource Yes

Resource Points of Contact ▼►Point of contact  Individual's name Raquel Hunt Organization's name Federal Railroad Administration (FRA) Contact's position GIS Program Manager Contact's role  custodian

Resource Maintenance ▼►Resource maintenance  Update frequency  annually

Resource Constraints ▼►Constraints  Limitations of use There are no access and use limitations for this item.

Spatial Reference ▼►ArcGIS coordinate system  * Type Projected * Geographic coordinate reference GCS_North_American_1983_HARN * Projection NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet * Coordinate reference details  Projected coordinate system  Well-known identifier 2893 X origin -120561100 Y origin -95444400 XY scale 36953082.294548117 Z origin -100000 Z scale 10000 M origin -100000 M scale 10000 XY tolerance 0.0032808333333333331 Z tolerance 0.001 M tolerance 0.001 High precision true Latest well-known identifier 2893 Well-known text PROJCS["NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1312333.333333333],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-77.0],PARAMETER["Standard_Parallel_1",38.3],PARAMETER["Standard_Parallel_2",39.45],PARAMETER["Latitude_Of_Origin",37.66666666666666],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2893]]

Reference system identifier  * Value 2893 * Codespace EPSG * Version 8.1.1

Spatial Data Properties ▼►Vector  ▼►* Level of topology for this dataset  geometry only

Geometric objects  Feature class name USDOT_RRCROSSINGS_MD * Object type  point * Object count 1749

ArcGIS Feature Class Properties  ▼►Feature class name USDOT_RRCROSSINGS_MD * Feature type Simple * Geometry type Point * Has topology FALSE * Feature count 1749 * Spatial index TRUE * Linear referencing FALSE

Data Quality ▼►Scope of quality information  ▼►Resource level  attribute Scope description  Attributes The States and railroads maintain their own file and get updated to the FRA. The information is reported to the FRA on the U.S. DOT-ARR Crossing inventory form.

Attributes The quality of the inventory can vary because a record of grade crossing location is being maintained by each state and railroad that is responsible for maintaining its respective information.

Lineage ▼►Lineage statement The data was downloaded from the HWY-Rail Crossing Inventory Files. All crossings that were closed or abandon were queried out of the data. All of the crossings with a zero within the latitude or longitude were queried out. Any crossing outside a bounding box of box ((Latitude >= 18 & Latitude <= 72) AND (Longitude >= -171 & Longitude <= -63)) were queried out.

Geoprocessing history ▼►Process  Date 2013-08-14 10:41:15 Tool location c:\program files (x86)\arcgis\desktop10.0\ArcToolbox\Toolboxes\Data Management Tools.tbx\Project Command issued Project RR_CROSSINGS_MD_USDOT \shagbfs\gis_projects\Railroad_Crossings_MD\Railroad_Crossings_MD.gdb\RR_CROSSINGS_MD_USDOT_83FTHARN PROJCS['NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet',GEOGCS['GCS_North_American_1983_HARN',DATUM['D_North_American_1983_HARN',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Lambert_Conformal_Conic'],PARAMETER['False_Easting',1312333.333333333],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-77.0],PARAMETER['Standard_Parallel_1',38.3],PARAMETER['Standard_Parallel_2',39.45],PARAMETER['Latitude_Of_Origin',37.66666666666666],UNIT['Foot_US',0.3048006096012192]] WGS_1984_(ITRF00)_To_NAD_1983_HARN GEOGCS['GCS_WGS_1984',DATUM['D_WGS_1984',SPHEROID['WGS_1984',6378137.0,298.25722356]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]] Include in lineage when exporting metadata No

Distribution ▼►Distributor  ▼►Contact information  Individual's name Office of Geospatial Information Systems Organization's name Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) Contact's role  distributor

Contact information  ▼►Phone  Voice 202-366-DATA

Address  Type  Delivery point 1200 New Jersey Ave. SE City Washington Administrative area DC Postal code 20590 Country US e-mail address answers@bts.gov

Available format  Name Shapefile Version 2013 File decompression technique no compression applied

Ordering process  Instructions Call (202-366-DATA), or E-mail (answers@bts.gov) RITA/BTS to request the National Transportation Atlas Databases (NTAD) 2013 DVD. The NTAD DVD can be ordered from the online bookstore at www.bts.gov. Individual datasets from the NTAD can also be downloaded from the Office of Geospatial Information Systems website at http://www.bts.gov/programs/geographic_information_services/

Transfer options  Transfer size 6.645

Medium of distribution  Medium name  DVD

How data is written  iso9660 (CD-ROM) Recording density 650 Density units of measure Megabytes

Transfer options  Online source  Description  National Transportation Atlas Databases (NTAD) 2013

Distribution format  * Name Shapefile Version 2013

Transfer options  * Transfer size 0.047

Online source  Location http://www.bts.gov/programs/geographic_information_services/

Fields ▼►Details for object USDOT_RRCROSSINGS_MD ▼►* Type Feature Class * Row count 1749

Field FID ▼►* Alias FID * Data type OID * Width 4 * Precision 0 * Scale 0 * Field description Internal feature number.

* Description source ESRI

* Description of values Sequential unique whole numbers that are automatically generated.

Field Shape ▼►* Alias Shape * Data type Geometry * Width 0 * Precision 0 * Scale 0 * Field description Feature geometry.

* Description source ESRI

* Description of values Coordinates defining the features.

Field OBJECTID ▼►* Alias OBJECTID * Data type Integer * Width 9 * Precision 9 * Scale 0

Field CROSSING ▼►* Alias CROSSING * Data type String * Width 7 * Precision 0 * Scale 0 Field description US DOT Valid Crossing ID Number

Description source FRA

Field RAILROAD ▼►* Alias RAILROAD * Data type String * Width 4 * Precision 0 * Scale 0 Field description The

Puget Sound 2002 - 1 foot Aerials for ArcGIS Online/Bing Maps/Google Maps, etc. Includes areas north to Everett; east to Monroe, Sammamish, and Buckley; west to Vashon, Bremerton, and Gig Harbor; South to Roy.Contact Info: Name: GIS Team Email: GISteam@cityoftacoma.orgCompany: Triathlon, Inc.Flight Date: June, 2002Original ArcGIS coordinate system: Type: Projected Geographic coordinate reference: GCS_North_American_1983_HARN Projection: NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet Well-known identifier: 2927Geographic extent - Bounding rectangle: West longitude: -122.695504 East longitude: -121.932319 North latitude: 48.027739 South latitude: 46.980475Extent in the item's coordinate system: West longitude: 1103000.000000 East longitude: 1283000.000000 South latitude: 608000.000000 North latitude: 986000.000000

Service Area 2005 - 6 inch Aerials for ArcGIS Online/Bing Maps/Google Maps, etc.Coverage area includes Gig Harbor, Fox Island, McNeil Island, Anderson Island, and more land to the west and north.Contact Info: Name: GIS Team Email: GISteam@cityoftacoma.orgPhotos supplied by Mapcon Mapping.Photos taken in July, 2005.Original ArcGIS coordinate system: Type: Projected Geographic coordinate reference: GCS_North_American_1983_HARN Projection: NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet Well-known identifier: 2927Geographic extent - Bounding rectangle: West longitude: -122.852199 East longitude: -121.962361 North latitude: 47.418869 South latitude: 46.754961Extent in the item's coordinate system: West longitude: 1058000.000000 East longitude: 1274000.000000 South latitude: 527000.000000 North latitude: 764000.000000

U.S. State Plane Zones (NAD 1983) represents the State Plane Coordinate System (SPCS) Zones for the 1983 North American Datum within United States.

Several State Plane Coordinate System zones are not shown in this dataset, including Puerto Rico, the U.S. Virgin Islands, American Samoa, Guam, and Louisiana's offshore zone.

This guidance note concerns the management of spatial data for UK Continental Shelf (UKCS) petroleum operations.

USNG is standard that established a nationally consistent grid reference system. It provides a seamless plane coordinate system across jurisdictional boundaries and map scales; it enables precise position referencing with GPS, web map portals, and hardcopy maps. USNG enables a practical system of geo-addresses and a universal map index. This data resides in the GCS 1983 coordinate system and is most suitable for viewing over North America. This layer shows 100-meter grid squares.

USGS is assessing the feasibility of map projections and grid systems for lunar surface operations. We propose developing a new Lunar Transverse Mercator (LTM), the Lunar Polar Stereographic (LPS), and the Lunar Grid Reference Systems (LGRS). We have also designed additional grids designed to NASA requirements for astronaut navigation, referred to as LGRS in Artemis Condensed Coordinates (ACC). This data release includes LGRS grids finer than 25km (1km, 100m, and 10m) in ACC format. LTM, LPS, and LGRS grids are not released here but may be acceded from https://doi.org/10.5066/P13YPWQD. LTM, LPS, and LGRS are similar in design and use to the Universal Transverse Mercator (UTM), Universal Polar Stereographic (LPS), and Military Grid Reference System (MGRS), but adhere to NASA requirements. LGRS ACC format is similar in design and structure to historic Army Mapping Service Apollo orthotopophoto charts for navigation. The Lunar Transverse Mercator (LTM) projection system is a globalized set of lunar map projections that divides the Moon into zones to provide a uniform coordinate system for accurate spatial representation. It uses a Transverse Mercator projection, which maps the Moon into 45 transverse Mercator strips, each 8°, longitude, wide. These Transverse Mercator strips are subdivided at the lunar equator for a total of 90 zones. Forty-five in the northern hemisphere and forty-five in the south. LTM specifies a topocentric, rectangular, coordinate system (easting and northing coordinates) for spatial referencing. This projection is commonly used in GIS and surveying for its ability to represent large areas with high positional accuracy while maintaining consistent scale. The Lunar Polar Stereographic (LPS) projection system contains projection specifications for the Moon’s polar regions. It uses a polar stereographic projection, which maps the polar regions onto an azimuthal plane. The LPS system contains 2 zones, each zone is located at the northern and southern poles and is referred to as the LPS northern or LPS southern zone. LPS, like its equatorial counterpart LTM, specifies a topocentric, rectangular, coordinate system (easting and northing coordinates) for spatial referencing. This projection is commonly used in GIS and surveying for its ability to represent large polar areas with high positional accuracy while maintaining consistent scale across the map region. LGRS is a globalized grid system for lunar navigation supported by the LTM and LPS projections. LGRS provides an alphanumeric grid coordinate structure for both the LTM and LPS systems. This labeling structure is utilized similarly to MGRS. LGRS defines a global area grid based on latitude and longitude and a 25×25 km grid based on LTM and LPS coordinate values. Two implementations of LGRS are used as polar areas require an LPS projection and equatorial areas a Transverse Mercator. We describe the differences in the techniques and methods reported in this data release. Request McClernan et. al. (in-press) for more information. ACC is a method of simplifying LGRS coordinates and is similar in use to the Army Mapping Service Apollo orthotopophoto charts for navigation. These grids are designed to condense a full LGRS coordinate to a relative coordinate of 6 characters in length. LGRS in ACC format is completed by imposing a 1km grid within the LGRS 25km grid, then truncating the grid precision to 10m. To me the character limit, a coordinate is reported as a relative value to the lower-left corner of the 25km LGRS zone without the zone information; However, zone information can be reported. As implemented, and 25km^2 area on the lunar surface will have a set of a unique set of ACC coordinates to report locations The shape files provided in this data release are projected in the LTM or LPS PCRSs and must utilize these projections to be dimensioned correctly. LGRS ACC Grids Files and Resolution: LGRS ACC Grids in LPS portion: Amundsen_Rim 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Nobile_Rim_2 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Haworth 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Faustini_Rim_A 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile de_Gerlache_Rim_2 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Connecting_Ridge_Extension 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Connecting_Ridge 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Nobile_Rim_1 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Peak_Near_Shackleton 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile de_Gerlache_Rim' 'Leibnitz_Beta_Plateau 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Malapert_Massif 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile de_Gerlache-Kocher_Massif 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile LGRS ACC Grids in LTM portion: Apollo_11 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Apollo_12 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Apollo_14 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Apollo_15 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Apollo_16 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile Apollo_17 1km Grid Shapefile 100m Grid Shapefile 10m Grid Shapefile LTM, LPS, and LGRS PCRS shapefiles utilize either a custom transverse Mercator or polar Stereographic projection. For PCRS grids the LTM and LPS projections are recommended for all LTM, LPS, and LGRS grid sizes. See McClernan et. al. (in-press) for such projections. For GIS utilization of grid shapefiles projected in Lunar Latitude and Longitude should utilize a registered lunar geographic coordinate system (GCS) such as IAU_2015:30100 or ESRI:104903. This only applies to grids that cross multiple LTM zones. Note: All data, shapefiles require a specific projection and datum. The projection is recommended as LTM and LPS or, when needed, IAU_2015:30100 or ESRI:104903. The datum utilized must be the Jet Propulsion Laboratory (JPL) Development Ephemeris (DE) 421 in the Mean Earth (ME) Principal Axis Orientation as recommended by the International Astronomy Union (IAU) (Archinal et. al., 2008).

**THIS NEWER 2016 DIGITAL MAP REPLACES THE OLDER 2014 VERSION OF THE GRI GATE Geomorphological-GIS data. The Unpublished Digital Pre-Hurricane Sandy Geomorphological-GIS Map of the Gateway National Recreation Area: Sandy Hook, Jamaica Bay and Staten Island Units, New Jersey and New York is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (gate_geomorphology.gdb), a 10.1 ArcMap (.MXD) map document (gate_geomorphology.mxd), individual 10.1 layer (.LYR) files for each GIS data layer, an ancillary map information (.PDF) document (gate_geomorphology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.TXT) and FAQ (.HTML) formats, and a GIS readme file (gate_gis_readme.pdf). Please read the gate_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O’Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. Google Earth software is available for free at: http://www.google.com/earth/index.html. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Rutgers University Institute of Marine and Coastal Sciences. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (gate_metadata_faq.html; available at http://nrdata.nps.gov/geology/gri_data/gis/gate/gate_pre-sandy_metadata_faq.html). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:6,000 and United States National Map Accuracy Standards features are within (horizontally) 5.08 meters or 16.67 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 18N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Gateway National Recreation Area.