Changes between Initial Version and Version 1 of Ticket #11682


Ignore:
Timestamp:
2015-07-10T21:30:37+02:00 (10 years ago)
Author:
flaimo
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11682 – Description

    initial v1  
    1414c) How large can the CSV file be. Can JOSM handle the import of 100000 lines and above or does a maximum number of lines limit need to be implemented to ensure the stability of the running program?
    1515d) In case the CSV file contains a column with an external ID there could be an addon functionality which tries to synchronise the objects of an open data layer with the ones of the CSV file based on that ID. The user could mark the ID column during the import using a simple checkbox and afterwards JOSM updates all existing objects with those IDs it can find in the data layer. Of course there would be the need to handle conflicts on a case per case basis but also in batches (aka “Skip all existing objects”, “Only add new tags”, “Replace data of all existing objects”, and so on.). The same sould be implemented if the CSV file contains a column with the OSM database ID of an object as long as the object type (node or way) matches the existing one.
     16
     17Real life example: My home town provides a list of all managed trees as a CSV file (german "Baumkataster") which gets updated regularly. This way updating the data without having to have database knowledge would be a breeze.
    1618
    1719==== Please provide any additional information below. Attach a screenshot if possible.