Have you considered using a different style of roads? Those dashed lines works on overland maps because they're only representative of the feature, but on close-up maps like these, they come out looking a bit out of place. Maybe a dirt brown fill with a small edge fade instead?

Most scale bars are 100, but there are exceptions like the style from that thread, where it is 200. Some styles also have multiple lengths, like the Schley overland style which as two at 100 and one at 200

The easiest way to check the scale of it in any style is simply to place it (Make sure the current symbol scale is 1) and measure it using the Info->Distance tool.

Digging a bit, I found that transparency only works for images if they are set to use alpha transparency in CC3+.

Use the :CC2EDIT: on the image, and switch it to alpha transparency, and it should work fine. (remember to thaw that frozen layer first, otherwise you can't edit it)

That problem occur if you just insert the house image into your drawing instead of the actual house symbol.

There are more information in the symbol than just the image, and CC3+ needs this information to generate a proper floorplan from the building.

The reason you have just a house image and not a house symbol in your map in the first place is most likely through the use of the :ICON_CATALOG: button. When you click this, you can either browse and pick a symbol catalog file (.fsc file), OR you can browse to a folder full of images, pick any image, and then have all the images from the folder showing up in the symbol catalog window. But if you do the latter (pick an image instead of symbol catalog when browsing) it means you will only get them as images, NOT symbols, because the extra information is in the symbol catalog file.

Instead, you should ALWAYS pick a symbol catalog file (.fsc), or just use the symbol catalog buttons in the toolbar as they will load the symbol catalogs properly.

Talking a bit with Joe here, it turns out that the problem is with the api from travellermap that we use with the importer.

If you look at the metadata for your sector, you see that travellermap simply do not give us a color for the sectors at all:

# Other
#
border 0107 0207 0307 0406 0506 0605 0606 0507 0407 0308 0208 0109 0108 0107

# Other
#
border 1821 1921 1920 1919 2019 2119 2219 2319 2418 2419 2420 2521 2522 2421 2322 2222 2123 2122 2021 1922 1821

# Other
#
border 1201 1302 1401 1501 1601 1701 1601 1502 1402 1303 1203 1202 1201

Normally, the color should be last on the the line for every border entry, and this is where the importer finds the color to use. And without travellermap providing us with a color, CC3+ defaults to white.

Here's an example of another sector which do provide colors correctly, notice the color names at the end of the border statements, after the coordinates:

# Plavian League
#
label 1814 Plavian League
border 1412 1512 1612 1712 1811 1911 2010 2011 2012 2113 2013 2014 2015 2016 2017 1918 1818 1718 1617 1616 1615 1614 1514 1413 1412 hotpink

# Renkard Union
#
label 3033 Renkard Union
border 3029 3129 3128 3227 3226 3227 3328 3329 3330 3331 3332 3333 3334 3335 3235 3135 3034 3033 3032 3031 3030 3029 red

# Swanfei Free Worlds
#
label 2721 Swanfei Free Worlds
border 2520 2619 2618 2718 2817 2918 2919 2920 2921 2821 2722 2621 2521 2520 white

I have no idea why travellermap doesn't give us the color for your sector, as there are clearly colors on the visible map.

Each sector is a polygon though, so it shouldn't be too time consuming to just change colors in CC3+ after the import.