Please do not import inaccurate data with the intent of fixing it
later. If you want to practice an import, correct your data first, then
import it later. Too often imported data sets with errors gets
forgotten and then there is a bunch of poor data in the database.
I recommend surveying all the points and to correct all the external
data, then importing, if you really want to practice importing.
James
On 2/1/23 12:20, James via Imports wrote:
Since there are only ~100 bike parkings in the dataset, all in our
CBD, I plan to check them all in person at the end of the import. The
main reason I'm doing this is to get more experience with imports and
josm. I have already added a few bike parking spots manually outside
the CBD. Does this still seem worrying to you?
Also, I'm not sure what you mean by highway=* with respect to bike
parking.
On 2 February 2023 2:50:13 am AEST, Marc_marc <[email protected]>
wrote:
Hello,
Le 01.02.23 à 09:32, James via Imports a écrit :
I'm relatively new at OSM Does anyone have anything they'd
like to add, any advice, or any reasons I shouldn't go ahead
with this?
starting a import when you describe yourself as "relatively new"
is maybe not a good idea.
it would be better to do the first additions classically, find out how to
deal with highway=* to divide, errors in existing data, poor location in
opendata, ...
if you still want to do an import, you have probably read that
the guideline asks you to make a wiki page describing your project
Regards,
Marc
------------------------------------------------------------------------
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
_______________________________________________
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
_______________________________________________
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
