MapInfo Pro

Hello,
I've recently been doing some population change maps in MapInfo 2021 for the main Australian state capitals using census data, based on one done for Melbourne a few years ago.
Maps for Sydney, Brisbane, Adelaide and Perth were done by saving copies of the workspace and tables, and moving text and boxes to other parts of the country as needed (PDF's at https://johncleverdon.neocities.org/portfolio under the "ABS Censuses: Population change maps" item).
The first 3 cities were OK for moving the text and boxes, although the graphics for the scale bar and CC logo had to be rotated.
Doing that for Perth became a problem, as once the text and boxes were moved from Adelaide to Perth, it was difficult to select and move the text as needed for the map.
I upgraded to v2023 but still had the same problem, any idea why?
I've attached a zip file with the MapInfo tables for Adelaide and Perth text, see if anyone has the same issue once moving the text / boxes from the Adelaide location to that for Perth.
Regards, John Cleverdon

Coordinate of your TAB files are MGA Zone 55, but a bounded version. This means coordinates are only possible within those bounds and objects can not be moved outside. Change to an un-bounded version or use LatLong for your text/box tables.

Normally the advantage of bounded tables are higher accuracy, but you probably don't need that.

Hello,
I've recently been doing some population change maps in MapInfo 2021 for the main Australian state capitals using census data, based on one done for Melbourne a few years ago.
Maps for Sydney, Brisbane, Adelaide and Perth were done by saving copies of the workspace and tables, and moving text and boxes to other parts of the country as needed (PDF's at https://johncleverdon.neocities.org/portfolio under the "ABS Censuses: Population change maps" item).
The first 3 cities were OK for moving the text and boxes, although the graphics for the scale bar and CC logo had to be rotated.
Doing that for Perth became a problem, as once the text and boxes were moved from Adelaide to Perth, it was difficult to select and move the text as needed for the map.
I upgraded to v2023 but still had the same problem, any idea why?
I've attached a zip file with the MapInfo tables for Adelaide and Perth text, see if anyone has the same issue once moving the text / boxes from the Adelaide location to that for Perth.
Regards, John Cleverdon

Hello Uffe,
Thanks for the clearing that up.
Because the table for the census data that I was using was based on Lat/Long (being Australia-wide), see the bottom of the screen dump below, I had missed / overlooked the fact that the tables for the text and boxes etc was on MGA instead.

Regards, John

Coordinate of your TAB files are MGA Zone 55, but a bounded version. This means coordinates are only possible within those bounds and objects can not be moved outside. Change to an un-bounded version or use LatLong for your text/box tables.

Normally the advantage of bounded tables are higher accuracy, but you probably don't need that.

Hello,
I've recently been doing some population change maps in MapInfo 2021 for the main Australian state capitals using census data, based on one done for Melbourne a few years ago.
Maps for Sydney, Brisbane, Adelaide and Perth were done by saving copies of the workspace and tables, and moving text and boxes to other parts of the country as needed (PDF's at https://johncleverdon.neocities.org/portfolio under the "ABS Censuses: Population change maps" item).
The first 3 cities were OK for moving the text and boxes, although the graphics for the scale bar and CC logo had to be rotated.
Doing that for Perth became a problem, as once the text and boxes were moved from Adelaide to Perth, it was difficult to select and move the text as needed for the map.
I upgraded to v2023 but still had the same problem, any idea why?
I've attached a zip file with the MapInfo tables for Adelaide and Perth text, see if anyone has the same issue once moving the text / boxes from the Adelaide location to that for Perth.
Regards, John Cleverdon

Hey John

It looks to me as if you are using the map window to create what are layout elements (text boxes, scalebars, and some images)

Have you considered using the layout window to hold these elements and inside a "clean" map underneath these elements?

I have created a small example of how that could look below.

Hello Uffe,
Thanks for the clearing that up.
Because the table for the census data that I was using was based on Lat/Long (being Australia-wide), see the bottom of the screen dump below, I had missed / overlooked the fact that the tables for the text and boxes etc was on MGA instead.

Regards, John

Coordinate of your TAB files are MGA Zone 55, but a bounded version. This means coordinates are only possible within those bounds and objects can not be moved outside. Change to an un-bounded version or use LatLong for your text/box tables.

Normally the advantage of bounded tables are higher accuracy, but you probably don't need that.

Hello,
I've recently been doing some population change maps in MapInfo 2021 for the main Australian state capitals using census data, based on one done for Melbourne a few years ago.
Maps for Sydney, Brisbane, Adelaide and Perth were done by saving copies of the workspace and tables, and moving text and boxes to other parts of the country as needed (PDF's at https://johncleverdon.neocities.org/portfolio under the "ABS Censuses: Population change maps" item).
The first 3 cities were OK for moving the text and boxes, although the graphics for the scale bar and CC logo had to be rotated.
Doing that for Perth became a problem, as once the text and boxes were moved from Adelaide to Perth, it was difficult to select and move the text as needed for the map.
I upgraded to v2023 but still had the same problem, any idea why?
I've attached a zip file with the MapInfo tables for Adelaide and Perth text, see if anyone has the same issue once moving the text / boxes from the Adelaide location to that for Perth.
Regards, John Cleverdon