external names should use rasdaman, not petascope

[Peter Baumann]

In many places "petascope" is used, eg, war files, in WPS ("petascope.wps.n52.ProcessCoverages"). This is confusing for the users of rasdaman, branding should be uniform - in the end, petascope is just one out of many rasdaman components. Hence, in all code the naming should be replaced accordingly.

Endpoints are to be renamed as follows:
/rasdaman (landing page with desctiption of server and pointers to available endpoints)
/rasdaman/ows (landing page for OGC Web Services, with pointers to second level ones)
/rasdaman/ows/wps
/rasdaman/ows/wms
/rasdaman/ows/wcs : including extensions such as WCS-T
/rasdaman/ows/wcps
/rasdaman/rasql : endpoint for the upcoming web interface to rasql

The sources for the landing pages are in source:applications/petascope/templates

Documentation for upcoming 9.0 to be updated accordingly

[Dimitar Misev]

Maybe we should also change the package structure in petascope from petascope.* org.rasdaman.*

[Peter Baumann]

…and rephrase the petascope default HTML page.

[abeccati]

Looks related to #270

There we had different endpoints but we can resume to have a single "rasdaman" root

/rasdaman (landing page with desctiption of server and pointers to available endpoints)
/rasdaman/ows : single endpoint for all OGC web services interfaces (WCS, WMS, WCPS, etc)
/rasdaman/rasql : endpoint for the upcoming web interface to rasql

[abeccati]

As the codebase stands now, we'd like to avoid checking which service request is for which service type but want to keep them grouped so we can change our mind in future without having a new (common endpoint to define = ows).

Updating accordingly, that will be the 9.0 endpoint definition.

[abeccati]

Adding detail for wcst interface (supported by WCS). Linkning and superseding (opted for separate endpoints for now) ticket #270 (Raising priority to that of superseded one).

[Peter Baumann]

shold we use lowercase wcs etc. for homogeneity?

[Dimitar Misev]

I vote for lowercase.

I'll still say that the /ows doesn't bring anything essential but 4 redundant bytes.

[abeccati]

Indeed all lowercase sounds good, updated

[abeccati]

interim work

[abeccati]

Attached patch changes external names (and war archive also) to rasdaman

I cannot test it due to:
​https://groups.google.com/forum/#!topic/rasdaman-dev/HakA4S47UUs

There are still few things to be addressed:
/rasdaman (landing page with desctiption of server and pointers to available endpoints)
/rasdaman/ows (landing page for OGC Web Services, with pointers to second level ones)
/rasdaman/ows/wcs : including extensions such as WCS-T (done but requires dedicated class to handle versions and extensions such as wcs-t, relies on petascope interface for now)

Futhermore, sending a WCS request gives a null pointer exception while sending it to the "nonexistant" ows/wcs2 endpoint gets a complaint about version

Feel free to pick it up and build on it for testing

[Piero Campalani]

Patch submitted, but keep the ticket open until we solve the issues listed by Alan in comment:11, that is:

• missing landing pages;
• WCS servlet to be unique for different versions and extensions.

This means, if I'm not wrong, that PetascopeInterface will probably be dropped or strongly revised.

[Piero Campalani]

See changeset:40a95ec.

Replying to pcampalani:

Patch submitted, […]

[abeccati]

I think /rasdaman/ows can be covered by the current petascope landing page (or a revision of it I guess) while the server level one should hold overall server/endpoints info