Quantcast
Channel: GeoMedia PostGIS data server
Viewing all 238 articles
Browse latest View live
↧

Commented Issue: Add Polish coordinate systems [1498]

March 28, 2013, 1:29 am
$
0
0
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.
Comments: ** Comment from web user: pkrejcir **

Thank you for the csf files. I'll include them in the next release. Pavel

↧
Search

Source code checked in, #22744

March 28, 2013, 9:56 am
↧
↧

Released: PostGIS GDO 1.2.0.4 (Mar 28, 2013)

March 28, 2013, 10:01 am
$
0
0
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
  • Added support for Polish coordinate systems

Fixed from previous versions
  • Added support for EPSG 26910
  • Improved handling of NUMERIC and DECIMAL data types
  • 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.4 (Mar 28, 2013)

March 28, 2013, 10:01 am
$
0
0
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
  • Added support for Polish coordinate systems

Fixed from previous versions
  • Added support for EPSG 26910
  • Improved handling of NUMERIC and DECIMAL data types
  • 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
↧

New Post: GeoMedia Professional 2013 Vs. PostGIS data server

April 29, 2013, 7:43 am
$
0
0
Hi. I'm tryingo to connect to a PostGIS DB using GeoMedia Professional 2013, but after setting up the connection the tables aren't loaded.

The following error is displayed:

The GDO object PostGIS.GDatabase is not registered correctly. Please reinstall the application to assure proper registration.

I've already reinstalled the data server and re-registered it. The data server files were copied at C:\Program Files (x86)\Common Files\Intergraph\GeoMedia\PostGISGDObin

GeoMedia, PostGIS data server, PostgreSQL and PostGIS are installed on their latest stable versions. The OS is Windows 7 Ultimate x64.

Note: I can connect to the same DB using this version of PostGIS data server over GeoMedia Professional 6.1 (both installed on another computer)

Isn't PostGIS data server compatible with GeoMedia 2013?

Thanks for your attention.

EDIT: I also tried to use the binaries from 'BuildMS' folder and it was not successful.
↧
↧

Closed Feature: Adding ESPG:31276 [889]

May 16, 2013, 1:49 am
$
0
0
Hello, could you please add EPSG:31276. See csf file attached. Please, it's urgent!
↧

Closed Feature: Adding EPSG:4317 [842]

May 16, 2013, 1:49 am
$
0
0
Hello, could you please add EPSG:4317. See csf file attached. Thanks.
↧

Closed Issue: Adding EPSG:2180 [808]

May 16, 2013, 1:49 am
$
0
0
Thanks for a great tool! Could you please attach EPSG2180 support in the next build. See attached epsg2180.csf file.
↧
Search

Closed Feature: Adding EPSG:2100 [750]

May 16, 2013, 1:49 am
$
0
0
Hi,
could you please add the attached EPSG2100.csf?
 
Thank you very much,
↧
↧

Closed Issue: Unable to display a feature class [689]

May 16, 2013, 1:49 am
$
0
0
Hi,
There seems to be a problem with GeoMedia displaying a feature class after removing a column. The steps taken are listed below.
1. Output Feature Class (linear geometries) from KML connection to postgres database. The new postgres feature class was displayed in the map window and I was able to edit and delete geometries without any problems.
2. After I deleted a field from the new postgres feature class (a text field that I don't need eg FontColor column), I am not able to display the table in map window any more. When I try to do this I get a Yes/No dialog box that says:
"Error creating legend entry for -----------(feature class name)
Source: GeoMedia
Description: Invalid geometry field name lineargeometry for the given recordset
Continue operation?"
Clicking the Yes and No buttons doesn't seem to do anything. I did not remove or edit the geometry field, only one of the text attribute fields.
 
This problem happens whichever way I delete the field, either through GeoMedia (Warehouse -> Feature Class Definition) or Postgres database itself (pgAdmin III user interface).
I tried re-creating feature class metadata for this table using PsgDBUtils.exe (check box next to the feature class) but that crashes the program and I can't do it.
I also tried using the debug version of PsgDBUtils.exe but it also crashes giving the following output:
 
DB Encoding:
Numeric: 6
Name: UTF8
Prepare statement in 'GetMetaTableNames' failed
PQ Error:
ERROR: relation "galiastable" does not exist
LINE 1: select TableName from galiastable where TableType = $1
DbuExecuteCommand
DEALLOCATE stmtgeom
DbuExecuteCommand
DEALLOCATE stmtftr
DbuExecuteCommand
DEALLOCATE stmttbls
 
Checking the database with pgAdmin III, I can see that the "galiastable" is there. All database creation and GeoMedia connections have been done as the postgres super user.
 
We need this sorted out pretty quickly as the project is under way already.
Looking forward to your reply.
 
P.S. My version numbers are:
PostgresSQL 9.0.3-1.6.1
PostGIS 1.5.2-3.2
pgAdmin III 1.12.1
PostGisGDO 1.0.0.11
GeoMedia 06.01.06.19
↧

Closed Issue: attribute query problem with cyrillic text [675]

May 16, 2013, 1:49 am
$
0
0
Hi, we are trying to perform an attribute query in Geomedia Professional.
The server is PostgreSQL 9.1 with PostGis 1.5.3, and database is created with UTF8 encoding. Database collation and character type are ‘Bulgarian_Bulgaria.1251’.
There is a “Table1” table with the following columns:
id serial NOT NULL,
name character varying(50),
geometry geometry
We added without any problems three rows using Geomedia Professional and each of rows contains cyrillic letters in the “name” column.
 
When we tried to perform attribute query against the table and the “where” clause contains cyrillic letters (for example: name = ‘Бургас’), the following errors occurred
“Error encountered creation of attribute query.
GeoMediaCommand Object doesn't support this action”.
 
There is no problem, when the “where” clause contains only latin characters or numbers.
 
There is database backup in the attachment.
Database name is ‘gdotestcase’, owner is ‘gdouser’.
↧

Closed Feature: Adding UTM35N coordinate system [673]

May 16, 2013, 1:49 am
$
0
0
Could you add UTM 35N (EPSG32635) coordinate system to the next version. See attached csf files. Thank's in advance
↧

Closed Feature: Add french coordinate system [657]

May 16, 2013, 1:49 am
$
0
0
Hi, Could you please add these french coordinate system to the next version. See attached csf files. Thank's
↧
↧

Closed Feature: Add coordinate system [641]

May 16, 2013, 1:49 am
$
0
0
Could you add this coordinate system to the next version EPSG29192. See attached csf file. Thanks.
↧

Closed Issue: replace coordinate system definition EPSG32633 [601]

May 16, 2013, 1:49 am
$
0
0
Could you to correct EPSG32633 definition, replacing EUREFS89 as Geodetic Datum with WGS84 as you was done
in EPSG32632 and in EPSG32634 definition ?
 
The three definitions of coordinate system should to be homogeneous.
 
see attacched csf file whith geodetic datum wgs84
 
thanks Massimiliano
↧
Search

Closed Feature: Coordinate system to add [505]

May 16, 2013, 1:49 am
$
0
0
Could you add this coordinate system to the next version.
--see attached csf file
Thanks
Daði Björnsson
↧

Closed Feature: EPSG2056.csf; EPSG21781.csf [495]

May 16, 2013, 1:49 am
$
0
0
Hi Pavel. I attached the two EPSG files for Switzerland. Thank you! Raphael
↧
↧

Closed Issue: EPSG31466.csf, EPSG25832.csf [476]

May 16, 2013, 1:49 am
$
0
0
Hello Pavel, I submit the .csf-Files we need. Thanks a lot, Marcus
↧

Closed Issue: Installation Win2008 Server (Missing Fields in Warehouse Connection) [469]

May 16, 2013, 1:49 am
$
0
0
Hi, me again having some trouble. ;)
Now I want to install PostGIS Dataserver in an WebMap Win 2008 Server environment. GM is patched to 06.01.10.14 (English).
The Installation runs well, with Admin-Rights via the console. I tried GM with Admin rights as well.
If I now want to add a PostGIS connection the Password Field is missing. I as well can’t open a GWS with valid connection from a different machine (WinXP).
 
Is there any other way to install? or what’s going wrong here?
 
Thanks,
Twain
↧

Closed Issue: Creating a Table via Feature Class Definition Causes Crash [385]

May 16, 2013, 1:49 am
$
0
0
GMP 6.1.10 and Posgres Plus 8.4. Using Feature Class Definition to create a new Point feature class causes GMP to crash to the desktop. The table is created with the exception of the geometry field. When an attempt is made to edit the table via FCD and add the geometry, GMP crashes to the desktop again.\
 
Workflow
1) Make a connection to a Posgres/PostGIS db.
2) Open Feature Class Definition.
3) Add a PID autonumber primary key, and select point type for the geometry.
4) Select OK and crash to the desktop.
↧
Viewing all 238 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>