Hi,
> Moreover, the tool puts a fixme in those places
> because with the data provided it is not possible to distinguish between the
> different types of garages (private or public) and the local mapper (who
> know the place) has decided that this is the best tag for them.
Just like Andy said i
Hi everyone,
During this weekend some people of the Spanish community have been
discussing in which cases would be suitable to import some things from
Catastro to OSM.
Everything that is imported from Catastro will need to be approved by the
Spanish OSM organizers and it will only be uploaded wit
ncluding the address information
From: Ander Pijoan [mailto:ander.pij...@deusto.es]
Sent: Monday, February 25, 2013 12:42 AM
Cc: OSM Imports List
Subject: Re: [Imports] [Talk-es] [Cat2Osm2] Tool for exporting Spanish
Cadastre data in OSM suitable format
Hi everyone,
During this weekend some p
> - landuse=greenfield, building=yes, building=garage,
> leisure=swimming_pool, barrier=wall, and entrance=yes is an odd set of
> features to import. Not that there's anything wrong with that.
The mapper thinks that this was the information needed in that zone.
> - Some buildin
Hi,
Cruz Enrique Borges wrote:
> > - Last time it was discussed there was no consensus that buildings
> > should be imported split based on building plan data, e.g.
> > http://maps.paulnorman.ca/imports/review/cigarral/building.png
>
> In the Spanish list there is a rather consensus that
> Usefulness is in the eye of the beholder. While you may find it interesting
> to have all this 3D information, I'd find it much more useful to have building
> outlines in OSM that are complete. The single building parts make not much
> sense for anything but 3D rendering.
For us is a _vital_ in
Cruz Enrique Borges wrote:
Usefulness is in the eye of the beholder. While you may find it interesting
to have all this 3D information, I'd find it much more useful to have building
outlines in OSM that are complete. The single building parts make not much
sense for anything but 3D rendering.
F
On Thu, Feb 28, 2013 at 08:36:15AM +0100, Cruz Enrique Borges wrote:
> > Usefulness is in the eye of the beholder. While you may find it interesting
> > to have all this 3D information, I'd find it much more useful to have
> > building
> > outlines in OSM that are complete. The single building par
> "The height of a building gives a lot of information about the people
> living in that building" - please explain it. For me it sounds amusing
The information about the height is code as "number of floors" in the
source file (catastro). Even more, you can make a fair guess making
"3m = 1 floo
> From: Cruz Enrique Borges [mailto:cruz.bor...@deusto.es]
> Sent: Wednesday, February 27, 2013 11:36 PM
> To: imports@openstreetmap.org
> Subject: Re: [Imports] [Talk-es] [Cat2Osm2] Tool for exporting Spanish
> Cadastre data in OSM suitable format
>
> > Usefulness is in
2013/2/28 Paul Norman :
>> From: Cruz Enrique Borges [mailto:cruz.bor...@deusto.es]
>> Sent: Wednesday, February 27, 2013 11:36 PM
> The concerns being expressed are about using multiple ways to represent one
> building. How big do you estimate the import will be total, both in number
> of building
(Separating this from the other discussion about buildings)
> From: Cruz Enrique Borges [mailto:cruz.bor...@deusto.es]
> Sent: Tuesday, February 26, 2013 1:30 AM
> Subject: Re: [Imports] [Talk-es] [Cat2Osm2] Tool for exporting Spanish
> Cadastre data in OSM suitable format
>
Cruz Enrique Borges wrote:
"The height of a building gives a lot of information about the people
living in that building" - please explain it. For me it sounds amusing
The information about the height is code as "number of floors" in the
source file (catastro). Even more, you can make a fair gu
> Well, as I pointed out previously[1], we kind of need to see to be able to
> comment on it. My understanding is that thanks to restrictions put on the
> original data, it can't be distributed, so all we're left with is a .osm
> file. Also, for a .osm creation program of cat2osm's complexity a .os
Hi,
On 27 February 2013 22:45, Sarah Hoffmann wrote:
>> In the Spanish list there is a rather consensus that it is worth to upload
>> that data. Moreover, in this particular thread someone said that it would
>> be a shame that we does not import that information because it would be
>> very useful
Well these fixme are put because they need local survey.
I mean, for example, we know there is a parking space, but we did not have
enoght information to know if it is public or private.
So what will you suggest? The only options that came to my mind are:
+ Do not import these features.
+ Put a
On jeudi 28 février 2013, Cruz Enrique Borges Hernandez wrote:
> Well these fixme are put because they need local survey.
What you mean is that you don't require that the importer corrects the fixmes
before the upload ? And that it should be corrected on the long run ?
Then I'd say most of the h
> Then you don't need a fixme, but a QA tool to list the parking spaces
> currently in OSM not yet having a access=private/public
> Noone will forget to remove the fixme if the correction is done because it is
> determined by the new added access tag.
> (See pieren's comment about osmose)
This i
Le jeudi 28 février 2013 22:25:28, Cruz Enrique Borges Hernandez a écrit :
> > However, if your goal is this, then I understand the fixmes are just a
> > "JOSM enlightening trick" to be removed before the upload, then your
> > import tool chain becomes different and yes you can provide
> > un-uplo
> From: Cruz Enrique Borges Hernandez [mailto:cruz.bor...@deusto.es]
> Sent: Thursday, February 28, 2013 2:30 AM
> To: Paul Norman
> Cc: imports@openstreetmap.org
> Subject: Re: [Imports] [Talk-es] [Cat2Osm2] Tool for exporting Spanish
> Cadastre data in OSM suitable format
&
2013/3/2 Paul Norman :
>
> My general practice is to try to make imports like normal mapping. For the
> cases you've shown so far this would be addresses on the house.
>
> You haven't shown any rural cases so far, but what you're doing can actually
> make it worse. The common rural case is a lot
> From: Cruz Enrique Borges [mailto:cruz.bor...@deusto.es]
> Sent: Thursday, February 28, 2013 1:48 AM
> To: imports@openstreetmap.org
> Subject: Re: [Imports] [Talk-es] [Cat2Osm2] Tool for exporting Spanish
> Cadastre data in OSM suitable format
>
> > "The height
> From: Cruz Enrique Borges Hernandez [mailto:cruz.bor...@deusto.es]
> Sent: Thursday, February 28, 2013 3:10 AM
> Subject: Re: [Imports] [Talk-es] [Cat2Osm2] Tool for exporting Spanish
> Cadastre data in OSM suitable format
>
> > No one should be uploading while the
Am 28/feb/2013 um 21:10 schrieb Cruz Enrique Borges Hernandez
:
>
> + Do not import these features.
+1, upload them after verification
cheers,
Martin
___
Imports mailing list
Imports@openstreetmap.org
http://lists.openstreetmap.org/listinfo/impo
Am 27/feb/2013 um 22:45 schrieb Sarah Hoffmann :
> The single building parts make not much
> sense for anything but 3D rendering. And I suspect that they are going to
> give you a big headache once you get around to mapping addresses.
building parts are fine, but they are not an alternative
Am 02/mar/2013 um 00:43 schrieb Paul Norman :
> The entrance=yes node won't be used for routing. If you have the address on
> the building, it will put you at the closest mapped road to the building
so you're proposing mapping for the routers because they currently don't
interpret entrance
Am 02/mar/2013 um 09:55 schrieb Paul Norman :
> If you don't know the height and are just estimating it from the number of
> floors, you shouldn't include a height tag.
+1, use building:levels (or similar) instead
cheers,
Martin
___
Imports maili
27 matches
Mail list logo
