Dear GRASS-Developers,
while thinking about using GRASS 5.7 as a 'PostGIS-data-editor' I am
facing the problem, that areas are only read as boundaries by UMN
Mapserver.
You know about that, I guess.
But are there some workarounds to display GRASS-modified PostGIS-data
correctly in UMN Mapserver?!
Another question is about the user management with roles, views etc. in
Postgres.
Is it possible to apply this user management of Postgres to the db-user
who is modifying the PostGIS database?
Any suggestion would be highly appreciated.
Thank you
Stephan Holl
--
Stephan Holl
GnuPG Key-ID: 11946A09
19:27:54 up 4:56, 1 user, load average: 0.00, 0.00, 0.00
On Friday 23 January 2004 19:40, Stephan Holl wrote:
Dear GRASS-Developers,
while thinking about using GRASS 5.7 as a 'PostGIS-data-editor' I am
facing the problem, that areas are only read as boundaries by UMN
Mapserver.
You know about that, I guess.
But are there some workarounds to display GRASS-modified PostGIS-data
correctly in UMN Mapserver?!
Another question is about the user management with roles, views etc. in
Postgres.
Is it possible to apply this user management of Postgres to the db-user
who is modifying the PostGIS database?
Any suggestion would be highly appreciated.
There are too many problems with PostGIS in GRASS, I thing, that
the best would be to remove or at leas disable PostGIS and maybe
shapefile and support only OGR sources as read only with pseudotopology.
Why do you need data stored in PostGIS? It is impossible to publish
the data anybody is working on. Editing may be done in GRASS native
and once finished, you can run v.out.ogr.
Radim
On Friday 23 January 2004 19:40, Stephan Holl wrote:
> Dear GRASS-Developers,
>
> while thinking about using GRASS 5.7 as a 'PostGIS-data-editor' I am
> facing the problem, that areas are only read as boundaries by UMN
> Mapserver.
> You know about that, I guess.
>
> But are there some workarounds to display GRASS-modified PostGIS-data
> correctly in UMN Mapserver?!
>
> Another question is about the user management with roles, views etc. in
> Postgres.
> Is it possible to apply this user management of Postgres to the db-user
> who is modifying the PostGIS database?
There are too many problems with PostGIS in GRASS, I thing, that
the best would be to remove or at leas disable PostGIS and maybe
shapefile and support only OGR sources as read only with pseudotopology.
OK, thanks for your statement.
Why do you need data stored in PostGIS? It is impossible to publish
the data anybody is working on. Editing may be done in GRASS native
and once finished, you can run v.out.ogr.
V.digit should be used to edit a postgis-database in order complete existing
data.
AFAIK there is permanent work on the data, so the postgis-data should be
edited by GRASS.
It should be stored in PostGIS, because the data is served through
mapserver, and the database-server is a PostGIS-Server.
So you think, there is no "easy" sollution to make GRASS-Postgis
UMN-mapserver compatible?!
Perhaps it would be possible to store my data as shapefiles, which can be
edited by v.digit.
I will think about that.
Anyway, thanks for your help.
Cheers
Stephan Holl
--
+++ GMX - die erste Adresse für Mail, Message, More +++
Bis 31.1.: TopMail + Digicam für nur 29 EUR http://www.gmx.net/topmail
On Tuesday 27 January 2004 17:17, Stephan Holl wrote:
> Why do you need data stored in PostGIS? It is impossible to publish
> the data anybody is working on. Editing may be done in GRASS native
> and once finished, you can run v.out.ogr.
V.digit should be used to edit a postgis-database in order complete
existing data.
AFAIK there is permanent work on the data, so the postgis-data should be
edited by GRASS.
It should be stored in PostGIS, because the data is served through
mapserver, and the database-server is a PostGIS-Server.
Currently it is not possible to edit GRASS vectors with geometry stored in PostGIS.
You cannot use data which are under construction in mapserver, IMHO.
What kind of data, how often do you need to update the version in mapserver?
Data are edited by one or more users at the same time?
So you think, there is no "easy" sollution to make GRASS-Postgis
UMN-mapserver compatible?!
Yes, no easy solution.
Perhaps it would be possible to store my data as shapefiles, which can be
edited by v.digit.
I will think about that.
No, shapefiles cannot be edited, the same problem - SFS as PosGIS.
Why native format and v.out.ogr is a problem?
Radim