Platform: Website
Browser, if a website issue: Mac, Chrome AND Safari
Screenshots of what you are seeing:
Chrome error
Safari Error
Description of problem:
When I try to download “Reviewed” Insect observations in the Chicago Region, the exporter preview says there are 215. When I attempt to download these 215 observations, the exporter throws the “Can’t download over 200,000 observations” error in both Chrome and Safari.
I fought with it for a while, it continued to reject the export if I set them timeframe from “2024” - “06-20-2025” or “2024” - “2025”. Eventually, I was able to coax it into doing the full export with " d1=01-01-2024 &d2=06-20-2025"
I think what is happening is that exporting “Reviewed: Yes” without date parameters is somehow being interpreted as a giant number, even though the preview export says it’s only 215
Step 1: Prepare an export. The final output code is:
quality_grade=any &reviewed=true &identifications=any &iconic_taxa=Insecta &place_id=124278 &without_taxon_id=48663 &hrank=famil
Step 2: Set region to “Chicago Region, US”
Step 3: Add checkboxes for desired boxes, specifically County, State, Order, Family, Genus, and select all for Observation Fields
Output’s checkboxes:
Columns id, uuid, observed_on_string, observed_on, time_observed_at, time_zone, user_id, user_login, user_name, created_at, updated_at, quality_grade, license, url, image_url, sound_url, tag_list, description, num_identification_agreements, num_identification_disagreements, captive_cultivated, oauth_application_id, place_guess, latitude, longitude, positional_accuracy, private_place_guess, private_latitude, private_longitude, public_positional_accuracy, geoprivacy, taxon_geoprivacy, coordinates_obscured, positioning_method, positioning_device, place_county_name, place_state_name, species_guess, scientific_name, common_name, iconic_taxon_name, taxon_id, taxon_order_name, taxon_family_name, taxon_genus_name, field:associated+plant+name, field:associated+species+with+names+lookup, field:interaction-%3Eherbivore+of, field:interaction-%3Evisited+flower+of, field:name+of+associated+plant, field:nectar++plant, field:nectar+%2F+pollen+delivering+plant, field:nectar+plant, field:robbing+nectar
Here’s the final workaround successful export:
Queryquality_grade=any&reviewed=true&identifications=any&iconic_taxa=Insecta&place_id=124278&without_taxon_id=48663&hrank=family&d1=01-01-2024&d2=06-20-2025
Columns id, uuid, observed_on_string, observed_on, time_observed_at, time_zone, user_id, user_login, user_name, created_at, updated_at, quality_grade, license, url, image_url, sound_url, tag_list, description, num_identification_agreements, num_identification_disagreements, captive_cultivated, oauth_application_id, place_guess, latitude, longitude, positional_accuracy, private_place_guess, private_latitude, private_longitude, public_positional_accuracy, geoprivacy, taxon_geoprivacy, coordinates_obscured, positioning_method, positioning_device, place_county_name, place_state_name, species_guess, scientific_name, common_name, iconic_taxon_name, taxon_id, taxon_order_name, taxon_family_name, taxon_genus_name, field:associated+plant+name, field:associated+species+with+names+lookup, field:interaction-%3Eherbivore+of, field:interaction-%3Evisited+flower+of, field:name+of+associated+plant, field:nectar++plant, field:nectar+%2F+pollen+delivering+plant, field:nectar+plant, field:robbing+nectar
TLDR: It seems like exporting “Reviewed: Yes” requires a date parameter in order to be accepted as an export.