[Imports] Spanish cadastre
Jaime Crespo
jynus at jynus.com
Sun Mar 25 12:42:55 UTC 2012
Here are some more up-to-date results of the tool. Please note two things:
* Your suggestions both big (relation simplification) and small
(tagging changes) have not been reflected on this version, only the
defects that were detected two weeks ago (I think Avila extract is one
of the oldest result files)
* Here you have several files: the only one intended to be used as a
basis for an import is the first one (after manual merging and
fixing). The other links are osm geometries (not intended to be
uploaded directly in any case) just to show you the different ways
this tool can be used (street ways with names but with horrible
unconnected geometry, block of houses boundaries, address nodes,
etc.).
<http://www.openstreetmap.es/wp-content/uploads/2012/03/logrono_completo_sin_ejes.osm.gz>
<http://www.openstreetmap.es/wp-content/uploads/2012/03/logrono-EJES.osm.gz>
<http://www.openstreetmap.es/wp-content/uploads/2012/03/logrono-MASA.osm.gz>
<http://www.openstreetmap.es/wp-content/uploads/2012/03/logrono-PORTALES.osm.gz>
El día 25 de marzo de 2012 07:03, Paul Norman <penorman at mac.com> escribió:
> Outlook is being uncooperative with replying inline, but hopefully this
> isn’t too hard to decode…
>
>
>
> I downloaded Avila.osm from
> http://paginaspersonales.deusto.es/cruz.borges/Avila.zip (60k relations,
> 148k ways, 406k nodes) and will be reviewing it in a separate message. I
> have a number of concerns, but it will take some time to review the file.
>
>
>
> I am not certain where the shell scripts are. I believe they are in SVN. The
> shell scripts require knowledge of how the API works, but this is no
> different than importing with JOSM.
>
>
>
> It is generally considered easier to work with complicated relations in JOSM
> than Potlatch2. If you spent an hour fixing a relation, it sounds like
> creating a new relation would be simpler.
>
>
>
> In any case, regardless of if relation support could use improvements, an
> import isn’t allowed to screw up the editing experience in Potlatch or JOSM
> (http://wiki.openstreetmap.org/wiki/Import/Guidelines#Don.27t_screw_up_the_data.21)
>
>
>
> From: Cruz Enrique Borges Hernández [mailto:cruz.borges at deusto.es]
> Sent: Saturday, March 24, 2012 5:43 AM
>
>
> To: imports at openstreetmap.org
> Subject: [Imports] Spanish cadastre
>
>
>
>> The problem with TIGER I believe is that the converter added lots of
>> non-geographical data, some unverifiable and mostly easy to obtain from
>> TIGER itself provided that the tlid is maintained.
>
>
>
> I did not know the TIGER case but in this case we have the politics of only
> use ALREADY existing metadata. Even in that case, we only use where we can
> make sure the traduction is correct ussing more general tags when in doubt.
> We haveeven switch in the cat2osm tool that create different files acording
> to their "correctness".
>
> With that in mind, the cadestre data is update every four month and could be
> update that way becasue we have already consider that in the tool. Satellite
> images are update much less frequently and local view from time to time can
> help to maintain this data. But in the end, the desission on import or not
> to import the data have to be taken by the local importer. In the results
> page there are files that the LOCAL MAPPING COMUNITY have been corrected and
> said it case with the reality of the place. They are waiting for approval to
> proceed to upload the data. The best example probably is
>
> http://wiki.openstreetmap.org/wiki/Spanish_Cadastre/results/Avila
>
> but there are others in
>
> http://wiki.openstreetmap.org/wiki/Spanish_Cadastre/results/.
>
>> The import guidelines prohibit imports that make editing very complicated
>> in the current editors.
>
> Deffine "very complicated". I think that the data ALREADY in the database is
> VERY VERY DIFFICULT to edit NOW.
> I have spend more that one hour to FIX a single relation with JOSM!!!!! We
> need to fix the editor, not the data!!!!
>
>> JOSM is not well suited for uploading lots of data. I think the best way
>> is
>> to edit with JOSM and either upload small groups of objects at once or
>> save
>> the .osm file, create a .osc file from it, sort it to keep ways near their
>> nodes and then upload it with one of the shell scripts.
>
> Can you point us to these shell scripts? We have though that it is forbiden
> to use them in any case. We are currently talking follow this aproach:
> editing and conflating in JOSM and after the aproval of local comunity the
> data will be uploaded by the person in charge of that area using some script
> that split and upload the data in small chunks.
>
>
>
> --
> Cruz Enrique Borges Hernández
> Email: cruz.borges at deusto.es
>
> DeustoTech Energy
> Telefono: 944139000 ext.2052
> Avda. Universidades, 24
> 48007 Bilbao, Spain
>
>
> _______________________________________________
> Imports mailing list
> Imports at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/imports
>
--
Jaime Crespo
More information about the Imports
mailing list