- Other infrastructure
- 10 · 100 · 1,000 MW
Map
- Other infrastructure
1 asset
1 asset. Basemap: Protomaps, © OpenStreetMap contributors, ODbL.
CATO Inc
Petroleum product terminal owner
As filed: CATO INC
Key facts
Petroleum product terminal owner · 0 projects- Projects
- 0projects
- Assets
- 1
- States
- MD
- Headquarters
- Charlotte, United States Source: Wikidata
- Website
- catofashions.com Source: Wikidata
- Listed
- NYSE: CATO Source: SEC EDGAR
- Wikipedia
- English article Source: Wikidata
- Parent
- No parent recordedNo parent recordedLike 48,119 of 50,272 companies here. Why
Assets 1
Assets
1
- Petroleum product terminal: 1 assets, 1 asset
Owns 1 petroleum product terminal
| Name. Sort by name, A to Z | Type. Sort by type, A to Z | Role. Sort by role, A to Z | State. Sort by state, A to Z | Held by |
|---|---|---|---|---|
| CATO INC, SALISBURY | Petroleum product terminal | Owns | US-MD | CATO INC |
Sources EIA Energy Atlas
Sources
- EIA US Energy Atlas — Petroleum Product Terminals (points; owner company, EIA-815)Source: U.S. Energy Information Administration, U.S. Energy Atlas, Petroleum Product Terminals (as of September 2021)
Sources 3
Registers
3
Reuse terms
- 3 Open license
Latest read
2026-11-09
From its recordsSourcesThe registers behind this company's assets, projects and RFPs and the facts under its name; the company record itself is derived from them.
Sources
-
View at source →
EIA Energy Atlas ·
EIA US Energy Atlas — Petroleum Product Terminals (points; owner company, EIA-815)
Source: U.S. Energy Information Administration, U.S. Energy Atlas, Petroleum Product Terminals (as of September 2021) · license
EIA Copyrights and Reuse, https://www.eia.gov/about/copyrights_reuse.php (READ 2026-10-25, HTTP 200; quoted on us.eia.atlas.crude_oil_pipelines): "U.S. government publications are in the public domain and are not subject to copyright protection. You may use and/or distribute any of our data, files, databases ... you should use an acknowledgment, which includes the publication date". The layer's own metadata (PetroleumProduct_Terminals_US_202109.shp.xml, READ 2026-10-25) useLimit: "None (public use). Users are advised to thoroughly review the metadata to understand the appropriate use and limitations of the data . These data and related graphics, if available, are not legal documents and are not intended to be used as such."; idCredit "U.S. Energy Information Administration"; abstract "All operable bulk petroleum product terminals located in the 50 States and the District of Columbia with a total bulk shell storage capacity of 50,000 barrels or more, and/or ability to receive volumes from tanker, barge, or pipeline. Survey locations adjusted using public data. Source: "EIA-815, Monthly Bulk Terminal and Blender Report." As of September 2021." Atlas item licenseInfo not readable (Token Required; no public item).
Summary only: the source’s license keeps the full record at the source.
-
View at source →
Wikidata ·
Wikidata — company items (official website, headquarters, description, LEI, stock listing, English Wikipedia link)
Source: Wikidata (CC0) · license
Wikidata:Copyright (https://www.wikidata.org/wiki/Wikidata:Copyright, read 2026-10-22): "All structured data from the main, Property, Lexeme, and EntitySchema namespaces is available under the Creative Commons CC0 License; text in the other namespaces is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply." Wikidata:Licensing (read 2026-10-22): "All structured data (i.e. the main, Property, Lexeme, and EntitySchema namespaces) is released into the public domain under Creative Commons Zero." Access terms that bind us: Wikimedia Foundation User-Agent Policy (read 2026-10-22) "Scripts should use an informative User-Agent string with contact information, or they may be blocked without notice." and "Do not copy a browser's user agent for your bot, as bot-like behavior with a browser's user agent will be assumed malicious."; Wikimedia Foundation API Usage Guidelines v1.0 (2024-08-26) "When using Wikimedia APIs, an operator must: Follow the User-Agent policy ...; Follow rate limiting requests ...; Follow the requirements of the content licenses when republishing downloaded or cached data" and must not "Spread Wikimedia API requests over multiple user agents to hide excessive use by a single operator"; Robot policy (wikitech, read 2026-10-22) "Honor every directive in our robots.txt file.", "When we reply with a 429 Too Many Requests status code respect the delay specified by the Retry-After header", and, Action API rules, "If unauthenticated, keep the concurrency of your requests to 1 at a time, and below 5 requests per second overall." and "if your request takes more than 1 second to serve, please wait 5 seconds before making another request."; Wikidata Query Service User Manual (mediawiki.org, read 2026-10-22) "SPARQL queries can be submitted directly to the SPARQL endpoint with a GET or POST request to https://query.wikidata.org/sparql", "One client (user agent + IP) is allowed 60 seconds of processing time each 60 seconds", "Clients exceeding the limits above are throttled with HTTP code 429. Use Retry-After header to see when the request can be repeated." and "access to the service is limited to 5 parallel queries per IP."
Summary only: the source’s license keeps the full record at the source.
-
View at source →
SEC EDGAR ·
SEC EDGAR company tickers with exchange (company_tickers_exchange.json — CIK, EDGAR conformed name, ticker, exchange)
Source: U.S. Securities and Exchange Commission, EDGAR · license
SEC website, "Privacy and Information Security" (https://www.sec.gov/about/privacy-information, read 2026-10-22), Website Dissemination: "Information presented on sec.gov is considered public information and may be copied or further distributed by users of the web site without the SEC’s permission. Please consider appropriate citation to the SEC as the source." SEC "Accessing EDGAR Data" (https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data, read 2026-10-22): "Current max request rate: 10 requests/second."; "Please declare your user agent in request headers: Sample Declared Bot Request Headers: User-Agent: Sample Company Name AdminContact@<sample company domain>.com"; on this file: "We periodically update these files to provide functionality for EDGAR searches, but do not guarantee accuracy or scope." A compilation by a federal agency (17 U.S.C. §105).
Summary only: the source’s license keeps the full record at the source.
Around this company
Nearby 0
within 25 kmProjects
0
of 2 before the technology filter
0 of 2 · gas, oil and hydrogen technologiesNearbyShowing 0 of 2 nearby projects, narrowed to gas, oil and hydrogen technologies because this company operates oil or liquids infrastructure. Show all 2
No projects of the chosen technologies within 25 km of these assets. Show all technologies.