MapInfo Pro

Expand all | Collapse all

problems with bounded coordinate systems in 17.0 (and 17.0.4)

  • 1.  problems with bounded coordinate systems in 17.0 (and 17.0.4)

    Posted 13 days ago
      |   view attached

    Hi.
    I'm having problems selecting: Bounded UTM Zone 32 ETRS89\p25832

    When I create a table setting the projection to Bounded UTM Zone 32 ETRS89\p25832, somehow it keeps using the non-bounded projection..

    I've also noticed that in the Map Preferences setting dialogue, under table and session projections, I can choose:  Danish Bounded Coordinate Systems -> Bounded UTM Zone 32 ETRS89 [EPSG:25832] , but somehow it keeps returning to : ETRS TM Zone32, Northern Hemisphere (ETRS89)[EPSG:3044]

    Am I doing something wrong?
    How do I create a table using the Bounded UTM Zone 32 ETRS89\p25832?

    -I could of course define it myself using the CoordSys Bounds Manager tool, but it would be easier if I could just choose it from the projection list..

    I suspect I could have something to do with the MAPINFOW.proj file?
    Here's how the two projections look in the text editor

    "--- Danish Coordinate Systems ---"
    "UTM Zone 32 Euref89\p25832", 8, 115, 7, 9.0, 0, 0.9996, 500000, 0

    "--- Danish Bounded Coordinate Systems---"
    "Bounded UTM Zone 32 ETRS89\p25832", 2008, 115, 7, 9.0, 0, 0.9996, 500000, 0, 50000.0, 5750000.0, 1050000.0, 6750000.0

     Regards
    Casper Skaaning  Andersen

     



    ------------------------------
    Casper Skaaning Andersen
    UNIVERSITY OF AARHUS
    Aarhus C
    ------------------------------


  • 2.  RE: problems with bounded coordinate systems in 17.0 (and 17.0.4)

    Posted 13 days ago

    Hi Casper

    It's the order of the different coordinate systems in the MapInfow.prj that "get's in your way".

    I'm guessing that the table does get created using the bounded coordinate system you select. MapInfo will look for the parameters of the coordinate system and find the first match in the projection file.

    If not, that's a bigger problem.

    If you always want to use the bounded Danish coordinate systems, you can cut these coordinate systems from their current place in the MapInfow.prj file, and paste them at the top of the file. Save the file and restart MapInfo Pro.

    Now you will notice, that it will select the bounded coordinate system.

    In the Danish version of MapInfo Pro the two sets of Danish coordinate systems are by default at the top of the file. But the bounded coordinate systems are below the unbounded coordinate systems. This is not the case in the English version because... well not everybody is Danish.



    ------------------------------
    Peter Horsbøll Møller
    Pitney Bowes
    ------------------------------



  • 3.  RE: problems with bounded coordinate systems in 17.0 (and 17.0.4)

    Posted 13 days ago
    Hi Peter.
    The cut & paste solution worked
    However (in my end) the problem seems to occur in both in the English and the Danish Version

    -anyways
    Thanks a lot

    ------------------------------
    Casper Skaaning Andersen
    UNIVERSITY OF AARHUS
    Aarhus C
    ------------------------------



  • 4.  RE: problems with bounded coordinate systems in 17.0 (and 17.0.4)

    Posted 13 days ago

    Good to hear you got it working, Casper.

    And well, yes, .. I forgot that we had forgotten to get the Danish coordinate systems to the top in the Danish version of 17.0.

    Fingers crossed that will be corrected in the upcoming v2019 next year.



    ------------------------------
    Peter Horsbøll Møller
    Pitney Bowes
    ------------------------------



  • 5.  RE: problems with bounded coordinate systems in 17.0 (and 17.0.4)

    Posted 10 days ago
    Edited by Duri Bradshaw 10 days ago
    deleted, see other post


  • 6.  RE: problems with bounded coordinate systems in 17.0 (and 17.0.4)

    Posted 10 days ago
    Edited by Duri Bradshaw 10 days ago
    Hi Casper,

    I have the same problem when I use the Victorian bound version of Map Grid of Australia 1994 (MGA94)

    MapInfow.prj
    "MGA Zone 55 (GDA 94)\p28355", 8, 116, 7, 147, 0, 0.9996, 500000, 10000000
    "VIC MGA Zone 55 (GDA 94)", 2008, 116, 7, 147, 0, 0.9996, 500000, 10000000, -500000, 5000000, 1500000, 7000000

    When you check the coordinate system of a newly created file it will tell you it's is "MGA Zone 55 (GDA 94)" rather than "VIC MGA Zone 55 (GDA 94)" but you can see that the bounds have been set correctly, granted I was a little confused at first.

    Be careful if you place the bound version above the unbound version in your MapInfow.prj as MapInfo will then tell you that unbound data is using the bound coordinate system as shown here

    ------------------------------
    Duri Bradshaw
    Spatial IT Consultant
    Insight GIS
    ------------------------------