Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

not-in-map-features for each city/village not helpful #992

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments
Closed

not-in-map-features for each city/village not helpful #992

openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: stoecker
[Submitted to the original trac issue database at 7.40pm, Tuesday, 24th June 2008]

The maplint annotations of tiles@home produce a not-in-map-features for each city/town entry (probably due to the OpenGeoDB entries). Could these tags be added, so these warnings disappear.

@openstreetmap-trac
Copy link
Author

Author: bob[at]cakebox.net
[Added to the original trac issue at 3.47pm, Thursday, 26th June 2008]

I guess this is what some import somewhere in the world tagged, could you please add here what tags this is about?

@openstreetmap-trac
Copy link
Author

Author: stoecker
[Added to the original trac issue at 4.11pm, Thursday, 26th June 2008]

E.g. see http://www.informationfreeway.org/?lat=50.95209750864039&lon=14.130068979438459&zoom=13&layers=B000T000F

Example of city Bischofswerda:

    <node lon="14.17972370" lat="51.12777920" timestamp="2008-05-04T12:32:48" user="stoecker" id="30362074" >
      <tag k="created_by" v="Potlatch 0.7b" />
      <tag k="openGeoDB:loc_id" v="14552" />
      <tag k="openGeoDB:auto_update" v="population,is_in" />
      <tag k="openGeoDB:name" v="Bischofswerda" />
      <tag k="openGeoDB:is_in_loc_id" v="256" />
      <tag k="openGeoDB:is_in" v="Bautzen,Dresden,Sachsen,Bundesrepublik Deutschland,Europe" />
      <tag k="openGeoDB:version" v="0.2.6.11 / 2007-12-04 / http://fa-technik.adfc.de/code/opengeodb/dump/" />
      <tag k="openGeoDB:layer" v="6" />
      <tag k="openGeoDB:combination_of_public_administration" v="Verwaltungsgemeinschaft Bischofswerda/Rammenau" />
      <tag k="is_in" v="Bautzen,Dresden,Sachsen,Bundesrepublik Deutschland,Europe" />
      <tag k="openGeoDB:population" v="13413" />
      <tag k="openGeoDB:telephone_area_code" v="03594" />
      <tag k="openGeoDB:community_identification_number" v="14272020" />
      <tag k="openGeoDB:license_plate_code" v="BZ" />
      <tag k="openGeoDB:sort_name" v="BISCHOFSWERDA" />
      <tag k="openGeoDB:type" v="Stadt" />
      <tag k="openGeoDB:postal_codes" v="01877" />
      <tag k="name" v="Bischofswerda" />
      <tag k="opengeodb:lon" v="14.1785733" />
      <tag k="opengeodb:lat" v="51.1274811" />
      <tag k="place" v="town" />
      <tag k="population" v="13413" />
    </node>

In think this is triggered by all these opengeodb:xxx and openGeoDB:xxx fields.

I'm not sure, but at least allover Europe this affects nearly all villages (except very small), towns and cities.

@openstreetmap-trac
Copy link
Author

Author: bob[at]cakebox.net
[Added to the original trac issue at 4.32pm, Thursday, 26th June 2008]

The not-in-map_features update script has been broken since map features was converted to templates, I'm looking at fixing it now and will add ignores for these at the same time.

@openstreetmap-trac
Copy link
Author

Author: bobkare
[Added to the original trac issue at 1.58pm, Friday, 27th June 2008]

(In [8519]) New version of not-in-map_features that handles the new template format, closes #816. Also ignores openGeoDB:* tags, fixes #992

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant