Custom Query (2765 matches)
Results (19 - 21 of 2765)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #391 | fixed | Missing new line in CCRS output | ||
| Description |
Tiny little bug: newline char is missing after the <?xml version="1.0" encoding="ISO-8859-1"?> <CompoundCRS ... > ... <identifier codeSpace='OGC'>...</identifier> <name>...</name> ... </CompoundCRS> |
|||
| #415 | fixed | Missing license header in some WCS2 GML snippets templates | ||
| Description |
Some file in Petascope source which are used as template documents for GML are missing the licence header since they do not represent a whole XML document. A README file should be added, specifying that all the files inside that directory (petascope.wcs2.templates) belong to the licence. |
|||
| #481 | wontfix | rasdl's --database parameter ignored | ||
| Description |
The rasdl —database parameter is effectively only used for display purposes. For example, I erroneously thought I could print the data type definitions for my data base 'PS9RASBASE' with $ rasdl —database PS9RASBASE -p but I still got the RASBASE type definitions (a database which I happen to have also on my system). Furthermore, if —connect and —database are used together they're not checked for consistency. For example the command below effectively shows the type definitions for my PS9RASBASE database, but pretends it shows the ones of GUNDEL_GAUKEL, which doesn't even exist on my system: $ rasdl —database GUNDEL_GAUKEL -connect PS9RASBASE -p rasdl: rasdaman schema and database manipulation tool, rasdaman v8.4.0rc.2-107-g1b868d7 on base DBMS pgsql — generated on 10.10.2013 13:35:42. rasdaman database 'GUNDEL_GAUKEL' type definitions generated on: Thu Oct 10 16:16:24 2013 marray base types … |
|||
