Posts Tagged ‘ogc’
Wednesday, February 3rd, 2010
I may be a gonzo or it’s just that today I didn’t have my notorious 4th coffee in my favourite Winnie The Pooh cup I got from Pantera on our 14th (or 15th?) anniversary we celebrated a month ago, so…
Apparently, there are situations in which PostGIS could be an affordable anti-GML vaccine jab. It seems there is a potential market for PostGIS to conquer. Perhaps it wouldn’t be estimated as profitable as the H1N1 but who knows what will happen if no one takes a brave stand and stop GML designers! Here I’d eagerly conclude with one of the famous Scottish sentences :-)
Back to the subject matter. Today, I spotted an interesting question on the StackOverflow archives: Is it possible to export spatial data from Sql Server 2008 in gml2 format?. Natively? No, there is no such solution. Presumably, Microsoft thinks forward and thinks GML 2 is a legacy standard. Fair enough, someone has to draw a line between prehistoric and modern, somewhere. Why Microsoft? Again?
Facing such a tremendous suffer Microsoft exposed SQL Server users to, I suggested to visit the “underworld” for a while and hire PostGIS to do the dirty job.
Paraphrasing Andrei Alexandrescu’s, hysterically famous recently, sentence: SQL Server should go!.
Tags: database, gml, ogc, opengis, postgis, rdbms, sptial, sql, sql server, stackoverflow
Posted in gis, open source, osgeo, postgis | No Comments »
Thursday, December 3rd, 2009
Regina crafted matrix of functions available in upcoming PostGIS 1.5. Currently, PostGIS 1.5 is available from trunk in the Subversion repository.
The PostGIS 1.5 documentation is available under the manual-svn node and here is the PostGIS Function Support Matrix.
Regina, great job!
By the way, there is an interesting problem with check marks. does anyone know how to define check marks based on Unicode and make them visible in IE8?
Tags: function, matrix, ogc, postgis, Regina Obe, support
Posted in gis, open source, osgeo, postgis | 3 Comments »
Monday, October 26th, 2009
A couple of minutes ago, Mr Carl Reed, CTO at the Open Geospatial Consortium, posted the GeoTIFF project mailing list with message that may interest hundreds of thousands of users of geospatial raster data around the world. It is thread titled GeoTIFF and the OGC. Hot!
Tags: Carl Reed, geotiff, libgeotiff, ogc, opengeospatial, specification, standard
Posted in geotiff, gis, open source, osgeo | No Comments »
Monday, October 12th, 2009
The recent discussion on LinkedIn OGC forum about Advantages and disadvantages of Open Source GIS has reached at times hot temperatures. Good, as long as a discussion is factual. Unfortunately, the current one sometimes lacks of facts. Shawn Owston has started throwing heavy stones without, again, giving any facts or real examples:
One of the major “issues” with OSGeo in particular is the open and slanderous at times propoganda that is communicated regarding “commercial” companies regarding software quality, maintenance schedule and delivery of bug fixes to their constituent markets.
I agree with propaganda but I do not agree with slanderous propaganda. I have never seen anybody talking or writing on behalf of OSGeo who would be spreading defamation about anyone or anything in the industry or outside.
Shawn, it’s just not right. Please, drop the heavy stones away and pick the facts.
Tags: apollo, defamation, erdas, linkedin, ogc, osgeo, Shawn Owston
Posted in author, open source, osgeo | 4 Comments »
Saturday, October 10th, 2009
I do not advocate anything or anyone. All right, may be I do advocate but only a few small tiny things like C++ programming language, generic programming and high quality of software code and design and my dog, of course. However, I let myself to go down in the discussion about advantages and disadvantages of Open Source GIS on OGC forum at LinkedIn and somewhat at OSGeo mailing list too.
A human nature pisses me off, sometimes. (I am a human being, in case of doubt.) The world is bloody relative but we love to sling absolutes around. Yeah, we love this game! We are not good in learning from mistakes, anyway. Thus, the only achievement of attempting to apply a patch to someone’s buggy ignorance is a waste of time and may be a bit of training in fast typing or boxing ;-)
Paul is right recommending don’t feed the troll!. But, what has been learned is going to be lost, naturally.
Tags: c++, discussion, forum, foss, fsf, gdal ogr json geojson driver format gis geospatial feat, human, ignorance, linkedin, linkedin.com, myth, nature, objectivity, ogc, open source, philosophy, programming, rambling, religion, Shawn Owston, thoughts
Posted in author, c++, gis, open source, osgeo | 3 Comments »
Tuesday, October 6th, 2009
Having problems with understanding semantic of EMPTY geometry?
Paul Ramsey has started wrapping up a proper article on PostGIS Wiki explaining most of the issues related to understanding of emptiness of geometries bothering the community of PostGIS users, and OGC standards users in general.
Check it like it’s hot DevWikiEmptyGeometry. Thanks Paul!
Tags: empty, geometry, ggl, ogc, paul ramsey, postgis, ramsey, standard, wkt
Posted in ggl, gis, osgeo, postgis | No Comments »
Thursday, August 21st, 2008
In PostGIS world, I often need to construct geometry from Well-Known-Binary (WKB) or PostGIS EWKB stream encoded as hex stream. It’s easy to do if I have access to PostgreSQL/PostGIS client which accepts SQL queries:
SELECT
ST_AsText(
ST_GeomFromWKB(
decode('0101000000e5d022dbf93e2e40dbf97e6abc743540', 'hex'),
4326))
I often need to do the same directly in C++ code – parse hex encoded binary stream to raw stream of bytes. Here is simple hex decoder I use:
#include <sstream>
#include <string>
#include <vector>
typedef std::vector<unsigned char> ewkb_t;
// bytes [out] - buffer for binary output
void hex_to_bytes(std::string const& hexstr, ewkb_t& bytes)
{
bytes.clear();
for(std::string::size_type i = 0; i < hexstr.size() / 2; ++i)
{
std::istringstream iss(hexstr.substr(i * 2, 2));
unsigned int n;
iss >> std::hex >> n;
bytes.push_back(static_cast<unsigned char>(n));
}
}
For example, I use it to build FDO geometry objects using another utility CreateGeometryFromExtendedWkb defined in FDO provider for PostGIS:
// POINT (1.234 5.678)
std::string ewkbhex("01010000005839B4C876BEF33F83C0CAA145B61640");
ewkb_t ewkb;
hex_to_bytes(ewkbhex, ewkb);
if (!ewkb.empty())
{
FdoPtr<fdoigeometry> g = CreateGeometryFromExtendedWkb(ewkb);
// ... use geometry
}
Tags: binary, bytes, c++, decode, fdo, fgf, hex, ogc, postgis, stream, wkb
Posted in author, c++, fdo, gis, programming | No Comments »