AW: Re: [Qgis-developer] MapInfo and QGIS – An overview « Nathans MapInfo and .Net Blog

[Andreas Neumann]

yes,

it would be fine if the results of geometry processing results in
segmentized geometries, but the original arcs should be able to be stored
in Postgis, visualized and edited in QGIS and some basic operations should
be supported, even if the result is a segmentized geometry.

Andreas

On Wed, December 8, 2010 10:08 am, Ziegler Stefan wrote:
> Probably it would be feasible if we start with a postgis provider that
> is able to read/write arcs since it doesn't need ogr. I would not care
> about the spatial operators/functions that does not support arcs and
> segmentize them for the action. But I really would like to be able to
> know if there is an arc instead of just seeing a lot of vertexes.
>
> regards
> Stefan
>
>> -----Ursprüngliche Nachricht-----
>> Von: Andreas Neumann [mailto:a.neumann at carto.net]
>> Gesendet am: Mittwoch, 8. Dezember 2010 09:30
>> An: Milo van der Linden
>> Cc: qgis-developer at lists.osgeo.org
>> Betreff: Re: [Qgis-developer] MapInfo and QGIS
>> =?iso-8859-1?Q?=E2=80=93_An_overview_=C2=AB_Nathans_MapInfo_an
>> d_.Net_Blo
>> g?=
>>
>> yes - arcs would be nice to have in the Open Source GIS stack. I would
>> need them as well.
>>
>> However, it would be a lot of work to implement it in the whole stack:
>> geos, proj4, ogr, QGIS, Postgis (already supports arcs, but
>> not yet for
>> all operators/functions)
>>
>> I am still hoping it will happen some day ...
>>
>> In my opinion the support of arcs is one of the main
>> differences between
>> the more established, commercial GIS and QGIS. All of the
>> survey data in
>> Switzerland contains arcs. Currently, in OS GIS one has to segment the
>> data on import ...
>>
>> Andreas
>>
>> On Tue, December 7, 2010 5:55 pm, Milo van der Linden wrote:
>> > Yes, nice comparison. Thanks Nathan for giving us this!
>> >
>> > As a former MapInfo consultant, I can say that there is one
>> more thing
>> > qGIS lacks, well, not qGIS in particular but OGR: arcs. Besides that
>> > it is a myth that mapinfo uses the same sql across all tables. You
>> > simply have to convert every table to mapinfo's own file format in
>> > order to work with it.
>> >
>> > Performance is a minor issue in my opinion; if everything is a
>> > shapefile, qGIS is almost as fast as MapInfo. MapInfo is particulary
>> > malperforming with wms layers, wfs layers are almost impossible.
>> >
>> >
>> >
>> > 2010/12/7 Giovanni Manghi <giovanni.manghi at gmail.com>:
>> >>
>> http://woostuff.wordpress.com/2010/12/06/mapinfo-and-qgis-an-overview/
>> >>
>> >>
>> >> _______________________________________________
>> >> Qgis-developer mailing list
>> >> Qgis-developer at lists.osgeo.org
>> >> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> >>
>> > _______________________________________________
>> > Qgis-developer mailing list
>> > Qgis-developer at lists.osgeo.org
>> > http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> >
>>
>>
>> --
>> Andreas Neumann
>> http://www.carto.net/neumann/
>> http://www.svgopen.org/
>>
>> _______________________________________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>


-- 
Andreas Neumann
http://www.carto.net/neumann/
http://www.svgopen.org/