Import plan.at

about plan.at

In 1997 plan.at was started with an Autodesk MapGuide-Server by the b2b publisher Compass-Verlag as the first Austrian mapping portal. Until 2008 plan.at produced its own geographic data originally produced by a German company, which ended their production in the late 90ies. The geographic Material has about the double of the road length of OSM.

Change to OSM 2008

In Octobre 2008 the idea was born to switch to OpenStreetMap and release all the geographic material onto CC-BY-SA or oDBL. After a meeting with Mikel Maron, a member of the foundation board and a legal check, merging will start in Decembre 2008 in close touch with the community.

Technischer Ablauf

The data are present for each Bezirk in Autodesk map files (*.dwg). Over different Layer the type of object is indicated and in the object data is postal code, name and possibly road number indicated. The OSM data were read in into a PostgreSQL server, which can be used now to compare with the new data. The plan.at data are exported from AutoCAD in WGS-84, examined for the relative Lagegenauig and adapted accordingly if necessary. In the PostgreSQL server the Nodes is compared with the OSM Nodes, so that existing Node Ids will übermnommen can. Objects, which lie in ranges, where still no OSM object is, (so the plan) automated imported. Objects, which compete with existing, are imported only in arrangement with the Community in small portions or used for comparison purposes. The technical completion takes place via Wolfgang W. Wasserburger (osm (RK) wasserburger.at).

Wichtiges zum Import, Vorgangsweise

The accuracy of the material already available is generally better, therefore one should supplement as far as possible the present objects simply with data by CoPy/paste (CTRL-C works in Potlatch, CRTL-V not, therefore one must insert with the mouse right click > Insert). The other possibility is to show all GPS TRACKs, and to shift the new imported roads simply to the correct place (usually complete road shift, and then still another few Nodes adapt), and then to delete the old road. In many places are also so far only the GPS TRACKs, but still nobody drew in roads. So one can move the new road to the correct place and nothing needs to be deleted.

In cities where already very much is registered (" PRIO 3" , should be imported with vorangesetzem namespace. This is however very much manual work. Then one emphasizes all roads without names coloured, transmits the missing information from the import to the old road (postal zip code and street name is times the most important, and at the best also still is_in= the day - whereby I not white whether with search for roads on this consideration is taken from the current programs), and loescht more nacher the imported road raus (thus after all important information was transferred). The roads are imported with namespace, therefore one sees editing them only with, her however with rendern by maps is not considered. Meaningful it is nevertheless to have the goal after at the latest 7 days the new information to have transferred so that they edit other people with do not irritate.

Welche Möglichkeiten gibt es fuer den Import -->

• Normal import of a whole district without regard
• Import of a whole district and one or several rectangles (500x500m, this accurately fits better more largely there please at least and overlapping roads nevertheless does not clean-come) not at all and/or with namespace
• Complete import with namespace (reasonable for Vienna, state capitals, other very well mapped areas).
• Import by namespace (or not at all), if in the distance from 100m no other object is registered in the OSM. After my import experience this is however not reasonable, because one will lose too much, and have a great many unconnected roads in fragments.

Expenditure of time I needed about 10 hours for the import of Neunkirchen. In addition User:Quarksteilchen also worked 1-2 hours (AFAIK) on it. Neunkirchen was the district with the largest data set at had plan.at, and still quite few mapped, however more than I had thought, since I had simply underestimated the district surface (I estimated after the import was so 15-20% of all roads doubly available). A rectangle around Neunkirchen was completely left empty with the import, since everything was here already present including street names.

Parallel arbeiten With Potlatch each Edit is registered after that to click a new object directly in OSM. With JOSM only after the Upload. Here it may occur that the work overlaps. If thus several persons work on a district, then one should be in contact by IRC, mail, etc., to prevent double work.

Deletion of the Fixme tags with the import is connected

IMHO these tags should be deleted if on good aerial photograph or by GPS TRACKs it is verified that the way actually exists and also is drawn correctly. Until this happens, one should leave the Fixme in place. (please supply other opinions here - I'm not sure what is the best way here).

I just found this project awesome. I would like to perhaps use Babelfish for a quick translation of what your doing, so I can keep track and perhaps learn too. (would that be OK? I created a page Importing Government Data to try to address the issues, as (i think) everyone has simmilar problems. Thanks --acrosscanadatrails 04:43, 19 December 2008 (UTC) Yahoo! Babel Fish translation (needs editing work).
English speaking people please excuse, that some of the following facts are only stated in german language.
You can find the german site here: WikiProject_Austria/Import_plan.at