-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Survey list on geoserver with all surveys (including embargoed) and full coordinates (for SQ+ and website) #1286
Comments
From NRMN meeting email from Lizzi (17 Aug 2023): |
harvester changes are in prod. |
Documenting for reference: Direction was added but further progress on endpoint publication was hindered by harvester issue which incidentally impacted the public endpoints harvest and refresh in Geoserver-123/portal ( #1352) he issue with the Harvester has been resolved (aodn/harvesters#1032) enabling successful harvesting of data from the public endpoint into the harvest DB and subsequent publication on the portal. Changes to the ep_tpac published on Geoserver-rc need to be communicated to Ming |
ep_TPAC layer deployed to Prod. |
The geoserver endpoint available at Also (more importantly) the has_pqs_catalogued field is incorrect. all the entries say 'false'. |
To download the full list of features in the ep_tpac layer (or any geoserver layer), you need to remove |
Thank you, that would be great. There is some momentum today from Ari to look into utilizing this endpoint so it would be good to make sure its correct. |
There is a need for a survey list available on the geoserver which contains all surveys (including embargoed surveys from WA). This can be used by TPAC for cataloguing PQs, and Squidle+ for referencing the the TPAC API and also ingesting metadata for images (eg. depth, date).
For these sources the fields necessary are:
survey_id, location, site_code, site_name, latitude, longitude, depth, survey_date, hour, direction, pq_zip_url
Latitude and Longitude can be in full resolution (not truncated to 2 decimal points).
The text was updated successfully, but these errors were encountered: