Re: [Talk-at] kittsee - semiautomated import of buildings from basemap.at

2013-12-27 Diskussionsfäden martin ringer
Eigentlich eine gute Idee für den Import, aber bitte vorher genau durch 
diskutieren.
Ein Import nur mit Gebäuden halte ich für nicht ausreichend, es müsste 
unbedingt die volle Adresse angefügt sein. Sonst sinkt die Bereitschaft 
nachträglich Sachen dazuzufügen oder zu ändern.
Ich will nicht meine Orte komplett überarbeiten müssen!


 Date: Thu, 26 Dec 2013 17:09:08 +0100
 From: frede...@remote.org
 To: talk-at@openstreetmap.org
 Subject: Re: [Talk-at] kittsee - semiautomated import of buildings from   
 basemap.at
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hi,
 
 before this is imported it would at least need proper
 documentation on the Wiki import catalogue.
 
 In addition to the points mentioned by Michael -
 
  * adjacent buildings do not share nodes * no multipolygons at
  buildings with holes - those would have to be created manually *
  The buildings are not orthogonalized (q in JOSM) * nodes at very
  obtuse angles (e.g. 88°) should be removed.
 
 I would like to add
 
 * source tag on every building (source tag on changeset would be enough)
 * existing buildings are not reflected - they would have to be removed
 from the import data.
 * very small buildings seem to be badly traced (triangular shapes etc)
 - - perhaps just drop everything below 10 square metres or so.
 
 There seem to be a number of mismatches between the data and Bing
 imagery - but I guess that's because basemap.at is newer? Examples:
 http://www.remote.org/frederik/tmp/kittsee.png
 
 Bye
 Frederik
 
 - -- 
 Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09 E008°23'33
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.11 (GNU/Linux)
 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
 
 iQEcBAEBAgAGBQJSvFSXAAoJEOx/uhGAJu9H1EcH/inTfdlr5O2KTLkIiiueRrfI
 hZvIjzgCxNvSj2SBgq2gWO3HayE6+X2yzUWOvQH3LCo5h1CT+qtvl1oL3cczlxhJ
 dn1a0dLAtZ3lgog+GshkRSm2Ih6lvaeWE5VUByZuvlgy4YYC/USXx912+Q5UASdr
 LkbMRhcdM0QwBY1vgBXOatYnzBONRzkylO1ngFV91Rx6Ggh4hdsAP3bjyf6eyQmC
 v4SNecG7uNPgC4cmpkM16R9EoKbCuqxhzfmY0QcaqgIFEujiTHbHLU0NqkEAbjys
 LmBhIiDZdL2RdL0Kp0zQ8uUnN3CLOVPiy9sseYWpXzZpV8Z4a3u9OzfmcCfXOSs=
 =PT+P
 -END PGP SIGNATURE-
 
 ___
 Talk-at mailing list
 Talk-at@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk-at
  ___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [Talk-at] kittsee - semiautomated import of buildings from basemap.at

2013-12-26 Diskussionsfäden Jozef Riha
hello all,

i've been playing a bit with potrace - a bitmap to vector tool trying to
automate building shapes extraction from basemap.at (
http://wiki.openstreetmap.org/wiki/AT/basemap). as this could be considered
mass import, i would like to have austrian mapper community
checked/approved this first. i am planning to do a few fixes here and there
but generally i consider https://db.tt/eUm1BLmg to be ready for upload to
osm. please let me know if it meets your quality criteria for imports or
just share your thoughts/ideas.

vielen dank,


jose (greetings from slovakia)
___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [Talk-at] kittsee - semiautomated import of buildings from basemap.at

2013-12-26 Diskussionsfäden Michael Maier
On 26/12/13 11:01, Jozef Riha wrote:
 hello all,

Hello Jozef,

 
 i've been playing a bit with potrace 

Impressive result - can you provide a how-to for recreating (and maybe
improving) the steps you've accomplished?


- a bitmap to vector tool trying to
 automate building shapes extraction from basemap.at http://basemap.at
 (http://wiki.openstreetmap.org/wiki/AT/basemap). as this could be
 considered mass import, i would like to have austrian mapper community
 checked/approved this first. i am planning to do a few fixes here and
 there but generally i consider https://db.tt/eUm1BLmg to be ready for
 upload to osm. please let me know if it meets your quality criteria for
 imports or just share your thoughts/ideas.

I've reviewed it, but there are some flaws which (in my opinion) are
blocking the import:
* adjacent buildings do not share nodes
* no multipolygons at buildings with holes - those would have to be
created manually
* The buildings are not orthogonalized (q in JOSM)
* nodes at very obtuse angles (e.g. 88°) should be removed.

 
 vielen dank,

Ein großes Danke for your efforts!

 
 
 jose (greetings from slovakia)

Greetings,
Michael

-- 
Michael Maier, Student of Telematics @ Graz University of Technology
OpenStreetMap Graz http://osm.org/go/0Iz@paV
http://wiki.osm.org/Graz
http://wiki.osm.org/Graz/Stammtisch



signature.asc
Description: OpenPGP digital signature
___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [Talk-at] kittsee - semiautomated import of buildings from basemap.at

2013-12-26 Diskussionsfäden Frederik Ramm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

before this is imported it would at least need proper
documentation on the Wiki import catalogue.

In addition to the points mentioned by Michael -

 * adjacent buildings do not share nodes * no multipolygons at
 buildings with holes - those would have to be created manually *
 The buildings are not orthogonalized (q in JOSM) * nodes at very
 obtuse angles (e.g. 88°) should be removed.

I would like to add

* source tag on every building (source tag on changeset would be enough)
* existing buildings are not reflected - they would have to be removed
from the import data.
* very small buildings seem to be badly traced (triangular shapes etc)
- - perhaps just drop everything below 10 square metres or so.

There seem to be a number of mismatches between the data and Bing
imagery - but I guess that's because basemap.at is newer? Examples:
http://www.remote.org/frederik/tmp/kittsee.png

Bye
Frederik

- -- 
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09 E008°23'33
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSvFSXAAoJEOx/uhGAJu9H1EcH/inTfdlr5O2KTLkIiiueRrfI
hZvIjzgCxNvSj2SBgq2gWO3HayE6+X2yzUWOvQH3LCo5h1CT+qtvl1oL3cczlxhJ
dn1a0dLAtZ3lgog+GshkRSm2Ih6lvaeWE5VUByZuvlgy4YYC/USXx912+Q5UASdr
LkbMRhcdM0QwBY1vgBXOatYnzBONRzkylO1ngFV91Rx6Ggh4hdsAP3bjyf6eyQmC
v4SNecG7uNPgC4cmpkM16R9EoKbCuqxhzfmY0QcaqgIFEujiTHbHLU0NqkEAbjys
LmBhIiDZdL2RdL0Kp0zQ8uUnN3CLOVPiy9sseYWpXzZpV8Z4a3u9OzfmcCfXOSs=
=PT+P
-END PGP SIGNATURE-

___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [Talk-at] kittsee - semiautomated import of buildings from basemap.at

2013-12-26 Diskussionsfäden Andreas Labres
On 26.12.13 17:09, Frederik Ramm wrote:
 There seem to be a number of mismatches between the data and Bing
 imagery - but I guess that's because basemap.at is newer? Examples:
 http://www.remote.org/frederik/tmp/kittsee.png

(ich antworte auf Deutsch)

Es ist sehr zu empfehlen, mit geoimage.at zu vergleichen, weil das (meist) das
Aktuellste ist. Dort sieht man z.B., dass die nördlichen zwei Fragezeichen
offensichtlich abgerissen sind. Das Problem ist, es kann alles veraltet sein,
auch basemap.at (scheint mir beim südlichsten Fragezeichen = Gst. Kittsee 203/2
so zu sein).

Man sieht aber auch Fehler, z.B. das Haus ganz im NO (2421 Landstraße 13a, Gst.
Kittsee 186/2) hat in Wahrheit eine rechteckige Grundfälche, der Algorithmus hat
da eine Nische erfunden, die es nicht gibt.

Und wie schon gesagt, bitte bestehende Gebäude beachten. Zusätzlich sollte man
auch Adressen möglichst vollständig erfassen, was in aller Regel höchstens
halbautomatisch möglich ist (Jedenfalls ist die Info, auf welche Straße sich
eine Hausnummer bezieht, in basemap.at nicht vorhanden, das muss man wissen oder
recherchieren!).

/al

___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [Talk-at] kittsee - semiautomated import of buildings from basemap.at

2013-12-26 Diskussionsfäden Jozef Riha
Thank you all for sharing your views. I chose not to go further with the
import - instead I will describe the procedure I used  - maybe someone
could come up with improvements that would make the result look
better/actually usable.

- create a basemap.at xml config for mobac (http://mobac.sourceforge.net/),
select and export to png file (zoom: 19)
- open png file in gimp, select - by color, click on one building,
copypaste to new file, threshold, index - 2 colours (potrace requires
bi-color image), save buildings into pnm file
- potrace -t 100 -k 0.3 -o kittsee.svg -s kittsee.pnm
- import to josm (importvec plugin, 10 000 units = 1995 m)
- select all ways (^f - type:way - simplify using simplifyarea plugin,
using too aggressive values could result in triangular buildings, OTOH too
forgiving ones could leave you with too many nodes and/or speckles caused
by nearby housenumbers or jpeg artefacts
- turn on basemap.at tms background and align, tidy up, add tags

All the best,

jose

On Thu, Dec 26, 2013 at 5:09 PM, Frederik Ramm frede...@remote.org wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi,

 before this is imported it would at least need proper
 documentation on the Wiki import catalogue.

 In addition to the points mentioned by Michael -

  * adjacent buildings do not share nodes * no multipolygons at
  buildings with holes - those would have to be created manually *
  The buildings are not orthogonalized (q in JOSM) * nodes at very
  obtuse angles (e.g. 88°) should be removed.

 I would like to add

 * source tag on every building (source tag on changeset would be enough)
 * existing buildings are not reflected - they would have to be removed
 from the import data.
 * very small buildings seem to be badly traced (triangular shapes etc)
 - - perhaps just drop everything below 10 square metres or so.

 There seem to be a number of mismatches between the data and Bing
 imagery - but I guess that's because basemap.at is newer? Examples:
 http://www.remote.org/frederik/tmp/kittsee.png

 Bye
 Frederik

 - --
 Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09 E008°23'33
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.11 (GNU/Linux)
 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

 iQEcBAEBAgAGBQJSvFSXAAoJEOx/uhGAJu9H1EcH/inTfdlr5O2KTLkIiiueRrfI
 hZvIjzgCxNvSj2SBgq2gWO3HayE6+X2yzUWOvQH3LCo5h1CT+qtvl1oL3cczlxhJ
 dn1a0dLAtZ3lgog+GshkRSm2Ih6lvaeWE5VUByZuvlgy4YYC/USXx912+Q5UASdr
 LkbMRhcdM0QwBY1vgBXOatYnzBONRzkylO1ngFV91Rx6Ggh4hdsAP3bjyf6eyQmC
 v4SNecG7uNPgC4cmpkM16R9EoKbCuqxhzfmY0QcaqgIFEujiTHbHLU0NqkEAbjys
 LmBhIiDZdL2RdL0Kp0zQ8uUnN3CLOVPiy9sseYWpXzZpV8Z4a3u9OzfmcCfXOSs=
 =PT+P
 -END PGP SIGNATURE-

 ___
 Talk-at mailing list
 Talk-at@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk-at

___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


Re: [Talk-at] kittsee - semiautomated import of buildings from basemap.at

2013-12-26 Diskussionsfäden Robert Kaiser

Jozef Riha schrieb:

Thank you all for sharing your views. I chose not to go further with the
import - instead I will describe the procedure I used  - maybe someone
could come up with improvements that would make the result look
better/actually usable.


Thanks both for the work in figuring this out (as well as trying it and 
now describing it here) and for not going forward with it in that 
straight way.
For the latter, we unfortunately know that there are many inaccuracies 
in the basemap.at data so it needs to be looked over by people with 
local knowledge when taking it as a source for any OSM work. That 
doesn't mean it's useless, on the contrary it can be very helpful, but 
it always has to be taken with a grain of salt and verified by other 
material and ideally people who know the scenery on the ground.


Thanks and Cheers,
Robert Kaiser


___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at