Milki-Way : A web enabled SCM project using GIS
Monday, December 11, 2006
Friday, November 03, 2006
While Creating database
Please remeber that while designing your database in postgresql using pgAdmin give UTF8 encoding,, it is easy to test your queries in pgAdmin client. Otherwise you have to give always table name in double quotesfor eg. select * from "table"
Error in Database query
There was a problem while using postgresql as backend, I can not execute the queries.Later I understood the problem that I gave my table name as user and it is already a built in table in postgresql. So my friends never give table name those already there in database
Blog updating error
Hai friends, few days before we are not able to update our blog, becuase some error occured while updating. We recovered the problem by rollbacking our blog. We already stored a backup of our previous posts..Tuesday, October 17, 2006
System Requirements Specification for Milki-Way
System Requirements Specification for Milki-Way UploadedClick the Link below to Download
[PDF]
Monday, October 16, 2006
Last Week
Last Week | |
---|---|
PostgreSQL Installed | 07-10-2006 |
How to use PostGIS for Spatial Queries | 09-10-2006 |
Discussion About GeoServer | 11-10-2006 |
GeoServer Configured | 12-10-2006 |
Tried GeoServer Demos | 13-10-2006 |
Discussion on SRS | 17-10-2006 |
SRS version 1.0 posted | 18-10-2006 |
Wednesday, October 11, 2006
Tuesday, October 10, 2006
use of geoserver or mapserver
We have been investigating the viability of using geoserver
in this project.
Mapserver is another alternative.
GeoServer is a server. It is open source and it allows users to view and edit geographic data. GeoServer is written in 100% pure JavaTM and is deployed as a J2EE (Java2 Enterprise Edition) web application. GeoServer is compatible with standard J2EE servers, such as Apache Tomcat and Resin.
GeoServer supports several standard industry databases out of the box, including Oracle Spatial, ArcSDE, PostGIS and ESRI Shape Files. GeoServer supports OpenGIS GML version 2.1.