Note:- Only publicly available Legal data can be worked upon.

Unlock a world of legal information with APISCRAPY's user-friendly services – Federal Court Data, State Court Record Data, legal data scraping, and PACER Data. We've made it simple for anyone, from legal professionals to researchers and businesses, to access over 100 million publicly available legal records.

Our Federal Court Data service provides details on federal legal matters, while State Court Record Data gives insights into state-level legal proceedings. With our legal data scraping capabilities, we ensure you have access to the information you need without any hassle. Plus, our integration with PACER Data ensures a comprehensive and reliable source for legal records.

Key Features:

Federal Court Data: Get insights into legal matters at the federal level, all at your fingertips.

State Court Record Data: Access information on legal proceedings at the state level, tailored to your specific needs.

Legal Data Scraping Made Easy: We've simplified the process of gathering legal data, making it accessible for everyone.

PACER Data Integration: Our platform integrates seamlessly with PACER Data, ensuring a reliable and complete source of legal records.

Over 100 Million Records: APISCRAPY provides access to a vast database of over 100 million publicly available legal records, offering unparalleled insights.

Whether you're a legal professional, researcher, or business looking for easy access to legal information, APISCRAPY's services cater to your needs. Choose us for straightforward and comprehensive legal data services, where simplicity and accessibility meet for your convenience.

[ Related Tags: public court records, online court records, federal court cases, Federal court case number search, find Federal court cases, court case by state, court Datasets, state court data, supreme court data, USA court datasets, Federal Court Data API , Litigation Data, Legal Data, Legal API, Legal Law, Legal Court records, Crime records, County court Datasets, All county court Datasets, Legal Analytics, Legal Intelligence, Legal Research, Attorney Data, Legal Parties Data, Judge Data, Case Research, Data Integration, US legal Data API, pacer case locator, pacer court records, free pacer search, pacer criminal case search, federal courts pacer, pacer API , pacer case locator free ]

This dataset was created to help users to go between County - State Name, State-County FIPS, City, or to ZIP Code. Most importantly, this dataset was created because we shouldn't have to pay for free & public data.

Assumptions - HUD uses the most up to date Zip Code boundaries from the USPS when they post their new Quarterly data. *ZIP Codes are updated on a regular basis. Here is an example announcement from the USPS. - City data only available from 2018 onward.

Data Sources

US HUD https://www.huduser.gov/portal/datasets/usps.html

Census Bureau The table data, direct link. This data is only updated once every census, 10 years. The details of the National County text file can be found here

USPS Zip to City Lookup More information can be found here. It's a free API from the USPS. Need to create a username to pull the data.

Data Dictionary

Files 2018 -> Newer - ZIP ZIP Code - STCOUNTFP US State & County FIPS ID - CITY City for that Zip/Fips Code - STATE US State - COUNTYNAME US County Name - CLASSFP FIPS Class Code, as defined by the Census

Files 2010-2017 - ZIP ZIP Code - COUNTYNAME US County Name - STATE US State - STCOUNTFP US State & County FIPS ID - CLASSFP FIPS Class Code, as defined by the Census

FIPS Class Code Details Source Copied 7/29/17

• H1 identifies an active county or statistically equivalent entity that does not qualify under subclass C7 or H6.
• H4 identifies a legally defined inactive or nonfunctioning county or statistically equivalent entity that does not qualify under subclass H6.
• H5 identifies census areas in Alaska, a statistical county equivalent entity.
• H6 identifies a county or statistically equivalent entity that is a really coextensive or governmentally consolidated with an incorporated place, part of an incorporated place, or a consolidated city.
• C7 identifies an incorporated place that is an independent city; that is, it also serves as a county equivalent because it is not part of any county, and a minor civil division (MCD) equivalent because it is not part of any MCD.

Acknowlegement

Foto von Annie Spratt auf Unsplash

Bitcoin Historical Data (2018-2024) - 15M, 1H, 4H, and 1D Timeframes

Dataset Overview

This dataset contains historical price data for Bitcoin (BTC/USDT) from January 1, 2018, to the present. The data is sourced using the Binance API, providing granular candlestick data in four timeframes: - 15-minute (15M) - 1-hour (1H) - 4-hour (4H) - 1-day (1D)

This dataset includes the following fields for each timeframe: - Open time: The timestamp for when the interval began. - Open: The price of Bitcoin at the beginning of the interval. - High: The highest price during the interval. - Low: The lowest price during the interval. - Close: The price of Bitcoin at the end of the interval. - Volume: The trading volume during the interval. - Close time: The timestamp for when the interval closed. - Quote asset volume: The total quote asset volume traded during the interval. - Number of trades: The number of trades executed within the interval. - Taker buy base asset volume: The volume of the base asset bought by takers. - Taker buy quote asset volume: The volume of the quote asset spent by takers. - Ignore: A placeholder column from Binance API, not used in analysis.

Data Sources

Binance API: Used for retrieving 15-minute, 1-hour, 4-hour, and 1-day candlestick data from 2018 to the present.

File Contents

1. btc_15m_data_2018_to_present.csv: 15-minute interval data from 2018 to the present.
2. btc_1h_data_2018_to_present.csv: 1-hour interval data from 2018 to the present.
3. btc_4h_data_2018_to_present.csv: 4-hour interval data from 2018 to the present.
4. btc_1d_data_2018_to_present.csv: 1-day interval data from 2018 to the present.

Automated Daily Updates

This dataset is automatically updated every day using a custom Python program.
The source code for the update script is available on GitHub:
🔗 Bitcoin Dataset Kaggle Auto Updater

Licensing

This dataset is provided under the CC0 Public Domain Dedication. It is free to use for any purpose, with no restrictions on usage or redistribution.

UniCourt’s PACER API provides you with a real-time interface and bulk access to the entire PACER database of civil and criminal federal court data from U.S. District Courts, Bankruptcy Courts, Courts of Appeal, and more.

Our PACER API fully integrates with PACER data so you can streamline pulling the court data you need to automate your internal workflows while saving money on outrageous fees.

Leave behind PACER’s outdated search tools for a modern case search with the precision you need.

Search Smarter and Curb Costs

• With UniCourt’s PACER API you can download the court data you need and lower your PACER costs by pulling data smarter. • When you search for court cases using our API for PACER, your search results show (1) which cases are already available in UniCourt, (2) when they were added to our database and last updated, and (3) the UniCourt Case IDs for each case so you can easily pull any additional data you need. • Don’t pay for PACER data when you don’t have to and stop wasting time logging into PACER everyday when there’s a smarter way to search.

Bulk Access to PACER Data and Documents

• Get the complete historical data set you need for criminal and civil PACER data seamlessly integrated with all your internal applications and client facing solutions. • Leverage UniCourt's extensive free repository of case metadata, docket entries, and court documents to get bulk API access to PACER data without breaking your budget. • Get bulk court data from PACER that has been normalized with our artificial intelligence and enriched with other public data sets like attorney bar data, Secretary of State data, and judicial data.

Track PACER Litigation at Scale

• Combine the power of UniCourt’s PACER API with our Court Data API to track your litigation at scale. • Automatically track PACER cases with ease and receive alerts when new docket updates are available so you never miss a federal court filing. • Save money on outrageous PACER fees by leveraging the sophisticated algorithms we’ve developed to intelligently track court cases in bulk without incurring over-the-top fees.

OpenAQ has collected 231,965,688 air quality measurements from 8,469 locations in 65 countries. Data are aggregated from 105 government level and research-grade sources. https://medium.com/@openaq/where-does-openaq-data-come-from-a5cf9f3a5c85 Note: this dataset is temporary not updated. We're currently working to update it as soon as possible.Disclaimers:- Some records contain encoding issues on specific characters; those issues are present in the raw API data and were not corrected.- Some dates are set in the future: those issues also come from the original data and were not corrected.

A log of dataset alerts open, monitored or resolved on the open data portal. Alerts can include issues as well as deprecation or discontinuation notices.

subject to appropriate attribution.

CIMIS data is available to the public free of charge via a web Application Programming Interface (API). The CIMIS Web API delivers data over the REST protocol from an enterprise production platform. The system provides reference evapotranspiration (ETo) and weather data from the CIMIS Weather Station Network and the Spatial CIMIS System. Spatial CIMIS provides daily maps of ETo and solar radiation (Rs) data at 2-km grid by coupling remotely sensed satellite data with point measurements from the CIMIS weather stations. In summary, the data provided through the CIMIS Web API is comprised by a) Weather and ETo data registered at the CIMIS Weather Station Network (more than 150 stations located throughout the state of California and b) Spatial CIMIS System data that provides statewide ETo and solar radiation (Rs) data as well as aeraged ETo by zip-codes. The RESTful HTTP services reach a broader range of clients; including Wi-Fi aware irrigation smart controllers as well as browser and mobile applications, all while expanding the delivery options by providing data in either JSON or XML formats.

The Department of the Prime Minister and Cabinet is no longer maintaining this dataset. If you would like to take ownership of this dataset for ongoing maintenance please contact us.

PLEASE READ BEFORE USING

The data format has been updated to align with a tidy data style (http://vita.had.co.nz/papers/tidy-data.html).

The data in this dataset is manually collected and combined in a csv format from the following state and territory portals:

• https://www.cmtedd.act.gov.au/communication/holidays
• https://www.nsw.gov.au/about-nsw/public-holidays
• https://nt.gov.au/nt-public-holidays
• https://www.qld.gov.au/recreation/travel/holidays/public
• https://www.safework.sa.gov.au/resources/public-holidays
• https://worksafe.tas.gov.au/topics/laws-and-compliance/public-holidays
• https://business.vic.gov.au/business-information/public-holidays
• https://www.commerce.wa.gov.au/labour-relations/public-holidays-western-australia

The data API by default returns only the first 100 records. The JSON response will contain a key that shows the link for the next page of records. Alternatively you can view all records by updating the limit on the endpoint or using a query to select all records, i.e. /api/3/action/datastore_search_sql?sql=SELECT * from "{{resource_id}}".

All cities with a population > 1000 or seats of adm div (ca 80.000)Sources and ContributionsSources : GeoNames is aggregating over hundred different data sources. Ambassadors : GeoNames Ambassadors help in many countries. Wiki : A wiki allows to view the data and quickly fix error and add missing places. Donations and Sponsoring : Costs for running GeoNames are covered by donations and sponsoring.Enrichment:add country name

Band Protocol is a cross-chain data oracle platform that aggregates and connects real-world data and APIs to smart contracts. Band's flexible oracle design allows developers to query any data including real-world events, sports, weather, random numbers and more. Developers can create custom-made oracles using WebAssembly to connect smart contracts with traditional web APIs within minutes. BandChain is designed to be compatible with most smart contract and blockchain development frameworks. It does the heavy lifting jobs of pulling data from external sources, aggregating them, and packaging them into the format that’s easy to use and verified efficiently across multiple blockchains. This dataset is one of many crypto datasets that are available within the Google Cloud Public Datasets . As with other Google Cloud public datasets, you can query this dataset for free, up to 1TB/month of free processing, every month. Watch this short video to learn how to get started with the public datasets. Want to know how the data from these blockchains were brought into BigQuery, and learn how to analyze the data? Dowiedz się więcej

Band Protocol is a cross-chain data oracle platform that aggregates and connects real-world data and APIs to smart contracts. Band's flexible oracle design allows developers to query any data including real-world events, sports, weather, random numbers and more. Developers can create custom-made oracles using WebAssembly to connect smart contracts with traditional web APIs within minutes. BandChain is designed to be compatible with most smart contract and blockchain development frameworks. It does the heavy lifting jobs of pulling data from external sources, aggregating them, and packaging them into the format that’s easy to use and verified efficiently across multiple blockchains. This dataset is one of many crypto datasets that are available within the Google Cloud Public Datasets . As with other Google Cloud public datasets, you can query this dataset for free, up to 1TB/month of free processing, every month. Watch this short video to learn how to get started with the public datasets. Want to know how the data from these blockchains were brought into BigQuery, and learn how to analyze the data? Learn more

Statistics of trips taken on HireDevice in Hamilton City. To get data for this dataset, please call the API directly talking to the HCC Data Warehouse: https://api.hcc.govt.nz/OpenData/get_hiredevice_trip?Page=1&Start_Date=2020-10-01&End_Date=2020-10-02. For this API, there are three mandatory parameters: Page, Start_Date, End_Date. Sample values for these parameters are in the link above. When calling the API for the first time, please always start with Page 1. Then from the returned JSON, you can see more information such as the total page count and page size. For help on using the API in your preferred data analysis software, please contact dale.townsend@hcc.govt.nz. NOTE: Anomalies and missing data may be present in the dataset. Column_InfoTrip_Id, varchar : Unique identifier of the tripTrip_Duration, int : Duration of the trip in secondsTrip_Distance, int : Distance of the trip in metresDevice_Id, varchar : Unique identifier of the GPS device on the scooterVehicle_Id, varchar : Unique identifier of the scooterStart_Time, datetime : Date and time that the trip startedEnd_Time, datetime : Date and time that the trip ended Relationship This table is referenced by HireDevice_Route Analytics For convenience Hamilton City Council has also built a Quick Analytics Dashboard over this dataset that you can access here. Disclaimer Hamilton City Council does not make any representation or give any warranty as to the accuracy or exhaustiveness of the data released for public download. Levels, locations and dimensions of works depicted in the data may not be accurate due to circumstances not notified to Council. A physical check should be made on all levels, locations and dimensions before starting design or works. Hamilton City Council shall not be liable for any loss, damage, cost or expense (whether direct or indirect) arising from reliance upon or use of any data provided, or Council's failure to provide this data. While you are free to crop, export and re-purpose the data, we ask that you attribute the Hamilton City Council and clearly state that your work is a derivative and not the authoritative data source. Please include the following statement when distributing any work derived from this data: ‘This work is derived entirely or in part from Hamilton City Council data; the provided information may be updated at any time, and may at times be out of date, inaccurate, and/or incomplete.'

Drop off and pick up records of HireDevice in Hamilton City. To get data for this dataset, please call the API directly talking to the HCC Data Warehouse: https://api.hcc.govt.nz/OpenData/get_hiredevice_status_change?Page=1&Start_Date=2020-10-01&End_Date=2020-10-02. For this API, there are three mandatory parameters: Page, Start_Date, End_Date. Sample values for these parameters are in the link above. When calling the API for the first time, please always start with Page 1. Then from the returned JSON, you can see more information such as the total page count and page size. For help on using the API in your preferred data analysis software, please contact dale.townsend@hcc.govt.nz. NOTE: Anomalies and missing data may be present in the dataset.

Column_InfoId, bigint : Unique identifier of the eventDevice_Id, varchar : Unique identifier of the GPS device on the scooterVehicle_Id, varchar : Unique identifier of the scooterVehicle_Type, varchar : Vehicle type - always scooterEvent_Type, varchar : Type of event that occurredEvent_Type_Reason, varchar : Why the event happened - rebalance or maintenanceEvent_Time, datetime : Date and time that the event occurredBattery_Pct, numeric : Battery percentage of the scooter a the time of the status changeLongitude, numeric : East-west geographic coordinatesLatitude, numeric : North-south geographic coordinates

Relationship






Analytics

For convenience Hamilton City Council has also built a Quick Analytics Dashboard over this dataset that you can access here.

Disclaimer

Hamilton City Council does not make any representation or give any warranty as to the accuracy or exhaustiveness of the data released for public download. Levels, locations and dimensions of works depicted in the data may not be accurate due to circumstances not notified to Council. A physical check should be made on all levels, locations and dimensions before starting design or works.

Hamilton City Council shall not be liable for any loss, damage, cost or expense (whether direct or indirect) arising from reliance upon or use of any data provided, or Council's failure to provide this data.

While you are free to crop, export and re-purpose the data, we ask that you attribute the Hamilton City Council and clearly state that your work is a derivative and not the authoritative data source. Please include the following statement when distributing any work derived from this data:

‘This work is derived entirely or in part from Hamilton City Council data; the provided information may be updated at any time, and may at times be out of date, inaccurate, and/or incomplete.'

The Copernicus DEM is a Digital Surface Model (DSM) which represents the surface of the Earth including buildings, infrastructure and vegetation. This DSM is derived from an edited DSM named WorldDEM, where flattening of water bodies and consistent flow of rivers has been included. In addition, editing of shore- and coastlines, special features such as airports, and implausible terrain structures has also been applied.

The WorldDEM product is based on the radar satellite data acquired during the TanDEM-X Mission, which is funded by a Public Private Partnership between the German State, represented by the German Aerospace Centre (DLR) and Airbus Defence and Space. OpenTopography is providing access to the global GLO-90 Defence Gridded Elevation Data (DGED) 2023_1 version of the data hosted by ESA via the https PRISM service. Details on the Copernicus DSM can be found on this ESA site.

• Previous to July 23rd 2024, OpenTopography was providing access to the Copernicus data through the public AWS S3 bucket established by Sinergise. As of July 23rd 2024, Opentopography is providing the DGED 2023_1 version of GLO-90 as downloaded directly from ESA (direct download instructions can be found here)
• The original gridded data from ESA is in geographic coordinates where the longitudinal cell spacing increases as a function of latitude for regions north of 50N and south of 50S. For more details see the Grid Spacing section of the Copernicus DEM handbook. In order to keep the pixel dimensions uniform, OpenTopography resamples data north of 50 degrees latitude and south of -50 degrees latitude in order to output a consistent 3 Arc-second product for data accessed through the web-interface or API. Users who need data north of 50N or south of 50S, and prefer to use the original, longitude-varying grid spacing can download cloud optimized geotiff (COG) versions of the tiles from our bulk download interface, or download the original data directly from ESA.
• The GLO-90 datasets are available on a free basis for the general public under the terms and conditions of the Copernicus license found here.

The Car Park API provides real time and historical occupancy of selected car parks. This API provides the occupancy for Transport Park&Ride car parks. Transport Park&Ride is designed to free-up more spaces at commuter car parks for those who want to travel on public transport. The data feed contains the parking occupancy information by type in real time. The Sydney Metro stations for Tallawong, Bella Vista, Hills Showground, Cherrybrook and Kellyville are reporting real time occupancy levels. It is intended other car park occupancy data will be enabled via this API in the future. Click here for more information on Transport Park&Ride.

The Government is committed to the transparency of the Grand Debate and this requirement of transparency is also borne by the College of Guarantors. Thus, all contributions to the debate, whether sent by post, by email or via online forms, will eventually be accessible to all. The restitution of local initiative meetings, the replies to the questionnaires, the citizens’ notebooks opened in the town halls, the free contributions, will be progressively and regularly released online under free license. ### Data Re-Use License This license allows the exhaustive reuse of data anonymised by any citizen. All data will also be accessible via an API, making automated processing possible. Everyone will therefore be able to appropriate the fruit of the collective reflection of the participants in the Grand Débat. In order to determine the rights and duties of re-users, the Grand Débat mission has adopted the open license of Etalab, which you agree to respect by downloading the data made available on this site or by using the APIs. Here are the main features of this “Open License”: — an open, free and free license that provides the necessary legal certainty for producers and re-users of public data; — a licence that promotes the widest re-use by allowing the reproduction, redistribution, adaptation and commercial exploitation of data; — a license which is part of an international context and is compatible with the standards of open data licenses developed abroad, in particular those of the British Government (Open Government Licence) and other international standards (ODC-BY, CC-BY 2.0). — a strong requirement of transparency of data and quality of sources by making the mention of paternity mandatory.

Harness AI-Driven Precision for Global Company Insights Leverage cutting-edge AI agents to fetch and validate company registry data in real-time, bypassing obsolete databases. Unlike traditional providers, our service dynamically retrieves data directly from government registries worldwide, ensuring up-to-the-minute accuracy and eliminating outdated records.

Key Features 1. AI-Powered Real-Time Access: Deploy autonomous AI agents to collect and structure data from any national registry, even those with dynamic layouts or authentication barriers.

1. Universal Registry Compatibility: Seamlessly extract data from 250+ countries, including hard-to-access regions, with automatic translation and normalization.

2. Document Processing: Parse financial filings, annual reports, and legal documents (PDF, DOCX) using NLP-driven analysis. Extract key attributes like ownership structures, director details, and compliance status.

3. Format Flexibility: Receive data via API, CSV, JSON, or custom formats (e.g., PostgreSQL DB, Google Sheets) with hourly/daily refresh options.

4. 99% Accuracy Guarantee: Multi-layer validation via AI cross-referencing and human audits ensures error-free datasets.

Data Sourcing & Coverage 1. Sources: Direct integration with 1,800+ government registries of your choice on demand, supplemented by AI-enhanced verification of public filings and regulatory submissions.

1. Attributes: Company name, registration number, directors, shareholders, financials, litigation history, and industry-specific certifications (e.g., ISO, NAICS).

2. Historical Data: 10+ years of archived records, updated in real-time.

Use Cases 1. Due Diligence: Verify company legitimacy for mergers, acquisitions, or partnerships.

1. Compliance: Streamline KYC/AML workflows with automated registry checks.

2. Market Research: Track competitor expansions, ownership changes, or industry trends.

3. Risk Management: Monitor regulatory violations or financial instability signals.

4. Credit Reporting: Automate end-to-end credit report creation process.

Technical Specifications 1. Delivery: API (REST/GraphQL), SFTP, cloud sync (AWS S3, Google Cloud).

1. Integration: Custom connectors for Salesforce, HubSpot, and BI tools (Tableau, Power BI).

2. Latency: Sub-5-second to 60 mins response time for on-demand queries based on the complexity and response time of registry.

Why Choose Us? 1. Pioneers in AI Agent Technology: Outperform static datasets with live registry scraping.

1. GDPR/CCPA Compliance: Data sourced ethically from public registries, with audit trails on output.

2. Free Sample: Test 100 records at zero cost.

Vehicle travel time and delay data on routes in Hamilton City, based on Bluetooth sensor records. To get data for this dataset, please call the API directly talking to the HCC Data Warehouse: https://api.hcc.govt.nz/OpenData/get_traffic_route_stats?Page=1&Start_Date=2021-06-02&End_Date=2021-06-03. For this API, there are three mandatory parameters: Page, Start_Date, End_Date. Sample values for these parameters are in the link above. When calling the API for the first time, please always start with Page 1. Then from the returned JSON, you can see more information such as the total page count and page size. For help on using the API in your preferred data analysis software, please contact dale.townsend@hcc.govt.nz. NOTE: Anomalies and missing data may be present in the dataset. Column_InfoRoute_Id, int : Unique route identifierTravel_Time, int : Average travel time in seconds to travel along the routeDelay, int : Average travel delay in seconds, calculated as the difference between the free flow travel time and observed travel timeExcess_Delay, int : Excess Delay is similar to Delay, but it ignores recurring (expected) delays associated with peak times of dayDate, varchar : Starting date and time for the recorded delay and travel time, in 15 minute periods Relationship This table reference to table Traffic_Route Analytics For convenience Hamilton City Council has also built a Quick Analytics Dashboard over this dataset that you can access here. Disclaimer Hamilton City Council does not make any representation or give any warranty as to the accuracy or exhaustiveness of the data released for public download. Levels, locations and dimensions of works depicted in the data may not be accurate due to circumstances not notified to Council. A physical check should be made on all levels, locations and dimensions before starting design or works. Hamilton City Council shall not be liable for any loss, damage, cost or expense (whether direct or indirect) arising from reliance upon or use of any data provided, or Council's failure to provide this data. While you are free to crop, export and re-purpose the data, we ask that you attribute the Hamilton City Council and clearly state that your work is a derivative and not the authoritative data source. Please include the following statement when distributing any work derived from this data: ‘This work is derived entirely or in part from Hamilton City Council data; the provided information may be updated at any time, and may at times be out of date, inaccurate, and/or incomplete.'