Presagis

I have found an issue when converting airfields from the “built” format of FLAT into the Geocentric projection using Creator (TERRAIN/CONVERT DATABASE PROJECTION).

It would seem that my runway edges end up with cracks along them where they meet up with the taxiways coming onto the runways…I have concluded after much testing and re-projecting experiments that this is due to the fact that really long polygons (runways) that do not have enough/any vertices along their length have no way to “warp” during the process of reprojecting, thus as everything else warps, the runways do not (at least not properly)

Of course one answer is to before the conversion to Geo, add vertices along the length of the runway polygon, and tessellate or triangulate the polygon…

Now…the issue…Should not Creator check polygons that should need these extra vertices or may have a problem projecting either warn you, or even better yet, add vertices where needed during the process or reprojecting?

If you are asking whether Creator should fix your T-vertices before doing the conversion, I suppose it could.  Often, however, when we try to make Creator too smart (in situations like this), it ends up making someone else unhappy.

In this case, I would suggest using the T-Vertex Killer before you convert your database.  After all, your database has cracks to begin with.  They are merely magnified by the conversion process.