The data (name, year of birth, sex, and number) are from a 100 percent sample of Social Security card applications for 1880 on.
Popular Baby Names by Sex and Ethnic Group Data were collected through civil birth registration. Each record represents the ranking of a baby name in the order of frequency. Data can be used to represent the popularity of a name. Caution should be used when assessing the rank of a baby name if the frequency count is close to 10; the ranking may vary year to year.
The Place Name database is maintained by Survey and Mapping Office of LandsD. The original source of the Database is based on “A Gazetteer of Place Names” with the first edition published in 1960, containing placename features mapped at 1:25,000. The Database stores and maintains names of settlement (e.g. area, town, village), hydrographic features (e.g. river, channel), and topographic features (e.g. relief).
Attribution-NonCommercial-ShareAlike 4.0 (CC BY-NC-SA 4.0)https://creativecommons.org/licenses/by-nc-sa/4.0/
License information was derived automatically
Have you ever wondered where a place got its name from? This page is the beginning of a much larger project that will attempt to geospatially document as much as we are able to regarding Tennessee's history of place names. The data as it currently exists represents many years of work by my friend, the geographer and author, Allen Coggins. He provided me with an Access database with 11,720 records of places with information including: name origin, place description, notes, and the starting and ending dates of any associated post offices. This is the work that he managed to digitize from a card catalog (now in my possession). I estimate that the records in the database represent about 1/3rd of the card catalog's records. The data I present here relates to 2,349 records which I was able to easily (enough) match to the GNIS dataset (which has 77,746 Tennessee records in the version that I accessed 2/28/2025).The sheer volume of this project means that this will take years to develop. Index cards will need to be scanned and digitized. Records will need to be matched and georeferenced. All this will only be to catch up to where Allen got us. Surely we will learn more about origins of place names as the project progresses. We will need to accurately document our work along the way.
Search for a business by name. You can obtain business information and then proceed to purchase a certificate of good standing or other documents. The purpose of this search is simply to determine whether a company/entity exists and to provide basic information on the company/entity.
The first names file contains data on the first names attributed to children born in France since 1900. These data are available at the level of France and by department. The files available for download list births and not living people in a given year. They are available in two formats (DBASE and CSV). To use these large files, it is recommended to use a database manager or statistical software. The file at the national level can be opened from some spreadsheets. The file at the departmental level is however too large (3.8 million lines) to be consulted with a spreadsheet, so it is proposed in a lighter version with births since 2000 only. The data can be accessed in: - a national data file containing the first names attributed to children born in France between 1900 and 2022 (data before 2012 relate only to France outside Mayotte) and the numbers by sex associated with each first name; - a departmental data file containing the same information at the department of birth level; - a lighter data file that contains information at the department level of birth since the year 2000.
Street Name Master List - contains all the reserved and active street names.
https://whoisdatacenter.com/terms-of-use/https://whoisdatacenter.com/terms-of-use/
Snag Your Name LLC Whois Database, discover comprehensive ownership details, registration dates, and more for Snag Your Name LLC with Whois Data Center.
By Derek Howard [source]
This dataset provides an essential tool for generating gender-specific datasets from names alone. It contains information on the probability of a person's name belonging to a certain gender, based off of US Social Security records from the last century. This makes it easy to assign genders to datasets that do not natively include this data. All probability values were culled from records with 5 or more people associated with each name - so those individuals with less common monikers can still have their genders correctly predicted! With this resource, users can generate gender-aware data in no time, making gender identification in data sets more accurate and easier than ever
For more datasets, click here.
- 🚨 Your notebook can be here! 🚨!
This dataset provides a helpful resource when you need to accurately identify gender from names. With this dataset, you’ll be able to quickly and accurately assign genders to datasets that contain names but no other information about the person.
To get started, you will need a csv file with two columns: name and probability. The name column should contain the first names of the people in your dataset. The probability column should contain numbers between 0 and 1 indicating the likelihood that each name is associated with one specific gender (0 for male, 1 for female).
In addition to simply assigning genders from these probabilities alone, users of this dataset also have more control over their classifications - they can use it as either a baseline or as an absolute measure of accuracy depending on their exact needs/preferences. Experimentation is highly encouraged here!
Good luck!
Create gender-specific applications - tailor different apps to different genders based on the probability of a particular name belonging to a certain gender.
Generate gender neutral names - use this data to generate random names with no gender bias.
Automate record lookup - quickly and accurately assign genders based on the probability associated with their name
If you use this dataset in your research, please credit the original authors.
License
Unknown License - Please check the dataset description for more information.
File: name_gender.csv | Column name | Description | |:----------------|:--------------------------------------------------------------------| | name | The name of the person. (String) | | gender | The gender of the person. (String) | | probability | The probability of the gender being assigned to the person. (Float) |
If you use this dataset in your research, please credit the original authors. If you use this dataset in your research, please credit Derek Howard.
https://catalog.elra.info/static/from_media/metashare/licences/ELRA_VAR.pdfhttps://catalog.elra.info/static/from_media/metashare/licences/ELRA_VAR.pdf
https://catalog.elra.info/static/from_media/metashare/licences/ELRA_END_USER.pdfhttps://catalog.elra.info/static/from_media/metashare/licences/ELRA_END_USER.pdf
Provides comprehensive coverage for the major Chinese romanization systems and their variants, and if needed can be expanded considerably with dialectical variants (Cantonese, Hakka, Hokkien, etc.).
https://whoisdatacenter.com/terms-of-use/https://whoisdatacenter.com/terms-of-use/
Name Thread Corporation Whois Database, discover comprehensive ownership details, registration dates, and more for Name Thread Corporation with Whois Data Center.
This list is a work-in-progress and will be updated at least quarterly. This version updates column names and corrects spellings of several streets in order to alleviate confusion and simplify street name research. It represents an inventory of official street name spellings in the City of New Orleans. Several sources contain various spellings and formats of street names. This list represents street name spellings and formats researched by the City of New Orleans GIS and City Planning Commission.Note: This list may not represent what is currently displayed on street signs. City of New Orleans official street list is derived from New Orleans street centerline file, 9-1-1 centerline file, and CPC plat maps. Fields include the full street name and the parsed elements along with abbreviations using US Postal Standards. We invite your input to as we work toward one enterprise street name list.Status: Current: Currently a known used street name in New Orleans Other: Currently a known used street name on a planned but not developed street. May be a retired street name.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This is the first version of the HANA database. The minipics are from the police register sheets from Copenhagen which cover all adults residing in the capital of Denmark, Copenhagen, in the period from 1890 to 1912.
The labels in the .csv files refers to the main character on the original register sheets. Each row contain a reference to the corresponding image as the first element and the name as the second element. The HANA database consist of 1,105,904 files and labels. The last name is always only one word and if multiple last names were transcribed, the last of these were chosen as the last name, while the remaining were moved to the end of the first names. The first names can be up to 9 individual words.
All names are written in lower case letters and contain only characters which are used in Danish words, which implies 29 alphabetic characters i.e. this database include the letters æ, ø, and å.
If anything is missing or if you are interested in the original documents from Copenhagen Archives for improving on the cropouts, feel free to write me at sfw@sam.sdu.dk or my colleagues at University of Southern Denmark and University of Bristol.
We wish you the best of luck.
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 filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).
https://whoisdatacenter.com/index.php/terms-of-use/https://whoisdatacenter.com/index.php/terms-of-use/
.NAME.TR Whois Database, discover comprehensive ownership details, registration dates, and more for .NAME.TR TLD with Whois Data Center.
Approved street names are required to be included on the first submittal of all Final Subdivision Maps. Developers must use this Street Name Application to submit new street names for approval by the City.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
The National Hydrography Dataset (NHD) High Resolution flowlines were used as a base to provide additional information on the connectivity of the stream network for the hydrographic basins in and around Montana. In addition to the attributes that are published as part of the NHD data, two fields were added to the attribute table to associate streams that do not have a Geographic Names Information System (GNIS) name with the GNIS name and NHD reachcode of the nearest downstream named flowline. The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the nation's surface water drainage system. NHD data were originally developed at 1:100,000-scale and exists at that scale for the whole country. This high-resolution NHD, generally developed at 1:24,000/1:12,000 scale, adds detail to the original 1:100,000-scale NHD. Local resolution NHD is being developed where partners and data exist. The ...
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Polygon data set with the labels for the geonames from the topographic maps of the BEV Important fields and data types of the attribute table: Data source: geonam_text.shp
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The GBIF Backbone Taxonomy is a single, synthetic management classification with the goal of covering all names GBIF is dealing with. It's the taxonomic backbone that allows GBIF to integrate name based information from different resources, no matter if these are occurrence datasets, species pages, names from nomenclators or external sources like EOL, Genbank or IUCN. This backbone allows taxonomic search, browse and reporting operations across all those resources in a consistent way and to provide means to crosswalk names from one source to another.
It is updated regulary through an automated process in which the Catalogue of Life acts as a starting point also providing the complete higher classification above families. Additional scientific names only found in other authoritative nomenclatural and taxonomic datasets are then merged into the tree, thus extending the original catalogue and broadening the backbones name coverage. The GBIF Backbone taxonomy also includes identifiers for Operational Taxonomic Units (OTUs) drawn from the barcoding resources iBOL and UNITE.
International Barcode of Life project (iBOL), Barcode Index Numbers (BINs). BINs are connected to a taxon name and its classification by taking into account all names applied to the BIN and picking names with at least 80% consensus. If there is no consensus of name at the species level, the selection process is repeated moving up the major Linnaean ranks until consensus is achieved.
UNITE - Unified system for the DNA based fungal species, Species Hypotheses (SHs). SHs are connected to a taxon name and its classification based on the determination of the RefS (reference sequence) if present or the RepS (representative sequence). In the latter case, if there is no match in the UNITE taxonomy, the lowest rank with 100% consensus within the SH will be used.
The GBIF Backbone Taxonomy is available for download at https://hosted-datasets.gbif.org/datasets/backbone/ in different formats together with an archive of all previous versions.
The following 105 sources have been used to assemble the GBIF backbone with number of names given in brackets:
This data contains Corporation and Other Business Entity Name information for each entity. Each record contains a current or previous name for an entity in the electronic database. The records include the Department of State ID number, Date Filed, Name Type and Name Status.
The data (name, year of birth, sex, and number) are from a 100 percent sample of Social Security card applications for 1880 on.