Opened 12 years ago
Closed 8 years ago
#974 closed enhancement (wontfix)
Geospatial Foreign Data Wrappers
|Reported by:||robe||Owned by:||pramsey|
Now that PostgreSQL 9.1 has produced usable SQL/MED bindings and with raster we now have libgdal dependency. It seems to me we have all the ingredients to make some very slick geospatial data wrappers.
Here is an example from PgCon2011 talk leveraging these bindings:
Change History (20)
comment:1 by , 12 years ago
comment:4 by , 12 years ago
Yes that is what I was thinking.
comment:5 by , 11 years ago
comment:6 by , 11 years ago
comment:7 by , 11 years ago
|Type:||defect → enhancement|
To add more possible fdw-implementations
If fdw can be used against twitter it ought to be possible to use it against a gps-stream.
A fdw catching the data from gpsd.
comment:8 by , 10 years ago
This may need to require 9.2+ or higher. They've changed the API quite a bit in 9.2 for FDW to the point that trying to do a bunch of IFDEFs could become painful and most 9.1 FDWs are broken I believe. I got wind of this when I complained to Andrew I couldn't build my favortie FDW anymore on 9.2 and he fixed it but decided to have two parallel branches instead after that.
comment:9 by , 9 years ago
Did anyone start on this ? I'm starting to work on a ogr2ogr FWD for both vectors and rasters, with 9.3 min dependency as a focus. Not sure it'd make sense for it to be immediately part of postgis, rather than a separate module (as most FWD are).
comment:10 by , 9 years ago
not to my knowledge. I would like it to be part of postgis. Well as a separate extension similar to postgis_topology and postgis_tiger_geocoder that people can choose to or not to install. I figure the biggest group of users for it will already have postgis installed so why package separately
comment:11 by , 9 years ago
Are you planning to have write support?
comment:12 by , 9 years ago
No write support planned initially. The reason for a separate repository would mainly be to be able to have a faster release cycle.
comment:13 by , 9 years ago
okay got it or slower release cycle so along the lines of point_cloud.
For first version makes sense. I guess we can always decide later to bring it back in.
comment:14 by , 9 years ago
comment:15 by , 9 years ago
I found this project which may make implementation of an ogr2ogr (or generally GDAL) FDW easier: http://multicorn.org
It basically makes you do that in python…
comment:16 by , 9 years ago
I saw that but couldn't get the darn thing to work on windows . Perhaps I didn't try hard enough.
comment:17 by , 9 years ago
I tried a bit harder → https://github.com/Kozea/Multicorn/pull/69
comment:18 by , 8 years ago
|Milestone:||PostGIS Future → PostGIS 2.2.0|
I knew someone would step up to the plate to do this. Thanks pramsey. I'll be screaming if this doesn't compile on windows
comment:19 by , 8 years ago
comment:20 by , 8 years ago
|Status:||new → closed|
This really isn't a postgis concern, FDW's might work w/ postgis, but postgis doesn't have to do anything to make it happen.
You mean that could be an easy way to implement full support for out-of-db rasters (and out-of-db vectors of course!)?