erroneous coordinates from GM_AreaFeature_t.mPointList

Yann DUPUYYann DUPUY Global Mapper UserPosts: 34Trusted User
edited September 2013 in SDK
Hi Mike,

I've been experiencing strange visual artefacts in my application based on GlobalMapper 13.1, as shown above.
BugAGTLight_GlobalMapper.jpg

This happens quite often, but not systematically.

My treatment is as follow:
import planimetry layer into globalmapper
loop through features and make some corrections (counter-clockwise checking, multiple vertices with same coordinates...)
adjust geometry if any problem was solved

It seems that the faulty part is the access to existing geometry.
Debugging my code, I figured out that for some unknow reason, the vertices coordinates were not all in the current projection. For instance, out of 13 vertices, the second one was in the original projection (Lambert 93 in my example) while all the others were in the current projection (Lambert II Wide for me).
Then of course, giving bad coordinates back to GlobalMapper lead to the strips among my features.


Would you have any idea on what is going on there ?

Thanks,
Yann

Comments

  • global_mapperglobal_mapper Administrator Posts: 17,238
    edited September 2013
    Yann,

    That is very strange, I don't see anything in the current code that could cause that to happen, but perhaps there was back in the version you have. I can't recall any kind of issue like this though. Do the coordinates come out of the GM_GetAreaFeature call like that? Does it happen every time for particular features?

    Also if you call GM_GetAreaFeatureEx instead and pass in GM_GetFeature_UseLayerProj do they all come out in the native layer projection?

    Thanks,

    Mike
    Global Mapper Guru
    geohelp@bluemarblegeo.com
    Blue Marble Geographics for Coordinate Conversion, Image Reprojection and Vector Translation
  • Yann DUPUYYann DUPUY Global Mapper User Posts: 34Trusted User
    edited September 2013
    Hi Mike,
    Do the coordinates come out of the GM_GetAreaFeature call like that? Does it happen every time for particular features?

    Yes, the coordinates come out like that, and it does not seem to be with a particular feature. Though it seems to happen more often if I load one layer at a time, instead of all the layers at once. Sometimes, during my treatment, I have much more artefacts on the 2D cartographic view, but they disappear as soon as it is over.
    Also if you call GM_GetAreaFeatureEx instead and pass in GM_GetFeature_UseLayerProj do they all come out in the native layer projection?

    This seem to have solved my problem (or at least, significantly reduce the number of arbitrary erroneous cases!). I have to try this on several computers as I noticed that 64 bits Windows Seven systems were more sensitive to these errors than mine (32 bits Windows XP).
    I keep having the artefacts while applying my treatment but this is not a big deal as it comes correct at the end. If you want I can send you a short screen capture showing the strang e behaviour ?

    Thanks,
    Yann
  • global_mapperglobal_mapper Administrator Posts: 17,238
    edited September 2013
    Yann,

    You might also see about upgrading your SDK license to the latest v14 SDK as a ton of significant changes have been made (none to the API thought, so it's just a re-compile). No one else has reported an issue like this so I wonder if it's something that was just briefly in there. If you are already on the v13 SDK your SDK contract may include upgrades already. Contact gmorders@bluemarblegeo.com to see if you can move up to v14.

    Thanks,

    Mike
    Global Mapper Guru
    geohelp@bluemarblegeo.com
    Blue Marble Geographics for Coordinate Conversion, Image Reprojection and Vector Translation
  • Yann DUPUYYann DUPUY Global Mapper User Posts: 34Trusted User
    edited September 2013
    Yann,

    You might also see about upgrading your SDK license to the latest v14 SDK as a ton of significant changes have been made (none to the API thought, so it's just a re-compile). No one else has reported an issue like this so I wonder if it's something that was just briefly in there. If you are already on the v13 SDK your SDK contract may include upgrades already.

    Hi Mike,
    We've just renewed our SDK license, and bought additionnal runtime licenses. I have a question about that : are the runtime licenses sticked to a SDK version or any of them. I mean we bought v13 runtimes. If there happens to be a bug in this version, which is corrected in v14, shall we distribute the new DLL to our existing clients without extra-fee ? Or shall we buy V14 runtimes to fit the DLL version ?

    Thanks,
    Yann
  • global_mapperglobal_mapper Administrator Posts: 17,238
    edited September 2013
    Yann,

    With the newer SDKs you don't buy individual run-time licenses, you get a text license string that you normally pass in via the GM_SetLicenseKey function call. While that is tied to a major version (i.e. 14), when you upgrade your license to v14 you should get a new one for v14 so you just update your GM_SetLicenseKey call with the new license text and it will be built in to your application.

    Thanks,

    Mike
    Global Mapper Guru
    geohelp@bluemarblegeo.com
    Blue Marble Geographics for Coordinate Conversion, Image Reprojection and Vector Translation
Sign In or Register to comment.