Unless OXCE changes the definitions from the way X-Com WORLD.DAT handled it, latitude should be -85 and longitude of 2307 to put it in the location defined by krautbernd. Ufopaedia article here has information on how locations are defined.
OpenXCOM changes things, since it uses actual degrees instead of whatever the original uses. The wiki
also states that the location definition for cities hasn't been found (yet).
-85, 2307 puts the city at 85°N and whatever 2307 rolls over to. That's in the Arctic.
There are two "problems" with how OpenXCOM handles coordinates:
- The ruleset lists longitude first, while debug mode lists latitude first
- Negative latitude values indicate °N, not °S
Listing longitude before latitude makes sense from a mathematical or programmers point of view (x before y), but geographic coordinates are standardized (
ISO 6709) as to list northing/southing first. This is complicated by the fact that projected systems might list easting/westing first (UTM for example). I have no idea though why OpenXCOM uses negative values to indicate north. That's just counterintuitive.
OpenXCOM accepts positive and negative numbers for longitude, so 50°W can be entered as either -50 or 310.
I know how locations are defined, but I don't know where Maracaibo is. There are several places with that name.
The issue is, nobody is giving me correct cooedinates... Including your "longitude of 2307". So I kind of stopped caring.
I've only been able to find one city named "Maracaibo" that's located in Venezuela (at least using Wikipedia). The correct coordinates for the region.rul are -71.63, -71.63, -10.65, -10.65 or 288.37, 288.37, -10.65 - which unfortunately puts the city inside Lake Maracaibo in-game though. I'd suggest using
288, 288, -10.65, -10.65 or
-72, -72, -10.65, -10.65 instead.