How you store data depends on how you expect to search/use it. If you are going to need to be able to search for say all the values of water temperature in a given area at a given depth, you have to store all measurement points individually. (this is usefull if you do interpolation, create raster, and so)
If you first look for all data in a given area, then do something, you might store it with linestring. Lastly, depending again on the volume of the data and the usage, you could use the postgres extension pgpointcloud to store your data measurement efficiently. To be more precise, would store your sensing as point (X,Y,Depth ) with attributes (water temperature, conductivity, dissolved oxygen and chlorophyll fluorescence), and would regroup those points into patchs that correspond to points being sensed at the same time. "Writting an application" seems a little bit exagerated given the simplicity of what you want to do, more like wirtting a few functions (in plpgsql or python for instance) Cheers, Rémi C 2015-12-02 9:21 GMT+01:00 Bo Victor Thomsen <bo.victor.thom...@gmail.com>: > Have a look at the "hstore" functions in Postgres. Or maybe use the "json" > facilities in Postgres. Both approaches migth fit your needs > > Regards > > Bo Victor Thomsen > AestasGIS > Denmark > > 2015-12-01 21:02 GMT+01:00 Terry <terry.cur...@shaw.ca>: > >> >> We have been investigating how to get our marine data into and out of our >> PostGIS >> - GeoServer - GeoNetwork on a CentOS system, and we are looking for some >> advice. >> >> We often have the situation of marine data obtained from a sonde lowered >> vertically through the water column. >> The resulting data consists of a lat-long location, datetime, and sensors >> typically measuring water temperature, >> conductivity, dissolved oxygen and chlorophyll fluorescence as a >> function of pressure. >> >> We have typically created CSV files and entered them into PostGIS. We >> create a spatial index based upon the >> 2D lat-long position. This approach does not seem to maximally use the >> "relatedness" of the cast information. >> >> We are considering creating for each horizontal location and datetime a >> series of linestrings of (pressure, parameter) tuples, >> and then reading these into PostGIS. The resulting table records could >> then be up to a thousand times shorter, and searches potentially faster. >> This may imply that we need to write an application to form these >> linestrings, and another to create SQL commands. >> >> Alternatively, we are looking for a nice way to create NetCDF data from >> our profile data, and then input that into PostGIS. >> >> Any suggestions on contemplated approaches, or advice or links to prior >> technology for a similar situation? >> >> -- terry >> _______________________________________________ >> postgis-users mailing list >> postgis-users@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/postgis-users > > > > > -- > Med venlig hilsen > > Bo Victor Thomsen > > > _______________________________________________ > postgis-users mailing list > postgis-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/postgis-users >
_______________________________________________ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/postgis-users
