Facebook
TwitterSummary
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
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
This feature class is a derivative of the 2012 planimetric water layer. It was Generalized using the Cartographic Generalization tool, Simplify Polygon with the Bend Simplify option and a Minimal Allowable Offset tolerance of 5 feet. A collection of vector polygon features for water bodies within the Urban Development Boundary (UDB) and outside the UDB, approximately 938 square miles. The planimetric layer for Miami-Dade County was previously updated in 2007 by Woolpert. Aerial Cartographics of America's update is comprised of two individual updates: inside the UDB (542 square miles) performed using a on-screen/2D digitizing of the 2012 orthophotography captured by PhotoScience; and outside of the UDB (396 square miles) using on-screen/2D digitizing of the 2012 orthophotography captured by PhotoScience. Personnel that collected this data are either photogrammetrists trained in stereo collection or editors trained in ortho-photography based collection. Items included in the feature class: WATER BODIES (Polygons) Water lines and water under the bridge. Definition of particular fields in the Water feature class: Water = {0,1} where 0 = Feature does not represent water; 1 = Water feature. Type = {'', 'B'} where B = Water under the bridge. Possible combinations of these fields are: 0,''; 1,'';1, 'B'Updated: Biennially The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
This feature class is a derivative of the 2012 planimetric water layer. It was Generalized using the Cartographic Generalization tool, Simplify Polygon with the Bend Simplify option and a Minimal Allowable Offset tolerance of 5 feet. Additionally the land feature(s) was removed. A collection of vector polygon features for water bodies within the Urban Development Boundary (UDB) and outside the UDB, approximately 938 square miles. The planimetric layer for Miami-Dade County was previously updated in 2007 by Woolpert. Aerial Cartographics of America's update is comprised of two individual updates: inside the UDB (542 square miles) performed using a on-screen/2D digitizing of the 2012 orthophotography captured by PhotoScience; and outside of the UDB (396 square miles) using on-screen/2D digitizing of the 2012 orthophotography captured by PhotoScience. Personnel that collected this data are either photogrammetrists trained in stereo collection or editors trained in ortho-photography based collection. Items included in the feature class: WATER BODIES (Polygons) Water lines and water under the bridge. Definition of particular fields in the Water feature class: Water = {0,1} where 0 = Feature does not represent water; 1 = Water feature. Type = 'C' = canal, 'L' = Lake and 'B' = BayUpdated: Biennially The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere
Facebook
TwitterThe Federal Emergency Management Agency (FEMA) produces Flood Insurance Rate maps and identifies Special Flood Hazard Areas as part of the National Flood Insurance Program's floodplain management. Special Flood Hazard Areas have regulations that include the mandatory purchase of flood insurance for holders of federally regulated mortgages. In addition, this layer can help planners and firms avoid areas of flood risk and also avoid additional cost to carry insurance for certain planned activities. Dataset SummaryPhenomenon Mapped: Flood Hazard AreasGeographic Extent: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Mariana Islands and American Samoa.Projection: Web Mercator Auxiliary SphereData Coordinate System: USA Contiguous Albers Equal Area Conic USGS version (contiguous US, Puerto Rico, US Virgin Islands), WGS 1984 Albers (Alaska), Hawaii Albers Equal Area Conic (Hawaii), Western Pacific Albers Equal Area Conic (Guam, Northern Mariana Islands, and American Samoa)Cell Sizes: 10 meters (default), 30 meters, and 90 metersUnits: NoneSource Type: ThematicPixel Type: Unsigned integerSource: Federal Emergency Management Agency (FEMA)Update Frequency: AnnualPublication Date: May 7, 2025 This layer is derived from the May 7, 2025 version Flood Insurance Rate Map feature class S_FLD_HAZ_AR. The vector data were then flagged with an index of 94 classes, representing a unique combination of values displayed by three renderers. (In three resolutions the three renderers make nine processing templates.) Repair Geometry was run on the set of features, then the features were rasterized using the 94 class index at a resolutions of 10, 30, and 90 meters, using the Polygon to Raster tool and the "MAXIMUM_COMBINED_AREA" option. Not every part of the United States is covered by flood rate maps. This layer compiles all the flood insurance maps available at the time of publication. To make analysis easier, areas that were NOT mapped by FEMA for flood insurance rates no longer are served as NODATA but are filled in with a value of 250, representing any unmapped areas which appear in the US Census boundary of the USA states and territories. The attribute table corresponding to value 250 will indicate that the area was not mapped.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application. Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "flood hazard areas" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "flood hazard areas" in the search box, browse to the layer then click OK. In ArcGIS Pro you can use the built-in raster functions to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro. The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one. Processing TemplatesCartographic Renderer - The default. These are meaningful classes grouped by FEMA which group its own Flood Zone Type and Subtype fields. This renderer uses FEMA's own cartographic interpretations of its flood zone and zone subtype fields to help you identify and assess risk. Flood Zone Type Renderer - Specifically renders FEMA FLD_ZONE (flood zone) attribute, which distinguishes the original, broadest categories of flood zones. This renderer displays high level categories of flood zones, and is less nuanced than the Cartographic Renderer. For example, a fld_zone value of X can either have moderate or low risk depending on location. This renderer will simply render fld_zone X as its own color without identifying "500 year" flood zones within that category.Flood Insurance Requirement Renderer - Shows Special Flood Hazard Area (SFHA) true-false status. This may be helpful if you want to show just the places where flood insurance is required. A value of True means flood insurance is mandatory in a majority of the area covered by each 10m pixel. Each of these three renderers have templates at three different raster resolutions depending on your analysis needs. To include the layer in web maps to serve maps and queries, the 10 meter renderers are the preferred option. These are served with overviews and render at all resolutions. However, when doing analysis of larger areas, we now offer two coarser resolutions of 30 and 90 meters in processing templates for added convenience and time savings.Data DictionaryMaking a copy of your area of interest using copyraster in arcgis pro will copy the layer's attribute table to your network alongside the local output raster. The raster attribute table in the copied raster will contain the flood zone, zone subtype, and special flood hazard area true/false flag which corresponds to each value in the layer for your area of interest. For your convienence, we also included a table in CSV format in the box below as a data dictionary you can use as an index to every value in the layer. Value,FLD_ZONE,ZONE_SUBTY,SFHA_TF 2,A,, 3,A,,F 4,A,,T 5,A,,T 6,A,,T 7,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 8,A,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 9,A,ADMINISTRATIVE FLOODWAY,T 10,A,COASTAL FLOODPLAIN,T 11,A,FLOWAGE EASEMENT AREA,T 12,A99,,T 13,A99,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 14,AE,,F 15,AE,,T 16,AE,,T 17,AE,,T 18,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,T 19,AE,1 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,T 20,AE,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",T 21,AE,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",T 22,AE,ADMINISTRATIVE FLOODWAY,T 23,AE,AREA OF SPECIAL CONSIDERATION,T 24,AE,COASTAL FLOODPLAIN,T 25,AE,COLORADO RIVER FLOODWAY,T 26,AE,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 27,AE,COMMUNITY ENCROACHMENT,T 28,AE,COMMUNITY ENCROACHMENT AREA,T 29,AE,DENSITY FRINGE AREA,T 30,AE,FLOODWAY,T 31,AE,FLOODWAY CONTAINED IN CHANNEL,T 32,AE,FLOODWAY CONTAINED IN STRUCTURE,T 33,AE,FLOWAGE EASEMENT AREA,T 34,AE,RIVERINE FLOODWAY IN COMBINED RIVERINE AND COASTAL ZONE,T 35,AE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 36,AE,STATE ENCROACHMENT AREA,T 37,AH,,T 38,AH,,T 39,AH,FLOODWAY,T 40,AO,,T 41,AO,COASTAL FLOODPLAIN,T 42,AO,FLOODWAY,T 43,AREA NOT INCLUDED,,F 44,AREA NOT INCLUDED,,T 45,AREA NOT INCLUDED,,U 46,D,,F 47,D,,T 48,D,AREA WITH FLOOD RISK DUE TO LEVEE,F 49,OPEN WATER,,F 50,OPEN WATER,,T 51,OPEN WATER,,U 52,V,,T 53,V,COASTAL FLOODPLAIN,T 54,VE,,T 55,VE,,T 56,VE,COASTAL FLOODPLAIN,T 57,VE,RIVERINE FLOODWAY SHOWN IN COASTAL ZONE,T 58,X,,F 59,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,F 60,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,T 61,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD,U 62,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN CHANNEL,F 63,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD CONTAINED IN STRUCTURE,F 64,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COASTAL ZONE,F 65,X,0.2 PCT ANNUAL CHANCE FLOOD HAZARD IN COMBINED RIVERINE AND COASTAL ZONE,F 66,X,"1 PCT CONTAINED IN STRUCTURE, COMMUNITY ENCROACHMENT",F 67,X,"1 PCT CONTAINED IN STRUCTURE, FLOODWAY",F 68,X,1 PCT DEPTH LESS THAN 1 FOOT,F 69,X,1 PCT DRAINAGE AREA LESS THAN 1 SQUARE MILE,F 70,X,1 PCT FUTURE CONDITIONS,F 71,X,1 PCT FUTURE CONDITIONS CONTAINED IN STRUCTURE,F 72,X,"1 PCT FUTURE CONDITIONS, COMMUNITY ENCROACHMENT",F 73,X,"1 PCT FUTURE CONDITIONS, FLOODWAY",F 74,X,"1 PCT FUTURE IN STRUCTURE, COMMUNITY ENCROACHMENT",F 75,X,"1 PCT FUTURE IN STRUCTURE, FLOODWAY",F 76,X,AREA OF MINIMAL FLOOD HAZARD, 77,X,AREA OF MINIMAL FLOOD HAZARD,F 78,X,AREA OF MINIMAL FLOOD HAZARD,T 79,X,AREA OF MINIMAL FLOOD HAZARD,U 80,X,AREA OF SPECIAL CONSIDERATION,F 81,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,F 82,X,AREA WITH REDUCED FLOOD RISK DUE TO LEVEE,T 83,X,FLOWAGE EASEMENT AREA,F 84,X,1 PCT FUTURE CONDITIONS,T 85,AH,COASTAL FLOODPLAIN,T 86,AE,,U 87,AE,FLOODWAY,F 88,X,AREA WITH REDUCED FLOOD HAZARD DUE TO ACCREDITED LEVEE SYSTEM,F 89,X,530,F 90,VE,100,T 91,AE,100,T 92,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO LEVEE SYSTEM,T 93,A99,AREA WITH REDUCED FLOOD HAZARD DUE TO NON-ACCREDITED LEVEE SYSTEM,T 94,A,COMBINED RIVERINE AND COASTAL FLOODPLAIN,T 250,AREA NOT INCLUDED,Not Mapped by FEMA, Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Dataset description: This repository contains data pertaining to the manuscript "Mawrth Vallis, Mars, classified using the NOAH-H deep-learning terrain classification system." submitted to Journal of Maps. NOAH-H Mosaics: Mawrth_Vallis_NOAHH_Mosaic_DC_IG_25cm4bit_20230121_reclass.zip This folder contain mosaics of terrain classifications for Mawrth Vallis, Mars, made by the Novelty or Anomaly Hunter - HiRISE (NOAH-H) deep learning convolutional neural network developed for the European Space Agency (ESA) by SCISYS Ltd. In coordination with the Open University Planetary Environments Group. These folders contain the NOAH-H mosaics, as well as ancillary files needed to display the NOAH-H products in geographic information software (GIS). Included are two large raster datasets, containing the NOAH-H classification for the entire study area. One uses the 14 descriptive classes of the terrain, and the other with the five interpretative groups (Barrett et al., 2022). · Mawrth_Vallis_NOAHH_Mosaic_DC_25cm4bit_20230121_reclass.tif Contains the full 14 class “Descriptive Classes” (DC) dataset, reclassified so that pixel values reflect the original NOAH-H ontology, and not the priority rankings described in Wright et al., (2022) and Barrett et al., (2022b). It is accompanied by all auxiliary files required to view the data in GIS. · Mawrth_Vallis_NOAHH_Mosaic_IG_25cm4bit_20230121_reclass.tif Contains the 5 class “Interpretive Groups” (IG) dataset, reclassified so that pixel values reflect the original NOAH-H ontology, and not the priority rankings described in Wright et al., (2022) and Barrett et al., (2022b). It is accompanied by all auxiliary files required to view the data in GIS. Symbology layer files: NOAH-H_Symbology.zip This folder contains GIS layer file and colour map files for both the Descriptive Classes (DC) and interpretive Groups (IG) versions of the classification. These can be applied to the data using the symbology options in GIS. Georeferencing Control points: Mawrth_Vallis_Final_Control_Points.zip This file contains the control points used to georeferenced the 26 individual HiRISE images which make up the mosaic. These allow publicly available HiRISE images to be aligned to the terrain in Mawrth Vallis, and thus the NOAH-H Mosaic. Twenty-six 25 cm/pixel HiRISE images of Mawrth Vallis were used as input for NOAH-H. These are:
PSP_002140_2025_RED
PSP_002074_2025_RED
ESP_057351_2020_RED
ESP_053909_2025_RED
ESP_053698_2025_RED
ESP_052274_2025_RED
ESP_051931_2025_RED
ESP_051351_2025_RED
ESP_051219_2030_RED
ESP_050217_2025_RED
ESP_046960_2025_RED
ESP_046670_2025_RED
ESP_046525_2025_RED
ESP_046459_2025_RED
ESP_046314_2025_RED
ESP_045536_2025_RED
ESP_045114_2025_RED
ESP_044903_2025_RED
ESP_043782_2025_RED
ESP_043637_2025_RED
ESP_038758_2025_RED
ESP_037795_2025_RED
ESP_037294_2025_RED
ESP_036872_2025_RED
ESP_036582_2025_RED
ESP_035804_2025_RED NOAH-H produced corresponding 25 cm/pixel rasters where each pixel is assigned a terrain class based on the corresponding pixels in the input HiRISE image. To mosaic the NOAH-H rasters together, first the input HiRISE images were georeferenced to the HRSC basemap (HMC_11E10_co5) tile, using CTX images as an intermediate step. High order (spline, in ArcGIS Pro 3.0) transformations were used to make the HiRISE images georeference closely onto the target layers. Once the HiRISE images were georeferenced, the same control points and transformations were applied to the corresponding NOAH-H rasters. To mosaic the georeferenced NOAH-H rasters the pixel values for the classes needed to be changed so that more confidently identified, and more dangerous, classes made it into the mosaic (see dataset manuscript for details. To produce a HiRISE layer which fits the NOAH-H classification, download one of the listed HiRISE images from https://www.uahirise.org/, Select the corresponding control point file from this archive and apply a spline transformation through the GIS georeferencing toolbar. Manually Mapped Aeolian Bedforms: Mawrth_Manual_TARs.zip The manually mapped data was produced by Fawdon, independently of the NOAH-H project, as an assessment of “Aeolian Hazard” at Mawrth Vallis. This was done to inform the ExoMars landing site selection process. This file contains two GIS shape files, containing the manually mapped bedforms for both the entire mapping area, and the HiRISE image ESP_046459_2025_RED where the two datasets were compared on a pixel scale. The full manual map is offset slightly from the NOAH-H, since it was digitised from bespoke HiRISE orthomosaics, rather than from the publicly available HiRISE Red band images. It is suitable for comparison to the NOAH-H data with 100m-1km aggregation as in figure 8 of the associated paper. It is not suitable for pixel scale comparison. The map of ESP_046459_2025_RED was manually georeferenced to the NOAH-H mosaic, allowing for direct pixel to pixel comparisons, as presented in figure 6 of the associated paper. Two GIS shape files are included: · Mawrth_Manual_TARs_ESP_046459_2025.shp · Mawrth_Manual_TARs_all.shp Containing the high fidelity data for ESP_046459_2025, and the medium fidelity data for the entire area respectively. The are accompanied by ancillary files needed to view them in GIS. Gridded Density Statistics This dataset contains gridded density maps of Transverse Aeolian Ridges and Boulders, as classified by the Novelty or Anomaly Hunter – HiRISE (NOAH-H). The area covered is the runner up candidate ExoMars landing site in Mawrth Vallis, Mars. These are the data shown in figures; 7, 8, and S1. Files are presented for every classified ripple and boulder class, as well as for thematic groups. These are presented as .shp GIS shapefiles, along with all auxiliary files required to view them in GIS. Gridded Density stats are available in two zip folders, one for NOAH-H predicted density, and one for manually mapped density. NOAH-H Predicted Density: Mawrth_NOAHH_1km_Grid_TAR_Boulder_Density.zip Individual classes are found in the files: · Mawrth_NOAHH_1km_Grid_8TARs.shp · Mawrth_NOAHH_1km_Grid_9TARs.shp · Mawrth_NOAHH_1km_Grid_11TARs.shp · Mawrth_NOAHH_1km_Grid_12TARs.shp · Mawrth_NOAHH_1km_Grid_13TARs.shp · Mawrth_NOAHH_1km_Grid_Boulders.shp Where the text following Grid denotes the NOAH-H classes represented, and the landform classified. E.g. 8TARs = NOAH-H TAR class 8. The following thematic groups are also included: · Mawrth_NOAHH_1km_Grid_8_11continuousTARs.shp · Mawrth_NOAHH_1km_Grid_12_13discontinuousTARs · Mawrth_NOAHH_1km_Grid_8_10largeTARs.shp · Mawrth_NOAHH_1km_Grid_11_13smallTARs.shp · Mawrth_NOAHH_1km_Grid_8_13AllTARs.shp When the numbers denote the range of NOAH-H classes which were aggregated to produce the map, followed by a description of the thematic group: “continuous”, “discontinuous”, “large”, “small”, “all”. Manually Mapped Density Plots: Mawrth_Manual_1km_Grid.zip These GIS shapefiles have the same format as the NOAH-H classified ones. Three datasets are presented for all TARs (“_allTARs”), Continuous TARs (“_con”) and Discontinuous TARs (“_dis”) · Mawrth_Manual_1km_Grid_AllTARs.shp · Mawrth_Manual_1km_Grid_Con.shp · Mawrth_Manual_1km_Grid_Dis.shp Related public datasets: The HiRISE images discussed in this work are publicly available from https://www.uahirise.org/. and are credited to NASA/JPL/University of Arizona. HRSC images are credited to the European Space Agency; Mars Express mission team, German Aerospace Center (DLR), and the Freie Universität Berlin (FUB). They are available at the ESA Planetary Science Archive (PSA) https://www.cosmos.esa.int/web/psa/mars-express and are used under the Creative Commons CC BY-SA 3.0 IGO licence. SPATIAL DATA COORDINATE SYSTEM INFORMATION All NOAH-H files and derivative density plots have the same projected coordinate system: “Equirectangular Mars” - Projection: Plate Carree - Sphere radius: 3393833.2607584 m SOFTWARE INFORMATION All GIS workflows (georeferencing, mosaicking) were conducted in ArcGIS Pro 3.0. NOAH-H is a deep learning semantic segmentation software developed by SciSys Ltd for the European Space Agency to aid preparation for the ExoMars rover mission.
Facebook
TwitterLast Revised: February 2016
Map Information
This nowCOAST™ time-enabled map service provides maps depicting the
latest global forecast guidance of water currents, water temperature, and
salinity at forecast projections: 0, 12, 24, 36, 48, 60, 72, 84, and 96-hours
from the NWS/NCEP Global Real-Time Ocean Forecast System (GRTOFS). The surface
water currents velocity maps display the direction using white or black
streaklets. The magnitude of the current is indicated by the length and width
of the streaklet. The maps of the GRTOFS surface forecast guidance are updated
on the nowCOAST™ map service once per day.
For more detailed information about layer update frequency and timing, please reference the
nowCOAST™ Dataset Update Schedule.
Background Information
GRTOFS is based on the Hybrid Coordinates Ocean Model (HYCOM), an eddy resolving, hybrid coordinate numerical ocean prediction model. GRTOFS has global coverge and a horizontal resolution of 1/12 degree and 32 hybrid vertical layers. It has one forecast cycle per day (i.e. 0000 UTC) which generates forecast guidance out to 144 hours (6 days). However, nowCOAST™ only provides guidance out to 96 hours (4 days). The forecast cycle uses 3-hourly momentum and radiation fluxes along with precipitation predictions from the NCEP Global Forecast System (GFS). Each forecast cycle is preceded with a 48-hr long nowcast cycle. The nowcast cycle uses daily initial 3-D fields from the NAVOCEANO operational HYCOM-based forecast system which assimilates situ profiles of temperature and salinity from a variety of sources and remotely sensed SST, SSH and sea-ice concentrations. GRTOFS was developed by NCEP/EMC/Marine Modeling and Analysis Branch. GRTOFS is run once per day (0000 UTC forecast cycle) on the NOAA Weather and Climate Operational Supercomputer System (WCOSS) operated by NWS/NCEP Central Operations.
The maps are generated using a visualization technique developed by the Data Visualization Research Lab at The University of New Hampshire's Center for Coastal and Ocean Mapping (http://www.ccom.unh.edu/vislab/). The method combines two techniques. First, equally spaced streamlines are computed in the flow field using Jobard and Lefer's (1977) algorithm. Second, a series of "streaklets" are rendered head to tail along each streamline to show the direction of flow. Each of these varies along its length in size, color and transparency using a method developed by Fowler and Ware (1989), and later refined by Mr. Pete Mitchell and Dr. Colin Ware (Mitchell, 2007).
Time Information
This map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.
In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.
This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.
This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.
When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.
Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:
Issue a returnUpdates=true request (ArcGIS REST protocol only)
for an individual layer or for the service itself, which will return
the current start and end times of available data, in epoch time format
(milliseconds since 00:00 January 1, 1970). To see an example, click on
the "Return Updates" link at the bottom of the REST Service page under
"Supported Operations". Refer to the
ArcGIS REST API Map Service Documentation
for more information.
Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against
the proper layer corresponding with the target dataset. For raster
data, this would be the "Image Footprints with Time Attributes" layer
in the same group as the target "Image" layer being displayed. For
vector (point, line, or polygon) data, the target layer can be queried
directly. In either case, the attributes returned for the matching
raster(s) or vector feature(s) will include the following:
validtime: Valid timestamp.
starttime: Display start time.
endtime: Display end time.
reftime: Reference time (sometimes referred to as
issuance time, cycle time, or initialization time).
projmins: Number of minutes from reference time to valid
time.
desigreftime: Designated reference time; used as a
common reference time for all items when individual reference
times do not match.
desigprojmins: Number of minutes from designated
reference time to valid time.
Query the nowCOAST™ LayerInfo web service, which has been created to
provide additional information about each data layer in a service,
including a list of all available "time stops" (i.e. "valid times"),
individual timestamps, or the valid time of a layer's latest available
data (i.e. "Product Time"). For more information about the LayerInfo
web service, including examples of various types of requests, refer to
the
nowCOAST™ LayerInfo Help Documentation
References
Fowler, D. and C. Ware, 1989: Strokes for Representing Vector Field Maps. Proceedings: Graphics Interface '98 249-253. Jobard, B and W. Lefer,1977: Creating evenly spaced streamlines of arbitrary density. Proceedings: Eurographics workshop on Visualization in Scientific Computing. 43-55. Mitchell, P.W., 2007: The Perceptual optimization of 2D Flow Visualizations Using Human in the Loop Local Hill Climbing. University of New Hampshire Masters Thesis. Department of Computer Science. NWS, 2013: About Global RTOFS, NCEP/EMC/MMAB, College Park, MD (Available at http://polar.ncep.noaa.gov/global/about/). Chassignet, E.P., H.E. Hurlburt, E.J. Metzger, O.M. Smedstad, J. Cummings, G.R. Halliwell, R. Bleck, R. Baraille, A.J. Wallcraft, C. Lozano, H.L. Tolman, A. Srinivasan, S. Hankin, P. Cornillon, R. Weisberg, A. Barth, R. He, F. Werner, and J. Wilkin, 2009: U.S. GODAE: Global Ocean Prediction with the HYbrid Coordinate Ocean Model (HYCOM). Oceanography, 22(2), 64-75. Mehra, A, I. Rivin, H. Tolman, T. Spindler, and B. Balasubramaniyan, 2011: A Real-Time Operational Global Ocean Forecast System, Poster, GODAE OceanView –GSOP-CLIVAR Workshop in Observing System Evaluation and Intercomparisons, Santa Cruz, CA.
Facebook
TwitterMap of Environmental Resource Permit boundaries or locations for the Florida Dept. Of Environmental Protection (FDEP) and the five Florida water management districts:Northwest Florida Water Management District (NWFWMD)South Florida Water Management District (SFWMD)Southwest Florida Water Management District (SWFWMD)St. Johns River Water Management District (SJRWMD)Suwannee River Water Management District (SRWMD) Clicking on a permit will present a pop-up with basic information for that permit. Additional information, including access to all permit-related documents, can be obtained by selecting the "More info" link in the pop-up.Boundaries for SFWMD, SWFWMD, and SJRWMD are independently served by each agency via web services. Point locations for FDEP are served by FDEP via a web service. Boundaries or locations for SRWMD and NWFWMD are served by SJRWMD web services.This web map was developed for the Florida Shared Services Project. The goals of the project are to: Develop a collaborative framework that the water management districts can use for joint application development effortsEstablish a common understanding of the technology associated with using Esri’s ArcGIS Online productEstablish a governance model for shared application developmentUpdated March 2014 with FDEP data.Updated May 15, 2014 with new SWFWMD service url.Updated August 15, 2014 with new SFWMD service url.Updated September 25, 2014 to repair transparency settings that had changed to 0 instead of 25% - perhaps after service updates?Updated January 7, 2015 to address problems with pop-ups not appearing or not being correct for both SFWMD and SWFWMD.Updated May 7, 2015 with new NWFWMD service url.Updated May 14, 2015 with new SRWMD service url.Updated July 25, 2016 through ago-assistant.esri.com, using JSON editor. Corrected item IDs for NWFWMD.Updated August 1, 2016 with new SWFWMD service url. Created brand new web map.Updated August 17, 2016 with replacement SFWMD service url. Created brand new web map.Updated September 12, 2018 with SSL site references and REST service connections for SWFWMD, SJRWMD, SRWMD and NWFWMD.Update February 26, 2019 through https://ago-assistant.esri.com/: new service urls for SJRWMD, SRWMD and NWFWMD.Update August 29, 2019 to include PERMITTING_PROGRAM = BEACH AND COASTAL SYSTEMS.Updated spring 2024 to use new SFWMD service urls, with native projected coordinate system.Updated August 8, 2024 for overwrite of SFWMD service url, to again use Web Mercator.
Facebook
TwitterBeta Notice: This item is currently in beta and is intended for early access, testing, and feedback. It is not recommended for production use, as functionality and content are subject to change without notice.Land cover describes general characteristics of the Earth's surface. The USA Annual NLCD land cover layer represents the predominant surface state within the mapping year with respect to broad categories of artificial or natural surface cover. This annual time-enabled service of the National Land Cover Database groups land cover into 16 classes based on a modified Anderson Level II classification system. Classes include vegetation type, development density, and agricultural use. Bodies of water, permanent ice and snow, and barren lands are also identified. Confidence in the value of each pixel is not even. Use the USA NLCD Land Cover Confidence 1985-2024 layer to determine the confidence value for each pixel.Annual NLCD Product User Guide: https://www.usgs.gov/centers/eros/science/annual-nlcd-science-product-user-guideDataset SummaryPhenomenon Mapped: Land Cover of the Conterminous USAGeographic Extent: Conterminous USA (lower 48 states + DC)Mosaic Projection: Albers Equal Area Conic, on WGS84 spheroid (AEA_WGS84)Data Coordinate System: Albers Equal Area Conic, on WGS84 spheroid (AEA_WGS84)Cell Size: 30-mPixel Type: 8-bit unsigned integerSource Type: ThematicTime Extent: Annually 1985-2024Analysis: Optimized for AnalysisSource: National Land Cover Database, Multi-Resolution Land Characteristics ConsortiumData Vintage: Version 1.1, June 2025 Publication Date: June 2025The Annual National Land Cover Database products are created through a cooperative project conducted by the Multi-Resolution Land Characteristics Consortium (MRLC). The MRLC Consortium is a partnership of federal agencies, consisting of the U.S. Geological Survey, the National Oceanic and Atmospheric Administration, the U.S. Environmental Protection Agency, the U.S. Department of Agriculture, the U.S. Forest Service, the National Park Service, the U.S. Fish and Wildlife Service, the Bureau of Land Management and the USDA Natural Resources Conservation Service. The NLCD is part of the NGDA and is considered the authoritative land cover product from the U.S. federal government. What can you do with this layer?Identify land cover classes during the years 1985-2024.Analyze land cover classes in a particular year 1985-2024.Disable the time series, then overlay with transparency and the multiply blend mode over basemaps and relief to stain basemaps with color, giving the basemap economic context. Useful for operational layers such as business locations.Play the time series as an animation to visualize and understand land cover changes over four decades.Time SeriesThis layer is served as a time series. To display a particular year of land cover data, select the year of interest with the time slider in your map client. You may also use the time slider to play the service as an animation. We recommend a one year time interval when displaying the series.Annual NLCD vs Legacy NLCDAnnual NLCD and the Legacy NLCD layers are significantly different. A table below shows differences in features between the two datasets. Annual NLCD Legacy NLCDRelease FrequencyYearlyEvery 2-3 YearsNumber of land cover classes1616, plus 4 additional for AlaskaYears includedYearly, from 1985 to 20242001, 2004, 2006, 2008, 2011, 2013, 2016, 2019, 2021Production MethodInvolves three types of deep learning models integrated into a novel geospatial artificial intelligence (AI) solution to process, encode, and map land cover using Landsat timeseries imagery & curated sets of land cover training dataNLCD utilizes supervised classification algorithms, particularly decision trees, to classify Landsat satellite imagery. Training data includes high-resolution orthophotography, local datasets, field-collected points, and Forest Inventory Analysis data.The Annual NLCD layer uses an Albers projection optimized for the lower 48 states. The Legacy NLCD includes Alaska, Hawaii, and Puerto Rico, and thus a North America Albers projection was used in that layer to minimize distortion around its wider geography and facilitate comparison. Optimized for analysis means this layer does not have size constraints for analysis and it is recommended for multisource analysis with other layers optimized for analysis. See the Living Atlas Imagery Layers Optimized for Analysis Group for a complete list of imagery layers optimized for analysis. Processing TemplatesSaturated Renderer for Visualization and Analysis - This renderer has the same symbols as the Esri cartographic renderer, but the colors are extra saturated, giving the map user rich color to use when transparency and/or blend modes may be applied to the layer. This renderer is useful for land cover over a basemap or relief. This is the default. Esri Cartographic Renderer for Visualization and Analysis - Land cover drawn with Esri symbols that are desaturated.MRLC Cartographic Renderer for Visualization and Analysis - Cartographic renderer using the land cover symbols as issued by NLCD (the same symbols as is on the dataset when you download them from MRLC).Simplified Renderer for Visualization and Analysis - NLCD reclassified into 10 broad classes. These broad classes may be easier to use in some analyses, applications or maps.Isolate Developed Areas for Visualization and Analysis - Cartographic renderer which only displays the four developed classes (21, 22, 23, 24), developed open space plus low, medium, and high intensity development classes.Isolate Forested Areas for Visualization and Analysis - Cartographic renderer which only displays the three forest classes (41, 42, 43), deciduous, coniferous, and mixed forest.Isolate (single NLCD class) for Visualization and Analysis - Isolates a single class in the NLCD.USA Annual NLCD Land Cover service classes with corresponding index number (raster value):11. Open Water - areas of open water, generally with less than 25% cover of vegetation or soil.12. Perennial Ice/Snow - areas characterized by a perennial cover of ice and/or snow, generally greater than 25% of total cover.21. Developed, Open Space - areas with a mixture of some constructed materials, but mostly vegetation in the form of lawn grasses. Impervious surfaces account for less than 20% of total cover. These areas most commonly include large-lot single-family housing units, parks, golf courses, and vegetation planted in developed settings for recreation, erosion control, or aesthetic purposes.22. Developed, Low Intensity - areas with a mixture of constructed materials and vegetation. Impervious surfaces account for 20% to 49% percent of total cover. These areas most commonly include single-family housing units.23. Developed, Medium Intensity - areas with a mixture of constructed materials and vegetation. Impervious surfaces account for 50% to 79% of the total cover. These areas most commonly include single-family housing units.24. Developed High Intensity - highly developed areas where people reside or work in high numbers. Examples include apartment complexes, row houses and commercial/industrial. Impervious surfaces account for 80% to 100% of the total cover.31. Barren Land (Rock/Sand/Clay) - areas of bedrock, desert pavement, scarps, talus, slides, volcanic material, glacial debris, sand dunes, strip mines, gravel pits and other accumulations of earthen material. Generally, vegetation accounts for less than 15% of total cover.41. Deciduous Forest - areas dominated by trees generally greater than 5 meters tall, and greater than 20% of total vegetation cover. More than 75% of the tree species shed foliage simultaneously in response to seasonal change.42. Evergreen Forest - areas dominated by trees generally greater than 5 meters tall, and greater than 20% of total vegetation cover. More than 75% of the tree species maintain their leaves all year. Canopy is never without green foliage.43. Mixed Forest - areas dominated by trees generally greater than 5 meters tall, and greater than 20% of total vegetation cover. Neither deciduous nor evergreen species are greater than 75% of total tree cover.52. Shrub/Scrub - areas dominated by shrubs; less than 5 meters tall with shrub canopy typically greater than 20% of total vegetation. This class includes true shrubs, young trees in an early successional stage or trees stunted from environmental conditions.71. Grassland/Herbaceous - areas dominated by gramanoid or herbaceous vegetation, generally greater than 80% of total vegetation. These areas are not subject to intensive management such as tilling, but can be utilized for grazing.81. Pasture/Hay - areas of grasses, legumes, or grass-legume mixtures planted for livestock grazing or the production of seed or hay crops, typically on a perennial cycle. Pasture/hay vegetation accounts for greater than 20% of total vegetation.82. Cultivated Crops - areas used for the production of annual crops, such as corn, soybeans, vegetables, tobacco, and cotton, and also perennial woody crops such as orchards and vineyards. Crop vegetation accounts for greater than 20% of total vegetation. This class also includes all land being actively tilled.90. Woody Wetlands - areas where forest or shrubland vegetation accounts for greater than 20% of vegetative cover and the soil or substrate is periodically saturated with or covered with water.95. Emergent Herbaceous Wetlands - Areas where perennial herbaceous vegetation accounts for greater than 80% of vegetative cover and the soil or substrate is periodically saturated with or covered with water.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.
Facebook
TwitterLast Revised: February 2016
Map Information
This nowCOAST™ time-enabled map service provides maps depicting the
latest global forecast guidance of water currents, water temperature, and
salinity at forecast projections: 0, 12, 24, 36, 48, 60, 72, 84, and 96-hours
from the NWS/NCEP Global Real-Time Ocean Forecast System (GRTOFS). The surface
water currents velocity maps display the direction using white or black
streaklets. The magnitude of the current is indicated by the length and width
of the streaklet. The maps of the GRTOFS surface forecast guidance are updated
on the nowCOAST™ map service once per day.
For more detailed information about layer update frequency and timing, please reference the
nowCOAST™ Dataset Update Schedule.
Background Information
GRTOFS is based on the Hybrid Coordinates Ocean Model (HYCOM), an eddy resolving, hybrid coordinate numerical ocean prediction model. GRTOFS has global coverge and a horizontal resolution of 1/12 degree and 32 hybrid vertical layers. It has one forecast cycle per day (i.e. 0000 UTC) which generates forecast guidance out to 144 hours (6 days). However, nowCOAST™ only provides guidance out to 96 hours (4 days). The forecast cycle uses 3-hourly momentum and radiation fluxes along with precipitation predictions from the NCEP Global Forecast System (GFS). Each forecast cycle is preceded with a 48-hr long nowcast cycle. The nowcast cycle uses daily initial 3-D fields from the NAVOCEANO operational HYCOM-based forecast system which assimilates situ profiles of temperature and salinity from a variety of sources and remotely sensed SST, SSH and sea-ice concentrations. GRTOFS was developed by NCEP/EMC/Marine Modeling and Analysis Branch. GRTOFS is run once per day (0000 UTC forecast cycle) on the NOAA Weather and Climate Operational Supercomputer System (WCOSS) operated by NWS/NCEP Central Operations.
The maps are generated using a visualization technique developed by the Data Visualization Research Lab at The University of New Hampshire's Center for Coastal and Ocean Mapping (http://www.ccom.unh.edu/vislab/). The method combines two techniques. First, equally spaced streamlines are computed in the flow field using Jobard and Lefer's (1977) algorithm. Second, a series of "streaklets" are rendered head to tail along each streamline to show the direction of flow. Each of these varies along its length in size, color and transparency using a method developed by Fowler and Ware (1989), and later refined by Mr. Pete Mitchell and Dr. Colin Ware (Mitchell, 2007).
Time Information
This map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.
In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.
This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.
This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.
When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.
Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:
Issue a returnUpdates=true request (ArcGIS REST protocol only)
for an individual layer or for the service itself, which will return
the current start and end times of available data, in epoch time format
(milliseconds since 00:00 January 1, 1970). To see an example, click on
the "Return Updates" link at the bottom of the REST Service page under
"Supported Operations". Refer to the
ArcGIS REST API Map Service Documentation
for more information.
Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against
the proper layer corresponding with the target dataset. For raster
data, this would be the "Image Footprints with Time Attributes" layer
in the same group as the target "Image" layer being displayed. For
vector (point, line, or polygon) data, the target layer can be queried
directly. In either case, the attributes returned for the matching
raster(s) or vector feature(s) will include the following:
validtime: Valid timestamp.
starttime: Display start time.
endtime: Display end time.
reftime: Reference time (sometimes referred to as
issuance time, cycle time, or initialization time).
projmins: Number of minutes from reference time to valid
time.
desigreftime: Designated reference time; used as a
common reference time for all items when individual reference
times do not match.
desigprojmins: Number of minutes from designated
reference time to valid time.
Query the nowCOAST™ LayerInfo web service, which has been created to
provide additional information about each data layer in a service,
including a list of all available "time stops" (i.e. "valid times"),
individual timestamps, or the valid time of a layer's latest available
data (i.e. "Product Time"). For more information about the LayerInfo
web service, including examples of various types of requests, refer to
the
nowCOAST™ LayerInfo Help Documentation
References
Fowler, D. and C. Ware, 1989: Strokes for Representing Vector Field Maps. Proceedings: Graphics Interface '98 249-253. Jobard, B and W. Lefer,1977: Creating evenly spaced streamlines of arbitrary density. Proceedings: Eurographics workshop on Visualization in Scientific Computing. 43-55. Mitchell, P.W., 2007: The Perceptual optimization of 2D Flow Visualizations Using Human in the Loop Local Hill Climbing. University of New Hampshire Masters Thesis. Department of Computer Science. NWS, 2013: About Global RTOFS, NCEP/EMC/MMAB, College Park, MD (Available at http://polar.ncep.noaa.gov/global/about/). Chassignet, E.P., H.E. Hurlburt, E.J. Metzger, O.M. Smedstad, J. Cummings, G.R. Halliwell, R. Bleck, R. Baraille, A.J. Wallcraft, C. Lozano, H.L. Tolman, A. Srinivasan, S. Hankin, P. Cornillon, R. Weisberg, A. Barth, R. He, F. Werner, and J. Wilkin, 2009: U.S. GODAE: Global Ocean Prediction with the HYbrid Coordinate Ocean Model (HYCOM). Oceanography, 22(2), 64-75. Mehra, A, I. Rivin, H. Tolman, T. Spindler, and B. Balasubramaniyan, 2011: A Real-Time Operational Global Ocean Forecast System, Poster, GODAE OceanView –GSOP-CLIVAR Workshop in Observing System Evaluation and Intercomparisons, Santa Cruz, CA.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Facebook
TwitterSummary
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