Thanks for the prompt reply and for adding the missing detail to my
explanation.
Yes, a function or procedure with some logic(similar to that of MI
Pro) to maintain some sort of consistency is required. That's all,
not asking for much, hehe. I'm quite surprised that this is not an
OGC standard to have centroid on features, or even if it had to be a
"secondary centroid".
I applied my mind, and have some ideas of how to approach it, and it
will be quite complex I'm sure. I'm thinking of using the Centroid of
each polygon as a starting point for a line to be drawn out to the top
& and bottom and left to right, using the envelope of the polygon to
determine the extents. Then I'll calculate the length of the
intersection of each line where they intersect with the polygon. Then
use the mid point of the longest intersection segment, which is
nearest to the starting point as the centroid. This might end up a
bit more complicated once I get going, and if this works I can refine
it with further logic.
Thanks again
Rudi
On Oct 13, 10:27 am, "Lars I. Nielsen (GisPro)" <
L...@gispro.dk>
wrote:
> Hi Rudi,
> I assume you mean "MS SQL Server 2008 however, ..., returns Long/Lat coordinates of THE CENTER OF the bounds of the geometry".
> You probably won't find a simpe formula for this, as the geometry could be a multi-polygon of multiple tiny polynesian islands, so to speak.
> I assume you're looking for a solution in MS/SQL (i.e. as a stored procedure or a function), as the Centroid() function in MapInfo Pro should do the trick very nicely.
> Will a point anywhere on the surface do, or should it be as close to the bounds center as possible ? I think Pro has some logic to the latter effect.Best regards / Med venlig hilsen Lars I. Nielsen GIS & DB Integrator GisPro