Opened 12 years ago
Closed 9 years ago
#312 closed feature (fixed)
Web interface for loading geo-spatial data
Reported by: | Dimitar Misev | Owned by: | Dimitar Misev |
---|---|---|---|
Priority: | major | Milestone: | Future |
Component: | petascope | Version: | 8.3 |
Keywords: | Cc: | ||
Complexity: | Very Hard |
Description (last modified by )
rasdaman is a domain-independed array DBMS, but via it's petascope component it becomes a geo-spatial server with support for various OGC standards — WCS, WCPS, WCS-T.
Currently data can be loaded into rasdaman in two ways:
- By using the rasql language, e.g. via the rasql client tool. This does not provide support for inserting geo-spatial information, which needs to be done manually with SQL scripts.
- By using rasimport, a client tool based on GDAL which can extract geo-information from the input files and automatically insert it into petascope, along with the data into rasdaman.
WCS-T (an OGC standard for updating coverages) is on the agenda for implementation in petascope. A prerequisite for WCS-T implementation is enabling petascope (a Java servlet) to insert coverages itself. There are two possibilities for achieving this:
- Use native system calls to the rasimport command-line tool, which would be very hackish and potentially dangerous.
- Implement it directly in petascope by using the Java bindings for GDAL, and provide a generic interface that can be used by WCS-T implementation or further clients.
Further work would then include
- Implementing WCS-T
- Implementing a web application (an admin page in petascope), that allows to easily load data by selecting files and filling in metadata details (in case it's missing from the files themselves and GDAL can't figure it out).
Related ticket #292
Change History (2)
comment:1 by , 12 years ago
Description: | modified (diff) |
---|
comment:2 by , 9 years ago
Complexity: | → Very Hard |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Has been addressed.