Talk:HIFLD/Finance

Federal Reserve Banks/Branches

Tagging

• The source data contains phone numbers (AREA_ and PHONE fields), will these not be imported? The tagging table does not mention them.
• The source data contains an ADDRESS2 field. The tagging table does not mention it. It seems worthwhile to include
• The source data contains a ZIPP4 field. This is not mentioned in the tagging table. It seems worthwhile to include.
• I couldn't find a suitable tag, but it seems we should have a specific tag for central banks (in this case the Federal Reserve). It is different than government finance, which may be a tax collecting agency (IRS in the US) or the Treasury.

Geocoding Precision

• The source data contains a field called GEOPREC (geocoding precision). Those features that have "BLOCKFACE" in this field were only located to the correct block and correct side of the street (face). These features should be manually reviewed and not bulk uploaded.

Age of Data

• The source data contains a GEODATE field. The values for all of the features are from 2006! Do we really want to be importing data that is 17 years old? While I don't think the US has created any new Federal Reserve Banks, there may be new branches, or branches may have moved. I would not import this data. If you are interested in Federal Reserve Banks, I would do your own research. There isn't that many of them.

--Tekim (talk) 00:09, 9 July 2023 (UTC)

Financial Processing Centers

Tagging

• The suggested tagging, government=tax is not appropriate, these are not just tax collection centers. It includes locations where credit cards and checks are processed, as well as defense payment centers (DFAS) --Tekim (talk) 00:23, 9 July 2023 (UTC)
• The suggested tagging, office=government is also not appropriate. The dataset contains private banks (although perhaps they handle payments on behalf of the government), e.g. First Citizens Bank --Tekim (talk) 00:26, 9 July 2023 (UTC)
• Generally we don't use a source=* tag on individual features, rather we put that in the change set comment. Personally, I could go either way on this, but this is my understanding of the community consensus. --Tekim (talk) 00:35, 9 July 2023 (UTC)
• The source data contains an ADDRESS2 field, but it doesn't appear in the tagging table. It seems worthwhile to include it. --Tekim (talk) 00:35, 9 July 2023 (UTC)
• The source data contains a ZIPP4 field, but it doesn't appear in the tagging table. It seems worthwhile to include it. --Tekim (talk) 00:35, 9 July 2023 (UTC)
• The source data contains phone numbers (PHONE and AREA_ fields), but these fields do not appear in the tagging table. It seems worthwhile to include it. --Tekim (talk) 00:35, 9 July 2023 (UTC)

Age of Data

• The source data contains a GEODATE field. The values for all of the features are from 2006! Do we really want to be importing data that is 17 years old? I would not import this data! --Tekim (talk) 00:23, 9 July 2023 (UTC)

Geocoding Precision

• The source data contains a field call GEOHOW. All features that have "AUTO" in this field should be individually manually reviewed. This indicates they were auto geocoded, a process that can often yield incorrect results.
• The source data contains a field called GEOPREC (geocoding precision). Those features that have "BLOCKFACE" in this field were only located to the correct block and correct side of the street (face). These features should be manually reviewed and not bulk uploaded.

Possible Duplicates with Federal Reserve Dataset

• The source data contains records for Federal Reserve locations. In some cases these should be removed from the data as they are also contained in the Federal Reserve dataset, however, a sub tag may be added to the Federal Reserve feature indicating that it processes payments (although I suspect all do). --Tekim (talk) 00:23, 9 July 2023 (UTC)

Gold Bullion Repositories

Tagging

• These are locations where large amounts of gold are stored, the proposed tagging shop=pawnbroker is not remotely appropriate. Also, shop=collector + collector=coins is not appropriate. --Tekim (talk) 00:46, 9 July 2023 (UTC)

Data Age

• This data is from 2006, It is way out of date. Do not import!!!--Tekim (talk) 00:46, 9 July 2023 (UTC)

Duplicates with other HIFLD Datasets

• This dataset contains at least one record for a Federal Reserve location, this should be removed, although that Federal Reserve location may get a sub tag indicating that it stores gold.--Tekim (talk) 00:46, 9 July 2023 (UTC)
• This dataset contains at lest one record for a US Mint (Denver), this should be removed as it appears in another HIFLD dataset, although a sub tag may be appropriate.--Tekim (talk) 00:46, 9 July 2023 (UTC)

US Mint Bureau of Engraving and Printing

Current OSM Data

• All of the features in this source dataset are already in OSM, with the exception of the West Point Mint.
• Some of the tagging differs between this source dataset and the data in OSM however, for example
  • name=United States Bullion Depository (OSM), vs name=Fort Knox Bullion Depository (HIFLD).
  • name=The United States Mint (OSM) vs name=United States Mint Headquarters (HIFLD)
• There may be value in conflating some of the tags from this source dataset with the existing OSM data, for example address and phone information is often not complete in the existing OSM data.

Quality

• The Bureau of Engraving and Printing in DC has the same address as the Bureau of Engraving and Printing Annex even though they are on opposite sides of the street. I believe the address for the Annex is correct.