[OSM-talk-nl] Importing trees in Utrecht

0 views
Skip to first unread message

Pieter van Mill via Talk-nl

unread,
Sep 27, 2020, 12:45:16 PM9/27/20
to imp...@openstreetmap.org, tal...@openstreetmap.org, pie...@osmstart.com
Hello everyone,

I would like to start a project to import trees in the city of Utrecht, The Netherlands.

The wiki page of this project can be found here: https://wiki.openstreetmap.org/wiki/Utrecht_tree_import

Before I do more work on this project I would like to see if this is a good project to do. The data that could be imported can be found on this map: https://gemu.maps.arcgis.com/apps/webappviewer/index.html?id=53c67672c1fa46e5bef555a611b58301

The license for the dataset is CC-0 which makes it compatible with the ODbL license.

If there are any comments I would love to hear them,

Pieter (pcmill)

_______________________________________________
Talk-nl mailing list
Tal...@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-nl

Sebastiaan Couwenberg

unread,
Sep 27, 2020, 1:25:23 PM9/27/20
to tal...@openstreetmap.org
On 9/27/20 6:44 PM, Pieter van Mill via Talk-nl wrote:
> If there are any comments I would love to hear them,

More mappers are active on the forum, you'll get more feedback there.

https://forum.openstreetmap.org/viewforum.php?id=12

Since you only talk about importing, also think about how the data will
be updated.

Kind Regards,

Bas

--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

Pander via Talk-nl

unread,
Sep 28, 2020, 6:08:51 AM9/28/20
to OpenStreetMap NL discussion list, Pander

On 9/27/20 19:25, Sebastiaan Couwenberg wrote:
> On 9/27/20 6:44 PM, Pieter van Mill via Talk-nl wrote:
>> If there are any comments I would love to hear them,
> More mappers are active on the forum, you'll get more feedback there.
>
> https://forum.openstreetmap.org/viewforum.php?id=12
>
> Since you only talk about importing, also think about how the data will
> be updated.
And how to merge with existing trees that are (almost) on the same
location to prevent duplicates. This step could also be repeated with
update actions. Probably a generated list of possible duplicates that
have to be merged semi automatically. Must be tools for this available
already. Note that exiting trees can have more data, so that should be
kept in the merge.
>
> Kind Regards,
>
> Bas

St Niklaas

unread,
Sep 28, 2020, 6:30:39 AM9/28/20
to OpenStreetMap NL discussion list


Van: Pieter van Mill via Talk-nl <tal...@openstreetmap.org>
Verzonden: zondag 27 september 2020 18:44
Aan: imp...@openstreetmap.org <imp...@openstreetmap.org>; tal...@openstreetmap.org <tal...@openstreetmap.org>
CC: pie...@osmstart.com <pie...@osmstart.com>
Onderwerp: [OSM-talk-nl] Importing trees in Utrecht
 

St Niklaas

unread,
Sep 28, 2020, 6:42:47 AM9/28/20
to OpenStreetMap NL discussion list
Beste Pieter van Mill,

Het klinkt aardig, maar een korte en vluchtige blik brengt enige lacunes aan het licht. De database zou slechts de Utrechtse bomen behelsen, maar niet de er naast staande andere bomen.
Dit kwam aan het licht bij een blik op bijvoorbeeld Fort bij Rhijnauwen, gelegen midden in het Amelisweerdse landgoed.
Dat brengt me op eerder aangeroerde acties als controle en updates, 150.000 is nogal een groot aantal, is het misschien een idee om de import slechts dan uit te voeren als er een werkgroep >1 aan mee werkt en ook de noodzakelijke controles (als noodzakelijk) uitvoerd.
Deze methode is ook bij de BAG import gevolgd, geen import zonder lokale en plaatselijk controle !

Hendrikklaas

Pander

unread,
Sep 28, 2020, 7:29:54 AM9/28/20
to OpenStreetMap NL discussion list

On 9/28/20 12:07, Pander via Talk-nl wrote:
> On 9/27/20 19:25, Sebastiaan Couwenberg wrote:
>> On 9/27/20 6:44 PM, Pieter van Mill via Talk-nl wrote:
>>> If there are any comments I would love to hear them,
>> More mappers are active on the forum, you'll get more feedback there.
>>
>> https://forum.openstreetmap.org/viewforum.php?id=12
>>
>> Since you only talk about importing, also think about how the data will
>> be updated.
> And how to merge with existing trees that are (almost) on the same
> location to prevent duplicates. This step could also be repeated with
> update actions. Probably a generated list of possible duplicates that
> have to be merged semi automatically. Must be tools for this available
> already. Note that exiting trees can have more data, so that should be
> kept in the merge.
Note, StreetComplete also adds details to trees that should not get lost
in uploads or upgrades.
Reply all
Reply to author
Forward
0 new messages