>* For my import I will update the pointers of edges my own, could you*>*
>Sandro point me to*>* specifications of next_*_edge.*
I guess shoulkd better spend time to optimize the actual ISO function
rather than think to do own low level function.
The controls to do a right ISO topology are man
On Fri, Sep 28, 2012 at 05:00:59PM +0200, Mario Jurcevic wrote:
> It will help if Topology validation could be defined by rules, so
> that during import
> of already topological data the user can disable it or enable it as needed.
That you can do it yourself.
Make up a schema, write your rules, im
It will help if Topology validation could be defined by rules, so that
during import
of already topological data the user can disable it or enable it as needed.
For my import I will update the pointers of edges my own, could you
Sandro point me to
specifications of next_*_edge.
Thanks
--
On Fri, Sep 28, 2012 at 02:50:03PM +0200, Mario Jurcevic wrote:
>
> On 09/27/2012 10:06 AM, Sandro Santilli wrote:
> >You can always skip all tests and insert the edges straight away, if
> >you know exactly what's expected as the structure. It will be faster.
> >You can then check with ST_Validate
On 09/27/2012 10:06 AM, Sandro Santilli wrote:
You can always skip all tests and insert the edges straight away, if
you know exactly what's expected as the structure. It will be faster.
You can then check with ST_ValidateTopology what's missing
(theoretically). That's what the TIGER loader does,
Sandro Santilli a écrit :
You mean curves ? No, not currently. There's no topological operation
working for curves so it would not work to do that: can't tell if two
edges cross each other until ST_Cross(curve,curve) is implemented.
With center and radius of curvature you could transform a curv
On Thu, Sep 27, 2012 at 09:11:28AM +0200, Mario Jurcevic wrote:
> Hi,
> the cadastre data ( Suisse ) are full of this overlaps, It happens
> when they introduce arc curves ( specially with streets ),
> i suppose due to inaccuracy of the computation of the arc points or
> for historically reason (
Hi,
the cadastre data ( Suisse ) are full of this overlaps, It happens when
they introduce arc curves ( specially with streets ),
i suppose due to inaccuracy of the computation of the arc points or for
historically reason ( digitizing errors ) or simply
because is cheaper to measure.
Attached
Hi,
"cadastre" data means that you're french ?
I do the same, importing french survey data in postgis 2.0 with topology.
I think that you're not in the right way. Have a look at
topogeo_addpolygon function with tolerance=0.
It's a better way to fix french survey data topology troubles.
Mar
On Wed, Sep 26, 2012 at 04:04:26PM +0200, Mario Jurcevic wrote:
> I am testing postgis topology with cadastre data, overlapping of
> edges with given tolerance is allowed.
Why so ?
> How to handle this kind of data: insert,modify,etc?
> Is possible to temporary disable the validation and or imp
Hello,
I am testing postgis topology with cadastre data, overlapping of edges
with given tolerance is allowed.
How to handle this kind of data: insert,modify,etc?
Is possible to temporary disable the validation and or implement a
custom validation?
Thanks in advance
Mario Jurcevic
___
11 matches
Mail list logo
