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/
Loudoun County Parcel X,Y coordinates table. Available in Latitude and Longitude decimal degrees and Virginia State Plane North.
https://en.wikipedia.org/wiki/Public_domainhttps://en.wikipedia.org/wiki/Public_domain
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).
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"
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset contains all basic primary school details including address, longitude/latitude, geo (XY) coordinates and eircode information
Utah FORGE has been established to develop, test, and improve the technologies and techniques required to develop EGS-type geothermal resources. Drilling of the first of two deep deviated wells, 16A(78)-32, will begin in the second half of 2020. This well will serve as the injection well for the injection-production well pair that will form the heart of the laboratory. This submission contains an archive of well location data within the Roosevelt Hot Springs geothermal area. An Excel spreadsheet is included containing updated GPS data for Utah FORGE wells drilled during Phase 2C (56-32, 68-32, 78-32). This data was collected over time by the Utah Geological Survey and contains all coordinates collected and the final averaged XY coordinates in both Longitude and Latitude and UTM Zone 12, NAD83. Elevation is also included. GIS shapefiles with well points are provided in the archive.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Parking citations with latitude / longitude (XY) in US Feet coordinates according to the NAD_1983_StatePlane_California_V_FIPS_0405_Feet projection.
Tags
survey, environmental behaviors, lifestyle, status, PRIZM, Baltimore Ecosystem Study, LTER, BES
Summary
BES Research, Applications, and Education
Description
XY Positions for BES telephone survey. The BES Household Survey 2003 is a telephone survey of metropolitan Baltimore residents consisting of 29 questions. The survey research firm, Hollander, Cohen, and McBride conducted the survey, asking respondents questions about their outdoor recreation activities, watershed knowledge, environmental behavior, neighborhood characteristics and quality of life, lawn maintenance, satisfaction with life, neighborhood, and the environment, and demographic information. The data from each respondent is also associated with a PRIZM� classification, census block group, and latitude-longitude. PRIZM� classifications categorize the American population using Census data, market research surveys, public opinion polls, and point-of-purchase receipts. The PRIZM� classification is spatially explicit allowing the survey data to be viewed and analyzed spatially and allowing specific neighborhood types to be identified and compared based on the survey data. The census block group and latitude-longitude data also allow us additional methods of presenting and analyzing the data spatially.
The household survey is part of the core data collection of the Baltimore Ecosystem Study to classify and characterize social and ecological dimensions of neighborhoods (patches) over time and across space. This survey is linked to other core data including US Census data, remotely-sensed data, and field data collection, including the BES DemSoc Field Observation Survey.
The BES 2003 telephone survey was conducted by Hollander, Cohen, and McBride from September 1-30, 2003. The sample was obtained from the professional sampling firm Claritas, in order that their "PRIZM" encoding would be appended to each piece of sample (telephone number) supplied. Mailing addresses were also obtained so that a postcard could be sent in advance of interviewers calling. The postcard briefly informed potential respondents about the survey, who was conducting it, and that they might receive a phone call in the next few weeks. A stratified sampling method was used to obtain between 50 - 150 respondents in each of the 15 main PRIZM classifications. This allows direct comparison of PRIZM classifications. Analysis of the data for the general metropolitan Baltimore area must be weighted to match the population proportions normally found in the region. They obtained a total of 9000 telephone numbers in the sample. All 9,000 numbers were dialed but contact was only made on 4,880. 1508 completed an interview, 2524 refused immediately, 147 broke off/incomplete, 84 respondents had moved and were no longer in the correct location, and a qualified respondent was not available on 617 calls. This resulted in a response rate of 36.1% compared with a response rate of 28.2% in 2000. The CATI software (Computer Assisted Terminal Interviewing) randomized the random sample supplied, and was programmed for at least 3 attempted callbacks per number, with emphasis on pulling available callback sample prior to accessing uncalled numbers. Calling was conducted only during evening and weekend hours, when most head of households are home. The use of CATI facilitated stratified sampling on PRIZM classifications, centralized data collection, standardized interviewer training, and reduced the overall cost of primary data collection. Additionally, to reduce respondent burden, the questionnaire was revised to be concise, easy to understand, minimize the use of open-ended responses, and require an average of 15 minutes to complete.
The household survey is part of the core data collection of the Baltimore Ecosystem Study to classify and characterize social and ecological dimensions of neighborhoods (patches) over time and across space. This survey is linked to other core data, including US Census data, remotely-sensed data, and field data collection, including the BES DemSoc Field Observation Survey.
Additional documentation of this database is attached to this metadata and includes 4 documents, 1) the telephone survey, 2) documentation of the telephone survey, 3) metadata for the telephone survey, and 4) a description of the attribute data in the BES survey 2003 survey.
This database was created by joining the GDT geographic database of US Census Block Group geographies for the Baltimore Metropolitan Statisticsal Area (MSA), with the Claritas PRIZM database, 2003, of unique classifications of each Census Block Group, and the unique PRIZM code for each respondent from the BES Household Telephone Survey, 2003. The GDT database is preferred and used
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Parking citations with latitude / longitude (XY) in US Feet coordinates according to the NAD_1983_StatePlane_California_V_FIPS_0405_Feet projection.
Attribution-NonCommercial-ShareAlike 3.0 (CC BY-NC-SA 3.0)https://creativecommons.org/licenses/by-nc-sa/3.0/
License information was derived automatically
These TowCam navigation files were generated during 2002 R/V Melville cruise VANC01MV along a minor rift originating at the East Pacific Rise (EPR) at 2°40'N continuing southeastward for ~65 km. Photographs were assigned the position of the ship, assuming minimal layback of the camera sled. The files are in ASCII text format and present with the latitude and longitude in decimal degrees. There is one navigation file per TowCam deployment. The files were generated as part of a project called Geochemical and Geological Investigations of the Incipient Rift at 2° 40'N, East of the East Pacific Rise. Funding was provided by NSF awards OCE00-96360 and OCE00-99154.
This dataset contains the location of all active fire stations and fire related facilities within the City of Toronto. The locations are identified by XY (latitude and longitude) coordinates.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Parking citations with latitude / longitude (XY) in US Feet coordinates according to the NAD_1983_StatePlane_California_V_FIPS_0405_Feet projection.
Attribution 2.5 (CC BY 2.5)https://creativecommons.org/licenses/by/2.5/
License information was derived automatically
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is gravity anomaly data of the Auckland and Whangarei volcanic fields (AVF and WVF) in the northern part of North Island. The X-Y coordinate system of this dataset is NZTM, and the Longitude-Latitude coordinate system is NZGD2000. The uploader gathers this data from a series of AVF day trip fieldworks (2021 - 2023), a week-long WVF campaign (2022), correspondences with authors, and the following theses lodged in The University of Auckland's General Library:Auckland Volcanic FieldCaleb John Gasston (2017)Hellen Anne Williams (2003)Sian Julia France (2003)Mazin Al-Salim (2000)Dev Kumar Affleck (1999)Craig Andrew Miller (1996)Shane Robert Moore (1996)David Rout (1991)Grant Willis Roberts (1980)Isla Margaret Nixon (1977)Helen Joan Anderson (partially, 1977)Whangarei Volcanic FieldPaul Johann Röllin (1991)All names and years of the respective data contributors have been included in the CSV files.
This data set provides a means of identifying an x-y coordinate for the approximate center (centroid) of landnet units based on the corresponding standardized PLSS description (e.g., for PLSS Section this is DTRS -- Direction, Township, Range, and Section codes). This process is sometimes referred to as "protraction". The Landnet centroid shapefile includes coordinates in WTM83/91 and latitude/longitude expressed as decimal degrees or degrees, minutes and seconds.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
If you use this dataset, please cite the IJRR data paper (bibtex is below). We present a dataset collected from a canoe along the Sangamon River in Illinois. The canoe was equipped with a stereo camera, an IMU, and a GPS device, which provide visual data suitable for stereo or monocular applications, inertial measurements, and position data for ground truth. We recorded a canoe trip up and down the river for 44 minutes covering 2.7 km round trip. The dataset adds to those previously recorded in unstructured environments and is unique in that it is recorded on a river, which provides its own set of challenges and constraints that are described in this paper. The data is divided into subsets, which can be downloaded individually. Video previews are available on Youtube: https://www.youtube.com/channel/UCOU9e7xxqmL_s4QX6jsGZSw The information below can also be found in the README files provided in the 527 dataset and each of its subsets. The purpose of this document is to assist researchers in using this dataset. Images ====== Raw --- The raw images are stored in the cam0 and cam1 directories in bmp format. They are bayered images that need to be debayered and undistorted before they are used. The camera parameters for these images can be found in camchain-imucam.yaml. Note that the camera intrinsics describe a 1600x1200 resolution image, so the focal length and center pixel coordinates must be scaled by 0.5 before they are used. The distortion coefficients remain the same even for the scaled images. The camera to imu tranformation matrix is also in this file. cam0/ refers to the left camera, and cam1/ refers to the right camera. Rectified --------- Stereo rectified, undistorted, row-aligned, debayered images are stored in the rectified/ directory in the same way as the raw images except that they are in png format. The params.yaml file contains the projection and rotation matrices necessary to use these images. The resolution of these parameters do not need to be scaled as is necessary for the raw images. params.yml ---------- The stereo rectification parameters. R0,R1,P0,P1, and Q correspond to the outputs of the OpenCV stereoRectify function except that 1s and 2s are replaced by 0s and 1s, respectively. R0: The rectifying rotation matrix of the left camera. R1: The rectifying rotation matrix of the right camera. P0: The projection matrix of the left camera. P1: The projection matrix of the right camera. Q: Disparity to depth mapping matrix T_cam_imu: Transformation matrix for a point in the IMU frame to the left camera frame. camchain-imucam.yaml -------------------- The camera intrinsic and extrinsic parameters and the camera to IMU transformation usable with the raw images. T_cam_imu: Transformation matrix for a point in the IMU frame to the camera frame. distortion_coeffs: lens distortion coefficients using the radial tangential model. intrinsics: focal length x, focal length y, principal point x, principal point y resolution: resolution of calibration. Scale the intrinsics for use with the raw 800x600 images. The distortion coefficients do not change when the image is scaled. T_cn_cnm1: Transformation matrix from the right camera to the left camera. Sensors ------- Here, each message in name.csv is described ###rawimus### time # GPS time in seconds message name # rawimus acceleration_z # m/s^2 IMU uses right-forward-up coordinates -acceleration_y # m/s^2 acceleration_x # m/s^2 angular_rate_z # rad/s IMU uses right-forward-up coordinates -angular_rate_y # rad/s angular_rate_x # rad/s ###IMG### time # GPS time in seconds message name # IMG left image filename right image filename ###inspvas### time # GPS time in seconds message name # inspvas latitude longitude altitude # ellipsoidal height WGS84 in meters north velocity # m/s east velocity # m/s up velocity # m/s roll # right hand rotation about y axis in degrees pitch # right hand rotation about x axis in degrees azimuth # left hand rotation about z axis in degrees clockwise from north ###inscovs### time # GPS time in seconds message name # inscovs position covariance # 9 values xx,xy,xz,yx,yy,yz,zx,zy,zz m^2 attitude covariance # 9 values xx,xy,xz,yx,yy,yz,zx,zy,zz deg^2 velocity covariance # 9 values xx,xy,xz,yx,yy,yz,zx,zy,zz (m/s)^2 ###bestutm### time # GPS time in seconds message name # bestutm utm zone # numerical zone utm character # alphabetical zone northing # m easting # m height # m above mean sea level Camera logs ----------- The files name.cam0 and name.cam1 are text files that correspond to cameras 0 and 1, respectively. The columns are defined by: unused: The first column is all 1s and can be ignored. software frame number: This number increments at the end of every iteration of the software loop. camera frame number: This number is generated by the camera and increments each time the shutter is triggered. The software and camera frame numbers do not have to start at the same value, but if the difference between the initial and final values is not the same, it suggests that frames may have been dropped. camera timestamp: This is the cameras internal timestamp of the frame capture in units of 100 milliseconds. PC timestamp: This is the PC time of arrival of the image. name.kml -------- The kml file is a mapping file that can be read by software such as Google Earth. It contains the recorded GPS trajectory. name.unicsv ----------- This is a csv file of the GPS trajectory in UTM coordinates that can be read by gpsbabel, software for manipulating GPS paths. @article{doi:10.1177/0278364917751842, author = {Martin Miller and Soon-Jo Chung and Seth Hutchinson}, title ={The Visual–Inertial Canoe Dataset}, journal = {The International Journal of Robotics Research}, volume = {37}, number = {1}, pages = {13-20}, year = {2018}, doi = {10.1177/0278364917751842}, URL = {https://doi.org/10.1177/0278364917751842}, eprint = {https://doi.org/10.1177/0278364917751842} }
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
File List bivalve.txt
Description The ASCII text data frame bivalve.txt contains 200 rows of observations corresponding to the 0.25 square meter sample plots on a 250 m × 500 m area on the sandflat of Wiroa Island, Manukau Harbor, New Zealand (data from Legendre et al. 1997). The 21 column variables are: LN.MACG15, logarithm of counts of Macomona >15 mm; MACG15, counts of Macomona >15 mm; ELEV.M, bed elevation in meters above chart datum; ELEV2, ELEV.M squared; ELEV3, ELEV.M cubed; X.CTR, longitude coordinates centered to mean 0; Y.CTR, latitude coordinates centered to mean 0; X2, X.CTR squared; XY, X.CTR multiplied by Y.CTR; Y2, Y.CTR squared; X3, X.CTR cubed; X2Y, X2 multiplied by Y.CTR; XY2, X.CTR multiplied by Y2; Y3, Y.CTR cubed; EBBSTRESS, ebb tide bed shear stress (N/m2); SWWAVEWORK, southwest wave work per unit of bed area (kg/s2); WSWWAVEWORK, west, southwest wave work per unit of bed area (kg/s2); WATER.G20CM, proportion of time the plot is covered by water >20 cm deep during spring tide (0 - 1); LRGWAVE.STIR, proportion of time large waves stir the plot during spring tide (0 - 1); FLDSTRESS, flood tide bed shear stress (N/m2); and SHELLHASH, bivalve shell hash (g) in the bed sediment. Missing values are indicated by NA.
http://www.gesetze-im-internet.de/geonutzv/http://www.gesetze-im-internet.de/geonutzv/
Dies sind Daten, die vom Deutschen Wetterdienst mit dem COSMO-DE-Modell erhoben und über das Pamore-Programm bezogen wurden. Es handel sich um Assimilationsanalyse-Daten. Die Assimilationsanalyse ist ein erneuter Durchlauf des COSMO-DE Modells mit Messstationsdaten als Randbedingung. Sie stellt nach Möglichkeit das tatsächlich gewesene Wetter dar. Alle Wind- und Temperaturdaten sind von den DWD-Angaben direkt übernommen und aus dem COSMO-DE-Modell. Urheber der Daten ist somit der Deutsche Wetterdienst. Es handelt sich hierbei um eine Aufbereitung, Zusammenstellung und einen Zuschnitt der Daten in ein, für die Energiesystemsimulation, handliches und niederschwellig zugängliches Format. Dateiformat: hdf5 - Version 1 (erstellt mit Matlab) Jede Datei enthält als Werte: Latitudes in °, /latitude, 2D-Gitter, single-precision (4-Byte floating point), (X Y) Longitudes in °, /longitude, 2D-Gitter, single-precision (4-Byte floating point), (X Y) Die eigentlichen Werte (s.u.), /
Lizenz: GeoNutzV
XY Table to Point geoprocess:PRIM_LAT_DEC - Official feature latitude location, NAD 83 DEC-decimal degrees. PRIM_LONG_DEC - Official feature longitude location, NAD 83 DEC-decimal degrees (per https://www.fgdl.org/metadata/fgdl_html/gnis_jul15.htm).Source References:https://www.usgs.gov/u.s.-board-on-geographic-names/download-gnis-datahttps://geonames.usgs.gov/docs/metadata/gnis.txtPCS - GCS_North_American_1983
Not seeing a result you expected?
Learn how you can add new datasets to our index.
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/