Re: [OSM-talk-fr] Moulinette pour convertir codes Insee en GPS > GPX ?

2019-10-02 Thread Jérôme Seigneuret
Bonjour,

@christian sur l'api adresse on peut aussi imaginer de définir le niveau
exact où une limite à prévoir dans les types d'objets recherchés,
output=voie, lieudit,ville,commune

Jérôme






Le mer. 2 oct. 2019 à 22:56, Christian Quest  a
écrit :

> api-adresse.data.gouv.fr est fait pour géocoder des adresses, pas des
> noms de ville avec leur code INSEE, ça c'est le boulot de geo.api.gouv.fr
>
> Du coup, oui, 3190 moulins, ça peut être plein de choses...
>
>
> Le mer. 2 oct. 2019 à 19:17, Shohreh  a écrit :
>
>> Samy Mezani wrote
>> > L'API est faite pour automatiser tout ça :
>> >
>> > https://geo.api.gouv.fr/adresse (descendre à /search/csv/)
>>
>> Merci beaucoup.
>>
>> Si d'autres cherchent à faire la même chose :
>> 1. (nécessaire?) Convertir les données entrée en UTF8
>> 2. Downloader curl.exe dans le même répertoire
>> 3. curl --insecure -o output.csv -X POST -F data=@input.csv -F
>> citycode=NOMCOLONNECODEINSEE https://api-adresse.data.gouv.fr/search/csv/
>>
>> Bizarrement, il y a des villes que le serveur n'a pas réussi à géocoder
>> (lat,lon vides):
>>
>> 3190Moulins
>> 44090   La Marne
>> 77083   Champs-sur-Marne
>> 88212   Grand
>> 92072   Sèvres
>> 93039   L'Île-Saint-Denis
>> 93066   Saint-Denis
>>
>>
>>
>> --
>> Sent from: http://gis.19327.n8.nabble.com/France-f5380434.html
>>
>> ___
>> Talk-fr mailing list
>> Talk-fr@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-fr
>>
>
>
> --
> Christian Quest - OpenStreetMap France
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-ca] Postcodes in Canada

2019-10-02 Thread Kyle Nuttall
I've found a good resource to use is a business website. Particularly a store 
with multiple locations, a mall directory, or a BIA. They have several postal 
codes that are associated with their respective addresses.

Unfortunately it does require manual work (or you could pair a scrapper with a 
geocoder to do the tedious part) but given there is no available datasets we're 
licenced to use currently, it's the only public resource I know of where you 
can get pockets of postal codes.

As more and more get added, the zones will begin to reflect their true shape 
more accurately and it'll be easier to extrapolate.

I know it's not the best answer but any bit helps I suppose.

On Oct. 2, 2019 21:33, John Whelan  wrote:
I had long discussions with Canada Post about postcodes years ago.  I was 
working with Treasury Board standards group at the time looking at addressing 
standards and I'm very aware of the limitations.

Rural post codes are very definitely an issue and not all postcodes used by 
Stats Canada and other government departments for example are physical 
locations.

Open Data would be nice but realistically it isn't going to happen in the short 
term.

Having said that what is doable is spotting postcodes that do exist but are not 
in OpenStreetMap then tagging a building with an address that includes a 
postcode in that postcode.

For example  if K4A 1M7 exists in the map then it would be reasonable to assume 
that K4A 1M6 - 1M1 should also exist so could be looked for.

Cobourg is an example where there are far fewer postcodes than one might like 
to see.

Cheerio John



Kevin Farrugia wrote on 2019-10-02 8:53 PM:
I don't want to rain on the postal code party, and maybe I'm a little jaded 
from using the data, but I use the Postal Code Conversion File (PCCF) from 
Statistics Canada (who get it from Canada Post) at work.  In general I would 
say that the postal code points are in mediocre shape.

Some things I've noticed about the data and postal codes in general:
* There is usually one postal code point per postal code, although there are 
cases where there can be several points for a postal code.  For example, with 
some postal codes, if you were to make them polygons, would generate multiple 
polygons that are intersected by other postal codes.
* Postal codes, especially rural ones, pop in and out of existence and so are a 
little harder to track and are less permanent than addresses.
* Postal codes will sometimes jump from one side of a road (even municipality) 
between years as they try to improve accuracy.
I would check out the Limitations section if you'd like to see more: 
https://www.canadapost.ca/cpc/assets/cpc/uploads/files/marketing/2017-postal-code-conversion-file-reference-guide-en.pdf

Forward Sortation Areas do exist as open data through Statistics Canada - 
StatsCan generates these FSA polygons based on respondents of the Census.  
There are two limitations to this dataset on which I would advise against 
importing it into OSM:
1) Since businesses do not respond to the Census, they generally do not have 
FSAs for large industrial areas.  These areas are covered by the nearest FSA 
that they know about/can define, but this can also cause some movements of 
boundaries from Census to Census.
2) Because postal codes are created for the purpose of mail sortation and 
delivery, the FSA boundaries StatsCan is able to create are not exact.
Here's the reference document if you're interested: 
https://www150.statcan.gc.ca/n1/pub/92-179-g/92-179-g2016001-eng.htm

If at some point they did release it as open data, it might be decent enough 
for the purposes of general geocoding in OSM, I just don't want people to think 
it's as well maintained and reliable as some other types of government data.

-Kevin (Kevo)


On Wed, 2 Oct 2019 at 20:39, James 
mailto:james2...@gmail.com>> wrote:
funny you should mention geocoder.ca

The owner of that website was sued by Canada Post because he was crowd sourcing 
postal codes. Just recently (2 ish years ago?) they dropped the lawsuit because 
they knew they didnt have a case(He came to the Ottawa meetups a couple of 
times)

On Wed., Oct. 2, 2019, 8:08 p.m. Jarek Piórkowski, 
mailto:ja...@piorkowski.ca>> wrote:
Yeah, Canada Post currently considers postal codes their commercial
data. Crowd-sourcing all or a substantial amount of full codes seems
infeasible. Crowd-sourcing the forward sortation areas (the first A1A)
seems difficult since verifiability is going to be a problem
especially around the edges of the areas.

The website OpenStreetMap.org returns results for some postal codes
from a third-party database https://geocoder.ca/?terms=1 which is not
ODbL-compatible either.

Partial mapping is causing some problems with tools like Nominatim
that attach the nearest tagged postcode to search results, often
resulting in improper postal codes for reverse address lookups,
however that is arguably a tooling problem and not an OSM problem 

Re: [Talk-de] Fragen, Anregung eines Neulings

2019-10-02 Thread Martin Trautmann via Talk-de
On 19-10-02 14:58, Roland Olbricht wrote:

> In diesem Fall gibt es unten links auf der Routing-Ansicht, drittes
> Symbol (Lupe vor Quadrat) eine sogenannte Debug-Ansicht

Danke für den Hinweis. Gibt es zu diesem Modus auch eine Doku?

Woher kommen die dort gezeigten Geschwindigkeiten? Sie entsprechen eher
realen Geschwindigkeiten als den dort vorgeschriebenen Limits, sind aber
unerwartet instabil und wirken damit fast wie live data.

Was bedeutet knall pink?

Schönen Gruß
Martin



signature.asc
Description: OpenPGP digital signature
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de


Re: [Talk-us] Maine leaf-off imagery?

2019-10-02 Thread Clifford Snow
Is there any lidar data available for the area? It might be a good
substitute for leaf-off imagery.

On Wed, Oct 2, 2019 at 6:19 PM Kevin Broderick 
wrote:

> Anyone have an ODbL-compatible source of leaf-off imagery for Maine, by
> any chance? I'm particularly interested in the area around Bethel, as I'm
> trying to update minor roadways, add buildings with driveways, etc.,
> and even switching between the various imagery available in id leaves a lot
> of questions unanswered. Leaf-off imagery would be incredibly helpful, the
> more so if it were actually recent.
>
> (Yes, I've been surveying where feasible, but I'm not about to start going
> up driveways to get building dimensions.)
>
> Many thanks.
>
> --
> Kevin Broderick
> k...@kevinbroderick.com
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>


-- 
@osm_washington
www.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-ca] Postcodes in Canada

2019-10-02 Thread John Whelan
I had long discussions with Canada Post about postcodes years ago.  I 
was working with Treasury Board standards group at the time looking at 
addressing standards and I'm very aware of the limitations.


Rural post codes are very definitely an issue and not all postcodes used 
by Stats Canada and other government departments for example are 
physical locations.


Open Data would be nice but realistically it isn't going to happen in 
the short term.


Having said that what is doable is spotting postcodes that do exist but 
are not in OpenStreetMap then tagging a building with an address that 
includes a postcode in that postcode.


For example  if K4A 1M7 exists in the map then it would be reasonable to 
assume that K4A 1M6 - 1M1 should also exist so could be looked for.


Cobourg is an example where there are far fewer postcodes than one might 
like to see.


Cheerio John



Kevin Farrugia wrote on 2019-10-02 8:53 PM:
I don't want to rain on the postal code party, and maybe I'm a little 
jaded from using the data, but I use the Postal Code Conversion File 
(PCCF) from Statistics Canada (who get it from Canada Post) at work.  
In general I would say that the postal code points are in mediocre shape.


Some things I've noticed about the data and postal codes in general:
* There is usually one postal code point per postal code, although 
there are cases where there can be several points for a postal code.  
For example, with some postal codes, if you were to make them 
polygons, would generate multiple polygons that are intersected by 
other postal codes.
* Postal codes, especially rural ones, pop in and out of existence and 
so are a little harder to track and are less permanent than addresses.
* Postal codes will sometimes jump from one side of a road (even 
municipality) between years as they try to improve accuracy.
I would check out the Limitations section if you'd like to see more: 
https://www.canadapost.ca/cpc/assets/cpc/uploads/files/marketing/2017-postal-code-conversion-file-reference-guide-en.pdf


Forward Sortation Areas do exist as open data through Statistics 
Canada - StatsCan generates these FSA polygons based on respondents of 
the Census.  There are two limitations to this dataset on which I 
would advise against importing it into OSM:
1) Since businesses do not respond to the Census, they generally do 
not have FSAs for large industrial areas.  These areas are covered by 
the nearest FSA that they know about/can define, but this can also 
cause some movements of boundaries from Census to Census.
2) Because postal codes are created for the purpose of mail sortation 
and delivery, the FSA boundaries StatsCan is able to create are not exact.
Here's the reference document if you're interested: 
https://www150.statcan.gc.ca/n1/pub/92-179-g/92-179-g2016001-eng.htm


If at some point they did release it as open data, it might be decent 
enough for the purposes of general geocoding in OSM, I just don't want 
people to think it's as well maintained and reliable as some other 
types of government data.


-Kevin (Kevo)


On Wed, 2 Oct 2019 at 20:39, James > wrote:


funny you should mention geocoder.ca 

The owner of that website was sued by Canada Post because he was
crowd sourcing postal codes. Just recently (2 ish years ago?) they
dropped the lawsuit because they knew they didnt have a case(He
came to the Ottawa meetups a couple of times)

On Wed., Oct. 2, 2019, 8:08 p.m. Jarek Piórkowski,
mailto:ja...@piorkowski.ca>> wrote:

Yeah, Canada Post currently considers postal codes their
commercial
data. Crowd-sourcing all or a substantial amount of full codes
seems
infeasible. Crowd-sourcing the forward sortation areas (the
first A1A)
seems difficult since verifiability is going to be a problem
especially around the edges of the areas.

The website OpenStreetMap.org returns results for some postal
codes
from a third-party database https://geocoder.ca/?terms=1 which
is not
ODbL-compatible either.

Partial mapping is causing some problems with tools like Nominatim
that attach the nearest tagged postcode to search results, often
resulting in improper postal codes for reverse address lookups,
however that is arguably a tooling problem and not an OSM
problem per
se.

This isn't going to be pretty until Canada Post is persuaded
to free
the data. Call your MP, everybody.

--Jarek

On Wed, 2 Oct 2019 at 17:38, john whelan
mailto:jwhelan0...@gmail.com>> wrote:
>
> " The number one request on open.canada.ca
 is to open the postal code database. 
Feel free to add your vote.
https://open.canada.ca/en/suggested-datasets;
>
> Cheerio John
>
> On Wed, 

[Talk-us] Maine leaf-off imagery?

2019-10-02 Thread Kevin Broderick
Anyone have an ODbL-compatible source of leaf-off imagery for Maine, by any
chance? I'm particularly interested in the area around Bethel, as I'm
trying to update minor roadways, add buildings with driveways, etc.,
and even switching between the various imagery available in id leaves a lot
of questions unanswered. Leaf-off imagery would be incredibly helpful, the
more so if it were actually recent.

(Yes, I've been surveying where feasible, but I'm not about to start going
up driveways to get building dimensions.)

Many thanks.

-- 
Kevin Broderick
k...@kevinbroderick.com
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread ndrw6

On 02/10/2019 14:20, Chris Hill wrote:


I would not like to see that happen. OSM maps real objects, postcodes 
are not real and only apply as a part of an object's address. They 
apply to buildings (delivery points on buildings really). The 
postcodes in Codepoint Open are centroids derived from a combination 
of all the delivery points that share the postcode so are not at all 
real-world objects.


Points with addr:* tags are commonly in use and accepted, there is no 
reason why addr:postcode would have to be different. When possible I 
also prefer tagging addresses on buildings or building:part but there 
are multiple conventions in use (points, points+interpolation, points on 
entrances).


If you want to apply postcodes to addresses you can see the map 
overlay I have produced which you can use in editors as an overlay: 
https://codepoint.raggedred.net/  I will update it again shortly. You 
can also derive postcodes from other open data sources such as FHRS data.


Thank you. I've been using your overlays a lot. However, given a choice, 
I would much more prefer a periodic, maintained import. Much less prone 
to errors, more up to date and easier to merge with buildings, if needed.


ndrw6



___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [Talk-ca] Postcodes in Canada

2019-10-02 Thread Kevin Farrugia
I don't want to rain on the postal code party, and maybe I'm a little jaded
from using the data, but I use the Postal Code Conversion File (PCCF) from
Statistics Canada (who get it from Canada Post) at work.  In general I
would say that the postal code points are in mediocre shape.

Some things I've noticed about the data and postal codes in general:
* There is usually one postal code point per postal code, although there
are cases where there can be several points for a postal code.  For
example, with some postal codes, if you were to make them polygons, would
generate multiple polygons that are intersected by other postal codes.
* Postal codes, especially rural ones, pop in and out of existence and so
are a little harder to track and are less permanent than addresses.
* Postal codes will sometimes jump from one side of a road (even
municipality) between years as they try to improve accuracy.
I would check out the Limitations section if you'd like to see more:
https://www.canadapost.ca/cpc/assets/cpc/uploads/files/marketing/2017-postal-code-conversion-file-reference-guide-en.pdf

Forward Sortation Areas do exist as open data through Statistics Canada -
StatsCan generates these FSA polygons based on respondents of the Census.
There are two limitations to this dataset on which I would advise against
importing it into OSM:
1) Since businesses do not respond to the Census, they generally do not
have FSAs for large industrial areas.  These areas are covered by the
nearest FSA that they know about/can define, but this can also cause some
movements of boundaries from Census to Census.
2) Because postal codes are created for the purpose of mail sortation and
delivery, the FSA boundaries StatsCan is able to create are not exact.
Here's the reference document if you're interested:
https://www150.statcan.gc.ca/n1/pub/92-179-g/92-179-g2016001-eng.htm

If at some point they did release it as open data, it might be decent
enough for the purposes of general geocoding in OSM, I just don't want
people to think it's as well maintained and reliable as some other types of
government data.

-Kevin (Kevo)


On Wed, 2 Oct 2019 at 20:39, James  wrote:

> funny you should mention geocoder.ca
>
> The owner of that website was sued by Canada Post because he was crowd
> sourcing postal codes. Just recently (2 ish years ago?) they dropped the
> lawsuit because they knew they didnt have a case(He came to the Ottawa
> meetups a couple of times)
>
> On Wed., Oct. 2, 2019, 8:08 p.m. Jarek Piórkowski, 
> wrote:
>
>> Yeah, Canada Post currently considers postal codes their commercial
>> data. Crowd-sourcing all or a substantial amount of full codes seems
>> infeasible. Crowd-sourcing the forward sortation areas (the first A1A)
>> seems difficult since verifiability is going to be a problem
>> especially around the edges of the areas.
>>
>> The website OpenStreetMap.org returns results for some postal codes
>> from a third-party database https://geocoder.ca/?terms=1 which is not
>> ODbL-compatible either.
>>
>> Partial mapping is causing some problems with tools like Nominatim
>> that attach the nearest tagged postcode to search results, often
>> resulting in improper postal codes for reverse address lookups,
>> however that is arguably a tooling problem and not an OSM problem per
>> se.
>>
>> This isn't going to be pretty until Canada Post is persuaded to free
>> the data. Call your MP, everybody.
>>
>> --Jarek
>>
>> On Wed, 2 Oct 2019 at 17:38, john whelan  wrote:
>> >
>> > " The number one request on open.canada.ca is to open the postal code
>> database.  Feel free to add your vote.
>> https://open.canada.ca/en/suggested-datasets;
>> >
>> > Cheerio John
>> >
>> > On Wed, 2 Oct 2019 at 13:32, john whelan  wrote:
>> >>
>> >> On the import mailing list there is a proposal to import postcodes in
>> the UK one of the reasons given was that many like to input a postcode to
>> get directions on smartphones using things like OSMand.
>> >>
>> >> I don't think an Open Data source with the correct licensing is
>> available in Canada but OSMand appears to be able to use the postcode if it
>> is entered in the map as part of the address.  Is there any Open Data that
>> might be useful?
>> >>
>> >> I don't know if it is possible but could something be used to extract
>> postcodes in the current map and from there perhaps we could come up with a
>> list of missing postcodes that need one address with it in mapped?
>> >>
>> >> As a minimum if you could add a few in you know from local knowledge
>> that might help fill in some gaps.
>> >>
>> >> Thoughts
>> >>
>> >> Thanks John
>> >
>> > ___
>> > Talk-ca mailing list
>> > Talk-ca@openstreetmap.org
>> > https://lists.openstreetmap.org/listinfo/talk-ca
>>
>> ___
>> Talk-ca mailing list
>> Talk-ca@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-ca
>>
> ___
> 

Re: [Talk-ca] Postcodes in Canada

2019-10-02 Thread John Whelan
I seem to recall the case was dropped as well. Having sad that I think 
the best way forward is


" The number one request on open.canada.ca  is to 
open the postal code database.  Feel free to add your vote. 
https://open.canada.ca/en/suggested-datasets;


and also add in a building that has a missing postcode.

For example I'm not sure a commitment from the "Stop Climate Change 
Party " to make them Open Data should mean we all vote for this party.  
I think current MPs are too busy with the election at the moment.


Cheerio John


James wrote on 2019-10-02 8:38 PM:

funny you should mention geocoder.ca 

The owner of that website was sued by Canada Post because he was crowd 
sourcing postal codes. Just recently (2 ish years ago?) they dropped 
the lawsuit because they knew they didnt have a case(He came to the 
Ottawa meetups a couple of times)


On Wed., Oct. 2, 2019, 8:08 p.m. Jarek Piórkowski, 
mailto:ja...@piorkowski.ca>> wrote:


Yeah, Canada Post currently considers postal codes their commercial
data. Crowd-sourcing all or a substantial amount of full codes seems
infeasible. Crowd-sourcing the forward sortation areas (the first A1A)
seems difficult since verifiability is going to be a problem
especially around the edges of the areas.

The website OpenStreetMap.org returns results for some postal codes
from a third-party database https://geocoder.ca/?terms=1 which is not
ODbL-compatible either.

Partial mapping is causing some problems with tools like Nominatim
that attach the nearest tagged postcode to search results, often
resulting in improper postal codes for reverse address lookups,
however that is arguably a tooling problem and not an OSM problem per
se.

This isn't going to be pretty until Canada Post is persuaded to free
the data. Call your MP, everybody.

--Jarek

On Wed, 2 Oct 2019 at 17:38, john whelan mailto:jwhelan0...@gmail.com>> wrote:
>
> " The number one request on open.canada.ca
 is to open the postal code database.  Feel
free to add your vote. https://open.canada.ca/en/suggested-datasets;
>
> Cheerio John
>
> On Wed, 2 Oct 2019 at 13:32, john whelan mailto:jwhelan0...@gmail.com>> wrote:
>>
>> On the import mailing list there is a proposal to import
postcodes in the UK one of the reasons given was that many like to
input a postcode to get directions on smartphones using things
like OSMand.
>>
>> I don't think an Open Data source with the correct licensing is
available in Canada but OSMand appears to be able to use the
postcode if it is entered in the map as part of the address.  Is
there any Open Data that might be useful?
>>
>> I don't know if it is possible but could something be used to
extract postcodes in the current map and from there perhaps we
could come up with a list of missing postcodes that need one
address with it in mapped?
>>
>> As a minimum if you could add a few in you know from local
knowledge that might help fill in some gaps.
>>
>> Thoughts
>>
>> Thanks John
>
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org 
> https://lists.openstreetmap.org/listinfo/talk-ca

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



--
Sent from Postbox 
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread ndrw6

On 02/10/2019 13:43, Russ Phillips via Talk-GB wrote:
I'm wondering if it would be feasible and advisable to import the UK 
postcode data from OS OpenData Codepoint 
. 



I support it. From my own experience, requests like this tend to attract 
objections, so it is important for people who agree with such proposals 
to speak out.


The key and, in my opinion, sufficient reasons for importing postcodes:

- Objectively, postcodes are an important type of addressing and 
geocoding data in the UK. We've had two quarterly projects encouraging 
adding postcodes to the OSM database. Some people (including myself) 
don't like the fact the postcodes are proprietary to Royal Mail but we 
are here to map the world, not to judge it.


- They are accepted in the OSM database and there is no tagging 
ambiguity. Their place is _in_ the OSM database, not in external 
overlays. They are searchable in most applications (OsmAnd, Maps.me), 
the exception is Nominatim, which uses an outdated overlay but this is 
more a workaround for lack of such data in the database, than a solution.


- Code-Point Open is a legal and open source of postcode data. In fact 
it is the _only_ legal source of such data in bulk. All other sources 
are either derived from CPO or are based on local knowledge.


All reasons _against_ the import I've seen so far are based on personal 
preferences. People are objecting because they don't like the idea of 
proprietary address data, do not find them important enough, do not find 
them comprehensive enough. These views are useful in establishing the 
context but are not a reason to block the import of what _is_ available.


Talking about technical aspects:

- The key (and deliberate) limitation Code-Point Open is that it doesn't 
distinguish between residential postcodes and postcodes assigned to 
"large users". This is not ideal but still useful - we know the postcode 
exists at a given location, we just can't be sure if it is the only 
postcode there.


- Quality of building in OSM database. Large buildings, especially in 
town centres, are often not partitioned correctly. Different parts may 
have different street names and postcodes. Code-Point Open may in fact 
be helpful in finding and correcting such issues.


- Some postcodes are for PO boxes (usually collocated with post offices) 
are are best left out.


My recommendation: import missing postcodes "as is" (as points) with 
extra tags denoting the import, import date and an accuracy metric from 
CPO. Keep it searchable and easy to remove or update, if necessary. 
Code-Point Open is updated quarterly and sometimes centroids move to 
another building. Filter out PO boxes and postcodes which are already in 
OSM (I usually check if there is an OSM object with a matching 
addr:postcode within a 10m radius of the code point). Do not attempt to 
merge them with buildings as it is not guaranteed to work in all cases. 
This is best done manually and in some cases it may require a survey.


Best regards,

ndrw6



___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [Talk-ca] Postcodes in Canada

2019-10-02 Thread James
funny you should mention geocoder.ca

The owner of that website was sued by Canada Post because he was crowd
sourcing postal codes. Just recently (2 ish years ago?) they dropped the
lawsuit because they knew they didnt have a case(He came to the Ottawa
meetups a couple of times)

On Wed., Oct. 2, 2019, 8:08 p.m. Jarek Piórkowski, 
wrote:

> Yeah, Canada Post currently considers postal codes their commercial
> data. Crowd-sourcing all or a substantial amount of full codes seems
> infeasible. Crowd-sourcing the forward sortation areas (the first A1A)
> seems difficult since verifiability is going to be a problem
> especially around the edges of the areas.
>
> The website OpenStreetMap.org returns results for some postal codes
> from a third-party database https://geocoder.ca/?terms=1 which is not
> ODbL-compatible either.
>
> Partial mapping is causing some problems with tools like Nominatim
> that attach the nearest tagged postcode to search results, often
> resulting in improper postal codes for reverse address lookups,
> however that is arguably a tooling problem and not an OSM problem per
> se.
>
> This isn't going to be pretty until Canada Post is persuaded to free
> the data. Call your MP, everybody.
>
> --Jarek
>
> On Wed, 2 Oct 2019 at 17:38, john whelan  wrote:
> >
> > " The number one request on open.canada.ca is to open the postal code
> database.  Feel free to add your vote.
> https://open.canada.ca/en/suggested-datasets;
> >
> > Cheerio John
> >
> > On Wed, 2 Oct 2019 at 13:32, john whelan  wrote:
> >>
> >> On the import mailing list there is a proposal to import postcodes in
> the UK one of the reasons given was that many like to input a postcode to
> get directions on smartphones using things like OSMand.
> >>
> >> I don't think an Open Data source with the correct licensing is
> available in Canada but OSMand appears to be able to use the postcode if it
> is entered in the map as part of the address.  Is there any Open Data that
> might be useful?
> >>
> >> I don't know if it is possible but could something be used to extract
> postcodes in the current map and from there perhaps we could come up with a
> list of missing postcodes that need one address with it in mapped?
> >>
> >> As a minimum if you could add a few in you know from local knowledge
> that might help fill in some gaps.
> >>
> >> Thoughts
> >>
> >> Thanks John
> >
> > ___
> > Talk-ca mailing list
> > Talk-ca@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-ca
>
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] Postcodes in Canada

2019-10-02 Thread Jarek Piórkowski
Yeah, Canada Post currently considers postal codes their commercial
data. Crowd-sourcing all or a substantial amount of full codes seems
infeasible. Crowd-sourcing the forward sortation areas (the first A1A)
seems difficult since verifiability is going to be a problem
especially around the edges of the areas.

The website OpenStreetMap.org returns results for some postal codes
from a third-party database https://geocoder.ca/?terms=1 which is not
ODbL-compatible either.

Partial mapping is causing some problems with tools like Nominatim
that attach the nearest tagged postcode to search results, often
resulting in improper postal codes for reverse address lookups,
however that is arguably a tooling problem and not an OSM problem per
se.

This isn't going to be pretty until Canada Post is persuaded to free
the data. Call your MP, everybody.

--Jarek

On Wed, 2 Oct 2019 at 17:38, john whelan  wrote:
>
> " The number one request on open.canada.ca is to open the postal code 
> database.  Feel free to add your vote. 
> https://open.canada.ca/en/suggested-datasets;
>
> Cheerio John
>
> On Wed, 2 Oct 2019 at 13:32, john whelan  wrote:
>>
>> On the import mailing list there is a proposal to import postcodes in the UK 
>> one of the reasons given was that many like to input a postcode to get 
>> directions on smartphones using things like OSMand.
>>
>> I don't think an Open Data source with the correct licensing is available in 
>> Canada but OSMand appears to be able to use the postcode if it is entered in 
>> the map as part of the address.  Is there any Open Data that might be useful?
>>
>> I don't know if it is possible but could something be used to extract 
>> postcodes in the current map and from there perhaps we could come up with a 
>> list of missing postcodes that need one address with it in mapped?
>>
>> As a minimum if you could add a few in you know from local knowledge that 
>> might help fill in some gaps.
>>
>> Thoughts
>>
>> Thanks John
>
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca

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


Re: [talk-au] topic A: the platform itself

2019-10-02 Thread Simon Slater
On Friday, 20 September 2019 5:03:10 PM AEST David Wales wrote:
> If the number of talk-au emails reaches overwhelming levels, it might be
> necessary to investigate other solutions. However, I don't think we have
> reached that point yet.
In that case, a digest option is good.  I get a list of posts, any 1 of which, 
or all, can be individually looked at as needed.

-- 
Regards
Simon Slater

Registered Linux User #463789 @ http://linuxcounter.net

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


Re: [Talk-at] Änderung von Bezirks- und Gemeindenamen in Tirol und Vorarlberg

2019-10-02 Thread wambacher

Am 02.10.19 um 21:06 schrieb PPete:
Der Mapper "beautifulplaces", welcher die kürzlichen Änderungen in 
Tirol und Vorarlberg durchgeführt hat, ...


Schon mal auf seine OSM-Seite geschaut? 
https://www.openstreetmap.org/user/beautifulplaces


Gruss

walter
--
My projects:

Admin Boundaries of the World 
Missing Boundaries 


Emergency Map 
Postal Code Map (Germany only) 
Fools (QA for zipcodes in Germany) 
Postcode Boundaries of Germany 
OSM Software Watchlist 

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


Re: [Talk-it] [import] gelatieri e pasticcieri FVG

2019-10-02 Thread Martin Koppenhoefer


sent from a phone

> On 3. Oct 2019, at 00:02, Alessandro P. via Talk-it 
>  wrote:
> 
> Scusate,
> giusto un paio di note:
> - per le pasticcerie non si usa shop=confectionery 
> https://wiki.openstreetmap.org/wiki/IT:Tag:shop%3Dconfectionery ?


io uso shop=pastry
https://wiki.openstreetmap.org/wiki/IT:Tag:shop%3Dpastry

è proprio un tag specifico per le pasticcerie, confectionery è per caramelle e 
altro dolciume...

Ciao Martin 


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


[Talk-us] Whole-US Garmin Map update - 2019-09-25

2019-10-02 Thread Dave Hansen
These are based off of Lambertus's work here:

http://garmin.openstreetmap.nl

If you have questions or comments about these maps, please feel
free to ask.  However, please do not send me private mail.  The
odds are, someone else will have the same questions, and by
asking on the talk-us@ list, others can benefit.

Downloads:

http://daveh.dev.openstreetmap.org/garmin/Lambertus/2019-09-25

Map to visualize what each file contains:


http://daveh.dev.openstreetmap.org/garmin/Lambertus/2019-09-25/kml/kml.html


FAQ



Why did you do this?

I wrote scripts to joined them myself to lessen the impact
of doing a large join on Lambertus's server.  I've also
cut them in large longitude swaths that should fit conveniently
on removable media.  

http://daveh.dev.openstreetmap.org/garmin/Lambertus/2019-09-25

Can or should I seed the torrents?

Yes!!  If you use the .torrent files, please seed.  That web
server is in the UK, and it helps to have some peers on this
side of the Atlantic.

Why is my map missing small rectangular areas?

There have been some missing tiles from Lambertus's map (the
red rectangles),  I don't see any at the moment, so you may
want to update if you had issues with the last set.

Why can I not copy the large files to my new SD card?

If you buy a new card (especially SDHC), some are FAT16 from
the factory.  I had to reformat it to let me create a >2GB
file.

Does your map cover Mexico/Canada?

Yes!!  I have, for the purposes of this map, annexed Ontario
in to the USA.  Some areas of North America that are close
to the US also just happen to get pulled in to these maps.
This might not happen forever, and if you would like your
non-US area to get included, let me know. 

-- Dave


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


[talk-au] Discussion I: Consultation ends and OSM Wiki starts

2019-10-02 Thread Herbert.Remi via Talk-au
# Discussion I: Consultation ends and OSM Wiki starts

Thanks for your support and assistance with the ACT OSM mapping project.
The consultation phase ends now and I will take your comments and consolidate 
the information into OSM Wiki pages in the ACT section.
I expect it will be an overview page and links to subpages for each topic. It 
is better on the smartphone screen in this way as there is not too much text 
per page.
Once the ACT OSM Wiki page is updated, it will be open for your comments again.
This could take about a month.
I will put a short note in this forum when the ACT OSM page has been updated.

Keywords: Australia, ACT, OSM Wiki___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [Talk-it] [import] gelatieri e pasticcieri FVG

2019-10-02 Thread Alessandro P. via Talk-it

Il 02/10/19 10:44, Cascafico Giovanni ha scritto:

Ciao Lista,

ho abbozzato una wiki [1] in inglese per l'import regione Friuli
Venezia Giulia del dataset Confartigianato delle attività economiche.
Commentate pure alla sezione discussione [2] per strafalcioni,
chiarimenti, suggerimenti.

I dettagli sono ancora in sviluppo. Se il pilota gelatieri e
pasticceri va bene, proseguirò con le altre attività.

Scusate,
giusto un paio di note:
- per le pasticcerie non si usa shop=confectionery 
https://wiki.openstreetmap.org/wiki/IT:Tag:shop%3Dconfectionery ?


- i numeri civici quando non hanno esponente numerico (come nell'esempio 
28/B) perchè mettere il carattere / in mezzo?


Alessandro

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


Re: [Talk-ca] Postcodes in Canada

2019-10-02 Thread john whelan
" The number one request on open.canada.ca is to open the postal code
database.  Feel free to add your vote.
https://open.canada.ca/en/suggested-datasets;

Cheerio John

On Wed, 2 Oct 2019 at 13:32, john whelan  wrote:

> On the import mailing list there is a proposal to import postcodes in the
> UK one of the reasons given was that many like to input a postcode to get
> directions on smartphones using things like OSMand.
>
> I don't think an Open Data source with the correct licensing is available
> in Canada but OSMand appears to be able to use the postcode if it is
> entered in the map as part of the address.  Is there any Open Data that
> might be useful?
>
> I don't know if it is possible but could something be used to extract
> postcodes in the current map and from there perhaps we could come up with a
> list of missing postcodes that need one address with it in mapped?
>
> As a minimum if you could add a few in you know from local knowledge that
> might help fill in some gaps.
>
> Thoughts
>
> Thanks John
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [OSM-talk-fr] Moulinette pour convertir codes Insee en GPS > GPX ?

2019-10-02 Thread Christian Quest
api-adresse.data.gouv.fr est fait pour géocoder des adresses, pas des noms
de ville avec leur code INSEE, ça c'est le boulot de geo.api.gouv.fr

Du coup, oui, 3190 moulins, ça peut être plein de choses...


Le mer. 2 oct. 2019 à 19:17, Shohreh  a écrit :

> Samy Mezani wrote
> > L'API est faite pour automatiser tout ça :
> >
> > https://geo.api.gouv.fr/adresse (descendre à /search/csv/)
>
> Merci beaucoup.
>
> Si d'autres cherchent à faire la même chose :
> 1. (nécessaire?) Convertir les données entrée en UTF8
> 2. Downloader curl.exe dans le même répertoire
> 3. curl --insecure -o output.csv -X POST -F data=@input.csv -F
> citycode=NOMCOLONNECODEINSEE https://api-adresse.data.gouv.fr/search/csv/
>
> Bizarrement, il y a des villes que le serveur n'a pas réussi à géocoder
> (lat,lon vides):
>
> 3190Moulins
> 44090   La Marne
> 77083   Champs-sur-Marne
> 88212   Grand
> 92072   Sèvres
> 93039   L'Île-Saint-Denis
> 93066   Saint-Denis
>
>
>
> --
> Sent from: http://gis.19327.n8.nabble.com/France-f5380434.html
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>


-- 
Christian Quest - OpenStreetMap France
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-GB] OSM UK volunteers required

2019-10-02 Thread Rob Nickerson
Hi Edward,

Sorry for the slow reply, you caught me at a busy time.

I think 2 and 3 are quite similar. Perhaps you could argue that 3 is more
focused on non public sector. Maybe we get improved content on our website
and  some leaflets ready (if needed) and then start sharing that content.
It might also include building our contacts so that we can answer more of
the questions we may receive.

The lobby element in 3 is possibly more focused on public sector. We've
made a start over the last year by responding to the government's
Geospatial Commission. Next steps would be to keep an eye out for similar
consultation opportunities whilst also looking for other avenues to do
direct promotion of OSM.

In any case across 2 and 3 we want to consider both public and private
sector - we'd like OSM to be embedded within all sectors.

As for 1, we've put out a call for ideas on the loomio group. Next step is
to see what contacts we have and start approaching them. I think it will be
easier if we have existing relationships but if not then we should try from
scratch.

So in summary it's quite an open scope. Ideas and suggestions welcome and
let's take it forward from there.

I'd be happy to take more questions on email or arrange a quick chat /
call. Let me know what works for you.

Best regards,
Rob

On Thu, 26 Sep 2019, 09:09 Edward Bainton,  wrote:

> Thank you, I think I could do a bit on 1, 2, and/or 3.
>
> 1, 3. Do you have brief case studies you could share as examples of what
> you're looking for?
>
> 2. Could you clarify what a 'lobby group' would lobby for?
>
> Thanks and best wishes
>
> Edward
>
>
>
> On Wed, 25 Sep 2019 at 22:33, Rob Nickerson 
> wrote:
>
>> Hi,
>>
>> Last month OSM UK (the non-profit community interest company) set out
>> it's strategy areas for the 2019/20 year. We have made a start on these but
>> a bit more volunteer time will allow us to speed them up.
>>
>> If you could volunteer some time for any of the following, please let me
>> know. Each requires some initial planning before implementing solutions.
>> Help at either stage is appreciated.
>>
>>1. Use the quarterly projects to partner with another organisation to
>>leverage their membership/supporters.
>>2. Pursue a role as a lobby group. That is, getting OSM on the radar
>>of large organisations.
>>3. Proactive outreach to businesses, organisations and academia to
>>show them a front door to using and contributing to OSM.
>>4. Enhance / nurture the Talent Directory.
>>5. Help shape tagging guidelines.
>>6. Develop guidelines to work out when OSM UK should and should not
>>support a mechanical edit / data import.
>>7. A micro-grant programme to support those who want to help us grow
>>the community via talks, workshops, etc.
>>8. Focus on map fixes (e.g. a quarterly project on Notes, Fixmes).
>>9. Assist with conflating TfL Cycle Infrastructure Data into OSM
>>
>> Thank you,
>> *Rob*
>> ___
>> Talk-GB mailing list
>> Talk-GB@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-gb
>>
>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [OSM-talk-fr] Nouvelle API du géocodeur et communes nouvelles

2019-10-02 Thread Christian Quest
Le but de cette demo est surtout de trouver un lieu et de le montrer
ensuite sur la carte, la présentation de ce qui ressemble à une adresse est
très accessoire ;)
C'est le mix adresses + POI qui n'est pas évident, ainsi que la volumétrie
globale:
- 16.4 millions d'adresses BANO
- 4 millions de lieux-dits BANO
- 2.8 millions de POI OSM
- 68000 geonames

BANO n'est pas totalement à jour sur les fusions de communes, c'est pour
cela que ce n'est pas forcément bien raccord.

Pour les codes postaux infra-communaux, on peut les cartographier dans OSM
(boundary=postal_code si ma mémoire est bonne), les scripts de BANO en
tiennent compte. C'est utilisé par exemple sur 75016/75116 ou 94100/94210.

Pour les communes nouvelles, il faut peut être revoir quelques trucs...

Et puis... La Poste ? Elle nous casse les pieds, qu'elle continue comme ça
et le courrier se réduira encore plus vite vers le zéro.
Ses bases contiennent les anciens noms de commune et peuvent très bien y
distribuer le courrier si elle en a envie (ce qui est à se demander).


Le mer. 2 oct. 2019 à 12:12, Rpnpif  a écrit :

> Bonjour,
>
> Merci à Christian pour la nouvelle API de consultation du géocodeur de
> http://demo.addok.xyhz/.
>
> Elle est très agréable à utiliser.
>
> Je voudrais attirer l'attention sur un problème lié aux communes
> nouvelles (encore un).
>
> Quand on recherche un lieu sur http://demo.addok.xyhz/ (mais c'est
> pareil sur Nominatim), la présentation de l'adresse est incomplète.
>
> Exemple spécifique à la France :
> La Poste demande que les adresses soient présentées sous la forme :
> La Rousserie (lieu-dit)
> Le Louroux-Béconnais (ancienne commune)
> 49370 Val-d'Erdre-Auxence (nouvelle commune)
>
> Elle tolère si le lieu-dit est unique sur la nouvelle commune (pas
> d’ambiguïté) :
> La Rousserie (lieu-dit)
> 49370 Val-d'Erdre-Auxence (nouvelle commune)
>
> Mais http://demo.addok.xyhz/ présente ainsi :
> La Rousserie (lieu-dit)
> 49370 Le Louroux-Béconnais (ancienne commune)
> Il manque l'info de la nouvelle commune.
>
> Là où ça se complique, c'est quand la nouvelle commune a plusieurs codes
> postaux.
> Par exemple Erdre-en-Anjou comporte des communes avec le code 49220 et une
> avec 49370.
>
> Comme ces codes sont basés en général sur les anciennes communes, on peut
> se baser sur cela pour le mettre devant le nom de la nouvelle pour un lieu
> déterminé.
>
> Par contre, il y a des communes et de nombreuses villes où le code postal
> est zoné par quartier ou rue ou partie de rue.
> Dans ce dernier cas, ne serait-il pas possible de créer des aires
> spécifiques pour l'attribut de code postal comme on les cantons ou autres à
> parir des données fournis par la Poste ?
>
> En résumé c'était deux questions : la présentation de l'adresse et le
> zonage du code postal.
>
> --
> Alain Rpnpif
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>


-- 
Christian Quest - OpenStreetMap France
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [talk-au] Discussion H: public transport – the end game

2019-10-02 Thread David Wales
This is a good point.

Is there a moderator who could check if something like this is the case?

Regards,
David

On 2 October 2019 10:46:00 pm AEST, Mateusz Konieczny  
wrote:
>
>
>2 Oct 2019, 09:19 by e...@mapillary.com:
>
>> For the health of the mailing list, it would make sense to limit his
>communications so we're not bombarded daily with his emails.
>>
>Volume is not the biggest problem -
>and it would be probably acceptable.
>
>For me main problem is "fire and forget"
>mode.
>
>Is he even reading replies?
>
>Maybe he is unable to respond because
>he had monthly digest or something
>similarly problematic?
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [Talk-us] Talk-us Digest, Vol 143, Issue 2

2019-10-02 Thread stevea
As I mentioned yesterday, I changed Case #3 from leisure=park to 
leisure=nature_reserve.  Your text describes it as being tagged leisure=park, 
which is no longer correct.

Steve

> On Oct 2, 2019, at 4:00 AM, talk-us-requ...@openstreetmap.org wrote:
> 
> http://www.remote.org/frederik/tmp/case3.png


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


Re: [OSM-talk-fr] Nouvelle API du géocodeur et communes nouvelles (code postal)

2019-10-02 Thread osm . sanspourriel

Le 02/10/2019 à 19:50, Rpnpif - rpn...@trob.eu a écrit :


Ah je ne connaissais pas boundary=postal_code. Merci beaucoup.

Donc ce serait bien de l'utiliser avec la commune nouvelle dans l'API
du géocodeur.


En général postal_code=xxx sur les admin de niveau 9 (les anciennes
communes) doit suffire.

Rien n'interdit à plusieurs communes de partager le même postal_code.

boundary=postal_code a sans doute des usages logiques en France, styles
secteurs ne correspondant pas à des limites administratives (y compris
regroupées) mais pas par chez moi. Quelques fois ça frise le ridicule
(un coin de ZI desservi par au moins deux facteurs : 40 rue des Lilas à
la fois à Chantepie et à Cesson-Sévigné).

Si on peut reposer sur des boundary=admin, ça évite de créer de
nouvelles relations trop faciles à casser (car peu utilisées).

Jean-Yvon

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


Re: [OSM-talk-fr] Nouvelle API du géocodeur et communes nouvelles (code postal)

2019-10-02 Thread Rpnpif
Le  2 octobre 2019, osm.sanspourr...@spamgourmet.com a écrit :

> Le 02/10/2019 à 12:10, Rpnpif - rpn...@trob.eu a écrit :
> > Bonjour,
> >
> > Merci à Christian pour la nouvelle API de consultation du géocodeur de
> > http://demo.addok.xyhz/.  
> 
> Il n'y pas un h en trop que tu as oublié de fumer ? ;-)

Oups oui, d'où vient ce h parasite ?
http://demo.addok.xyz/ c'est mieux.


> > En résumé c'était deux questions : la présentation de l'adresse et le 
> > zonage du code postal.  
> 
> Pour le zonage du code postal on a déjà ce qu'il faut:
> 
> Key:postal code
> 
> 
> boundary =postal_code
>  on a
> way or on a *relation* (a relation would also have type
> =boundary
> )
> 
> Tu peux aussi utiliser les boundary=admin avec postal_code.
> 
> Je dis bien postal_code, pas postcode qui est réservé aux adresses.

Ah je ne connaissais pas boundary=postal_code. Merci beaucoup.

Donc ce serait bien de l'utiliser avec la commune nouvelle dans l'API
du géocodeur.

-- 
Alain Rpnpif

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


[Talk-ca] Postcodes in Canada

2019-10-02 Thread john whelan
On the import mailing list there is a proposal to import postcodes in the
UK one of the reasons given was that many like to input a postcode to get
directions on smartphones using things like OSMand.

I don't think an Open Data source with the correct licensing is available
in Canada but OSMand appears to be able to use the postcode if it is
entered in the map as part of the address.  Is there any Open Data that
might be useful?

I don't know if it is possible but could something be used to extract
postcodes in the current map and from there perhaps we could come up with a
list of missing postcodes that need one address with it in mapped?

As a minimum if you could add a few in you know from local knowledge that
might help fill in some gaps.

Thoughts

Thanks John
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


[OSM-talk-fr] Tr: Demande de proposition de prestation pour création de carte

2019-10-02 Thread Adrien André via Talk-fr

Bonjour,

je fais suivre cette demande pour création de carte.

La limite de réponse est le 10 octobre 2019 à 12h.

Document joint : 
https://framadrop.org/r/Pgf5uuKoTj#eQiFVGj1UWQTpCI9KZr5Z1SC0/srprQ/K1r1x8u2S0k=


Cordialement,


 Message transféré 
Sujet : 	Demande de proposition de la prestation "Carte avec les points 
d'intérêt des établissements de santé et médico-sociaux de la zone 
transfrontalière de l’Oyapock" pour l'ARS de Guyane

Date :  Fri, 20 Sep 2019 11:50:31 +
De :VAN GASTEL, Benoît (ARS-GUYANE) 
Pour :  VAN GASTEL, Benoît (ARS-GUYANE) 
Copie à :   DUPLAN, Hélène (ARS-GUYANE) 



Bonjour,

Pour faire suite à nos différents échanges, je vous remercie de nous 
transmettre une proposition (devis ou convention) pour la prestation 
décrite ci-dessous pour pouvoir procéder à la sélection du prestataire 
pour une réalisation de la prestation avant fin novembre 2019.


Vous trouverez en pièce jointe un exemple « amateur » de carte et une 
requête de travail sur les données dans OpenStreetMap : 
http://overpass-turbo.eu/s/Mpp


Je reste à votre disposition pour tout renseignement complémentaire.

Cordialement.

http://arsgup973.sd.intranet.sante.gouv.fr/signature/imgs_signature/ars_guyane.jpeg 





*Benoît Van Gastel*
Ingénieur Sanitaire, MPH

Chargé de mission Santé Publique et Santé Environnement et de la 
coopération en santé avec le Brésil - Gerente de Projetos em Saúde 
Pública e Saúde Ambiental e Responsável pela cooperação em saúde com o 
Brasil - Public Health & Environmental Health Projects and Health 
Cooperation with Brazil


Tél : +594(0)5 94 25 72 82 - GSM : +594(0)6 94 27 50 07
Courriel : benoit.vangas...@ars.sante.fr 
 
@ars.sante.fr 



http://arsgup973.sd.intranet.sante.gouv.fr/signature/imgs_signature/territoire.jpeg
*ARS de Guyane*
66, avenue des Flamboyants - C.S 40696 - 97336 Cayenne Cedex - Fax : 
benoit.vangas...@ars.sante.fr 

www.ars.guyane.sante.fr 

*Description de la prestation :*

Carte avec les points d'intérêt pour présenter les emplacements et les 
informations de base (nom, type et gestionnaire) des établissements de 
santé et médico-sociaux de la zone transfrontalière de l’Oyapock entre 
la Guyane française et l’Amapá (Brésil).


*Le projet :*

1.Un fonds de carte avec légende à créer, par exemple avec comme source 
de données OpenStreetMap (https://www.openstreetmap.org) avec une 
emprise générale de la carte qui devra comprendre, au plus près, 
l’intégralité des communes de Régina, Ouanary, Saint Georges de 
l’Oyapock, Camopi et Oiapoque ;


2.En encart des zooms sur les bourgs des communes à une échelle adaptée ;

3.Les informations classiques sur les cartes (titre, échelle, légende, 
nord, date, sources…) ;


4.Des points d’intérêt qui seront fournis par l’ARS sous forme de « 
fichiers de formes » avec les données de localisation conforme à 
OpenStreetMap et les informations de base (nom, type et gestionnaire) 
des établissements de santé et médico-sociaux validées par l’ARS et les 
gestionnaires d’établissement ;


5.Des volets sur les bords de la carte qui permettront de présenter les 
informations de base (nom, type et gestionnaire) des points d’intérêt ;


6.Les logos des partenaires qui seront fournis par l’ARS.

Les livrables :

1.Fichiers pdf et jpg sous licence libre ou libre de droit de la carte 
*/avec/* les points d'intérêt pour l’édition d’une carte pour une 
publication haute résolution grand format (par exemple A1, 59,4 x 84,1 
cm) pour un affichage mural dans les établissements à l’attention du 
public et des professionnels ;


2.Fichiers pdf et jpg de la carte */sans/* les points d'intérêt avec les 
mêmes caractéristiques de résolution que le livrable 1.




Les ministères sociaux agissent pour un développement durable.

Préservons l'environnement : n'imprimons que si nécessaire !

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


Re: [OSM-talk-fr] Moulinette pour convertir codes Insee en GPS > GPX ?

2019-10-02 Thread Shohreh
Samy Mezani wrote
> L'API est faite pour automatiser tout ça :
> 
> https://geo.api.gouv.fr/adresse (descendre à /search/csv/)

Merci beaucoup.

Si d'autres cherchent à faire la même chose :
1. (nécessaire?) Convertir les données entrée en UTF8
2. Downloader curl.exe dans le même répertoire
3. curl --insecure -o output.csv -X POST -F data=@input.csv -F
citycode=NOMCOLONNECODEINSEE https://api-adresse.data.gouv.fr/search/csv/

Bizarrement, il y a des villes que le serveur n'a pas réussi à géocoder
(lat,lon vides):

3190Moulins
44090   La Marne
77083   Champs-sur-Marne
88212   Grand
92072   Sèvres
93039   L'Île-Saint-Denis
93066   Saint-Denis



--
Sent from: http://gis.19327.n8.nabble.com/France-f5380434.html

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


Re: [OSM-talk-fr] Nouvelle API du géocodeur et communes nouvelles (code postal)

2019-10-02 Thread osm . sanspourriel

Le 02/10/2019 à 12:10, Rpnpif - rpn...@trob.eu a écrit :

Bonjour,

Merci à Christian pour la nouvelle API de consultation du géocodeur de
http://demo.addok.xyhz/.


Il n'y pas un h en trop que tu as oublié de fumer ? ;-)

(...)


En résumé c'était deux questions : la présentation de l'adresse et le zonage du 
code postal.


Pour le zonage du code postal on a déjà ce qu'il faut:

Key:postal code


boundary =postal_code
 on a
way or on a *relation* (a relation would also have type
=boundary
)

Tu peux aussi utiliser les boundary=admin avec postal_code.

Je dis bien postal_code, pas postcode qui est réservé aux adresses.

Jean-Yvon

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


Re: [Talk-ca] Local mapathon, BC2020 imports and Climate resiliency challenge

2019-10-02 Thread Jonathan Brown
I’ll meet with Kelsey and try to get to an OSM Toronto Meetup to see how Nate 
and others end up doing it in Toronto. Maybe Kelsey and I can do adapt that 
experience for Northumberland County. We have a local group interested in bike 
trails that I can approach.  

I’m also interested in the HOT pilot “Integrating Machine Learning into the 
Tasking Manager: Notes on a Direction” 
https://www.hotosm.org/updates/integrating-machine-learning-into-the-tasking-manager/.
 I learned about this work at the session on “Assisted Intelligence - How 
humans map with the support of new technologies” that Felix (HOT) and Surabhi 
(Microsoft) presented at State of the Map in Heidelberg.

In the long run, I could see organizing a hackathon using the OSM building 
footprints and linked open data to design a climate resiliency planning 
challenge at the local level. (See example based on Open City Model: 
http://www.buildzero.org/).

Jonathan  
From: john whelan
Sent: Wednesday, October 2, 2019 12:13 PM
To: Jonathan Brown
Cc: talk-ca@openstreetmap.org; kelseysaunder...@gmail.com 

Subject: Re: [Talk-ca] Importing building and routing info 
regionally/locally(Jonathan)

I was under the impression that most buildings in both Port Hope and Cobourg 
had been manually mapped.

Now the outlines have been done it really needs boots on the ground to add 
detail.  There are addresses from Canvec which give an address range so Stats 
might have something better but I'm not sure.

What exactly are you looking for?  I'm sure if you and Kelsey were to sit down 
over a mug of coffee as the local mappers to the area you may decide that a 
buildings import would be useful but I'm not sure how many more buildings 
remain to be mapped in the area.  

Cheerio John

On Wed, 2 Oct 2019 at 06:10, Jonathan Brown  wrote:
Ditto Kevin’s post. Erik, I live in Cobourg and have an interest in working 
with local mappers to map Northumberland County. At the moment we only have one 
novice (myself) and Kelsey Saunders, a GIS grad. 
 
Jonathan 
 

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

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


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread Russ Phillips via Talk-GB
I didn't even know there was an OsmAnd forum ;) I'll go look for it, thanks.

Russ

⁣Get BlueMail for Android ​

On 2 Oct 2019, 16:47, at 16:47, Nick Allen  wrote:
>Hi Russ,
>
>Somewhere in tbe Osmand forum you should find a link for a postcode
>player
>you can download & use. I think it was Harry, one of the main people
>answering queries who produced it.
>
>Regards
>
>Nick
>my phone is responsible for any spelling mistakes!
>
>On Wed, 2 Oct 2019, 17:12 Russ Phillips via Talk-GB, <
>talk-gb@openstreetmap.org> wrote:
>
>> OsmAnd is what made me think of it. I'm using that for directions a
>lot
>> now, and it's common these days to give a postcode to plug into a sat
>nav,
>> but they frequently don't work in OsmAnd.
>>
>> I was somewhat surprised that it hadn't already been done, and I
>accept
>> all the reasons for not doing it.
>>
>> I'll look into alternatives.
>>
>> Russ
>>
>>
>> On 02/10/2019 15:52, SK53 wrote:
>>
>> I really see no point. The data are already present in Nominatim
>(albeit
>> perhaps not up-to-date) and search is the ONLY thing that so-called
>> postcode centroids can help with. DE24 (Sinfin) was imported long
>ago, see
>> this overpass query .
>>
>> What can be done is attempt to assign postcodes to streets, and
>various
>> incomplete efforts have been made over the years. Open Data provides
>full
>> addresses for around 70% of UK postcodes (principally Companies
>House, Food
>> Hygiene & National Register of Social Housing).
>>
>> What would be useful is a maintained set of postcode information
>based on
>> codepoint open/ONS postcode data/OS Local. The sorts of things which
>it
>> would be useful to know are:
>>
>>- Is the postcode centroid co-located with others (e.g., delivery
>>offices, some businesses, blocks of flats)
>>- Can the postcode be unambiguously assigned to a street & post
>town?
>>- Is the post code in use or not (ONS is now obviously 8 years
>old,
>>but still potentially useful). Greg's FHRS tracker does appear to
>indicate
>>a degree of churn with inner-city postcodes (although some of this
>will be
>>inadvertent use of more general rather than specific postcodes by
>people
>>filling in the FHRS forms)
>>- Is a postcode the sole postcode for that street?
>>
>> Somewhere I have an old CPO table with some of this data populated. I
>> think Geolytix had summary info associated with their post code
>sector
>> shape files as well.
>>
>> Adding addr:postcode to streets which have a single postcode is in my
>book
>> fine: numerous LAs put this on street signs (Rushcliffe & Gedling for
>> sure); it's an intermediate step to adding the addresses to houses
>Once
>> the postcodes which obviously belong to a single street are
>eliminated it's
>> often easier to work out where the others belong.
>>
>> Note that other than for FHRS we have no good source for Northern
>Ireland
>> postcodes at all. Equally assignment of rural postcodes is quite a
>bit
>> harder than urban ones. In re-reading bits of Chris's blog last night
>I
>> came across a post of his
>>  showing
>that
>> some postcodes move huge distances between releases.
>>
>> Jerry
>>
>> PS. The Sinfin postcodes possibly should be removed as they were
>added
>> IIRC before Mike Collinson's discussions with OSGB about OS Open
>Data.
>>
>> On Wed, 2 Oct 2019 at 13:44, Russ Phillips via Talk-GB <
>> talk-gb@openstreetmap.org> wrote:
>>
>>> Hi,
>>>
>>> I'm wondering if it would be feasible and advisable to import the UK
>>> postcode data from OS OpenData Codepoint
>>>
>
>>> .
>>>
>>> The licence is OSM compatible. My thinking was that we could create
>a
>>> node for each data point and set the addr:postcode tag. This would
>be
>>> useful for routing software like OsmAnd, since it would allow a user
>to
>>> enter a postcode as a destination.
>>>
>>> I'm happy to do the work, but the import guidelines
>>>  say that
>imports
>>> should be discussed on the imports@ list and the appropriate local
>>> communities, hence this email.
>>>
>>> Russ Phillips
>>>
>>>
>>> ___
>>> Talk-GB mailing list
>>> Talk-GB@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-gb
>>>
>> ___
>> Talk-GB mailing list
>> Talk-GB@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-gb
>>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [OSM-talk-fr] Moulinette pour convertir codes Insee en GPS > GPX ?

2019-10-02 Thread ades
Il y a aussi ça : https://www.data.gouv.fr/fr/datasets/admin-express/ 

ça remplace geofla, et il y a les coordonnées de toutes les communes,  x et y 
dans le système officiel, le  Rgf93. C’est du .shp donc utilisable par beaucoup 
de soft.
Le seul blême, c’est qu’en partant de 
https://www.data.gouv.fr/fr/datasets/admin-express/ 
 je n’arrive pas à 
télécharger. Ça m’avait fait le même coup avec la BDTopo hydrographie, pas 
moyen de DL la dernière édition, font p’tet exprès ?


> Le 2 oct. 2019 à 17:39, osm.sanspourr...@spamgourmet.com a écrit :
> 
> 
> Le 02/10/2019 à 17:20, Vincent Bergeot - vinc...@bergeot.org 
>  a écrit :
>> ceci : https://adresse.data.gouv.fr/csv  
>> 
>> si j'ai bien compris. 
>> 
> Si tu n'as pas bien compris ça marche aussi ;-).
> 
> Ne pas oublier de mettre une entête, par exemple 
> insee;col1;col2;col3;col4;col5
> 
> De sélectionner la colonne INSEE et de décoder en UTF-8.
> 
> Tu récupères latitude et longitude.
> 
> Après inutile de faire un GPX, Umap ou Leaflet savent lire de tels CSV.
> 
> Jean-Yvon
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr


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


Re: [Talk-it] [import] gelatieri e pasticcieri FVG

2019-10-02 Thread Damjan Gerl

Cascafico Giovanni je 2.10.2019 ob 10:44 napisal:

Ciao Lista,

ho abbozzato una wiki [1] in inglese per l'import regione Friuli
Venezia Giulia del dataset Confartigianato delle attività economiche.
Commentate pure alla sezione discussione [2] per strafalcioni,
chiarimenti, suggerimenti.

I dettagli sono ancora in sviluppo. Se il pilota gelatieri e
pasticceri va bene, proseguirò con le altre attività.




[1] https://wiki.openstreetmap.org/wiki/Import/Catalogue/AlimentareFVG
[2] https://wiki.openstreetmap.org/wiki/Talk:Import/Catalogue/AlimentareFVG


Direi molto bene. Procediamo con le gelaterie e vediamo cosa succede...

Ciao
e grazie
Damjan



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


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread Dave F via Talk-GB
I think this is a Win/JOSM problem - After pasting the URL If I move the 
cursor using the arrow keys the TMS URL is created.


Thanks
DaveF

On 02/10/2019 17:19, Chris Hill wrote:
Thanks for reporting a problem - I'll always try to respond if I can. 
The installation process has changed in the past but it looks familiar 
now.


I've just tested the installation instructions on JOSM version 15390 
and it worked as expected. The Okay button enabled when the URL (with 
https) and a name for the layer are both input, a max zoom can be 
added too.


I tried this on Mac OS and Linux and both worked. I don't have an easy 
access to Windows, but Java stuff should be cross platform I think.


You can use HTTP or HTTPS for the overlay as both are provided, I just 
think it's better to use HTTPS whenever possible.





___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread Chris Hill
Thanks for reporting a problem - I'll always try to respond if I can. 
The installation process has changed in the past but it looks familiar now.


I've just tested the installation instructions on JOSM version 15390 and 
it worked as expected. The Okay button enabled when the URL (with https) 
and a name for the layer are both input, a max zoom can be added too.


I tried this on Mac OS and Linux and both worked. I don't have an easy 
access to Windows, but Java stuff should be cross platform I think.


You can use HTTP or HTTPS for the overlay as both are provided, I just 
think it's better to use HTTPS whenever possible.


--
cheers
Chris Hill (chillly)


On 02/10/2019 16:55, Dave F wrote:
FYI in JOSM (latest) https wont generate a TMS URL. I had to change 
the pasted URL to http & then back again. then it generated & 
'ungreyed' the Okay button. Is this expected behaviour?


On 02/10/2019 15:37, Chris Hill wrote:

Thanks,

I've just updated with August 2019 data, the next update is due in 
November I think.







___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [Talk-ca] Importing building and routing info regionally/locally (Jonathan)

2019-10-02 Thread john whelan
I was under the impression that most buildings in both Port Hope and
Cobourg had been manually mapped.

Now the outlines have been done it really needs boots on the ground to add
detail.  There are addresses from Canvec which give an address range so
Stats might have something better but I'm not sure.

What exactly are you looking for?  I'm sure if you and Kelsey were to sit
down over a mug of coffee as the local mappers to the area you may decide
that a buildings import would be useful but I'm not sure how many more
buildings remain to be mapped in the area.

Cheerio John

On Wed, 2 Oct 2019 at 06:10, Jonathan Brown  wrote:

> Ditto Kevin’s post. Erik, I live in Cobourg and have an interest in
> working with local mappers to map Northumberland County. At the moment we
> only have one novice (myself) and Kelsey Saunders, a GIS grad.
>
>
>
> Jonathan
>
>
>
>
>
>
>
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [OSM-ja] 自動車専用の道路のタグ付け

2019-10-02 Thread info
Ras and Roadです。自分へのリプライです。

通行規制を地図に表現しようとしているわけですから、如何に複雑な通行規制であっても
現場の道路標識の意味を正確に理解しなければいけないことに気付きました。
道路標識の解釈に自信がないなら、その旨を note=* か fixme=* で記述すべきですね。

** Ras and Road **
___
Talk-ja mailing list
Talk-ja@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ja


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread Dave F via Talk-GB
FYI in JOSM (latest) https wont generate a TMS URL. I had to change the 
pasted URL to http & then back again. then it generated & 'ungreyed' the 
Okay button. Is this expected behaviour?


On 02/10/2019 15:37, Chris Hill wrote:

Thanks,

I've just updated with August 2019 data, the next update is due in 
November I think.




___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [OSM-talk-fr] Moulinette pour convertir codes Insee en GPS > GPX ?

2019-10-02 Thread Samy Mezani

Bonjour,

Le 02/10/2019 à 17:39, osm.sanspourr...@spamgourmet.com a écrit :


Le 02/10/2019 à 17:20, Vincent Bergeot - vinc...@bergeot.org a écrit :

ceci : https://adresse.data.gouv.fr/csv

si j'ai bien compris.


Si tu n'as pas bien compris ça marche aussi ;-).

Ne pas oublier de mettre une entête, par exemple

insee;col1;col2;col3;col4;col5

De sélectionner la colonne INSEE et de décoder en UTF-8.

Tu récupères latitude et longitude.



L'API est faite pour automatiser tout ça :

https://geo.api.gouv.fr/adresse (descendre à /search/csv/)

Samy

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


Re: [OSM-ja] 自動車専用の道路のタグ付け

2019-10-02 Thread info
Ras and Roadです。

xyzxyz2さん認識の通り、小田原箱根道路は自動車専用道路ではありません。
自動車専用道路の規制標識もありません。よって125cc以下の二輪も通行可能です。

風祭交差点付近の規制標識「車両通行止め(302)」は西湘バイパスに対する規制です。
規制標識「二輪車二人乗り通行禁止(310の2)」が並掲されているので、
自動車専用道路に対する規制であることがわかります。

Googleストリートビューを見ると、箱根口IC交差点付近、小田原箱根道路下り線接続路に
125cc以下の二輪車通行禁止の旨の黄色い立て看板(横浜国道事務所と小田原署の連名)
がありますが、これは法定標識でないので公安委員会は指定していないことがわかります。
通ってほしくないという意味でしょう。

・・・という具合に、道路標識の意味を深く理解しないとマッピングを誤りかねないのは
どうしたものか。道路行政に改善の余地があるのは事実ですが、我々の手が届くものでなし。

** Ras and Road **
___
Talk-ja mailing list
Talk-ja@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ja


Re: [OSM-talk-fr] Moulinette pour convertir codes Insee en GPS > GPX ?

2019-10-02 Thread osm . sanspourriel


Le 02/10/2019 à 17:20, Vincent Bergeot - vinc...@bergeot.org a écrit :

ceci : https://adresse.data.gouv.fr/csv

si j'ai bien compris.


Si tu n'as pas bien compris ça marche aussi ;-).

Ne pas oublier de mettre une entête, par exemple

insee;col1;col2;col3;col4;col5

De sélectionner la colonne INSEE et de décoder en UTF-8.

Tu récupères latitude et longitude.

Après inutile de faire un GPX, Umap ou Leaflet savent lire de tels CSV.

Jean-Yvon

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


Re: [OSM-talk-fr] adresses sur tronc d'arbres

2019-10-02 Thread osm . sanspourriel

Ca ne semble pas être des bornes kilométriques comme semble le penser David.

Vu que c'est référencé sur le parcours et par ordre, je ne pense pas non
plus que ce soit des numéros de parcelles.

Mais plutôt des repères propres au parcours.

ref= me semble correct, après il te reste à relier ces points
dans un route=fitness_trail
.

Jean-Yvon

Le 02/10/2019 à 15:44, David Crochet - david.croc...@free.fr a écrit :

Bonjour

Ce sont soit des numéros de parcelles dont les arbres des coins
desdites parcelles comportent ledit numéros, ou alors si cela se
trouvent sur un prarcours, des points décamétrique comme ici :
https://www.openstreetmap.org/node/2415885432

Cordialement

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


Re: [Talk-hr] Javni prijevoz u Zagrebu

2019-10-02 Thread Janko Mihelić
Super! Drago mi je da je pokus uspio. Vjerojatno postoje slučajevi kad je
dobro imati i stop_position, ali sad mi ne padaju na pamet. Možda u
autobusnom kolodvoru, gdje je sve jako gusto. Ali bez stop_position je
vjerojatno dobro za 99% slučajeva.

ned, 29. ruj 2019. u 16:24 Ivan Habunek  napisao je:

>
> Ako vi nemate ništa protiv, ja bih nastavio mapirati rute u ovom stilu,
> bez stop_position, pošto radi za routing, a i upute na OSM wikiju to
> predlažu.
>

Samo naprijed!
___
Talk-hr mailing list
Talk-hr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-hr


Re: [OSM-talk-fr] Amenity=telephone

2019-10-02 Thread Vincent de Château-Thierry
Bonjour,

> De: "Laurent Magréault" 
> 
> On a une cabine qui est bien devenue une boîte à livres à Conliège.
> J'ai préféré mettre was:amenity=telephone que historic=telephone qui
> est un tout petit peu plus utilisé en France d'après taginfo (mais
> on parle d'une dizaine d'unité).

Je réponds peut-être à côté mais pour une cabine encore visible sur le terrain 
mais non fonctionnelle, j'utilise plutôt disused:amenity :
https://taginfo.openstreetmap.org/tags/disused%3Aamenity=telephone

vincent

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


Re: [OSM-talk-fr] Moulinette pour convertir codes Insee en GPS > GPX ?

2019-10-02 Thread Vincent Bergeot

Le 02/10/2019 à 17:10, Shohreh a écrit :

Bonjour,

J'ai une liste de villes dans un fichier texte dont une des colonnes
contient le code Insee de la ville (plutôt que le code postal) :

Exemple :
=
01001;L'Abergement-Clémenciat;69199;Saint-Fons;5
=

J'ai besoin d'obtenir pour chaque ville ses coordonnées GPS et d'exporter le
tout en GPX pour afficher ça dans une carte.

Existe-t-il une moulinette, ou un moyen simple d'en écrire une ?


ceci : https://adresse.data.gouv.fr/csv

si j'ai bien compris.


--
Vincent Bergeot


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


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread Russ Phillips via Talk-GB
OsmAnd is what made me think of it. I'm using that for directions a lot 
now, and it's common these days to give a postcode to plug into a sat 
nav, but they frequently don't work in OsmAnd.


I was somewhat surprised that it hadn't already been done, and I accept 
all the reasons for not doing it.


I'll look into alternatives.

Russ


On 02/10/2019 15:52, SK53 wrote:
I really see no point. The data are already present in Nominatim  
(albeit perhaps not up-to-date) and search is the ONLY thing that 
so-called postcode centroids can help with. DE24 (Sinfin) was imported 
long ago, see this overpass query .


What can be done is attempt to assign postcodes to streets, and 
various incomplete efforts have been made over the years. Open Data 
provides full addresses for around 70% of UK postcodes (principally 
Companies House, Food Hygiene & National Register of Social Housing).


What would be useful is a maintained set of postcode information based 
on codepoint open/ONS postcode data/OS Local. The sorts of things 
which it would be useful to know are:


  * Is the postcode centroid co-located with others (e.g., delivery
offices, some businesses, blocks of flats)
  * Can the postcode be unambiguously assigned to a street & post town?
  * Is the post code in use or not (ONS is now obviously 8 years old,
but still potentially useful). Greg's FHRS tracker does appear to
indicate a degree of churn with inner-city postcodes (although
some of this will be inadvertent use of more general rather than
specific postcodes by people filling in the FHRS forms)
  * Is a postcode the sole postcode for that street?

Somewhere I have an old CPO table with some of this data populated. I 
think Geolytix had summary info associated with their post code sector 
shape files as well.


Adding addr:postcode to streets which have a single postcode is in my 
book fine: numerous LAs put this on street signs (Rushcliffe & Gedling 
for sure); it's an intermediate step to adding the addresses to 
houses  Once the postcodes which obviously belong to a single street 
are eliminated it's often easier to work out where the others belong.


Note that other than for FHRS we have no good source for Northern 
Ireland postcodes at all. Equally assignment of rural postcodes is 
quite a bit harder than urban ones. In re-reading bits of Chris's blog 
last night I came across a post of his 
 showing 
that some postcodes move huge distances between releases.


Jerry

PS. The Sinfin postcodes possibly should be removed as they were added 
IIRC before Mike Collinson's discussions with OSGB about OS Open Data.


On Wed, 2 Oct 2019 at 13:44, Russ Phillips via Talk-GB 
mailto:talk-gb@openstreetmap.org>> wrote:


Hi,

I'm wondering if it would be feasible and advisable to import the
UK postcode data from OS OpenData Codepoint

.

The licence is OSM compatible. My thinking was that we could
create a node for each data point and set the addr:postcode tag.
This would be useful for routing software like OsmAnd, since it
would allow a user to enter a postcode as a destination.

I'm happy to do the work, but the import guidelines
 say that
imports should be discussed on the imports@ list and the
appropriate local communities, hence this email.

Russ Phillips


___
Talk-GB mailing list
Talk-GB@openstreetmap.org 
https://lists.openstreetmap.org/listinfo/talk-gb

___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


[OSM-talk-fr] Moulinette pour convertir codes Insee en GPS > GPX ?

2019-10-02 Thread Shohreh
Bonjour,

J'ai une liste de villes dans un fichier texte dont une des colonnes
contient le code Insee de la ville (plutôt que le code postal) :

Exemple :
=
01001;L'Abergement-Clémenciat;69199;Saint-Fons;5
=

J'ai besoin d'obtenir pour chaque ville ses coordonnées GPS et d'exporter le
tout en GPX pour afficher ça dans une carte.

Existe-t-il une moulinette, ou un moyen simple d'en écrire une ?

Merci.



--
Sent from: http://gis.19327.n8.nabble.com/France-f5380434.html

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


Re: [OSM-talk-fr] Amenity=telephone

2019-10-02 Thread Laurent Magréault
Bonjour,

A titre de retour d'expérience, je viens d'en dégommer 12 sur 39 dans le
Jura en utilisant comme source Mapillary et les compte-rendus de conseils
municipaux qui se font souvent l'écho de la disparition des cabines.
On a une cabine qui est bien devenue une boîte à livres à Conliège. J'ai
préféré mettre was:amenity=telephone que historic=telephone qui est un tout
petit peu plus utilisé en France d'après taginfo (mais on parle d'une
dizaine d'unité).
Pour le reste, je verrais bien un signalement dans Osmose pour les plus
anciennes ou celles qui n'ont pas de survey:date.

___)```)___

Laurent Magréault d'Attoma
@ : laurent.magrea...@gmail.com


Le mer. 2 oct. 2019 à 11:54, Florian LAINEZ  a écrit :

> Hello,
> (4 ans plus tard !) le moment est peut-être venu pour faire le grand
> ménage @Donat.
> En effet un article de BFM
> 
> précise qu'il ne reste plus que 100 cabines en activité en France.
> La journaliste qui a écrit cet article m'a donné un contact chez Orange et
> j'ai fait la demande pour avoir la liste de cabines restantes, mais à mon
> avis on peut faire une croix dessus.
>
> A ce jour, notre projet recense 1490 cabines téléphoniques gérées par
> Orange ou France Télécom : https://overpass-turbo.eu/s/MMV (sans compter
> ceux dont l'operator n'est pas précisé)
> On en a donc 1390 de trop.
>
> Je pense qu'on a 2 situations à gérer :
> 1. la cabine est en zone blanche (
> https://www.data.gouv.fr/fr/datasets/mon-reseau-mobile) : dans le doute
> on ne touche pas pour l'instant
> 2. la cabine n'est pas en zone blanche.
> Dans ce cas on peut soit
> -être un peu bourrins et changer amenity=telephone en historic=telephone
> Tout en sachant qu'un grand nombre d'entre elles ont été démantelées.
> -être plus mesuré et rajouter un fixme="Cette ancienne cabine téléphonique
> n'est très certainement plus en service. Vérifier sur le terrain si elle
> existe encore. Si elle a été transformée en boîte à livres, merci de
> l'indiquer avec amenity=public_bookcase"
>
> Ma préférence va à la seconde solution avec en complément une mission
> pic4review voir un projet du mois pour nettoyer tout ça.
>
> Le lun. 1 juin 2015 à 09:29, Damouns  a écrit :
>
>> A Grenoble l'année dernière, j'ai vu démonter plusieurs cabines
>> téléphoniques située dans des quartiers différents, dans l'espace
>> d'une semaine.
>>
>> Comme je les avais cartographiées auparavant je me suis dit qu'il
>> fallait que je me programme un petit tour de vérification pour voir
>> lesquelles sont encore en place. Mais je n'ai pas eu le temps de le
>> faire depuis.
>>
>> En 2013 j'avais fais un post à ce propos :
>> http://www.openstreetmap.org/user/Damouns/diary/20175
>>
>> Toujours de pas de données en "open data" produites par Orange ou
>> l'Arcep, aujourd'hui en 2015.
>>
>> Damouns
>>
>> Le 1 juin 2015 01:37, Donat ROBAUX  a écrit :
>> > Bonsoir à tous,
>> >
>> > Un petit clin d'oeil à tous nos mappeurs fous:
>> >
>> http://www.estrepublicain.fr/edition-de-besancon/2015/05/31/besancon-a-terme-deux-cabines-telephoniques
>> >
>> > Leur localisation va devenir un service public à part entière. Elles
>> vont
>> > être plus dures à trouver qu'une cache de géocaching! A moins qu'Orange
>> nous
>> > fournisse la liste géoréférencée...
>> > Plus sérieusement, j'imagine que dans quelques années, lorsque le
>> mouvement
>> > de disparition des cabines sera fini, il y aura un grand nettoyage à
>> faire
>> > pour ne garder que celles qui sont encore debout.
>> >
>> > Votre avis?
>> >
>> > Donat
>> >
>> > PS: hâte de voir les documents du SOTMFR!
>> >
>> > ___
>> > Talk-fr mailing list
>> > Talk-fr@openstreetmap.org
>> > https://lists.openstreetmap.org/listinfo/talk-fr
>> >
>>
>> ___
>> Talk-fr mailing list
>> Talk-fr@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-fr
>>
>
>
> --
>
> *Florian Lainez*
> @overflorian 
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread SK53
I really see no point. The data are already present in Nominatim  (albeit
perhaps not up-to-date) and search is the ONLY thing that so-called
postcode centroids can help with. DE24 (Sinfin) was imported long ago, see
this overpass query .

What can be done is attempt to assign postcodes to streets, and various
incomplete efforts have been made over the years. Open Data provides full
addresses for around 70% of UK postcodes (principally Companies House, Food
Hygiene & National Register of Social Housing).

What would be useful is a maintained set of postcode information based on
codepoint open/ONS postcode data/OS Local. The sorts of things which it
would be useful to know are:

   - Is the postcode centroid co-located with others (e.g., delivery
   offices, some businesses, blocks of flats)
   - Can the postcode be unambiguously assigned to a street & post town?
   - Is the post code in use or not (ONS is now obviously 8 years old, but
   still potentially useful). Greg's FHRS tracker does appear to indicate a
   degree of churn with inner-city postcodes (although some of this will be
   inadvertent use of more general rather than specific postcodes by people
   filling in the FHRS forms)
   - Is a postcode the sole postcode for that street?

Somewhere I have an old CPO table with some of this data populated. I think
Geolytix had summary info associated with their post code sector shape
files as well.

Adding addr:postcode to streets which have a single postcode is in my book
fine: numerous LAs put this on street signs (Rushcliffe & Gedling for
sure); it's an intermediate step to adding the addresses to houses  Once
the postcodes which obviously belong to a single street are eliminated it's
often easier to work out where the others belong.

Note that other than for FHRS we have no good source for Northern Ireland
postcodes at all. Equally assignment of rural postcodes is quite a bit
harder than urban ones. In re-reading bits of Chris's blog last night I
came across a post of his
 showing that
some postcodes move huge distances between releases.

Jerry

PS. The Sinfin postcodes possibly should be removed as they were added IIRC
before Mike Collinson's discussions with OSGB about OS Open Data.

On Wed, 2 Oct 2019 at 13:44, Russ Phillips via Talk-GB <
talk-gb@openstreetmap.org> wrote:

> Hi,
>
> I'm wondering if it would be feasible and advisable to import the UK
> postcode data from OS OpenData Codepoint
> 
> .
>
> The licence is OSM compatible. My thinking was that we could create a node
> for each data point and set the addr:postcode tag. This would be useful for
> routing software like OsmAnd, since it would allow a user to enter a
> postcode as a destination.
>
> I'm happy to do the work, but the import guidelines
>  say that imports
> should be discussed on the imports@ list and the appropriate local
> communities, hence this email.
>
> Russ Phillips
>
>
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread Andy Robinson
Cheers Chris, always mightily useful.

 

Andy

 

From: Chris Hill [mailto:o...@raggedred.net] 
Sent: 02 October 2019 15:38
To: Tony OSM; OSM Talk GB
Subject: Re: [Talk-GB] Import UK postcode data?

 

Thanks,

I've just updated with August 2019 data, the next update is due in November I 
think. 

-- 
cheers
Chris Hill (chillly)

On 02/10/2019 15:24, Tony OSM wrote: 

Hi

Didn't know about your JOSM overlay - just added and it looks great.

Tony Shield (TonyS999)

On 02/10/2019 14:20, Chris Hill wrote:

I would not like to see that happen. OSM maps real objects, postcodes are not 
real and only apply as a part of an object's address. They apply to buildings 
(delivery points on buildings really). The postcodes in Codepoint Open are 
centroids derived from a combination of all the delivery points that share the 
postcode so are not at all real-world objects.

If you want to apply postcodes to addresses you can see the map overlay I have 
produced which you can use in editors as an overlay: 
https://codepoint.raggedred.net/  I will update it again shortly. You can also 
derive postcodes from other open data sources such as FHRS data. 

-- 
cheers
Chris Hill (chillly)
 

On 02/10/2019 13:43, Russ Phillips via Talk-GB wrote:

Hi,

I'm wondering if it would be feasible and advisable to import the UK postcode 
data from OS OpenData Codepoint 
 .

The licence is OSM compatible. My thinking was that we could create a node for 
each data point and set the addr:postcode tag. This would be useful for routing 
software like OsmAnd, since it would allow a user to enter a postcode as a 
destination.

I'm happy to do the work, but the import guidelines 
  say that imports 
should be discussed on the imports@ list and the appropriate local communities, 
hence this email.

Russ Phillips

 

 

-- 
cheers
Chris Hill (chillly)
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [talk-cz] Jízdní řády a linky MHD

2019-10-02 Thread Mirek Dlask
Souhrn je například v katalogu otevřených dat

https://data.gov.cz/datov%C3%A9-sady?dotaz=zast%C3%A1vky%C3%A1nka=1

Bohužel často jsou zastávky  zjednodušeny do jednoho bodu někdo uprostřed.
Polohová přesnost je mnohde, třeba i vpražském PIDu špatná.

M.D.

út 1. 10. 2019 v 22:37 odesílatel Mikoláš Štrajt  napsal:

> Zdar,
> probíraly se tu teď linky MHD. Vzhledem k tomu, že se o danou tématiku
> zajímám, tak zkusím shrnout, jaký je stav:
>
> Pro ČR existuje tzv. Celostátní informační systém o jízdních řádech. Jeho
> data byla po letech bojů Chapsu se Seznamem více méně otevřena pro širokou
> veřejnost. Celou tu historii si můžete přečíst na wiki -
> https://cs.wikipedia.org/wiki/Celost%C3%A1tn%C3%AD_informa%C4%8Dn%C3%AD_syst%C3%A9m_o_j%C3%ADzdn%C3%ADch_%C5%99%C3%A1dech
>
> Data najdete zde - ftp://ftp.cisjr.cz/ - nicméně (pokud vím) neobsahují
> žádné geografické informace, tj. pro OSM jsou v podstatě k ničemu.
>
> Pro nás zajímavější jsou data ve formátu GTFS - z těch se totiž dají
> vytáhnout jak jízdní řády, tak poloha zastávek a přibližná trasa linek.
>
> Krásně to má zpracované Praha  - viz https://pid.cz/o-systemu/opendata/
>
> Ještě jsem to našel pro Liberec - https://www.dpmlj.cz/opendata
>
> Další město už jsem nenašel, ale kde se dá hledat spojení na Google maps,
> tak to místní DP nebo IDS umí vygenerovat.
>
> U některých měst jdou sehnat alespoň seznamy zastávek, viz Plzeň:
>
>
> https://opendata.plzen.eu/dataset/gis-doprava-mestska-hromadna-doprava-zastavky-mhd
>
> * * *
>
> Co se týká zobrazování - já mám rozepsanou prohlížečku jízdních řádů. Viz
> http://jizdnirady.svita.cz/pid (zrovna včera jsem tam nahrál data)
>
> Pavel Machek má nějaký vyhledávač, ale netuším jak moc je to použitelné -
> https://gitlab.com/tui/tui/tree/master/timetab/
>
> + jde říct, že když máme GTFS tak už jsou použitelné různé opensource
> nástroje
>
> * * *
>
> A co se týká importu dat do OSM:
>
> Kdyby byl zájem, můžu napsat nějakou aplikaci, která tahle GTFS data
> předádět na nějaký GeoJSON nebo něco podobného a my to pak budeme moci
> importovat/opisovat podobně jako se to dělá např. s poštovníma schránkama.
> Nicméně NECHCI být ten, kdo to bude překlikávat, zas tolik času nemám (ani
> v zimě :-D).
>
> --
> Severák
> ___
> talk-cz mailing list
> talk-cz@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-cz
> https://openstreetmap.cz/talkcz
>
___
talk-cz mailing list
talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz
https://openstreetmap.cz/talkcz


Re: [talk-cz] Mapovani MHD was Re: SotM deníček - den třetí

2019-10-02 Thread Mirek Dlask
Ahoj,
rozdíl tam přece jen je. Trasu autobusem si vybrat nemohu. Jízdu s pistolí
na spánku řidiče vylučuji. Nechci jezdit tímto -
https://cs.wikipedia.org/wiki/V%C4%9Bze%C5%88sk%C3%BD_v%C5%AFz . Proto
„nepotřebuji vědět kudy".

Naopak cestu si rád vybírám a současná míra jejich zjednodušení mi vyhovuje.
Tvoje reakce je zbytečná. Popisuješ totéž jako „jzvc" jen jinými slovy.

Pro jistotu.
Nemám v úmyslu na současném stavu nic měnit. Už dnes je možné mít v
relacích veřejné dopravy pouze zastávky. Stačí ignorovat hlášky validátorů.

A proč?
Seznam zastávek vyčtu z jízdního řádu vždy,  trasu linek často nedokážu ani
odhadnout. Následně může někdo trasu projet, zaznamenat a k zastávkám ji
přidat.

Závěrem
se ještě vrátím k povzdechnutí od „jzvc"

oficielni reneder OSM pokud dobre vidim uz nejakych 8 let s klidem ignoruje
oficielne odsouhlaseny standard pro tagovani hromadne dopravy. Jinak
receno, ani ty zastavky na mape videt nejsou.

Za současnou situaci můžeme všichni kdo k tagům public_transport přidáváme
highway , railway. Pokud bychom je nepřidávali celosvětově, tak by se
nějaký čas zastávky nevykreslovaly a pak se vidělo. Nebo taky nevidělo.


M.D.


po 30. 9. 2019 v 20:31 odesílatel Petr Vozdecký  napsal:

> Od: Mirek Dlask 
> Předmět: Re: [talk-cz] Mapovani MHD was Re: SotM deníček - den třetí
>
> Ahoj,
> nepotřebuji vědět kudy bus jede. Jestli po Hlavní, nebo Souběžnou mi je
> jedno.
>
>
> To je jako: ...nepotřebuji vědět, kudy ta cesta/pěšina/silnice vede, stačí
> mi jen křižovatky, zjednodušíme si to na 2D drátový model a vše bude
> snazší, bude se to líp spravovat, nemusí se řešit změny geometrie cest mezi
> křižovatkami, bude to zabírat míň místa všude, navigovat "za 200m doleva"
> to bohatě stačí...
>
>
> Těch argumentů "pro" se dá najít vlastně strašně moc... ...a nakonec si
> strašně zjednodušíme práci... ...a vlastně úplně všechno :)
>
>
> vop
> ___
> talk-cz mailing list
> talk-cz@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-cz
> https://openstreetmap.cz/talkcz
>
___
talk-cz mailing list
talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz
https://openstreetmap.cz/talkcz


Re: [OSM-talk-fr] adresses sur tronc d'arbres

2019-10-02 Thread David Crochet

Bonjour

Ce sont soit des numéros de parcelles dont les arbres des coins desdites 
parcelles comportent ledit numéros, ou alors si cela se trouvent sur un 
prarcours, des points décamétrique comme ici : 
https://www.openstreetmap.org/node/2415885432


Cordialement

--

David Crochet


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


Re: [OSM-talk-fr] adresses sur tronc d'arbres

2019-10-02 Thread Cyrille37 OSM

Ne serait-ce pas des "repères" plutôt que les numéros pour des adresse ?

Cyrille37

Le 02/10/2019 à 15:09, Baptiste Lemoine - Cipher Bliss via Talk-fr a écrit :

hello,
je ne trouve pas comment catégoriser ce qui ressemble a des addresses 
sur des troncs d'arbres dans une forêt.
il y a un parcours sportif formant une route circulaire dans la forêt 
avec des équipements permettant de faire de l'escalade, des 
tractions,du saut de haie... voici une photo du panneau d'infos a 
l'entrée de la forêt.
https://www.mapillary.com/map/im/YC4fb2LeIVSO5ufjuw66bA (désolé pour 
la qualité, y'a des affichages agraphés sur le plan, c'est malin)
et voici a quoi ressemblent les marquages sur les arbres. on dirait 
clairement des adresses, sauf qu'il n'y a aucune maison dans cette 
foret, pas de boite postale non plus.
donc pour le moment j'ai mis des POI marquant une adresse avec juste 
un numéro, mais pas de nom de rue.

https://www.mapillary.com/map/im/TZyoV49PiGWKJx7Z9dtgmw

si quelqu'un a une idée de comment bien gérer ça :)

Baptiste LEMOINE - Dirigeant de Cipher Bliss.com 
 , N° SIRET: 79942416300027 



Tel 0185461173 / Signal 0627130837  , 
Telegram: Tykayn  , Mastodon: @tykayn 
 , Contact.vcf 



Sent with ProtonMail  Secure Email.


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


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread Chris Hill
I would not like to see that happen. OSM maps real objects, postcodes 
are not real and only apply as a part of an object's address. They apply 
to buildings (delivery points on buildings really). The postcodes in 
Codepoint Open are centroids derived from a combination of all the 
delivery points that share the postcode so are not at all real-world 
objects.


If you want to apply postcodes to addresses you can see the map overlay 
I have produced which you can use in editors as an overlay: 
https://codepoint.raggedred.net/ I will update it again shortly. You can 
also derive postcodes from other open data sources such as FHRS data.


--
cheers
Chris Hill (chillly)

On 02/10/2019 13:43, Russ Phillips via Talk-GB wrote:


Hi,

I'm wondering if it would be feasible and advisable to import the UK 
postcode data from OS OpenData Codepoint 
.


The licence is OSM compatible. My thinking was that we could create a 
node for each data point and set the addr:postcode tag. This would be 
useful for routing software like OsmAnd, since it would allow a user 
to enter a postcode as a destination.


I'm happy to do the work, but the import guidelines 
 say that 
imports should be discussed on the imports@ list and the appropriate 
local communities, hence this email.


Russ Phillips


___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


[OSM-talk-fr] adresses sur tronc d'arbres

2019-10-02 Thread Baptiste Lemoine - Cipher Bliss via Talk-fr
hello,
je ne trouve pas comment catégoriser ce qui ressemble a des addresses sur des 
troncs d'arbres dans une forêt.
il y a un parcours sportif formant une route circulaire dans la forêt avec des 
équipements permettant de faire de l'escalade, des tractions,du saut de haie... 
voici une photo du panneau d'infos a l'entrée de la forêt.
https://www.mapillary.com/map/im/YC4fb2LeIVSO5ufjuw66bA  (désolé pour la 
qualité, y'a des affichages agraphés sur le plan, c'est malin)
et voici a quoi ressemblent les marquages sur les arbres. on dirait clairement 
des adresses, sauf qu'il n'y a aucune maison dans cette foret, pas de boite 
postale non plus.
donc pour le moment j'ai mis des POI marquant une adresse avec juste un numéro, 
mais pas de nom de rue.
https://www.mapillary.com/map/im/TZyoV49PiGWKJx7Z9dtgmw

si quelqu'un a une idée de comment bien gérer ça :)

Baptiste LEMOINE - Dirigeant de Cipher Bliss.com , N° SIRET: 79942416300027

Tel 0185461173  / Signal 0627130837 , Telegram: Tykayn , Mastodon: @tykayn , 
Contact.vcf

Sent with ProtonMail Secure Email.

publickey - contact@cipherbliss.com - 0x548ACF17.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread David Woolley

On 02/10/2019 13:57, David Woolley wrote:
Whilst I'm not sure of the precise conclusions, this has been considered 
many many times before.  I think it may even have been done in some 
places.  I'd suggest a search of the list archives.


Also, the discussing tab on the wiki page you referenced contains 
discussion on this going back over 9 years, and expresses concern about 
the licensing.


As a minor point, although described as centroids, they are not actually 
centroids, but actually the nearest valid delivery point to the centroid.


My feeling is that, if considered acceptable, it would already have 
happened.



___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [Talk-de] Fragen, Anregung eines Neulings

2019-10-02 Thread Roland Olbricht

Sehr geehrter Herr Mehl,


https://routing.openstreetmap.de/?z=15=50.738180%2C8.291759=49.908459%2C8.647996=51.956580%2C7.632351=de=0=0

erhalte ich zwei unverständliche Umleitungen:

   - die A5 nicht bis zum Gambacher Kreuz, sondern vorher Abfahrt
     um Butzbach, Langengöns
   - um Herborn herum auf der B277,


erst einmal herzlich willkommen und danke für die Rückmeldung. Das ist
durchaus schon konkret genug, um den konkreten Mangel zu finden.

Das schöne bei Open-Source ist, dass jeder der Ursache noch weiter
nachgehen kann. Zum Nachfolgenden möchte ich Sie gerne ermuntern, aber
nicht verpflichten; für die erfahrenen Leser ist aber aber sicherlich
gut zu wissen:

In diesem Fall gibt es unten links auf der Routing-Ansicht, drittes
Symbol (Lupe vor Quadrat) eine sogenannte Debug-Ansicht:
https://routing.openstreetmap.de/debug/car.html#14/50.4915/8.6899
Dort bleibt die Fahrbahn Richtung Dortmund grau. D.h. aus Sicht der
Ruting-Software ist diese Fahrbahn nicht befahrbar.

Ab diesem Punkt könnte man den Macher der Routing-Software anschreiben,
https://routing.openstreetmap.de/about.html
liefert fossgis-routing-ser...@openstreetmap.de
als Ansprechpartner.

Oder selber herausfinden, warum die Fahrbahn nicht verwendet wird:
https://overpass-turbo.eu/s/MNy
liefert die fraglichen Elemente sowie die Elemente kurz davor und
dahinter, zum Anklicken mit Sicht auf die Tags.
Bei den Tags unterscheiden sich die routbaren Elemente von den nicht
routbaren Elementen am Ehesten durch das Tag "construction=yes".

Wie sich herausstellt, wenn man auf
https://routing.openstreetmap.de/about.html
nach den Routing-Regeln
https://github.com/fossgis-routing-server/cbf-routing-profiles/blob/master/car.lua
schaut, dann findet man, dass

avoid = Set {
[...]
  'construction',
  'proposed'
},

d.h. es wird in der Tat die Route von routing.openstreetmap.de nicht
genutzt, weil "construction=yes" gesetzt ist. Hier wäre jetzt die
Einschätzung gefragt, ob das Tag "construction=yes" gerechfertigt ist.
Aus der Erfahrung und Beschreibung auf
https://wiki.openstreetmap.org/wiki/DE:Key:construction
liest man, dass das Tag nicht verwendet werden sollte (sondern
"highway=construction" + "construction=motorway", wenn und nur wenn die
Fahrbahn unbefahrbar ist).

An dieser Stelle ließe sich nun entweder das Tag entfernen oder
sinnvollererweise per Changeset-Diskussion der Mapper kontaktieren, was
das Tag "construction=yes" eigentlich hätte sein sollen. Ich habe das in
https://www.openstreetmap.org/changeset/74156647
jetzt getan.

Wie gesagt, die komplette Recherche würde ich zwar nicht erwarten, aber
es ist ein guter Fall vorzuführen, warum durch Open Source man schnell
den richtigen Ansprechpartner mit dem richtigen Kontext finden kann.

Viele Grüße,

Roland Olbricht

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


Re: [Talk-GB] Import UK postcode data?

2019-10-02 Thread David Woolley
Whilst I'm not sure of the precise conclusions, this has been considered 
many many times before.  I think it may even have been done in some 
places.  I'd suggest a search of the list archives.


Note that this data is not suitable for reverse geo-coding, because I 
don't believe it distinguishes between single business and area codes.


(Better would be to convince the general public that a proprietary 
locator system is not the best way of providing a short code for an 
approximate location.)



On 02/10/2019 13:43, Russ Phillips via Talk-GB wrote:

Hi,

I'm wondering if it would be feasible and advisable to import the UK 
postcode data from OS OpenData Codepoint 
.


The licence is OSM compatible. My thinking was that we could create a 
node for each data point and set the addr:postcode tag. This would be 
useful for routing software like OsmAnd, since it would allow a user to 
enter a postcode as a destination.


I'm happy to do the work, but the import guidelines 
 say that imports 
should be discussed on the imports@ list and the appropriate local 
communities, hence this email.


Russ Phillips



___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb




___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [talk-au] Discussion H: public transport – the end game

2019-10-02 Thread Mateusz Konieczny


2 Oct 2019, 09:19 by e...@mapillary.com:

> For the health of the mailing list, it would make sense to limit his 
> communications so we're not bombarded daily with his emails.
>
Volume is not the biggest problem -
and it would be probably acceptable.

For me main problem is "fire and forget"
mode.

Is he even reading replies?

Maybe he is unable to respond because
he had monthly digest or something
similarly problematic?___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


[Talk-GB] Import UK postcode data?

2019-10-02 Thread Russ Phillips via Talk-GB

Hi,

I'm wondering if it would be feasible and advisable to import the UK 
postcode data from OS OpenData Codepoint 
.


The licence is OSM compatible. My thinking was that we could create a 
node for each data point and set the addr:postcode tag. This would be 
useful for routing software like OsmAnd, since it would allow a user to 
enter a postcode as a destination.


I'm happy to do the work, but the import guidelines 
 say that imports 
should be discussed on the imports@ list and the appropriate local 
communities, hence this email.


Russ Phillips


___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


[Talk-GB] 24 hour mapathon - Aberconwy

2019-10-02 Thread Rob Nickerson
Hi all,

I've not done a great deal of publicity about these, but as a reminder the
next 24 hour mapathon is coming up next Wednesday. This time we are mapping
Aberconwy.

There's no need to plan anything but feel free to do some prep if you like.
Just take a look at that bit of the map at any stage during the 24 hour
period. If you spot something you can add/update/improve go for it.
Alternatively just see how it's mapping compares to regions you're more
familiar with.

https://wiki.openstreetmap.org/wiki/UK_24_hour_mapathons

Thank you,
*Rob*
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


Re: [Talk-de] Fragen, Anregung eines Neulings

2019-10-02 Thread chris66

Am 02.10.2019 um 10:29 schrieb Albrecht Mehl via Talk-de:


1. Route unverständlich
===

Auf der Seite


https://routing.openstreetmap.de/?z=15=50.738180%2C8.291759=49.908459%2C8.647996=51.956580%2C7.632351=de=0=0 



erhalte ich zwei unverständliche Umleitungen:

   - die A5 nicht bis zum Gambacher Kreuz, sondern vorher Abfahrt
     um Butzbach, Langengöns
   - um Herborn herum auf der B277,



Ich vermute ein OSRM-internes Problem, da ich auf die Schnelle in
den Daten des Gamb-Kreuzes nichts auffälliges finden kann, und der
zweite OSM-Online-Router (graphhopper) korrekt routet.

https://www.openstreetmap.org/directions?engine=graphhopper_car=50.2901%2C8.6774%3B50.6136%2C8.3868#map=11/50.4531/8.5549

Ansonsten: Für Anregungen/Wünsche zu den Routern am besten direkt die
Router-Entwickler kontaktieren. Die lesen eventuell hier nicht mit.

Chris




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


[OSM-talk] GeoForAll contributions to the United Nations Sustainable Development Goals

2019-10-02 Thread Suchith Anand via talk
 GeoForAll community are pleased to announce webinar mini-conference on 
GeoForAll contributions to the United Nations Sustainable Development 
Goalsduring World Commons Week 2019.   




An important element of World Commons Week 2019 are establishing coordinated 
local events all over the world on commons related issues and practice. As part 
of the World Commons Week 2019,  there are a multitude of local events 
organized in different parts of the world all dedicated to raising awareness 
about the scholarship and practice of the Commons in many thematic areas, 
including water, forests, fisheries and marine settings; the global atmosphere; 
infrastructure, urban and rural areas; technology and software; and knowledge 
sharing and co-production.




Open source software and open educational resources are forms of Internet-based 
“commons” and that’s what the International Association for the Study of the 
Commons (IASC) organization is trying to promote. A link between GeoForAll and 
the IASC community is a natural one. The Second Annual Global World Commons 
Weekwill take place 6-12 October 2019. Details 
athttps://wcw2019.iasc-commons.org




Last year’s website is at http://worldcommonsweek.org . We thankProf. Charles 
Schweik (UMass Amherst) who is lead organiser of the WCW2019 for inviting 
GeoForAll community to share ideas. Dr. Victoria Rautenbach (GeoForAll chair) 
will welcome all participants to the mini-conference. The GeoForAll webinar 
mini-conference details are below. All are welcome.








GeoForAll contributions to the United Nations Sustainable Development Goals

October 10th 2019 (Thursday) at 1:00-3:00 PM GMT




Access to quality education and digital economy opportunities is key for 
getting rid of extreme poverty and enable broadly shared prosperity for all. 
“GeoForAll” is the Open Source Geospatial Foundation’s Education initiative and 
works in close collaboration with ICA, ISPRS, UN-GIS, AGILE, UCGIS , IGU and 
other partners worldwide in our mission for making geospatial education and 
digital economy opportunities accessible to all [1].  By combining the 
potential of free and open geospatial software, open data, open standards and 
open access to research publications will enable the creation of a sustainable 
innovation ecosystem for helping solve global cross disciplinary societal 
challenges from climate change mitigation to zero hunger. Service for the 
benefit and betterment of humanity is a key fundamental principle of GeoForAll 
and we want to contribute and focus our efforts for the United Nations 
Sustainable Development Goals. Free and Open Source Software for Geospatial has 
now made it possible for a large number of  government organisations, private 
companies and academics in both developed and developing countries to make use 
of geospatial software in many application domains. This will ensure that geo 
education and geo digital economy opportunities are also available to 
economically poor countries and economically poor people worldwide.  Central to 
“Geo for All” mission is the belief that knowledge is a public good and Open 
Principles in Education will enable broadly shared prosperity for all.

 

Program schedule and how to join at 
https://www.osgeo.org/foundation-news/geoforall-contributions-to-the-united-nations-sustainable-development-goals/




We thank Dr. Rafael Moreno and colleagues at the Open Source Geospatial Lab at 
University of Colorado, USA for hosting the GeoForAll mini-conference in 
support of World Commons Week 2019. The recordings will be made available at 
the GeoForAll webinar channel at 
https://www.youtube.com/channel/UCL1E2akvCNWP_nC0p5CpB8g/videos 




 We wish everyone a very productive week of celebrating the commons scholarship 
and practice.




Best wishes,




Suchith 







[1] 
https://www.osgeo.org/foundation-news/please-share-geoforall-teaching-research-resources-colleagues-students/







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


Re: [Talk-GB] Resurrecting the 'find the missing paths for 2026' project

2019-10-02 Thread Tony OSM

Hi

I've been using MapThe Paths for the last year to add my local ROW's to 
OSM - I find it a great help. If we can get all of the data into OSM it 
will enable all ROW users to identify in one source of ROWs and 
NOT.ROWs. This is important as I have identified several paths which 
perhaps should be ROW's or diversions not correctly mapped by the 
Highway Authority.



People provide walkers maps based on OSM - they are very useful when 
ROW's are correctly referenced, the route planning can go ahead with 
increased confidence that the route will not be contentious by routing 
over a private road/track.



I would like missing paths to be a regular feature until 2026, its our 
heritage some of which can only be identified by mapping.


Perhaps working nationally and with local Ramblers groups (another 
project) could a conduit be formed to enable ramblers to identify 
changes needed to the map (perhaps by listing tags and possible values).



Technically on MapThePaths can an option be made available to show  
highways (roads) as an optional overlay to help identify ways which 
perhaps should be included in OSM but are not.



Regards

Tony Shield

TonyS999


On 30/09/2019 18:25, Nick Whitelegg wrote:

Hi,

Was just thinking whether it would be worth us (as in OSM UK) 
resurrecting the 'missing paths for 2026' project?


A quick reminder - we have until 2026 to record historical rights of 
way which have fallen out of use in recent times, and the combination 
of OSM, council data and historical map layers (which I have been 
granted access to by NLS for MapThePaths) would be a good way to 
identify possible missing paths.


I made a start on this about a year ago, here's a quck mock-up showing 
council data in colours and OSM paths shown in white as a 'tippex' 
effect. This allows the identification of historical 'F.P' footpaths 
on the historical maps which do not correspond either to current 
council RoWs or current OSM paths, and thus would be candidates for 
investigation to see if the path is in a usable state or there is 
evidence of use.


http://mapthepaths.org.uk/?mode=1

Obviously it's perhaps not the best time of year to launch an outdoor 
project - but the next few months would be a good time to develop the 
project ready for use in the spring.


Anyone keen to work on this?
Gitlab: https://gitlab.com/nickw1/mapthepaths/

Thanks,
Nick




___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


[Talk-it] [talk:IT] Pagina wiki segnali stradali in Italia

2019-10-02 Thread Volker Schmidt
Sulla pagina
https://wiki.openstreetmap.org/wiki/IT:Road_signs_in_Italy
Si trova queste descrizioni e tagging per i due tipi di "ciclopedonali"

(A)
Pista ciclabile contigua al marciapiede (Footpath and cycleway):
highway=cycleway, foot=designated, bicycle=designated ed opzionale
segregated=yes

(B)
Percorso pedonale e ciclabile (Footpath and cycleway):
highway=cycleway, foot=designated, bicycle=designated ed opzionale
segregated=no

Ci sono vari problemi con queste righe
(ho già cambiato "designed" a  "designated"):

Per (A)

   - La traduzione inglese " Footpath and cycleway " è sbagliata. Dovrebbe
   essere "Segregated cycle/pedestrian path " (vedi
   https://wiki.openstreetmap.org/wiki/Road_signs_in_the_United_Kingdom)
   
   - "segregated=yes" è obbligatorio, non opzionale, per distinguere i due
   tipi di ciclopedonali.
   - la etichetta "highway=path" è preset in JOSM ed è quindi molto
   diffuso. Dovreebbe essere almeno menzionato
   - aggiungerei:
   "uso obbligatorio per ciclisti, se adiacente a una strada", cioè la
   strada aggiacente dovrebbe essere taggata con "bicycle=use_sidepath" (vedi
   https://wiki.openstreetmap.org/wiki/Tag:bicycle%3Duse_sidepath)

Per (B):

   - La traduzione inglese " Footpath and cycleway " è sbagliata. Dovrebbe
   essere " Shared cycle/pedestrian path" (vedi
   https://wiki.openstreetmap.org/wiki/Road_signs_in_the_United_Kingdom)
   
   - "segregated=no" è obbligatorio, non opzionale, per distinguere i due
   tipi di ciclopedonali.
   - l'etichetta "highway=cycleway" è sbagliata in Italia.
   Legalmente si tratta di un marciapiede sul quale i ciclisti possono
   circolare, ma i pedoni hanno precedenza. Quindi si potrebbe taggare
   "highway=footway". Preferisco i preset JOSM, cioè "highway=path".
   - aggiungerei:
   "uso non obbligatorio per ciclisti"

Che ne dite?
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it


[OSM-talk-fr] Nouvelle API du géocodeur et communes nouvelles

2019-10-02 Thread Rpnpif
Bonjour,

Merci à Christian pour la nouvelle API de consultation du géocodeur de
http://demo.addok.xyhz/.

Elle est très agréable à utiliser.

Je voudrais attirer l'attention sur un problème lié aux communes
nouvelles (encore un).

Quand on recherche un lieu sur http://demo.addok.xyhz/ (mais c'est
pareil sur Nominatim), la présentation de l'adresse est incomplète.

Exemple spécifique à la France : 
La Poste demande que les adresses soient présentées sous la forme :
La Rousserie (lieu-dit)
Le Louroux-Béconnais (ancienne commune)
49370 Val-d'Erdre-Auxence (nouvelle commune)

Elle tolère si le lieu-dit est unique sur la nouvelle commune (pas
d’ambiguïté) :
La Rousserie (lieu-dit)
49370 Val-d'Erdre-Auxence (nouvelle commune)

Mais http://demo.addok.xyhz/ présente ainsi :
La Rousserie (lieu-dit)
49370 Le Louroux-Béconnais (ancienne commune)
Il manque l'info de la nouvelle commune.

Là où ça se complique, c'est quand la nouvelle commune a plusieurs codes 
postaux.
Par exemple Erdre-en-Anjou comporte des communes avec le code 49220 et une avec 
49370.

Comme ces codes sont basés en général sur les anciennes communes, on peut se 
baser sur cela pour le mettre devant le nom de la nouvelle pour un lieu 
déterminé.

Par contre, il y a des communes et de nombreuses villes où le code postal est 
zoné par quartier ou rue ou partie de rue.
Dans ce dernier cas, ne serait-il pas possible de créer des aires spécifiques 
pour l'attribut de code postal comme on les cantons ou autres à parir des 
données fournis par la Poste ?

En résumé c'était deux questions : la présentation de l'adresse et le zonage du 
code postal.

-- 
Alain Rpnpif

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


Re: [Talk-ca] Importing building and routing info regionally/locally (Jonathan)

2019-10-02 Thread Jonathan Brown
Ditto Kevin’s post. Erik, I live in Cobourg and have an interest in working 
with local mappers to map Northumberland County. At the moment we only have one 
novice (myself) and Kelsey Saunders, a GIS grad. 

Jonathan 

We are a local/regional courier and trucking company in southern Ontario
> with a decent sized fleet.  We are using Mapbox for our mapping / nav
> engine, therefore subject to using OSM data.  We have noticed a number of
> “issues/lack of data” for southern Ontario.  This ranges from lack of lane
> info, to lack of buildings, missing streets, missing exit/on-ramps to for
> Hwy 400 (which we added, and had Mapbox expedite the changesets) as it
> affected navigation for our drivers.
>
>
>
> We are currently using a few devices to provide street level imagery via
> Mapillary, with a push coming shortly to map 1000km per day of street
> imagery.  We are currently mapping about 250km per day in York Region.  Our
> internal goal is to provide /gathered street level imagery for 75% York
> Region by end of January 2020.
>
>
>
> We are not in a position to provide map edits etc, as due to staff
> resources and lack of experience, our staff are not suited to become ‘map
> editors’ as our core business is transportation.  We are just trying to
> assist the editors with accurate ground level info.
>
>
>
> I would be interested in further understanding how we can become involved
> on a regional level to improve OSM in southern Ontario.


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


[OSM-talk-fr] Intégration

2019-10-02 Thread Florian LAINEZ
Hello,
J'ai l'impression que pour l'instant on ne s'est intéressé qu'à
l'intégration des bureaux de poste en eux-même de manière systématique, cf.
https://wiki.openstreetmap.org/wiki/France/data.gouv.fr/Import_des_points_de_contact_postaux

Néanmoins en France on a tout de même 1323 points qui ont le tag
post_office:type=post_partner cf. https://overpass-turbo.eu/s/MMQ ce qui
est un bon début concernant les commerces partenaires.
Ne compléterions-nous pas la liste sur la page
https://wiki.openstreetmap.org/wiki/FR:Key:post_office:type avec un tag
indiquant les points de retrait/dépôt Colissimo ?
Il est possible de les trouver via le site officiel de la Poste

bien qu'il n'y ai aucun jeu de données correspondant sur le site open data
 pour ces commerces partenaires.
Nous ne pouvons donc pas lancer une intégration via OSMOSE mais préciser le
tag utilisé me paraît une première étape.

-- 

*Florian Lainez*
@overflorian 
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [OSM-talk-fr] Amenity=telephone

2019-10-02 Thread Florian LAINEZ
Hello,
(4 ans plus tard !) le moment est peut-être venu pour faire le grand
ménage @Donat.
En effet un article de BFM

précise qu'il ne reste plus que 100 cabines en activité en France.
La journaliste qui a écrit cet article m'a donné un contact chez Orange et
j'ai fait la demande pour avoir la liste de cabines restantes, mais à mon
avis on peut faire une croix dessus.

A ce jour, notre projet recense 1490 cabines téléphoniques gérées par
Orange ou France Télécom : https://overpass-turbo.eu/s/MMV (sans compter
ceux dont l'operator n'est pas précisé)
On en a donc 1390 de trop.

Je pense qu'on a 2 situations à gérer :
1. la cabine est en zone blanche (
https://www.data.gouv.fr/fr/datasets/mon-reseau-mobile) : dans le doute on
ne touche pas pour l'instant
2. la cabine n'est pas en zone blanche.
Dans ce cas on peut soit
-être un peu bourrins et changer amenity=telephone en historic=telephone
Tout en sachant qu'un grand nombre d'entre elles ont été démantelées.
-être plus mesuré et rajouter un fixme="Cette ancienne cabine téléphonique
n'est très certainement plus en service. Vérifier sur le terrain si elle
existe encore. Si elle a été transformée en boîte à livres, merci de
l'indiquer avec amenity=public_bookcase"

Ma préférence va à la seconde solution avec en complément une mission
pic4review voir un projet du mois pour nettoyer tout ça.

Le lun. 1 juin 2015 à 09:29, Damouns  a écrit :

> A Grenoble l'année dernière, j'ai vu démonter plusieurs cabines
> téléphoniques située dans des quartiers différents, dans l'espace
> d'une semaine.
>
> Comme je les avais cartographiées auparavant je me suis dit qu'il
> fallait que je me programme un petit tour de vérification pour voir
> lesquelles sont encore en place. Mais je n'ai pas eu le temps de le
> faire depuis.
>
> En 2013 j'avais fais un post à ce propos :
> http://www.openstreetmap.org/user/Damouns/diary/20175
>
> Toujours de pas de données en "open data" produites par Orange ou
> l'Arcep, aujourd'hui en 2015.
>
> Damouns
>
> Le 1 juin 2015 01:37, Donat ROBAUX  a écrit :
> > Bonsoir à tous,
> >
> > Un petit clin d'oeil à tous nos mappeurs fous:
> >
> http://www.estrepublicain.fr/edition-de-besancon/2015/05/31/besancon-a-terme-deux-cabines-telephoniques
> >
> > Leur localisation va devenir un service public à part entière. Elles vont
> > être plus dures à trouver qu'une cache de géocaching! A moins qu'Orange
> nous
> > fournisse la liste géoréférencée...
> > Plus sérieusement, j'imagine que dans quelques années, lorsque le
> mouvement
> > de disparition des cabines sera fini, il y aura un grand nettoyage à
> faire
> > pour ne garder que celles qui sont encore debout.
> >
> > Votre avis?
> >
> > Donat
> >
> > PS: hâte de voir les documents du SOTMFR!
> >
> > ___
> > Talk-fr mailing list
> > Talk-fr@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-fr
> >
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>


-- 

*Florian Lainez*
@overflorian 
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr


Re: [Talk-GB] TfL cycle data published - schema mapping

2019-10-02 Thread Dave F via Talk-GB

Bike riders may like to read about  the latest mess concerning cycle lanes:

https://www.cyclinguk.org/blog/underhand-law-change-undermines-mandatory-cycle-lanes?fbclid=IwAR1oqOMvD9XjMFrLwKAr65Jw-8ifm0qXSNshRe7yhbKiZ2h7-sVlxsXLbyU

DaveF

On 22/09/2019 15:45, Mike Baggaley wrote:

I would prefer not to see cycleway:lane=mandatory as this suggests that 
cyclists have to use the lane when set. In the UK, the significance of the 
solid white line separating a cycle lane and main carriageway is that motor 
vehicles are not allowed to use the cycle lane, but cyclists can use either the 
cycle lane or main carriageway. I would only want to see mandatory used if 
there is also a separate sign prohibiting cyclists from the road (and I am not 
sure whether any of these exist). I suggest cycleway:lane={exclusive|advisory} 
which are existing tags according to the wiki. Note that UK cycle lanes can 
also be used by pedestrians, so are not strictly exclusive to cyclists.

Cheers,
Mike

• Mandatory/Advisory Cycle Lane: OSM has no differentiation between
mandatory (solid white line) and advisory (dashed white line) lane,
probably because this distinction is rare elsewhere in the world. A new tag
cycleway:lane={mandatory|advisory} is proposed as a backwards-compatible
addition that elaborates on cycleway=lane. This would be useful for routing
engines, who could infer a level of commitment to cyclists at each such
location.
https://bikedata.cyclestreets.net/tflcid/conversion/#clt_mandat



___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb



___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


[OSM-talk] HOT Microgrants 2020 - Call for Applications

2019-10-02 Thread Rebecca Firth
 Hi,

Very pleased to announce the call for applications for HOT Microgrants 2020
! HOT wants to support the development of OSM communities worldwide through
providing small grants to assist their activities. This year we're
providing Microgrants at 2 levels; $200-1000, and $1000-7000 USD.

The form to pitch your project is relatively simple, and you can reach out
to microgra...@hotosm.org with any questions. Pitches are due by *9 October*.
More info: https://www.hotosm.org/updates/HOT-launches-Microgrants-2020/

Thanks,

Rebecca

-- 
*Rebecca Firth*
Director, Community & Partnerships
rebecca.fi...@hotosm.org
@RebeccaFirthy


*Humanitarian OpenStreetMap Team*
*Using OpenStreetMap for Humanitarian Response & Economic Development*
web  | twitter  | facebook
 | donate 
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


[talk-latam] HOT Microgrants 2020

2019-10-02 Thread Rebecca Firth
Hola a todos,

La convocatoria de propuestas para HOT Microgrants 2020 esta abierta hasta
9 de Octubre. Si quieres aplicar para una beca, puedes leer mas informacion
en este blog, o enviar un email a microgra...@hotosm.org:
https://www.hotosm.org/updates/HOT-launches-Microgrants-2020/

Saludos,

Rebecca

-- 
*Rebecca Firth*
Director, Community & Partnerships
rebecca.fi...@hotosm.org
@RebeccaFirthy


*Humanitarian OpenStreetMap Team*
*Using OpenStreetMap for Humanitarian Response & Economic Development*
web  | twitter  | facebook
 | donate 
___
talk-latam mailing list
talk-latam@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-latam


Re: [Talk-GB] TfL cycle data published - schema mapping

2019-10-02 Thread Phillip Barnett
Apart from on motorways!

Sent from my iPhone

> On 2 Oct 2019, at 09:37, Andy Allan  wrote:
> 
>> On Wed, 2 Oct 2019 at 05:22, Wulf4096  wrote:
>> 
>> Hello,
>> in Germany we've got "Radfahrstreifen" (solid line) which are
>> additionally marked by bicycle signs. Only cyclists may use those, and
>> the sign forbids cyclists to use the main carriageway, unless they've
>> got a reason to.
>> 
>> And we've got "Schutzstreifen" (dashed line). Legally, from the view of
>> a cyclist, those marking don't exist, as they don't impose any rules on
>> cyclists (this has been ruled by court).  Other traffic may not use the
>> dashed lanes unless they've got a reason to.
>> 
>> So I guess it's similar markings and rules?
> 
> Similar markings, but different rules. There is no implication in the
> UK that a cyclist has to use a cycle lane, regardless of markings. You
> can ignore a solid-line-lane and ride in any other traffic lane,
> without needing any reason.
> 
> Thanks,
> Andy
> 
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb

___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


[talk-au] Mailing lists (was: Re: Discussion H: public transport – the end game)

2019-10-02 Thread Andy Townsend

On 02/10/2019 08:19, Edoardo Neerhut wrote:
it would make sense to limit his communications so we're not bombarded 
daily with his emails.


At the risk of stating the bleeding obvious, one thing that it is 
perhaps worth mentioning is that in most mail clients it's perfectly 
possible to "file unseen" certain emails at the recipient end (provided 
you're not reading the digest, of course).  I think that I'd struggle to 
make sense of some OSM mailing lists without that as an option.


Best Regards,

Andy



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


[Talk-it] [import] gelatieri e pasticcieri FVG

2019-10-02 Thread Cascafico Giovanni
Ciao Lista,

ho abbozzato una wiki [1] in inglese per l'import regione Friuli
Venezia Giulia del dataset Confartigianato delle attività economiche.
Commentate pure alla sezione discussione [2] per strafalcioni,
chiarimenti, suggerimenti.

I dettagli sono ancora in sviluppo. Se il pilota gelatieri e
pasticceri va bene, proseguirò con le altre attività.




[1] https://wiki.openstreetmap.org/wiki/Import/Catalogue/AlimentareFVG
[2] https://wiki.openstreetmap.org/wiki/Talk:Import/Catalogue/AlimentareFVG

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


Re: [Talk-GB] TfL cycle data published - schema mapping

2019-10-02 Thread Andy Allan
On Wed, 2 Oct 2019 at 05:22, Wulf4096  wrote:

> Hello,
> in Germany we've got "Radfahrstreifen" (solid line) which are
> additionally marked by bicycle signs. Only cyclists may use those, and
> the sign forbids cyclists to use the main carriageway, unless they've
> got a reason to.
>
> And we've got "Schutzstreifen" (dashed line). Legally, from the view of
> a cyclist, those marking don't exist, as they don't impose any rules on
> cyclists (this has been ruled by court).  Other traffic may not use the
> dashed lanes unless they've got a reason to.
>
> So I guess it's similar markings and rules?

Similar markings, but different rules. There is no implication in the
UK that a cyclist has to use a cycle lane, regardless of markings. You
can ignore a solid-line-lane and ride in any other traffic lane,
without needing any reason.

Thanks,
Andy

___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb


[Talk-de] Fragen, Anregung eines Neulings

2019-10-02 Thread Albrecht Mehl via Talk-de

Vor einer Autofahrt von

  Darmstadt, Veilchenweg 7

nach

  Münster, Achtermannstr. 24

habe ich auch OSM befragt, weil mir auf GoogleMap eine Information 
fehlte. ABER ...


1. Route unverständlich
===

Auf der Seite


https://routing.openstreetmap.de/?z=15=50.738180%2C8.291759=49.908459%2C8.647996=51.956580%2C7.632351=de=0=0

erhalte ich zwei unverständliche Umleitungen:

  - die A5 nicht bis zum Gambacher Kreuz, sondern vorher Abfahrt
um Butzbach, Langengöns
  - um Herborn herum auf der B277,

und das ohne jegliche Begründung - Unfall, Unwetter usw. Bei GoogleMap 
und bei ADAC waren beide Umleitungen nicht vorhanden, so dass ich 
vorgestern am Sonntag, wie dort vorgeschlagen, ohne die Umleitungen und 
problemlos gefahren bin.


  Wie kommt es zu solch falschen Vorschlägen?

2. Abschnittsweise Schnellinformation bei den Reisedetails
==

Die Reisedetails rechts zeigen die Reise in vielen, vielen Einzelheiten 
- ich habe sie nicht gezählt - auf. Es wäre schön, wenn es neben dieser 
'Vollinformation', für die ich dankbar bin, noch eine 
Abschnittsinformation gäbe:


  - bis zur Autobahn
  - auf der Autobahn bis zur ersten Streckenänderung, in meinem
Fall von der A5 am Gambacher Kreuz auf die A45
  - bis zur nächsten Streckenänderung, d.h. bis zum Westhofener
Kreuz
  - bis zur Ausfahrt Münster Süd
  - in die Stadt

GoogleMap bietet das ungefähr an.

Ist vorstellbar, dass jemand - eine Gruppe - so etwas
bei OSM ermöglicht?

3. Schnellorientierung anhand der Ausfahrten/Kreuz-Nummern
==

Schön wäre es, wenn ähnlich wie bei GoogleMap die Nummern in den Details 
angegeben wären.


4. Markierung der Rastplätze


Etliche Rastplätze sind mit Liebe zum Detail gezeichnet. Mir fehlte 
jedoch bei der Planung der Fahrt die Möglichkeit, im kleinen Maßstab auf 
die Schnelle Parkplätze, markiert z.B. mit einem P-Symbol, zu finden. 
Nicht jeder möchte sich die Karte groß zoomen und dann Kilometer für 
Kilometer nach einem Parkplatz Ausschau halten. Dass man später bei 
einem bestimmten Parkplatz dann noch die Ausstattung ansehen kann, ist 
nur eine Zugabe - Hauptsache ist die _schnelle_ Orientierung.


5. Rastplätze mit Toilette
==

Gerne möchte man bei der Planung sich etwa folgendes merken - Nummern 
sind ausgedacht, stimmen nicht:


   Rastplätze mit Toilette gibt es

   - zwischen 11 und 12
   - zwischen 14 und 15
   - zwischen 20 und 21

und diese Information, wie geschildert, möglichst einfach finden können.
Also müsste das Symbol 'P + WC' auch noch - oder wieder - deutlich auch 
auf Karte zu sehen sein, wenn sie recht klein ist.


Wie im Betreff geschrieben, bin ich Neuling, schreibe hier zum ersten 
Mal, weiß nicht, ob dies der richtige Ort, solche Fragen zu stellen, 
ist. Es ist immer misslich, bei opensource-Projekten nur Anregungen zu 
geben, selbst aber nichts beizutragen. Ich fürchte, dass ich als 
Achtzigjähriger auch künftig nicht sonderlich viel helfen kann - aber 
wie der Darmstädter sagt:


   Mer wert ja mol froe dörfe!

A. Mehl
--
Albrecht Mehl   
Veilchenweg 7   |Tel. (06151) 37 39 92
64291 Darmstadt, Germany|sehenswert - ungefähr 'Wir einsam im All'
 http://www.phrenopolis.com/perspective/solarsystem/index.html

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


Re: [OSM-talk-fr] switch2OSM

2019-10-02 Thread Florimond Berthoux
Bonjour,

Page accessible de la carte après trois clics et deux pages en
cherchant beaucoup, c'est trop loin.
La mention devrait être faite *sur* la page de la carte à mon avis.

Le mar. 1 oct. 2019 à 21:48, Vincent de Château-Thierry
 a écrit :
>
> Bonsoir,
>
> Le 28/09/2019 à 22:48, osm.sanspourr...@spamgourmet.com a écrit :
> >
> > Et le lien
> > https://blog.mappy.com/entreprise/conditions-dutilisations/copyright/
> >
> > © Mappy 2018. Tous droits réservés, reproduction interdite.
> >
> > Par vraiment ODbL mais s'ils parlent des tuiles pourquoi pas.
> >
> > Et les différentes sources de données se voient attribuées les
> > copyrights qui vont bien.
> >
> > Toutes ? Non visiblement on peut se moquer des données communautaires et
> > des collectivités :
> >
> > 2. AUTRES DONNÉES GÉOGRAPHIQUES
> > Natural Earth
> > GeoNames
> > OpenStreetMap
> > IleDeFranceMobilité
> > Toulouse
> > Lorient
> > Lille
> >
> > Oui, aucun lien vers les copyrights et conditions d'utilisation respectifs.
>
> Prise de contact ce matin, résultat cet après-midi : la page
> https://blog.mappy.com/entreprise/conditions-dutilisations/copyright/
> mentionne désormais "© les contributeurs OpenStreetMap" avec le lien qui
> va bien vers https://www.openstreetmap.org/copyright.
>
> vincent
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr



-- 
Florimond Berthoux

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


Re: [talk-au] Discussion H: public transport – the end game

2019-10-02 Thread Edoardo Neerhut
Frederik, the mailing list has been very patient and responsive to every
email Herbert has sent. They have provided many thoughtful and positive
responses and suggestions on how he can engage with the mailing list.

There has been no response from him.

For the health of the mailing list, it would make sense to limit his
communications so we're not bombarded daily with his emails. Herbert if you
wish to respond and acknowledge this email, please do prove me wrong. The
community welcomes new OpenStreetMappers.

On Wed, 2 Oct 2019 at 17:11, Frederik Ramm  wrote:

> Ewen,
>
> thank you for trying to be constructive in this matter. Herbert seems to
> have considerable difficulties with the medium It sounds like he has
> been collecting issues for a while and now tries to resolve them all at
> once, which can overload the capacity of the mailing list for reasonable
> discussion, as well as his own.
>
> Reaching out in the way you have done it here is commendable and I hope
> that Herbert will take you up on the offer. I would like to appeal to
> those who are already calling for a "mailing list ban" to have more
> patience. Mailing lists can be difficult to handle for someone who is
> new to the game and has perhaps spent a lifetime using other, more
> formalised forms of communication. Yes, there can be times when we need
> to kick someone out because productive discussion is not possible, but I
> feel that it we should try and be welcoming even to people who don't
> "get" us at their first attempt. They can turn out to be valuable
> members of the community, bringing different views to the table and
> broadening our horizon.
>
> Bye
> Frederik
>
> --
> Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"
>
> ___
> Talk-au mailing list
> Talk-au@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-au
>
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [talk-au] Discussion H: public transport – the end game

2019-10-02 Thread Frederik Ramm
Ewen,

thank you for trying to be constructive in this matter. Herbert seems to
have considerable difficulties with the medium It sounds like he has
been collecting issues for a while and now tries to resolve them all at
once, which can overload the capacity of the mailing list for reasonable
discussion, as well as his own.

Reaching out in the way you have done it here is commendable and I hope
that Herbert will take you up on the offer. I would like to appeal to
those who are already calling for a "mailing list ban" to have more
patience. Mailing lists can be difficult to handle for someone who is
new to the game and has perhaps spent a lifetime using other, more
formalised forms of communication. Yes, there can be times when we need
to kick someone out because productive discussion is not possible, but I
feel that it we should try and be welcoming even to people who don't
"get" us at their first attempt. They can turn out to be valuable
members of the community, bringing different views to the table and
broadening our horizon.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"

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


Re: [OSM-talk-fr] switch2OSM - Mappy.com

2019-10-02 Thread Cyrille37 OSM

Le 01/10/2019 à 21:47, Vincent de Château-Thierry a écrit :
Prise de contact ce matin, résultat cet après-midi : la page 
https://blog.mappy.com/entreprise/conditions-dutilisations/copyright/ 
mentionne désormais "© les contributeurs OpenStreetMap" avec le lien 
qui va bien vers https://www.openstreetmap.org/copyright.


Bravo! Efficace.

Cyrille37.


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


Re: [talk-au] Discussion H: public transport – the end game

2019-10-02 Thread Joshua Brown via Talk-au
+1 to the above on these emails.

Happy to support either a ban or education on mailing list practice.

-Josh


> On 2 Oct 2019, at 4:32 pm, Mateusz Konieczny  wrote:
> 
> +1 this is getting absurd.
> 
> What is the process for mailing list ban?
> 
> 2 Oct 2019, 01:40 by e...@mapillary.com:
> +1 to what Ewen said.
> 
> If we don't hear back from you I am in favour of blocking your emails. 
> 
> On Wed, 2 Oct 2019 at 09:39, Ewen Hill  > wrote:
> Herbert,
> Can we slow down a little and finalise one of these items and then move 
> on to the next please. We don't get much feedback from you after a number of 
> us have offered suggestions. There are no "thanks", no, "If you look at this 
> relation/way then this appears different". 
> 
> I would be only too happy to discuss offline some of your issues in a 
> Skype or email or any other method you wish. I, along with others would like 
> to know what the end game is. Are you doing a paper on OSM or are you a 
> committed editor or new to OSM. A lot of your questions could be answered by 
> Google or via the vast amount of information in the Wiki.
> 
>   I look forward to hearing from you off the list.
> 
> Ewen
> 
> On Wed, 2 Oct 2019 at 09:23, Herbert.Remi via Talk-au 
> mailto:talk-au@openstreetmap.org>> wrote:
> # Discussion H: public transport – the end game
> 
> Bus routes (relations) were changed in the ACT in 2019 with the introduction 
> of Civic to Gungahlin light rail, effective 29 April 2019. The bus network in 
> Canberra changed from a mesh network (bumble buses) to a “hub and spoke” 
> system, the “Rapid” bus network. Now, fast buses connect town centres and you 
> change for local connections. This was a radical change with many bus routes 
> being abolished and news one established. The new “spoke” routes are name R1, 
> R2, … to R10. The route R1 is not a bus route at all but the Civic to 
> Gungahlin light rail.
> 
> Summary of changes required to OSM relations:
> - Many routes deleted
> - New routes added
> - Nomenclature of all routes changed.
> 
> Resources
> 1. A detailed, folded poster map that shows all the new routes. I am aware 
> this is almost useless for the online community. Locals can get a copy for 
> free.
> *Canberra Transport Guide: your guide to Canberra’s bus and light rail 
> network*, Transport Canberra, 2019.
> 2. A DINA4 overview map of the Rapid bus network can be found on the ACT 
> Government website for a map.
> https://www.transport.act.gov.au/getting-around/timetables/routes-by-number 
> 
> 3. The Transport Canberra website has a wealth of information about the bus 
> network in general.
> https://www.transport.act.gov.au/ 
> 
> 
> QUESTION
> An audit and possible correction of all bus routes are required, similar to 
> the audit of all bike routes (discussion G). Some routes may have been 
> changed already and others are forgotten.
> **How to do this?**
> I am hoping that somebody may have experience with this sort of problem in 
> other cities.
> 
> I welcome your comments.
> keywords: Australia, ACT, bus network, ACT Government, TCCS, light rail, 
> relation, public transport
> ___
> Talk-au mailing list
> Talk-au@openstreetmap.org 
> https://lists.openstreetmap.org/listinfo/talk-au 
> 
> 
> 
> -- 
> Warm Regards
> 
> Ewen Hill
> Internet Development Australia
> ___
> Talk-au mailing list
> Talk-au@openstreetmap.org 
> https://lists.openstreetmap.org/listinfo/talk-au 
> 
> ___
> Talk-au mailing list
> Talk-au@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-au

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


Re: [talk-cz] nefunguje tracer LPIS

2019-10-02 Thread Zdeněk Pražák
díky za rychlou opravu

út 1. 10. 2019 v 20:05 odesílatel Marián Kyral  napsal:

> Ahoj,
>
> díky za nahlášení. Nějak jsem ho opravil ;-) (aktualizovali knihovnu a ta
> tak trochu změnila název :-( )
>
> Marián
>
>
> Dne 01. 10. 19 v 18:16 Zdeněk Pražák napsal(a):
>
> Nějak přestal fungovat tracer LPIS - po kliknutí se nic neděje
> Pražák
>
> ___
> talk-cz mailing 
> listtalk-cz@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-czhttps://openstreetmap.cz/talkcz
>
> ___
> talk-cz mailing list
> talk-cz@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-cz
> https://openstreetmap.cz/talkcz
>
___
talk-cz mailing list
talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz
https://openstreetmap.cz/talkcz


Re: [talk-au] Discussion H: public transport – the end game

2019-10-02 Thread Mateusz Konieczny
+1 this is getting absurd.

What is the process for mailing list ban?
2 Oct 2019, 01:40 by e...@mapillary.com:

> +1 to what Ewen said.
>
> If we don't hear back from you I am in favour of blocking your emails. 
>
> On Wed, 2 Oct 2019 at 09:39, Ewen Hill <> ewen.h...@gmail.com 
> > > wrote:
>
>> Herbert,
>>     Can we slow down a little and finalise one of these items and then move 
>> on to the next please. We don't get much feedback from you after a number of 
>> us have offered suggestions. There are no "thanks", no, "If you look at this 
>> relation/way then this appears different". 
>>
>>     I would be only too happy to discuss offline some of your issues in a 
>> Skype or email or any other method you wish. I, along with others would like 
>> to know what the end game is. Are you doing a paper on OSM or are you a 
>> committed editor or new to OSM. A lot of your questions could be answered by 
>> Google or via the vast amount of information in the Wiki.
>>
>>   I look forward to hearing from you off the list.
>>
>> Ewen
>>
>> On Wed, 2 Oct 2019 at 09:23, Herbert.Remi via Talk-au <>> 
>> talk-au@openstreetmap.org >> > wrote:
>>
>>> # Discussion H: public transport – the end game
>>>
>>> Bus routes (relations) were changed in the ACT in 2019 with the 
>>> introduction of Civic to Gungahlin light rail, effective 29 April 2019. The 
>>> bus network in Canberra changed from a mesh network (bumble buses) to a 
>>> “hub and spoke” system, the “Rapid” bus network. Now, fast buses connect 
>>> town centres and you change for local connections. This was a radical 
>>> change with many bus routes being abolished and news one established. The 
>>> new “spoke” routes are name R1, R2, … to R10. The route R1 is not a bus 
>>> route at all but the Civic to Gungahlin light rail.
>>>
>>> Summary of changes required to OSM relations:
>>> - Many routes deleted
>>> - New routes added
>>> - Nomenclature of all routes changed.
>>>
>>> Resources
>>> 1. A detailed, folded poster map that shows all the new routes. I am aware 
>>> this is almost useless for the online community. Locals can get a copy for 
>>> free.
>>> *Canberra Transport Guide: your guide to Canberra’s bus and light rail 
>>> network*, Transport Canberra, 2019.
>>> 2. A DINA4 overview map of the Rapid bus network can be found on the ACT 
>>> Government website for a map.
>>> https://www.transport.act.gov.au/getting-around/timetables/routes-by-number 
>>> 
>>> 3. The Transport Canberra website has a wealth of information about the bus 
>>> network in general.
>>> https://www.transport.act.gov.au/ 
>>>
>>>
>>> QUESTION
>>> An audit and possible correction of all bus routes are required, similar to 
>>> the audit of all bike routes (discussion G). Some routes may have been 
>>> changed already and others are forgotten.
>>> **How to do this?**
>>> I am hoping that somebody may have experience with this sort of problem in 
>>> other cities.
>>>
>>> I welcome your comments.
>>> keywords: Australia, ACT, bus network, ACT Government, TCCS, light rail, 
>>> relation, public transport
>>> ___
>>>  Talk-au mailing list
>>>  >>> Talk-au@openstreetmap.org 
>>>  >>> https://lists.openstreetmap.org/listinfo/talk-au 
>>> 
>>>
>>
>>
>> -- 
>> Warm Regards
>>
>> Ewen Hill
>> Internet Development Australia
>> ___
>>  Talk-au mailing list
>>  >> Talk-au@openstreetmap.org 
>>  >> https://lists.openstreetmap.org/listinfo/talk-au 
>> 
>>___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au