#3191 closed defect (wontfix)
coordinate reference system issue when exporting to Rasterlite
Reported by: | vincent | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.0.6 |
Component: | Raster | Version: | unspecified |
Keywords: | gdal export, Rasterlite | Cc: | |
CPU: | Unspecified | Platform: | Unspecified |
Description
r.out.gdal allows to export raster data to Rasterlite tables. It looks like the output raster table lacks a correct reference to the srid it should be linked to, i.e. in the geometry_column table, srid equals -1 for the newly written raster table.
Change History (8)
comment:1 by , 8 years ago
follow-up: 4 comment:2 by , 8 years ago
Yes, I've come to the same observation so far, but I don't know enough about how GRASS parses projection info to gdal; sorry for this rather naive question but in the case of GTiff driver why then is there no need to worry about coordinate reference system information for it to work?
Well, if you all prefer, we can close the ticket.
follow-up: 6 comment:4 by , 8 years ago
Replying to vincent:
Yes, I've come to the same observation so far, but I don't know enough about how GRASS parses projection info to gdal; sorry for this rather naive question but in the case of GTiff driver why then is there no need to worry about coordinate reference system information for it to work?
Well, if you all prefer, we can close the ticket.
taken from the GDAL ML
> is this intentional that there is no srs by a simple gdal_translate of a > geotiff to a Rasterlite db? From what I can see the driver doesn't handle adding a new entry in the spatial_ref_sys table if there's no AUTHORITY node, such as in your use case. From what I can see, it also probably doesn't properly support creating entries in spatial_ref_sys with Spatialite 4 layout (the driver has been likely developped during Spatialite 3 era) It is "intentional" in the meaning that this wasn't implemented, but could potentially be added. Could be worth a ticket in Trac. > maybe there is some other command line option related to Rasterlite db > which I'm missing? No, the workaround is the one you found. Make sure a EPSG code is attached to the input dataset, or assign it explictly
I think this ticket can be closed; but I'll open another one for the last issue mentioned above.
comment:5 by , 8 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
follow-up: 7 comment:6 by , 8 years ago
follow-up: 8 comment:7 by , 8 years ago
Replying to hellik:
Replying to hellik:
I think this ticket can be closed; but I'll open another one for the last issue mentioned above.
ticket opened; see #3193
Not sure I understand: do you mean adding this "AUTHORITY node" ability to r.out.gdal may help in the present case? or is there really something wrong with gdal?
comment:8 by , 8 years ago
Replying to vincent:
Replying to hellik:
Replying to hellik:
I think this ticket can be closed; but I'll open another one for the last issue mentioned above.
ticket opened; see #3193
Not sure I understand: do you mean adding this "AUTHORITY node" ability to r.out.gdal may help in the present case? or is there really something wrong with gdal?
regarding "AUTHORITY node", maybe yes.
as Even mentioned, there is nothing wrong in gdal, just not implemented.
Replying to vincent:
tested with
with data (downloadable here data.
testing with gdal_translate and r.out.gdal shows
so it seems to be a gdal "issue"; maybe it's also worth to ask in the GDAL ML?