I'm currently browsing and hacking about, trying to wind up some Danish zip/postal code to long/lat coordinate mappings, which will be followed by a conversion to SQL (the script to do this has already been made).

A few things though:

  1. For now, I've got my long/lat data off http://geonames.org/export/ which says they release it under the Creative Commons Attribution license. Is there a way to specify this attribution, or should I try and contact them and ask about it? (This source could be used for lots of other zipcode/area to long/lat mappings as well.)
  2. I have decided to use the new "regions" for the state/province. I just don't know how to abbreviate them. Do they have to be abbreviated? Does it have to be an official abbreviation? (There aren't any official abbreviations for any of the regions that I know of.) I was thinking of just calling them "Hovedstaden", "Midtjylland", "Nordjylland", "Sjælland", and "Syddanmark". (The legal/official names would have "Region " prepended.)
CommentFileSizeAuthor
#8 zipcodes.dk_.mysql_.txt107.04 KBvtcore
#4 zipcodes.dk_.zip120.68 KBmarcushenningsen
#3 zipcodes.dk_.txt111.17 KBmarcushenningsen

Comments

yesct’s picture

yesct commented
Status: Active » Postponed (maintainer needs more info)

might be related to
#73714: Support for the Netherlands (NL) location.nl.inc location.xx.inc

I think this module needs someone to look into the data updates that need to be made, and propose some general guidelines and findings about the options available.

This collection of issues might help:
#175193: Zip code database out of date

Does anyone know the answers to the questions from the original poster?

If anyone has a draft of the code to implement this, please post it. I'll mark this postponed, needs more info.

marcushenningsen’s picture

marcushenningsen commented
Status: Postponed (maintainer needs more info) » Needs review

For now this version might do the job. I haven't added anything for region.

marcushenningsen’s picture

marcushenningsen commented
StatusFileSize
new zipcodes.dk_.txt111.17 KB

For now this version might do the job. I haven't added anything for region. The file should be renamed to zipcodes.dk.mysql

Marcus

marcushenningsen’s picture

marcushenningsen commented
StatusFileSize
new zipcodes.dk_.zip120.68 KB

A revised version with regions added.

ankur’s picture

ankur commented

I think someone will need to chime in on whether we can just add this to the repository or not. Not sure whether or not the Creative Commons Attribution license would prevent this from being added to the Git repository for location, given that everything in the Git repository is supposed to be GPL.

Drupallover’s picture

Drupallover commented

Can you repost the file as it seems to be corrupted or something.

Thanks

podarok’s picture

podarok
🇺🇦 he/him/his
Primary language Ukrainian
Location Ukraine
commented
Version: 6.x-3.x-dev » 7.x-3.x-dev
Status: Needs review » Patch (to be ported)

All data updates have to be rolled against latest 7.x-3.x-dev and after that backported to 6.x-3.x
This one has to be uploaded in http://drupal.org/patch git diff format

vtcore’s picture

vtcore commented
Issue summary: View changes
StatusFileSize
new zipcodes.dk_.mysql_.txt107.04 KB

Here is a file with more accurate coordinates for the zip codes. I haven't included regions here, because I don't know what they should be.
Our client noticed that some of the zips we on the wrong place or were completely missing. The file is generated using http://findvej.dk/.

legolasbo’s picture

legolasbo
he/him
Primary language Dutch
Location Middelburg
commented
Assigned: Freso » Unassigned
Status: Patch (to be ported) » Needs work

This actually needs to be rolled into a drupal patch.