Re: [OSM-talk] XML database VS PostgreSQL for OSM

2011-10-26 Thread Robin Paulson
 Please don't comment on this if you don't know what an XML database is
 or how it functions. It is not a simple documentstore analogue to a
 filesystem.

ok, cheers.

-- 
robin

http://fu.ac.nz - Auckland's Free University

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] XML database VS PostgreSQL for OSM

2011-10-25 Thread Stefan de Konink
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Op 25-10-11 01:33, Robin Paulson schreef:
 On 19 October 2011 20:58, dre . gwen...@hotmail.fr wrote:
 Considering an OSM data fragment representing a town as Paris,
 London, etc, I wonder assets and drawbacks of using a XML file
 (myTown.osm) against tools as pgRouting or another PostgreSQL
 based database for routing, visualization, updates from main
 server?
 
 hi, you might get a better response on the dev mailing list.
 
 in brief, though: postgres will be a hell of a lot quicker serving 
 data than xml. xml is easy to read and process by hand, but it is
 slow and the files are big.

Please don't comment on this if you don't know what an XML database is
or how it functions. It is not a simple documentstore analogue to a
filesystem.

The hole benefit of XML databases is that they maintain document
structure and allow quick processing. The basic pain -for
openstreetmap- is they lack of a geospatial index, I don't know if
there are any XML databases currently on the market that do allow
spatial indices using GML extensions for example.

About 3 years ago I have loaded the planet into MonetDB4-XML which
basically functioned, given enough memory, which you would need for
'the planet' anyway. But XQuery is just not what the general public
likes to use on this database, although XAPI may indicate differently,
thats more XPath.


Stefan
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREKAAYFAk6m4UQACgkQYH1+F2Rqwn1mLACdH6Fo8QPlJrwlMwfGw38rnREg
ev0An1Sa14z2OPSylDBCl4ECsedOuIXB
=WVzP
-END PGP SIGNATURE-

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


[OSM-talk] XML database VS PostgreSQL for OSM

2011-10-24 Thread dre .

Hi,

Considering an OSM data fragment representing a town as Paris, London, etc, I 
wonder assets and drawbacks of using a XML file (myTown.osm) against tools as 
pgRouting or another PostgreSQL based database for routing, visualization, 
updates from main server?

Thanks

  ___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


[OSM-talk] XML database VS PostgreSQL for OSM

2011-10-24 Thread dre .

Hi,

Considering an OSM data fragment representing a town as Paris, London, etc, I 
wonder assets and drawbacks of using a XML file (myTown.osm) against tools as 
pgRouting or another PostgreSQL based database for routing, visualization, 
updates from main server?

Thanks

  ___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] XML database VS PostgreSQL for OSM

2011-10-24 Thread Robin Paulson
On 19 October 2011 20:58, dre . gwen...@hotmail.fr wrote:
 Considering an OSM data fragment representing a town as Paris, London, etc,
 I wonder assets and drawbacks of using a XML file (myTown.osm) against tools
 as pgRouting or another PostgreSQL based database for routing,
 visualization, updates from main server?

hi,
you might get a better response on the dev mailing list.

in brief, though: postgres will be a hell of a lot quicker serving
data than xml. xml is easy to read and process by hand, but it is slow
and the files are big.

-- 
robin

http://fu.ac.nz - Auckland's Free University

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk