Re: [OSM-talk] ford=no for highways which are known to have no fords?

[malenki]

On Tue, 31 May 2016 23:08:22 +0200,
Richard wrote:

> I found plenty of places where people have done everything
> correctly but accidentally applied the bridge/culvert/layer
> to the wrong way segment or one of the nodes - any way to 
> automate that even more?

And how will you get this people not to apply ford=no to the waterway
instead of the highway or to the wrong highway or to some node or
ford=yes to all of the highway?

I never saw so much energy wasted like in this discussion /not/ to map
certain things. How many bridges, fords, culverts or even nothing you
and all the other people involved could have mapped instead of replying
to this thread.

Oh my goodness!


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Overpass outage?

[Jérôme Seigneuret]

Hi,

Can you paste code part in response to this post. Thanks

Jérôme

2016-06-01 23:23 GMT+02:00 Richard :

> Hi,
>
> when trying to download data in JOSM through the Overpass API I am
> getting an error
>
> "Failed to download data: its format is either unsupported, ill-formed
> and/or inconsistent
>  Details (untranslated): Line 2 column 3: The markup declarations
> contained or pointed to by the document type declaration must be
> well-formed"
>
> indicating the overpass server returns ill-formed data or possibly DTD
> is inaccessible. Has anyone else seen that?
>
> Richard
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Overpass outage?

[Richard]

sorry for the noise, was a problem with my mobile provider.

> when trying to download data in JOSM through the Overpass API I am
> getting an error
> 
> "Failed to download data: its format is either unsupported, ill-formed and/or 
> inconsistent
>  Details (untranslated): Line 2 column 3: The markup declarations contained 
> or pointed to by the document type declaration must be well-formed"
> 
> indicating the overpass server returns ill-formed data or possibly DTD 
> is inaccessible. Has anyone else seen that?
> 
> Richard

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] Overpass outage?

[Richard]

Hi,

when trying to download data in JOSM through the Overpass API I am
getting an error

"Failed to download data: its format is either unsupported, ill-formed and/or 
inconsistent
 Details (untranslated): Line 2 column 3: The markup declarations contained or 
pointed to by the document type declaration must be well-formed"

indicating the overpass server returns ill-formed data or possibly DTD 
is inaccessible. Has anyone else seen that?

Richard

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Burger King use of OSM without Attribution

[Manfred A. Reiter]

Hi Mikel,

btw - and I don't know whether runtastic is you client ...

... I see that runtastic offers OSM, and when I choose it, the app shows
Google in the lower left corner and nothing from OSM.

To whom I have to report it?

cheers


Manfred

2016-05-31 23:29 GMT+02:00 Mikel Maron :

> Thanks -- yes appreciate the heads up on the issue, and please give us a
> few days to get this fixed. Mapbox takes attribution very seriously, and
> has relationships with the relevant customers to get this addressed.
>
> And by the way, working on setting up a contact point where attribution
> issues on Mapbox hosted maps can be directly reported.
>
> -Mikel
>
>
> * Mikel Maron * +14152835207 @mikel s:mikelmaron
>
>
> On Tuesday, May 31, 2016 5:03 PM, Milo van der Linden 
> wrote:
>
>
>
> I agree, as we are on "speaking terms"  with mapbox, it seems to me that
> we can easily fix this like gentlemen.
>
> Kind regards,
>
> Milo
>
> 2016-05-31 22:35 GMT+02:00 Benoît Barteaux :
>
> They don't seem to cut the image, as the problem seems to come from mapbox
> directly.
> I think that sending now a copyright notice to BK/mapbox would seem a bit
> premature and upfront. Give them time for the email to travel to the right
> person and to think/react for a bit. After some time then, maybe.
> Cheers,
> Benoit
>
> On 31/05/16 22:16, Clifford Snow wrote:
>
> Mikel,
> I wonder if they just crop the image for the website, cutting off
> attribution? They haven't replied to me, so I am going to look for
> something like a legal contact at Burger King. Though we could issue a
> copyright takedown to AWS.
>
>
>
> On Tue, May 31, 2016 at 11:21 AM, Mikel Maron 
> wrote:
>
> Thanks for the report, we're looking into sorting out this attribution
> issue at Mapbox.
>
> * Mikel Maron * +14152835207 @mikel s:mikelmaron
>
>
> On Saturday, May 28, 2016 4:51 AM, Milo van der Linden 
> wrote:
>
>
>
> Burgerking is using the static image api from mapbox:
>
>
> http://api.tiles.mapbox.com/v3/dondeinc.ilo032fk/url-http%3A%2F%2Fs3.amazonaws.com%2Fdonde-img%2Fpin-bk.png%3Fc%3D3(-117.4382504,47.71573001)/-117.4382504,47.71573001,16/640x640.png
> 
>
> So perhaps mapbox should be asked why attribution is not visible in the
> static image api.
>
> 2016-05-28 7:22 GMT+02:00 Clifford Snow < 
> cliff...@snowandsnow.us>:
>
> I notices a new user added a fast food node [1] in Spokane, WA. The name
> was entered as BK. Assuming it was probably a Burger King, I did a search
> and found that it was actually a Burger King restaurant. What I noticed was
> their map [2] was identical to OSM.
>
> I sent a message via their contact me link on the page asking that they
> comply with our terms of use.
>
> Has anyone else noticed Burger King using OSM data before?
>
> [1] 
> http://www.openstreetmap.org/changeset/39617650
> [2]
> 
> http://www.bk.com/restaurants/wa/spokane/1804-west-francis-ave-5816.html
>
> On a side note, I did send the user a message asking to verify the name.
> First time user with MAPS.ME .
>
> Clifford
>
> --
> @osm_seattle
> osm_seattle.snowandsnow.us
> OpenStreetMap: Maps with a human touch
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
>
>
> --
> [image: http://www.dogodigi.net] 
> *Milo van der Linden*
> web: dogodigi 
> tel: +31-6-16598808
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
>
>
>
> --
> @osm_seattle
> osm_seattle.snowandsnow.us
> OpenStreetMap: Maps with a human touch
>
>
> ___
> talk mailing 
> listtalk@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk
>
>
> --
> Cordialement,
> Besoins en programmation IT de pointe ?
> Contactez nous, BBashIT s'occupe de tout
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
>
>
> --
> [image: http://www.dogodigi.net] 
> *Milo van der Linden*
> web: dogodigi 
> tel: +31-6-16598808
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>


-- 
## Manfred Reiter - -
## www.weeklyOSM.eu
___
talk mailing list
talk@openstreetmap.org
https://list

Re: [OSM-talk] Osmose, duplicate housenumber

[Imre Samu]

>Osmose seems to follow the rule: One feature, one OSM element (or one
feature, one tag) and avoids duplicating data.

imho=yes

#1.
in Hungary - we don't have housenumber imports  ..  so all housenumber
collected by mappers.   And sometimes exist in the building - and most of
the times not.
And it is very hard to communicate that some shops allowed the
 "addr:housenumber"  - and others not.

imho :
- this rule  is not beginner friendly.


#2.
As I know, the iD Editor is not following this rule ..
And the "contact:housenumber"  is not used by projects ( = editors )
http://taginfo.openstreetmap.org/keys/contact%3Ahousenumber#projects

Probably we need to add the  "addr:housenumber"  to the exception list [1]
because  this "practice is firmly established and unlikely to change. "
[1]  http://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element


Imre


2016-06-01 10:16 GMT+02:00 althio :

>
>
> Łukasz Stelmach
>
>>
>> Can you explain why Osmose (and does it matter at all) warns about
>> duplicate housnumber when a shop (node) with a set of addr:* tags is
>> created inside a building (area) that is also tagged with addr:*?
>
>
>
> Osmose seems to follow the rule: One feature, one OSM element (or one
> feature, one tag) and avoids duplicating data.
>
> The rationale is certainly close to:
> http://wiki.openstreetmap.org/wiki/House_numbers/Bremen_Schema
>
> where you can use:
>  - addr:* tags for buildings or nodes on the street
>  - contact:* tags for contact information about a POI
>
> Best,
>
> -- althio
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Osmose, duplicate housenumber

[Łukasz Stelmach]

althio  writes:

> Łukasz Stelmach
>>
>> Can you explain why Osmose (and does it matter at all) warns about
>> duplicate housnumber when a shop (node) with a set of addr:* tags is
>> created inside a building (area) that is also tagged with addr:*?
>
> Osmose seems to follow the rule: One feature, one OSM element (or one
> feature, one tag) and avoids duplicating data.
>
> The rationale is certainly close to:
> http://wiki.openstreetmap.org/wiki/House_numbers/Bremen_Schema

This makes sens.

> where you can use:
>  - addr:* tags for buildings or nodes on the street
>  - contact:* tags for contact information about a POI

I will. Thanks.

-- 
Miłego dnia,
Łukasz Stelmach


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Osmose, duplicate housenumber

[Jérôme Seigneuret]

Hi,

Because there is 2 notions: building address and contact address.

In fact if you have create an addr:housenumber, all contacts addresses need
use contact:housenumber.

That is the same to all duplicate addr:* value if there exists on a contact
POI.

There is one POI (an unique) with addr:* (this addr poi can be locate on
same node as entrance or on building. It depends on choice of schema ) and
one or more POI with contact:* . In this case * can be same key=value as
addr:* values

for exemple: http://www.openstreetmap.org/node/369521753

old values




must be replace by:




Because building  is already
tagged
addr:city=Warszawa
addr:housenumber=129
addr:street=Aleja Niepodległości

Best,
Jérôme
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Osmose, duplicate housenumber

[althio]

Łukasz Stelmach

>
> Can you explain why Osmose (and does it matter at all) warns about
> duplicate housnumber when a shop (node) with a set of addr:* tags is
> created inside a building (area) that is also tagged with addr:*?



Osmose seems to follow the rule: One feature, one OSM element (or one
feature, one tag) and avoids duplicating data.

The rationale is certainly close to:
http://wiki.openstreetmap.org/wiki/House_numbers/Bremen_Schema

where you can use:
 - addr:* tags for buildings or nodes on the street
 - contact:* tags for contact information about a POI

Best,

-- althio
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] Osmose, duplicate housenumber

[Łukasz Stelmach]

Hi,

Can you explain why Osmose (and does it matter at all) warns about
duplicate housnumber when a shop (node) with a set of addr:* tags is
created inside a building (area) that is also tagged with addr:*?

http://osmose.openstreetmap.fr/en/map/#zoom=17&lat=52.2019584&lon=21.0101640&item=2060&level=3
-- 
Miłego dnia,
Łukasz Stelmach


pgpz1yYc5DJzX.pgp
Description: PGP signature
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk