Results 1 to 8 of 8

Thread: Some weird questions about maps, areas, regions and locations

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default

    There's a problem with this sort of hierarchical approach. While it's fine in most scenarios, it doesn't adequately handle areas/regions that don't fit neatly into a single parent area. Biomes or bioregions, for instance, likely don't correspond in any way to political borders. This edge case might not matter to you, though.

    As someone who has developed MUDs for fifteen years, I'd recommend not automatically labeling an entity based on its position within the spatial hierarchy. I'd suggest this be something that is configured. Instead of having world->continent->region->forest->something, I'd abstract this into a simple container schema. Use naming to capture what the container is. It's entirely possible, for instance, to have a forest within a large city, but also to have a large city within a forest. You could then just use "area" to describe pretty much anything (because it's a nebulous spatial term). You could also include some explicit spatial information, if you want.

    Area: World
    Contains: Continent1, Continent2, Ocean 1, Biosphere 1, City 1
    Container: None


    Area: Continent1
    Contains: City 2, Lake 1
    Container: World


    etc etc. You can add spatially explicit information to this as well.

  2. #2
    Guild Journeyer Raptori's Avatar
    Join Date
    Feb 2014
    Location
    Helsinki
    Posts
    211

    Default

    Quote Originally Posted by codechino View Post
    There's a problem with this sort of hierarchical approach. While it's fine in most scenarios, it doesn't adequately handle areas/regions that don't fit neatly into a single parent area. Biomes or bioregions, for instance, likely don't correspond in any way to political borders. This edge case might not matter to you, though.

    As someone who has developed MUDs for fifteen years, I'd recommend not automatically labeling an entity based on its position within the spatial hierarchy. I'd suggest this be something that is configured. Instead of having world->continent->region->forest->something, I'd abstract this into a simple container schema. Use naming to capture what the container is. It's entirely possible, for instance, to have a forest within a large city, but also to have a large city within a forest. You could then just use "area" to describe pretty much anything (because it's a nebulous spatial term). You could also include some explicit spatial information, if you want.

    Area: World
    Contains: Continent1, Continent2, Ocean 1, Biosphere 1, City 1
    Container: None


    Area: Continent1
    Contains: City 2, Lake 1
    Container: World


    etc etc. You can add spatially explicit information to this as well.
    Codechino's approach would probably work best for most situations, as it reflects how we really mean those words. If the hierarchy is necessary for some behind the scenes stuff though, you could consider a grid like the one posted by Azelor, with multiple different levels to it, and have that separate from the other naming system. It all depends on what you need it for really.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •