When a WFS query is performed (for example a GetCapabilities request) the reply from the Geo Web Publisher Server returns the bounding box coordinates using the incorrect decimal separator, the decimal separator is a comma “,” instead of a dot “.”. This causes the WFS client to read the incorrect coordinates. This issue is related to language regional settings and seems specfic to Windows Server 2003 server.
The issue is related to regional settings. Noticeable was the fact that modifying the language regional settings from the control panel wasn’t sufficient to resolve the issue because not all decimal separators are changed accordingly (it doesn’t change all the decimal separator related values from “,” to “.” in the registry.). The WFS GetCapabilities or GetFeature continued to return the incorrect comma "," instead of the dot "." as the decimal separator causing the WFS client to read the wrong coordinates.
We can workaround the issue configuring the sDecimal entry in the Windows Registry.
Note: In order to perform this workaround and as a safety precaution the registry should be backed up and depending on the system administration policies of your servers. There is the chance that a reboot to the server may push changes to the registry / regional settings back to a predefined configuration / state.
1. Go to Start > Run > Regedit2. In the Registry Editor go to Edit > Find3. In the find dialog type sDecimal, click find next4. Verify if the value of this entry is a ‘.’ Or a ‘,’, change if necessary5. Press F3 to move to the next entry and perform step 4 again until all the entries are changed to ".". You should have 6 entries that are related with sDecimal.6. reset IIS (not sure if this is needed but I did it)7. test the GetCapabilities and GetFeature from IE to verify that you get the “.”as the decimal separator. Now the coordinates decimal separator should be a ".".