You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DataONE node registry now contains lat/lon pairs for each node, so we can get node information from a query rather than hardcoding the static csv file. Update the Rmd file to get the data that way, as illustrated by this curl command (from @datadavev ):
echo"year,label,description,lon,lat,alt,name,uri"> dataone-nodes.csv
curl -s "https://cn.dataone.org/cn/v2/node"| xml sel -T -t \
-m "//node[(property/@key='CN_operational_status' and property='operational' or property='replicator') and identifier!='urn:node:CN']" \
-v "substring(property[@key='CN_date_operational'],1,4)" -o ",\"" \
-v "property[@key='CN_node_name']" -o "\",\"" \
-v "normalize-space(description)" -o "\"," \
-v "property[@key='CN_location_lonlat']" -o ",0," \
-v identifier -o "," \
-v "property[@key='CN_logo_url']" -n \
>> dataone-nodes.csv
The text was updated successfully, but these errors were encountered:
The DataONE node registry now contains lat/lon pairs for each node, so we can get node information from a query rather than hardcoding the static csv file. Update the Rmd file to get the data that way, as illustrated by this curl command (from @datadavev ):
The text was updated successfully, but these errors were encountered: