Sanitize site codes to follow ODM 1.1.1 conventions?

[emiliom]

Should WOFpy sanitize site codes from source data and handle (advertise and accept) only the sanitized versions in its service endpoints?

This potential need came up in #219, in the context of the Luquillo CZO ODM2 instance, its WOFpy implementation, and registration of that endpoint with the CUAHSI water data services. Copying statements from Martin Seul (CUAHSI) and @miguelcleon:

It seems you have spaces in the sitecode, could you remove them as this seems to create a problem for the harvesting, I’ll see on our end as well if we can mitigate this. In odm 1.1.1 allows sitecode in the range of AZ (case insensitive) , 0-9, and “.”, “-“, and “_”.
https://www.cuahsi.org/uploads/pages/img/ODM1.1DesignSpecifications_.pdf

Perhaps WOFpy should replace spaces in the sitecode with dashes or underscores.