↧
Source code checked in, #19566
↧
Released: PostGIS GDO 1.2.0.2 (Nov 23, 2012)
There are two important changes in this PostGIS GDO release. The source code has been upgraded so that it gets compiled with the latest version of MinGW. So we don't include MS VC++ build at the moment. The second change is that the
most of the Database Utilities functionality has been moved into PsgDBUtils.dll which can be reused by 3rd party application to administer GDO metadata.
Fixed in this version
Fixed from previous versions
Features supported from older versions
Fixed in this version
- Added MS build again and support for compiling with MS VS 2010
Fixed from previous versions
- Fixed another problem with MULTICURVE geometries
- Fixed problem with deleting tables
- Fixed problem with Text and Image feature classes not working with PostGIS 2.0
- Feature classes in Database Utilities alphabetically sorted
- Fixed problem with MULTICURVE geometries
- Fixed problem with pick lists
- Fixed problem with renaming table columns
- Added support for scandinavian coordinate systems
- Fixed problem with point geometries
- Fixed problem with spatial filter
- Arbitrary database encoding should be supported now (although not tested)
- Added support for G/I Toolkit
- Added EPSG 2169
- Added edit field for specifying the port. The field can be left blank.
Features supported from older versions
- The table and field names are CASE SENSITIVE now. Moreover, it is possible to use non-ASCII characters (e.g. Cyrillic) in the table and fields names. The names still cannot contain spaces, dots (except schema delimiter), comas, quotes and double quotes.
- schemas
- writable views
- user right handling
↧
↧
Created Release: PostGIS GDO 1.2.0.2 (Nov 23, 2012)
There are two important changes in this PostGIS GDO release. The source code has been upgraded so that it gets compiled with the latest version of MinGW. So we don't include MS VC++ build at the moment. The second change is that the most of the Database Utilities functionality has been moved into PsgDBUtils.dll which can be reused by 3rd party application to administer GDO metadata.
Fixed in this version
Fixed from previous versions
Features supported from older versions
Fixed in this version
- Added MS build again and support for compiling with MS VS 2010
Fixed from previous versions
- Fixed another problem with MULTICURVE geometries
- Fixed problem with deleting tables
- Fixed problem with Text and Image feature classes not working with PostGIS 2.0
- Feature classes in Database Utilities alphabetically sorted
- Fixed problem with MULTICURVE geometries
- Fixed problem with pick lists
- Fixed problem with renaming table columns
- Added support for scandinavian coordinate systems
- Fixed problem with point geometries
- Fixed problem with spatial filter
- Arbitrary database encoding should be supported now (although not tested)
- Added support for G/I Toolkit
- Added EPSG 2169
- Added edit field for specifying the port. The field can be left blank.
Features supported from older versions
- The table and field names are CASE SENSITIVE now. Moreover, it is possible to use non-ASCII characters (e.g. Cyrillic) in the table and fields names. The names still cannot contain spaces, dots (except schema delimiter), comas, quotes and double quotes.
- schemas
- writable views
- user right handling
↧
New Post: When to use BuildMS binaries
Hi Stefan,
I hoped that the binaries from latest version of MinGW should fix the problem with the dll registration. That was the reason I didn't created the MS build with the latest release. It is not clear from your post what is the problem. Can you give me some error message? Anyway, I have created a new build which includes MS VS build again.
Pavel
↧
New Post: When to use BuildMS binaries
Pavel,
seems like I made a mistake in the first place or something went wrong which I can't reproduce.
When selecting create new Postgis Connection in GM the mask popping up was for the input of an Oracle connection string, but by now, everything seems to work fine.
Sorry for the confusion and thank you for your quick reaction.
Stefan
↧
↧
New Post: Using PostGIS connection in Geomedia Object
Hi, I'm experiencing a problem when using Connection object in Geomedia Object, without an Application instance. When I call OpenRecordset on GDatabase object I receive a not yet implemented exception. The same thing when I ask for the output recordset on the originating pipe. How can I overcome this problem?
Of course I don't have this problem with different kind of connection.
Thx
↧
New Post: Using PostGIS connection in Geomedia Object
Please provide some more info about your system and programming language/tool used. Noone has ever reported something like that, so it is not a general problem. For example the following VB code snippet works normally:
Option Explicit
Private Sub Command1_Click()
Dim objConn As New Connection
Dim objRS As GRecordset
Dim objDB As GDatabase
With objConn
.Type = "PostGIS.GDatabase"
.Location = "deb-psg"
.ConnectInfo = "gdouser/gdouser@ussampledata"
.Connect
End With
If objConn.Status = 1 Then
Set objDB = objConn.Database
Set objRS = objDB.OpenRecordset("states")
objRS.MoveLast
MsgBox objRS.RecordCount
objRS.Close
Set objRS = Nothing
Set objDB = Nothing
objConn.Disconnect
End If
Set objConn = Nothing
End Sub
Thanks, Pavel
↧
New Post: Using PostGIS connection in Geomedia Object
I have a .Net C# application embedding Geomedia Objects (MapView, LegendView),whithout an Application object running
↧
New Post: Using PostGIS connection in Geomedia Object
I tested the same code with C#, VS 2010, and it works OK. Can you provide a test application? Pavel
↧
↧
New Post: Using PostGIS connection in Geomedia Object
Are you running it from a Geomedia Command? I'm not developing a Geomedia custom command. I have a Windows Form application hosting Geomedia controls. I will post the solution as soon as I can
↧
New Post: Using PostGIS connection in Geomedia Object
I am also running a stand alone application. I'll wait for your code. Pavel
↧
New Post: GDO psgDBUtils :
Hi,
I integrated dump database postgres / postgis (4 new schemas imported ).
(FYI, the integrated data are accessible via QGIS)
To make them accessible via Geomedia, I created the metadata via the "PostGIS GDO Database Utilities".
The schema "GDO" has been created.
Geomedia connection via the base PostGIS is enabled.
problems:
Could someone here have a solution for these problems?
I integrated dump database postgres / postgis (4 new schemas imported ).
(FYI, the integrated data are accessible via QGIS)
To make them accessible via Geomedia, I created the metadata via the "PostGIS GDO Database Utilities".
The schema "GDO" has been created.
Geomedia connection via the base PostGIS is enabled.
problems:
- No table is visible via Geomedia
-
I can create layers using Geomedia, but they are stored in the schema "public" of Postgres / PostGIS.
Could someone here have a solution for these problems?
- How to properly catalog all schemas existing in PostGIS, to make them accessible via Geomedia?
- How to create layers in a specific schema, via Geomedia ?
Thanks for your help !
jmlebarh (from France...)
↧
New Post: GDO psgDBUtils :
You should also check and possibly assign the metadata for particular feature classes. Click "Edit Feature Class Metadata..." button on the Database Utilities main page.
Pavel
Pavel
↧
↧
Created Issue: GeoMedia PostGIS data server and Geomedia 13 [1487]
I installed new GEOMEDIA Pro - 13.00.0000 Build 00242 and tried to use GeoMedia PostGIS data server.
Strange thing was that at first time there was a dialog for configuration of Postgis connection.
After closing the Geomedia and starting again the dialog disappeared (see the picture in the attached file).
Despite of that, if there is existing Postgis connection in the workspace, layers of that connection are usable as legend entries.
Strange thing was that at first time there was a dialog for configuration of Postgis connection.
After closing the Geomedia and starting again the dialog disappeared (see the picture in the attached file).
Despite of that, if there is existing Postgis connection in the workspace, layers of that connection are usable as legend entries.
↧
Released: PostGIS GDO 1.2.0.3 (Mar 18, 2013)
There are two important changes in this PostGIS GDO release. The source code has been upgraded so that it gets compiled with the latest version of MinGW. So we don't include MS VC++ build at the moment. The second change is that the
most of the Database Utilities functionality has been moved into PsgDBUtils.dll which can be reused by 3rd party application to administer GDO metadata.
Fixed in this version
Fixed from previous versions
Features supported from older versions
Fixed in this version
- Added support for EPSG 26910
- Improved handling of NUMERIC and DECIMAL data types
Fixed from previous versions
- Added MS build again and support for compiling with MS VS 2010
- Fixed another problem with MULTICURVE geometries
- Fixed problem with deleting tables
- Fixed problem with Text and Image feature classes not working with PostGIS 2.0
- Feature classes in Database Utilities alphabetically sorted
- Fixed problem with MULTICURVE geometries
- Fixed problem with pick lists
- Fixed problem with renaming table columns
- Added support for scandinavian coordinate systems
- Fixed problem with point geometries
- Fixed problem with spatial filter
- Arbitrary database encoding should be supported now (although not tested)
- Added support for G/I Toolkit
- Added EPSG 2169
- Added edit field for specifying the port. The field can be left blank.
Features supported from older versions
- The table and field names are CASE SENSITIVE now. Moreover, it is possible to use non-ASCII characters (e.g. Cyrillic) in the table and fields names. The names still cannot contain spaces, dots (except schema delimiter), comas, quotes and double quotes.
- schemas
- writable views
- user right handling
↧
Created Release: PostGIS GDO 1.2.0.3 (Mar 18, 2013)
There are two important changes in this PostGIS GDO release. The source code has been upgraded so that it gets compiled with the latest version of MinGW. So we don't include MS VC++ build at the moment. The second change is that the most of the Database Utilities functionality has been moved into PsgDBUtils.dll which can be reused by 3rd party application to administer GDO metadata.
Fixed in this version
Fixed from previous versions
Features supported from older versions
Fixed in this version
- Added support for EPSG 26910
- Improved handling of NUMERIC and DECIMAL data types
Fixed from previous versions
- Added MS build again and support for compiling with MS VS 2010
- Fixed another problem with MULTICURVE geometries
- Fixed problem with deleting tables
- Fixed problem with Text and Image feature classes not working with PostGIS 2.0
- Feature classes in Database Utilities alphabetically sorted
- Fixed problem with MULTICURVE geometries
- Fixed problem with pick lists
- Fixed problem with renaming table columns
- Added support for scandinavian coordinate systems
- Fixed problem with point geometries
- Fixed problem with spatial filter
- Arbitrary database encoding should be supported now (although not tested)
- Added support for G/I Toolkit
- Added EPSG 2169
- Added edit field for specifying the port. The field can be left blank.
Features supported from older versions
- The table and field names are CASE SENSITIVE now. Moreover, it is possible to use non-ASCII characters (e.g. Cyrillic) in the table and fields names. The names still cannot contain spaces, dots (except schema delimiter), comas, quotes and double quotes.
- schemas
- writable views
- user right handling
↧
Source code checked in, #22492
↧
↧
Commented Issue: GeoMedia PostGIS data server and Geomedia 13 [1487]
I installed new GEOMEDIA Pro - 13.00.0000 Build 00242 and tried to use GeoMedia PostGIS data server.
Strange thing was that at first time there was a dialog for configuration of Postgis connection.
After closing the Geomedia and starting again the dialog disappeared (see the picture in the attached file).
Despite of that, if there is existing Postgis connection in the workspace, layers of that connection are usable as legend entries.
Comments: ** Comment from web user: pkrejcir **
Strange thing was that at first time there was a dialog for configuration of Postgis connection.
After closing the Geomedia and starting again the dialog disappeared (see the picture in the attached file).
Despite of that, if there is existing Postgis connection in the workspace, layers of that connection are usable as legend entries.
Comments: ** Comment from web user: pkrejcir **
This looks like the GMPsgCtl.ocx is not registered properly. Pavel
↧
Commented Issue: GeoMedia PostGIS data server and Geomedia 13 [1487]
I installed new GEOMEDIA Pro - 13.00.0000 Build 00242 and tried to use GeoMedia PostGIS data server.
Strange thing was that at first time there was a dialog for configuration of Postgis connection.
After closing the Geomedia and starting again the dialog disappeared (see the picture in the attached file).
Despite of that, if there is existing Postgis connection in the workspace, layers of that connection are usable as legend entries.
Comments: ** Comment from web user: pzaffirov **
Strange thing was that at first time there was a dialog for configuration of Postgis connection.
After closing the Geomedia and starting again the dialog disappeared (see the picture in the attached file).
Despite of that, if there is existing Postgis connection in the workspace, layers of that connection are usable as legend entries.
Comments: ** Comment from web user: pzaffirov **
It is very strange!
I run several times register.bat (as administrator) batch file to unregister and register again dll and ocx file and restarted PC after registration, and I have no success.
After unregistration "PostGIS" was not listed in the available "Connection types".
After registration there was PostGIS connection type, but dialog for connection parameters missed.
Strange thing is that now I have PostGIS connection type and dialog for connection properties is there and works fine?!?
↧
Created Issue: Add Polish coordinate systems [1498]
Hello, could you please add Polish coordinate systems:
EPSG:3120: Pulkovo 1942(58) / Poland zone I
EPSG:2172: Pulkovo 1942(58) / Poland zone II
EPSG:2173: Pulkovo 1942(58) / Poland zone III
EPSG:2174: Pulkovo 1942(58) / Poland zone IV
EPSG:2175: Pulkovo 1942(58) / Poland zone V
EPSG:2176: ETRS89 / Poland CS2000 zone 5
EPSG:2177: ETRS89 / Poland CS2000 zone 6
EPSG:2178: ETRS89 / Poland CS2000 zone 7
EPSG:2179: ETRS89 / Poland CS2000 zone 8
See csf files attached.
EPSG:3120: Pulkovo 1942(58) / Poland zone I
EPSG:2172: Pulkovo 1942(58) / Poland zone II
EPSG:2173: Pulkovo 1942(58) / Poland zone III
EPSG:2174: Pulkovo 1942(58) / Poland zone IV
EPSG:2175: Pulkovo 1942(58) / Poland zone V
EPSG:2176: ETRS89 / Poland CS2000 zone 5
EPSG:2177: ETRS89 / Poland CS2000 zone 6
EPSG:2178: ETRS89 / Poland CS2000 zone 7
EPSG:2179: ETRS89 / Poland CS2000 zone 8
See csf files attached.
↧