Hi all,
My company's looking at making our geodata available online using an
OpenStreetMaps map and some kind of geodatabase that the OSM interface
accesses to display polygons with various attributes. The user should be
able to click on the polygon and read the attributes. Now, I know the online
interface is not the topic for this forum, but the whole thing is pretty
challenging for me and the databank with GRASS is threatening enough.
Does anybody have any experience with this type of project? I know e.g. that
GRASS can work with DBF, SQLite, PostgreSQL, MySQL RDBMS, MySQL embedded
databases, and UnixODBC. As a complete newbie to any kind of advanced
database systems, I don't know the differences there. What would you all
suggest? We're looking at a large amount of data, several ten thousand
polygons with associated with about 10 attributes each. What would be the
best option there and how would one set it up?
Any help, suggestions or... Pretty much any communication regarding this
matter would make me a very happy guy 
Thanks a lot in advance!
Best,
Daniel
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Online-database-with-GRASS-tp5324371p5324371.html
Sent from the Grass - Users mailing list archive at Nabble.com.
Hi... Just in case the question got lost, since it's been a few days since I
asked, here's my old post. I haven't gotten any replies yet 
Hi all,
My company's looking at making our geodata available online using an
OpenStreetMaps map and some kind of geodatabase that the OSM interface
accesses to display polygons with various attributes. The user should be
able to click on the polygon and read the attributes. Now, I know the online
interface is not the topic for this forum, but the whole thing is pretty
challenging for me and the databank with GRASS is threatening enough.
Does anybody have any experience with this type of project? I know e.g. that
GRASS can work with DBF, SQLite, PostgreSQL, MySQL RDBMS, MySQL embedded
databases, and UnixODBC. As a complete newbie to any kind of advanced
database systems, I don't know the differences there. What would you all
suggest? We're looking at a large amount of data, several ten thousand
polygons with associated with about 10 attributes each. What would be the
best option there and how would one set it up?
Any help, suggestions or... Pretty much any communication regarding this
matter would make me a very happy guy Thanks a lot in advance!
Best,
Daniel
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Online-database-with-GRASS-tp5324371p5335006.html
Sent from the Grass - Users mailing list archive at Nabble.com.
On 07/25/2010 04:42 PM, LeeDaniel wrote:
Hi... Just in case the question got lost, since it's been a few days since I
asked, here's my old post. I haven't gotten any replies yet
ֵThe best combination, IMHO is PostGIS for the database backend, and Openlayers for displaying on the web. It's certainly possible to display GRASS vectors directly on the web, but, unless there's some specific reason to choose this option, I wouldn't. It puts an added complexity into the toolchain.
Finish your analyses in GRASS, then export the vectors to PostGIS, and call the PostGIS spatial layers from a webpage with the Openlayers javascript library.
I don't think anyone can give more specific guidance until there are more specific questions.
--
Micha
Hi all,
My company's looking at making our geodata available online using an
OpenStreetMaps map and some kind of geodatabase that the OSM interface
accesses to display polygons with various attributes. The user should be
able to click on the polygon and read the attributes. Now, I know the online
interface is not the topic for this forum, but the whole thing is pretty
challenging for me and the databank with GRASS is threatening enough.
Does anybody have any experience with this type of project? I know e.g. that
GRASS can work with DBF, SQLite, PostgreSQL, MySQL RDBMS, MySQL embedded
databases, and UnixODBC. As a complete newbie to any kind of advanced
database systems, I don't know the differences there. What would you all
suggest? We're looking at a large amount of data, several ten thousand
polygons with associated with about 10 attributes each. What would be the
best option there and how would one set it up?
Any help, suggestions or... Pretty much any communication regarding this
matter would make me a very happy guy Thanks a lot in advance!
Best,
Daniel
--
Micha Silver
Arava Development Co. +972-52-3665918
http://surfaces.co.il
Thanks! Believe it or not, that really does help me quite a bit. I also got
some direct emails from some other forum users with tips on books and stuff.
I think this'll at least help me to start finding out what I need to find
out
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Online-database-with-GRASS-tp5324371p5339365.html
Sent from the Grass - Users mailing list archive at Nabble.com.
On Mon, Jul 26, 2010 at 9:14 PM, LeeDaniel <Lee.Daniel.1986@gmail.com> wrote:
Thanks! Believe it or not, that really does help me quite a bit. I also got
some direct emails from some other forum users with tips on books and stuff.
I think this'll at least help me to start finding out what I need to find
out
Please consider to post a summary here or to the GRASS Wiki!
thanks
Markus
Sure thing... I'll wait till the thing runs and then post the summary.
-Daniel
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Online-database-with-GRASS-tp5324371p5339425.html
Sent from the Grass - Users mailing list archive at Nabble.com.