Frequently Asked Questions

How do I update the file for my network?

To update a network, simply make the changes to the relevant JSON file and re-upload it. The new file will immediately replace the old one. We recommend this is done whenever there are changes to a network, for example, the addition of new sites, decommissioning of sites, or changes in site location or observations.

Does the file name matter?

No. The name of the JSON file does not matter when uploading it to NEMSR.  The code containing the network ID (e.g. "id": "12") within the JSON file does matter as the NEMSR validates the file to ensure the network has been registered. The list of registered networks and their IDs are shown at

How should decommissioned sites be handled?

If a site was previously operational and has been now decommissioned, we encourage you to include those sites in your network, particularly if the operating authority still makes the observational data available publically. The information model allows sites to be tagged as decommissioned through the Site Status attribute.

How will mobile platforms such as Argo buoys be handled?

Although we don’t have any mobile platforms in the first release, the NEMSR information model could accommodate such monitoring data with minor modifications.

Does the NEMSR keep the raw files after a successful upload?

Yes, every file uploaded to NEMSR is stored and backed-up in the case of disaster. User logs are also captured but neither will initially be available to data providers. They can be accessed manually by the system owner and can be made available upon request.

When I am validating a file, will it be possible to download the results?

In the first release validation results can only be viewed, and then copied and pasted, for data provider reference. Shortly after the initial release we hope to incorporate a download mechanism