[Talk-se] Ortnamnsimport från Lantmäteriets GSD-Terrängkartan

[Grigory Rechistov]

Hej!
Lång historia kort: jag har skapad en privat OSM API server som nu innehåller
samtliga 118 tusen importnoder. Man kan använda den för att ladda ner, jämföra,
redigera, radera flytta och eventuellt ladda upp punkter till den offentliga
OSM-databasen. Man "öppnar" både servrarna som två JOSM:s lager och flyttar noder
mellan lagren.
Här följer ett utdrag ur importplanen https://wiki.openstreetmap.org/wiki/Import/Catalogue/Lantm%C3%A4teriet_GSD-Terr%C3%A4ngkartans_ortnamnsimport#Private_API_server_workflow som beskriver processen
steg för steg.
 
============
Private API server workflow
A private OSM API v0.6 server is created to host a live copy of import data. The server URL is http://atakua.org:3000/api and it can be specified in JOSM settings to download and upload ready nodes.
Notes about the private API server
    The private API server is a slow home computer behind an even weaker front-end VPS. Please do not overload it with work.
    There are no guarantees that the server is available at any time, or at all. Its power and/or network connection may be down for undefined periods of time.
    The server runs a rough copy of the official osm.org website software.
        Only the API v0.6 endpoint is supposed to work at the specified URL. If something else works, it does so by accident.
        There is no real gliding map, no Overpass/Nominatim etc. services, no users (except one), no way to register users, no online editor etc.
        There is currently no tile server to visualize the DB contents. Having one would definitely help to see what areas are still not covered.
    A single account mapper is created to allow collaborators to make edits via OSM API. See the mailing list thread for the account's password.
    Please report your problems with the server to the talk-se mailing list.
The workflow is to download a group of nodes from the private API, edit them as needed, copy them to the public DB, and delete them from the private DB.
Step-by-step workflow
A recommended workflow is described below. JOSM and two data layers are used to download, edit and transfer nodes from the private API to the public API. Certain steps of the workflow may be adjusted when needed.
It is recommended to set up and activate a JOSM filter with query text "place=*" and inverted flag in order to shade everything not related to objects with place tags. It will shade a lot of visual clutter.
1. Use the JOSM download dialog with gliding window to download a chunk of data from the OSM API server into a new data layer.
2. Create a second empty data layer (keyboard shortcut Ctrl-N).
3. Change JOSM settings to expert mode. In JOSM settings change connection options to the private API URL.
4. Use the download dialog with gliding window to download a chunk of data for the same bounding box from the private API server. Now you have two data layers: the first one with "old" and the second one with "new" data.
5. Edit the "new" data in the second layer as you see fit: move, rename, delete, retag etc. Set up an satellite imagery background layer as a reference if needed.
6. When satisfied with the result, it is time to move the new nodes. Do not use JOSM's Merge function to copy nodes between layers! It won't work correctly as object IDs of the private API are incompatible with the main OSM DB.
7. Select all nodes (Ctrl-A), copy them to the clipboard (Ctrl-C). Switch to the first layer, and use Paste at source position (shortcut Ctrl-Alt-V) command to insert them. A copy of selected nodes (treated as newly created objects by JOSM) will be created.
8. Get back to the second layer and delete selected nodes. Then upload your changes to the private API DB. To do that, user account in JOSM settings must be set to mapper, not your normal import account.
    Yes, this is awkward to switch back and forth between two API URLs and two accounts via JOSM options. A ticket for a feature enhancement to address this inconvenience has not been closed since 2009.
    The deletion step is required to prevent other collaborators from working on the same nodes after you've moved them. Please mention your "real" user account in the changeset message.
9. Change back to the public OSM API and your import account in JOSM settings. Make sure to use a separate account containing word "import" when uploading data to the main DB; it is dictated by the OSM requirements.
10. Open the first data layer and upload it to the public API DB.
As a result of these steps, a set of nodes was moved from one DB to another DB.

==========
Den privata API:s kontouppgifter:
    användarnamn: mapper
    lösenord: at_at_how_med_cos
Ni kan leka med den! Rapportera gärna dina åsikter om hela ovanstående processen.
Tänk på att servern kan krascha när som helst. Jag håller på att semestra nästa
vecka och jag kommer troligen inte kunna åtgärda några uppstående problem tills
jag kommer tillbaka.
Om allt går bra ska jag snart inleda en diskussion på importlistan så att
man kan gå vidare till någon verklig resultat.
Tack!
 
 
 
Med vänliga hälsningar,
Grigory Rechistov
With best regards,
Grigory Rechistov
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-se/attachments/20200221/f2ea32f2/attachment.htm>