The above worked until recently (I do not know when it stopped working). However, now the parameter fg=geospatial causes it to return 0 results. If I remove that parameter, I will get a lot of results, but they are not limited to geospatial.
My question is, has the geospatial limiting parameter changed, and if so, what is the new parameter? If not, how would you recommend that I limit my results to only geo?
I've tried "metadata_type=geospatial" which works with the main data.gov homepage when you pick "Dataset Type" -> "geospatial" but this doesn't work with the api.
Hello,
I have an External Data Sources interface for finding geospatial data. Example search: https://www.lib.ncsu.edu/gis/search/search.php?q=counties
In my code, I have been using this path to obtain results in json that I can then parse: https://catalog.data.gov/api/3/action/package_search?q=counties&fq=geospatial
The above worked until recently (I do not know when it stopped working). However, now the parameter fg=geospatial causes it to return 0 results. If I remove that parameter, I will get a lot of results, but they are not limited to geospatial.
My question is, has the geospatial limiting parameter changed, and if so, what is the new parameter? If not, how would you recommend that I limit my results to only geo?
I've tried "metadata_type=geospatial" which works with the main data.gov homepage when you pick "Dataset Type" -> "geospatial" but this doesn't work with the api.
For now, I am using https://catalog.data.gov/api/3/action/package_search?q=$query to avoid having 0 results.
Thank you very much for your time and suggestions!
Jeff Essic