View Issue Details

IDProjectCategoryView StatusLast Update
0000675Main CAcert Websiteaccount administrationpublic2013-01-15 08:16
Reporterasim Assigned Toteus  
Status closedResolutionfixed 
Fixed in Version2009 Q1 
Summary0000675: Support request to add the location Hoogezand-Sappemeer to the database
DescriptionCould you please add the following to the location database?
Hoogezand-Sappemeer, Groningen, Netherlands
Latitude = 53.1567, Longitude = 6.7572
TagsNo tags attached.
Reviewed by
Test Instructions



2009-02-16 16:00

developer   ~0001273

Hoogezand is separated from Sappermeer. Should be two villages.


2009-02-17 10:30

reporter   ~0001275

Dear Teus,

Thank you for you processing my issue about the location. I don't want to be a nag, but:
- it is added with a typo in the location database. It should be "Hoogezand-Sappemeer" without the "r" behind "Sappe".
- Furthermore regarding your comment that it are two villages. You are right, it used to be two villages but in 1949 Sappemeer and Hoogezand were joined to become Hoogezand-Sappemeer. However a lot of typical Sappemeer people disagree like typical Hoogezand people disagree about the joining and they keep naming the villages seperately. But officially it is Hoogezand-Sappemeer, see also:

with kind regards,



2009-02-17 11:56

developer   ~0001276

typo in Sappemeer solved.

Issue History

Date Modified Username Field Change
2009-02-15 23:26 asim New Issue
2009-02-16 15:59 teus Status new => needs work
2009-02-16 15:59 teus Assigned To => teus
2009-02-16 16:00 teus Note Added: 0001273
2009-02-16 16:00 teus Status needs work => closed
2009-02-16 16:00 teus Resolution open => fixed
2009-02-17 10:30 asim Note Added: 0001275
2009-02-17 10:30 asim Status closed => needs feedback
2009-02-17 10:30 asim Resolution fixed => reopened
2009-02-17 11:56 teus Note Added: 0001276
2009-02-17 11:56 teus Status needs feedback => solved?
2009-04-09 20:55 Sourcerer Status solved? => closed
2009-04-09 20:55 Sourcerer Resolution reopened => fixed
2013-01-15 08:16 Werner Dworak Fixed in Version => 2009 Q1