"We were unable to create your resource." error upon attempted HydroShare export for some services

[ndebuhr]

Example service WebH2O myObservatory Data Publication Service.

Solution may involve only or partially HydroClient application changes.

Insights from Ken:

There are two main issues causing these errors.

The first is that the HydroClient is providing an incorrect SOAP url for all the Community Collaborative Rain, Hail and Snow Network data, which causes the resource creator to be unable to get the WaterML data. The url is mostly correct, but it should end with “?WSDL”. This isn’t hard to fix in the app, but I think it would be best to fix it on the HydroClient so it’s consistent and doesn’t cause problems with other apps. For example, Matthew used a couple different ways of obtaining data for the data series viewer, but I confirmed that these urls will also cause problems for the viewer when opened from HydroShare.

The second issue is related to some of the NWIS data services, and I suspect some of the smaller ones as well that I haven’t tested yet. When the resource creator app is launched from the HydroClient, a form almost identical to the refts files is sent to the resource creator. Some of the NWIS data doesn’t appear to have any methods metadata, so the whole methods section is missing from the form. It’s ok for this data to be empty, but even if it is, the form should still include the methods section and specify each value for this metadata, even if it is null. This is something I can probably update the app to handle, but I think it would be better for the HydroClient to be consistent on this so it doesn’t cause future problems.