The size of the map in CC won't affect the size of your export.

Hit the Options button once you have selected your bitmap export type, and use any of the controls in the dialog that opens to increase the size, resolution and other output options.

You can use any parameters you like, as long as the "Work size" (bottom right of the dialog) doesn't go much further than 10,000 x 10,000.

These are good ideas, and they are definitely the kinds of things I will be considering for the 'Birdseye Regional' style, later on this year (hopefully).

However...

With this continental/world scale style the cities and towns are so tiny as to be nothing more than dots. That's because Arragosa is almost 2,800 miles from tip to tip, and as long as the entire United States is wide (2,800 miles).

Mike Schley's Structure symbols are the largest we have, but even the largest Mike Schley city symbol looks like a smudge on this map. I put one in the middle of the desert below.

Your ideas are good, but I mean to save them for the regional version of this style.

I'm hoping that Birdseye Continental will become an option for converted FT world maps - a style that will be colourful and textured by terrain type, yet simple enough to be clear if used in a world map.

EDIT: And with that last thought in mind, I might need to do something about the lack of contrast between sea and land...

Using Count All in the Info menu, you can see there are over 100,000 entities in this drawing. That is because most of the buildings are House entities laid down in Streets. That's fine, but you can expect things to be a little slow.

If you hide the buildings there are only just over 8,000 entities - less than 1/10 of the total. The map also zooms and pans much faster.

So putting different districts on different layers as described in detail by Quenten above, you should find it a lot more maneagable.

I didn't have any trouble with CC crashing. Did you mean crashing to desktop, or just giving you a green screen within the map window? The green screen shows when CC uses all the available memory to calculate the new display, rather than trying to show you all the stages between then and now, and is quite normal on maps with this may entities.

The two level mapping is probably the best idea.

You can (if you don't find it too awkward constantly hiding and showing different layers) do largish cities in one map by putting each district on it's own layer and only having the layers you are working on visible.

I think (though I might be wrong) that when these two were named it might have been before 'layers' were commonly accepted as the industry standard as the things you draw on in bitmap apps. But I also get confused at times by the now non-standard names for things that we all used in the early days of computer graphics. I use bitmap apps more frequently than CC these days because I generate CC assets using Affinity, GIMP, Krita... etc, so it was several years before I stopped accidentally calling sheets layers, and layers sheets, back in the days when I was helping new mappers on a range of different mapping apps over at Cartographer's Guild.

However, that's a great explanation from Joseph Slayton about how it all works in CC.

These are the layers most commonly kept frozen so the entities on them don't get moved or deleted by mistake:

• MAP BORDER - should only have a rectangle or 4 defining lines (usually in bright green) that tell CC where the edge of the map is.
• SCREEN - Holds the white collar around the outside of the map to cover up bits of symbols and fills that don't lie within the map border.
• BACKGROUND - not always frozen, but I prefer it that way so I don't keep picking the edges or corners when mapping.

Layers that you shouldn't manually mess with:

• MERGE - is used by CC, and causes some really weird stuff to happen if it's hidden, or things end up on it by mistake.
• SYMBOL DEFINITION - I wouldn't know how to technically describe it, but this layer has something to do with logging or controlling what symbols are in the map.

Example maps usually have all the layers frozen so they can't be accidentally altered, but if you want to make a copy and unfreeze the layers to create your own version for a game, that's easy enough to do.