Re: [Talk-us] US Bureau of Land Management Boundaries

2019-01-05 Per discussione Martijn van Exel
Brad — I make use of BLM / NPS / NF boundary data a lot too. I use Gaia GPS for 
this, which overlays this data nicely with what’s in OSM[1]. There are lots of 
other outdoor apps that do the same. I prefer this data live outside of OSM as 
well for similar reasons as Ian stated. Knowing whether land is public or 
private or whether it’s inside or outside a NP, is important to me when I’m in 
the outdoors. I would much rather rely on an authoritative definition of these 
boundaries, than on whatever happens to be in OSM. Since there is no 
on-the-ground verifiability, boundary data is prone to growing stale, as you 
can see happening with census place boundaries. Unreliable data in this case is 
worse than no data at all.
If you’re looking to make a great impact on the map as an outdoors user, I 
would suggest mapping things you know and things you observe when you’re out 
there. Countless times have I been out in the middle of nowhere, to find that 
some mapper before me added a landmark, a water source, or something else that 
really helped me. That is what I like to pay forward.

Martijn

[1] https://www.gaiagps.com/offroad/#maps 
 

> On Jan 5, 2019, at 8:43 PM, brad  wrote:
> 
> Ian, 
> I want to import this data because I think its important for a complete map.  
>  We have national forest, wilderness  and national park boundaries in OSM!   
> This is no different.   If you look at many maps they show all of them.
> 
> I'd like it to show up on any map that I use.   I'm working on a 'better' 
> version for garmin using mkgmap.   I hope it gets rendered with OpenAndroMaps 
> too.   I haven't used the onine osm.org map very much.
> 
> I am excited to participate and improve OSM and in my opinion this is a big 
> gap in the OSM database.   Where I live, we don't use OSM for building 
> footprints, we use it to find our way in the national forest, the BLM land 
> and the national parks.   It's very useful to know what is public or private 
> land.
> 
> Brad 
> 
> On 1/5/19 8:19 PM, Ian Dees wrote:
>> Hi Brad, thanks for proposing this import and posting it here.
>> 
>> I would strongly prefer that we not import boundaries like this into OSM. 
>> Boundaries of all sorts are almost impossible to verify with OSM's "on the 
>> ground" rule, but BLM boundaries in particular are such an edge case (they 
>> have no other analog in the world, really) and almost never have apparent 
>> markings on the ground to check. Since these boundaries aren't visible, this 
>> data can never be improved by an OpenStreetMap contributor. The boundaries 
>> are defined by the government, and any sort of change to them would make 
>> them diverge from the official source.
>> 
>> But having said that, I'm curious why you wanted to import this data? Did 
>> you want to have it show up on the osm.org  map? Are you 
>> trying to build a custom map? Or are you excited to participate and improve 
>> OSM? If it's the latter, there's lots of other data that is a better fit to 
>> import into OSM: address points and building footprints come to mind, for 
>> example.
>> 
>> -Ian
>> 
>> On Sat, Jan 5, 2019 at 9:03 PM brad > > wrote:
>> I'd like to import BLM (US Bureau of Land Management) boundaries into 
>> OSM.This is not an automated import as you can see from my workflow.
>> 
>> Workflow:
>> Download shape file from PADUS (1 state at a time): 
>> https://gapanalysis.usgs.gov/padus/data/download/ 
>> 
>> Load into Qgis and filter for BLM boundaries
>> Clean up as necessary (there are some extraneous ways at state 
>> boundaries & elsewhere)
>> 
>> Convert to OSM with ogr2osm and the following tags
>>  tags.update({'type':'boundary'})
>>  tags.update({'boundary':'protected_area'})
>>  tags.update({'operator':'BLM'})
>>  tags.update({'ownership':'national'})
>>  tags.update({'protect_class':'27'})
>>  tags.update({'source':'US BLM'})
>>  use the shapefile attribute 'Unit_Nm' as the name
>> 
>> Import with JOSM
>> 
>> The San Luis unit (CO) is here for your inspection.
>> https://www.dropbox.com/s/qxv5gny2396ewki/sanLuisBLM.osm?dl=0 
>> 
>> 
>> Comments?
> 
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us

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


Re: [Talk-us] US Bureau of Land Management Boundaries

2019-01-05 Per discussione Ian Dees
On Sat, Jan 5, 2019 at 10:42 PM Joseph Eisenberg 
wrote:

> This data is no less verifiable than national forest boundaries and
> federal wilderness boundaries; these generally need to be checked against
> official sources, just as BLM boundaries will.
>
> Municipal boundaries are perhaps even harder to verify than boundaries of
> BLM land and National Forests in some States.
>

Those things shouldn't be in OSM either. They make it harder for people to
map and are out of date the moment the data is converted. If you want to
see this information on a map, it's available from the original source for
you to add to your own map. It's the same sort of data that can not be
improved by the community, so It doesn't belong in OSM.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] US Bureau of Land Management Boundaries

2019-01-05 Per discussione Joseph Eisenberg
This data is no less verifiable than national forest boundaries and federal
wilderness boundaries; these generally need to be checked against official
sources, just as BLM boundaries will.

Municipal boundaries are perhaps even harder to verify than boundaries of
BLM land and National Forests in some States.

But I wonder about using boundary=protected_area and class 27 for BLM land.
While this fits with the wiki definition of “land owned by the
public/government”, it’s odd to include this under protected_area, and it
is not specific.

If you are adding BLM lands that have any specific protection or planned
usage it would be good to try to find more specific classes, when possible.

There was a comment about this on the wiki discussion page:
https://wiki.openstreetmap.org/wiki/Talk:Tag:boundary%3Dprotected_area#Relationship_of_public.2FGovernment_and_protection
On Sun, Jan 6, 2019 at 12:45 PM brad  wrote:

> Ian,
> I want to import this data because I think its important for a complete
> map.   We have national forest, wilderness  and national park boundaries in
> OSM!   This is no different.   If you look at many maps they show all of
> them.
>
> I'd like it to show up on any map that I use.   I'm working on a 'better'
> version for garmin using mkgmap.   I hope it gets rendered with
> OpenAndroMaps too.   I haven't used the onine osm.org map very much.
>
> I am excited to participate and improve OSM and in my opinion this is a
> big gap in the OSM database.   Where I live, we don't use OSM for building
> footprints, we use it to find our way in the national forest, the BLM land
> and the national parks.   It's very useful to know what is public or
> private land.
>
>
> Brad
>
> On 1/5/19 8:19 PM, Ian Dees wrote:
>
> Hi Brad, thanks for proposing this import and posting it here.
>
> I would strongly prefer that we not import boundaries like this into OSM.
> Boundaries of all sorts are almost impossible to verify with OSM's "on the
> ground" rule, but BLM boundaries in particular are such an edge case (they
> have no other analog in the world, really) and almost never have apparent
> markings on the ground to check. Since these boundaries aren't visible,
> this data can never be improved by an OpenStreetMap contributor. The
> boundaries are defined by the government, and any sort of change to them
> would make them diverge from the official source.
>
> But having said that, I'm curious why you wanted to import this data? Did
> you want to have it show up on the osm.org map? Are you trying to build a
> custom map? Or are you excited to participate and improve OSM? If it's the
> latter, there's lots of other data that is a better fit to import into OSM:
> address points and building footprints come to mind, for example.
>
> -Ian
>
> On Sat, Jan 5, 2019 at 9:03 PM brad  wrote:
>
>> I'd like to import BLM (US Bureau of Land Management) boundaries into
>> OSM.This is not an automated import as you can see from my workflow.
>>
>> Workflow:
>> Download shape file from PADUS (1 state at a time):
>> https://gapanalysis.usgs.gov/padus/data/download/
>> Load into Qgis and filter for BLM boundaries
>> Clean up as necessary (there are some extraneous ways at state
>> boundaries & elsewhere)
>>
>> Convert to OSM with ogr2osm and the following tags
>>  tags.update({'type':'boundary'})
>>  tags.update({'boundary':'protected_area'})
>>  tags.update({'operator':'BLM'})
>>  tags.update({'ownership':'national'})
>>  tags.update({'protect_class':'27'})
>>  tags.update({'source':'US BLM'})
>>  use the shapefile attribute 'Unit_Nm' as the name
>>
>> Import with JOSM
>>
>> The San Luis unit (CO) is here for your inspection.
>> https://www.dropbox.com/s/qxv5gny2396ewki/sanLuisBLM.osm?dl=0
>>
>> Comments?
>>
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] US Bureau of Land Management Boundaries

2019-01-05 Per discussione brad

Ian,
I want to import this data because I think its important for a complete 
map.   We have national forest, wilderness  and national park boundaries 
in OSM!   This is no different.   If you look at many maps they show all 
of them.


I'd like it to show up on any map that I use.   I'm working on a 
'better' version for garmin using mkgmap.   I hope it gets rendered with 
OpenAndroMaps too.   I haven't used the onine osm.org map very much.


I am excited to participate and improve OSM and in my opinion this is a 
big gap in the OSM database.   Where I live, we don't use OSM for 
building footprints, we use it to find our way in the national forest, 
the BLM land and the national parks.   It's very useful to know what is 
public or private land.


Brad

On 1/5/19 8:19 PM, Ian Dees wrote:

Hi Brad, thanks for proposing this import and posting it here.

I would strongly prefer that we not import boundaries like this into 
OSM. Boundaries of all sorts are almost impossible to verify with 
OSM's "on the ground" rule, but BLM boundaries in particular are such 
an edge case (they have no other analog in the world, really) and 
almost never have apparent markings on the ground to check. Since 
these boundaries aren't visible, this data can never be improved by an 
OpenStreetMap contributor. The boundaries are defined by the 
government, and any sort of change to them would make them diverge 
from the official source.


But having said that, I'm curious why you wanted to import this data? 
Did you want to have it show up on the osm.org  map? 
Are you trying to build a custom map? Or are you excited to 
participate and improve OSM? If it's the latter, there's lots of other 
data that is a better fit to import into OSM: address points and 
building footprints come to mind, for example.


-Ian

On Sat, Jan 5, 2019 at 9:03 PM brad > wrote:


I'd like to import BLM (US Bureau of Land Management) boundaries into
OSM.    This is not an automated import as you can see from my
workflow.

Workflow:
Download shape file from PADUS (1 state at a time):
https://gapanalysis.usgs.gov/padus/data/download/
Load into Qgis and filter for BLM boundaries
Clean up as necessary (there are some extraneous ways at state
boundaries & elsewhere)

Convert to OSM with ogr2osm and the following tags
 tags.update({'type':'boundary'})
 tags.update({'boundary':'protected_area'})
 tags.update({'operator':'BLM'})
 tags.update({'ownership':'national'})
 tags.update({'protect_class':'27'})
 tags.update({'source':'US BLM'})
 use the shapefile attribute 'Unit_Nm' as the name

Import with JOSM

The San Luis unit (CO) is here for your inspection.
https://www.dropbox.com/s/qxv5gny2396ewki/sanLuisBLM.osm?dl=0

Comments?



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


Re: [Talk-us] US Bureau of Land Management Boundaries

2019-01-05 Per discussione Ian Dees
Hi Brad, thanks for proposing this import and posting it here.

I would strongly prefer that we not import boundaries like this into OSM.
Boundaries of all sorts are almost impossible to verify with OSM's "on the
ground" rule, but BLM boundaries in particular are such an edge case (they
have no other analog in the world, really) and almost never have apparent
markings on the ground to check. Since these boundaries aren't visible,
this data can never be improved by an OpenStreetMap contributor. The
boundaries are defined by the government, and any sort of change to them
would make them diverge from the official source.

But having said that, I'm curious why you wanted to import this data? Did
you want to have it show up on the osm.org map? Are you trying to build a
custom map? Or are you excited to participate and improve OSM? If it's the
latter, there's lots of other data that is a better fit to import into OSM:
address points and building footprints come to mind, for example.

-Ian

On Sat, Jan 5, 2019 at 9:03 PM brad  wrote:

> I'd like to import BLM (US Bureau of Land Management) boundaries into
> OSM.This is not an automated import as you can see from my workflow.
>
> Workflow:
> Download shape file from PADUS (1 state at a time):
> https://gapanalysis.usgs.gov/padus/data/download/
> Load into Qgis and filter for BLM boundaries
> Clean up as necessary (there are some extraneous ways at state
> boundaries & elsewhere)
>
> Convert to OSM with ogr2osm and the following tags
>  tags.update({'type':'boundary'})
>  tags.update({'boundary':'protected_area'})
>  tags.update({'operator':'BLM'})
>  tags.update({'ownership':'national'})
>  tags.update({'protect_class':'27'})
>  tags.update({'source':'US BLM'})
>  use the shapefile attribute 'Unit_Nm' as the name
>
> Import with JOSM
>
> The San Luis unit (CO) is here for your inspection.
> https://www.dropbox.com/s/qxv5gny2396ewki/sanLuisBLM.osm?dl=0
>
> Comments?
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


[Talk-us] US Bureau of Land Management Boundaries

2019-01-05 Per discussione brad
I'd like to import BLM (US Bureau of Land Management) boundaries into 
OSM.    This is not an automated import as you can see from my workflow.


Workflow:
Download shape file from PADUS (1 state at a time): 
https://gapanalysis.usgs.gov/padus/data/download/

Load into Qgis and filter for BLM boundaries
Clean up as necessary (there are some extraneous ways at state 
boundaries & elsewhere)


Convert to OSM with ogr2osm and the following tags
    tags.update({'type':'boundary'})
    tags.update({'boundary':'protected_area'})
    tags.update({'operator':'BLM'})
    tags.update({'ownership':'national'})
    tags.update({'protect_class':'27'})
    tags.update({'source':'US BLM'})
    use the shapefile attribute 'Unit_Nm' as the name

Import with JOSM

The San Luis unit (CO) is here for your inspection.
https://www.dropbox.com/s/qxv5gny2396ewki/sanLuisBLM.osm?dl=0

Comments?

Brad


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


Re: [Talk-at] Frohes Neues Jahr

2019-01-05 Per discussione Friedrich Volkmann

On 01.01.2019 02:49, scubbx wrote:

Eine der bedeutendsten Ereignisse des vergangenen Jahres war bestimmt,
dass das Konzept von VectorTiles salonfähig wurde (und durch eine der
ersten Implementierungen durch das OpenMapTiles Projekt auf Basis von
OSM Daten in performanter und effizienter Weise umgesetzt wurde. (!) ).



Für das kommende Jahr sind wieder einige Stammtische geplant (ich selber
kann nur für Wien sprechen [...]
Es trifft sich gut, wenn wir gleich beides verbinden können. Darum hoffe ich 
auf einen Stammtisch-Termin, wo ich Zeit habe. ;-)


Dass sich bei den Vector Tiles einiges getan hat, ging an mir vorbei, aber 
das ist sicher eine gute Sache. Ich hab schon in Bezug auf Höhenlinien 
versucht, mich damit zu beschäftigen, aber noch ohne Erfolg. Aus den OGD hab 
ich vor 2 Jahren eine IMG-Datei für Garmin-Geräte gemacht 
(http://steige.info/osm/data/at_hl.img) und hier auf Talk-AT davon 
berichtet. Das hat keinen interessiert, weil ich hier der einzige bin, der 
im Gebirge unterwegs ist. Aber für diesen Zweck sind genaue Höhenlinien halt 
extrem wichtig. Mir selber nutzen diese Höhenlinien bei meinen Touren sehr. 
Nun fehlt noch was, damit man sich auch am PC eine Karte mit Höhenlinien 
anschauen kann. Ein Overlay (in Openlayers oder Leaflet), das man über die 
Standardkarte legt, wär schon mal besser als gar nichts, aber dazu muss man 
das Shapefile, das beim Erzeugen der Höhenlinien mit gdal_contour rauskommt, 
in Tiles (am besten natürlich vector tiles) umwandeln, und das hab ich noch 
nicht zusammengebracht.


--
Friedrich K. Volkmann   http://www.volki.at/
Adr.: Davidgasse 76-80/14/10, 1100 Wien, Austria

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


[Talk-GB] Changing highway=ford to ford=yes.

2019-01-05 Per discussione Dave F

Hi
I'm about to do a GB wide edit changing highway=ford (545) to ford=yes 
(4814). I know a few contributors like to get upset about wide area 
edits, even when they been discussed, so I thought I'd give you a heads up.


Please read https://wiki.openstreetmap.org/wiki/Tag:highway=ford for the 
reasons.


Yes, it has been discussed a couple of times on Tagging, & once on 
OSM-carto when deciding on the icon to use.
That those discussions happened a few years ago, & you may not have been 
involved, does not negate the reasons for the swap.


Cheers
DaveF

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


[OSM-talk-fr] Mon projet 2018 : le réseau Anjoubus

2019-01-05 Per discussione Adrien Grellier
Bonjour,

Il y a un an, je m'étais fixé comme projet 2018 la cartographie du
réseau de bus du Maine et Loire : Anjoubus. Un an plus tard, c'est fait,
avec quelques jours de retard !

Les lignes sont en principe bonnes, mais il manque des arrêts. Lorsque
j'avais un doute (pas de marque sur le terrain ou sur l'orthophoto,
etc.), j'ai préféré ne rien mettre. De même, les lignes « à la demande »
ne sont pas cartographiées.

Je me suis basé sur l'OpenData 49, BD Ortho, les horaires de bus sur le
site officiel ainsi que mes connaissances du terrain.

J'ai essayé de documenté au mieux sur le wiki l'avancée de mes travaux :
https://wiki.openstreetmap.org/wiki/Maine-et-Loire/Transports_en_commun

Voici mon petit retour d'expérience:
- J'ai mis du temps à comprendre le balisage OSM des bus, c'est assez
compliqué, d'autant que la cartographie existante (bus d'Angers, Cholet)
ne respecte pas vraiment le nouveau schéma ! Sans les aides de JOSM, il
est vraiment difficile de cartographier correctement une ligne de bus.
- Globalement ce qui ma pris du temps est la création des arrêts et le
découpage des routes. Anjoubus est principalement en zone rurale,
pratiquement aucun arrêts n'existaient dans OSM. La mise à jour et
correction des relations est nettement plus facile.
- l'OpenData est globalement bon, mais moins précis que OSM (indication
des bretelles, nom pas cohérent avec ceux sur le terrain…) et avec
quelques paradoxes parfois (arrêt à 500m de la ligne…). La complexité de
certaines lignes m'a également beaucoup surpris !
– Il aurait été intéressant que ce travail dans OSM soit fait par
AnjouBus directement…
– Je n'ai pas trouvé de rendu OSM des transports en communs pratique.
Par exemple je n'ai pas trouvé de rendu affichant les lignes de bus avec
leurs couleurs, comme sur le site officiel :
http://anjoubus.paysdelaloire.fr/lignes-regulieres/plan-et-horaires/carte-interactive/

Pour ceux qui seraient intéressé, les horaires sont également en
OpenData… il est donc probablement possible de les avoir dans Navitia à
peu de frais, et donc dans les appli type transportr, ce qui serait un
gros plus pour les déplacements train+bus par exemple.


Et vous, c'était quoi vos projets 2018 ? Avez-vous réussit à les faire ?

Bonne année 2019 !

Adrien




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


Re: [Talk-it] aiuto con relazione

2019-01-05 Per discussione Marco
perfetto, sembra che grazie alle vostre dritte sia riuscito a sistemare, 
sia la relazione che il tag wikipedia, grazie!


Il 05/01/2019 12:56, Federico Cortese ha scritto:

On Sat, Jan 5, 2019 at 12:25 PM Marco  wrote:

2) aver aggiunto il parcheggio come membro (inner)
https://www.openstreetmap.org/way/228761854

Il gruppo di modifiche incriminato è il 66043868


E' proprio quella way il problema, perchè è indicata come inner, ma
interseca il poligono esterno (outer) della foresta.

Secondo me non ha senso avere un multipoligono di quelle dimensioni,
nato nel settembre del 2009 dall'import della CTR Lombardia in scala
1:10.000.
Man mano che si apportano modifiche sarebbe opportuno ridurlo in
porzioni ridotte.
Per esempio in corrispondenza del parcheggio si potrebbe spezzare in
due poligoni separati, lasciando la rotatoria ed il parcheggio fuori
dalla foresta.

Ti segnalo anche che con lo stesso changeset hai aggiunto un tag
wikipedia usando un formato errato:
https://www.openstreetmap.org/way/298912981
Questo il modo corretto: https://wiki.openstreetmap.org/wiki/Key:wikipedia

Ciao,
Federico

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


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


Re: [Talk-transit] New Key "Interval"

2019-01-05 Per discussione Leif Rasmussen
Yes, I think so.  Most existing uses use "interval"= in
MM or M format.

On Sat, Jan 5, 2019, 8:34 AM Noémie Lehuby  Hello,
>
> Thanks for the doc update, I'll start to work on the French versions.
>
> Is there already some places on OSM that uses theses tags (interval,
> opening_hours and duration) ?
> I would like to work on an evolution in OSM2GTFS (a software that turns
> OSM data to GTFS file) to handle them ;)
>
> Cheers !
>
> --
> Noémie Lehuby
> Jungle Bus - http://junglebus.io
>
> Le 04/01/2019 à 16:33, Leif Rasmussen a écrit :
>
> Thanks for suggestion this!
> I have updated all of the wiki pages you sent to include the key
> "interval".  I also added "duration" as an option to some of the pages
> missing that key.
> Leif Rasmussen
>
> On Thu, Jan 3, 2019 at 7:59 AM Noémie Lehuby 
> wrote:
>
>> Hi,
>>
>> Before we move on to the next proprosal, can you please also update the
>> according pages in the wiki in English so we can start translating the doc
>> about this new tag ?
>>
>> I think we need to mention the new key in these pages at least:
>> https://wiki.openstreetmap.org/wiki/Relation:route#Tags
>>
>> https://wiki.openstreetmap.org/wiki/Relation:route_master#Other_useful_tags
>>
>> https://wiki.openstreetmap.org/wiki/Tag:route%3Dferry#Tags_to_use_in_combination
>> https://wiki.openstreetmap.org/wiki/Tag:route%3Dbus
>>
>> https://wiki.openstreetmap.org/wiki/Buses#Step_2_-_Create_the_new_bus_relations
>> https://wiki.openstreetmap.org/wiki/Tag:route%3Dsubway
>> https://wiki.openstreetmap.org/wiki/Tag:route%3Dtram
>>
>> https://wiki.openstreetmap.org/wiki/Tag:route%3Dtrain#How_to_tag_a_train_relation_.3F
>>
>> nlehuby
>>
>> Date: Wed, 2 Jan 2019 19:49:08 -0500
>> From: Leif Rasmussen <354...@gmail.com>
>> To: talk-transit@openstreetmap.org
>> Subject: [Talk-transit] New Key "Departures"
>> Message-ID:
>> 
>> Content-Type: text/plain; charset="utf-8"
>>
>> The new key "interval" for adding the departure times interval of a public
>> transport route was recently approved after two weeks of voting.
>> I have created a new wiki page to document this key:
>> https://wiki.openstreetmap.org/wiki/Key:interval
>>
>> Full schedule information, however, is still impossible.  I originally
>> proposed using "timetable relations" to add full schedule information to
>> routes.  I have since realized that this would be a disaster just waiting
>> to happen.
>> I have now simplified the proposal to be easier to add and maintain, while
>> still keeping most of the same information in the database.
>>
>> The key "departures" is my solution to keeping timetables simple and easy
>> to maintain.
>>
>>
>> https://wiki.openstreetmap.org/wiki/Proposed_features/Public_transport_schedules/Departures
>>
>> I would love feedback to help make this proposal work for everyone.  I
>> know that for many bus routes, it would be impossibly difficult to add
>> (and
>> maintain) full schedule information.  Those routes should therefore only
>> include the tag "interval".  Others, however, including many ferry routes,
>> would be very easy to add schedule information to.
>>
>> Thanks,
>> Leif Rasmussen
>>
>>
___
Talk-transit mailing list
Talk-transit@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-transit


Re: [OSM-talk] What use is OpenStreetMap?

2019-01-05 Per discussione john whelan
I've collected these ideas and put them together in the wiki.

https://wiki.openstreetmap.org/wiki/WikiProject_Canada/Building_Canada_2020/municipalities

I may have left one or two out but I think practically everything is
covered in the links.

Thanks all for the input.

Cheerio John

On Fri, 4 Jan 2019 at 05:29, François Lacombe 
wrote:

> Hi
>
> Big use cases for utilities, network operators and urban planning
>
> English: https://www.openstreetmap.org/user/InfosReseaux/diary/47030
> French:
> https://www.openstreetmap.fr/cartographier-mondialement-linfrastructure-avec-openstreetmap/
>
> Furthermore, OSM is the only one to build and share a worldwide tagging
> model. Users can take the data but they can take the tagging model also and
> use it to refine third party data.
>
> All the best
>
> François
>
> Le ven. 4 janv. 2019 à 08:40, Oleksiy Muzalyev <
> oleksiy.muzal...@bluewin.ch> a écrit :
>
>> A detailed map is an essential tool for firefighters, ambulance, and
>> police. And not only of the town itself but also of the countryside
>> especially along railways and automobile roads.
>>
>> The city of Stockholm built an interactive public transportation map on
>> the basis of OSM: https://sl.se/en/ . People can see still at home when
>> their bus is arriving at the stop.
>>
>> The city of Odessa created the similar public transportation map but on
>> the basis of a commercial map: http://transport.odessa.ua/ . It was
>> extremely useful web-application, one could see how the trams' geo-markers
>> were moving on the map. The web-application became very popular, and the
>> commercial map underneath stopped working normally for some, probably also
>> commercial, reason.
>>
>> I mean a  municipal project which is based on an open data map running on
>> the municipal server could be more resilient and affordable, especially if
>> it becomes popular.
>>
>> A big separate topic is e-commerce delivery services. A rookie delivery
>> driver may search for an address in a city in some cases for hours. This
>> excessive driving could be reduced significantly if a driver could see a
>> delivery address on the map. It would mean less pollution, accidents,
>> pavement wear.
>>
>> Best regards,
>> Oleksiy
>>
>> On 03.01.19 22:07, John Whelan wrote:
>>
>> I got a phone call from someone who works for a municipality who was
>> passed my phone number.  Basically asking from a municipal government point
>> of view was there any advantage to the municipality in having their
>> municipality mapped in detail in OpenStreetMap.
>>
>> Off the top of my head businesses etc can provide map of where they are
>> located without payment and list their web sites and phone numbers etc.
>>
>> Is there a web page somewhere that covers this?
>>
>> It is quite a serious question and I suspect will be used to justify some
>> expenditure and effort to help enrich the map.
>>
>> Thanks John
>>
>>
>> --
>> Sent from Postbox
>> 
>>
>> ___
>> talk mailing 
>> listtalk@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk
>>
>>
>> ___
>> talk mailing list
>> talk@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk
>>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk-fr] Cad'ortho de Noël...

2019-01-05 Per discussione marc marc
quel est la plus-value d'avoir l'info en double
dans la définition des couches <> dans le wiki osm.org ?

prenons le cas des dates... on a une umap basé sur eventmachin
que je suggérais d'intégrer dans les headers du proxy-ign pour avoir
une info "automatiquement à jour" dans les différents éditeurs.
deuzeffe a passé pas mal de temps à récolter les données pour la maj.
mais 6 mois + tard on a tjs les anciennes données.
alors dupliquer des attributions, avant que quelqu'un croie utile d'y 
passer du temps, faudrait p'tre voir si cela rencontre un besoin

Augustin tu peux en dire un peu plus ?

Le 04.01.19 à 22:53, Vincent Privat a écrit :
> Sachant que j'ai déjà listé par mal d'infos côté JOSM et que je continue 
> quand j'ai le temps:
> https://josm.openstreetmap.de/wiki/Maps/France
> 
> Mais tout le monde peut aider, le wiki est communautaire.
> A+
> Vincent
> 
> Le ven. 4 janv. 2019 à 14:43, Christian Quest  > a écrit :
> 
> C'est bien ce que j'envisageais... rajouter une colonne "attribution"
> 
> Le ven. 4 janv. 2019 à 13:47, Augustin Doury  > a écrit :
> 
> Merci pour le retour. Du coup on pourrait rajouter les
> attributions dans une nouvelle colonne du tableau de la page Wiki.
> 
> Après quelques recherches je trouve quelques pistes dans les
> issues Github qui référencent certaines sources :
> 
> https://github.com/osm-fr/infrastructure/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aopen+ortho
> 
> N'ayant pas participé à l'identification des sources et à leur
> intégration je ne suis pas sûr de pouvoir réellement aider, mais
> s'il y a davantage d'infos quelque part à éplucher je peux essayer.
> 
> Bonne journée,
> 
> Augustin
> 
> Le 2019-01-04 13:25, Christian Quest a écrit :
> 
>> Il faut compléter cette page de wiki.
>> Tout ce qui est dans ce tableau est sous licence ouverte, mais
>> effectivement les attributions sont différentes en fonction
>> des zones.
>> J'ai aussi prévu de générer des shapefile/geojson avec les
>> emprises de chaque source pour à terme avoir une API
>> interrogeable qui dit ce qu'on voit sur une zone donnée...
>>
>> Le ven. 4 janv. 2019 à 10:28, Augustin Doury
>> mailto:xh...@mykolab.com>> a écrit :
>>
>> Salut,
>> Un grand merci pour ce gros boulot d'aggrégation ! c'est
>> super.
>> Dans les crédits de la uMap on trouve ce lien :
>> 
>> https://wiki.openstreetmap.org/wiki/FR:Serveurs/wms.openstreetmap.fr
>> Y a-t-il un endroit où on trouve la liste des sources et
>> des licences associées ? elles sont issues d'ici
>> http://professionnels.ign.fr/orthohr-par-departements#tab-3 et
>> donc sous LO ?
>> Bonne journée,
>> Augustin
>>
>> Le 2019-01-04 08:35, HELFER Denis (SNCF RESEAU / SIEGE
>> SNCF RESEAU / DT GE PPE) a écrit :
>>
>> Enfin sur Lyon, l'orthophoto est surtout à 8 cm. La
>> prise de vue drone ( a 1 cm) ne concerne que moins de
>> 10 ha.
>>
>> *De :*Christian Quest [mailto:cqu...@openstreetmap.fr
>> ]
>> *Envoyé :* jeudi 3 janvier 2019 23:17
>> *À :* Discussions sur OSM en français
>> > >
>> *Objet :* Re: [OSM-talk-fr] Cad'ortho de Noël...
>>
>> Je viens d'ajouter le 54 (Meurthe et Moselle)
>> provenant de l'Ortho HR de 2015 publiée en opendata
>> par la région Grand Est.
>>
>> J'ai aussi ajouté l'ortho 2015 de Brest.
>>
>> Vous trouverez sur la carte umap des marqueurs pour
>> les ortho les plus récentes ou d'une résolution au
>> delà de 20cm
>>
>> 
>> https://umap.openstreetmap.fr/fr/map/ortho-photos-opendata_278682#6/46.104/2.714
>>
>> Et le bouton pour accéder aux éditeurs (colonne de
>> gauche) est activé.
>>
>> Le ven. 28 déc. 2018 à 18:17, Christian Quest
>> > > a écrit :
>>
>> Les zones blanches en bord d'ortho se sont bien
>> améliorées, mais c'est pas encore parfait pour
>> certaines (quand le blanc n'est pas si blanc que ça).
>>
>> J'ai mis en place un cache de tuiles TMS... c'est
>> pas parfait, mais ça aide.
>>
>> Ajout de:
>>
>> - l'ortho HR 2017 est complète, 2016 et 2015 sont
>> encore à compléter sur 8 départements
>>
>> - Rennes 2014 (à 

Re: [Talk-it] aiuto con relazione

2019-01-05 Per discussione Federico Cortese
On Sat, Jan 5, 2019 at 12:25 PM Marco  wrote:
>
> 2) aver aggiunto il parcheggio come membro (inner)
> https://www.openstreetmap.org/way/228761854
>
> Il gruppo di modifiche incriminato è il 66043868
>

E' proprio quella way il problema, perchè è indicata come inner, ma
interseca il poligono esterno (outer) della foresta.

Secondo me non ha senso avere un multipoligono di quelle dimensioni,
nato nel settembre del 2009 dall'import della CTR Lombardia in scala
1:10.000.
Man mano che si apportano modifiche sarebbe opportuno ridurlo in
porzioni ridotte.
Per esempio in corrispondenza del parcheggio si potrebbe spezzare in
due poligoni separati, lasciando la rotatoria ed il parcheggio fuori
dalla foresta.

Ti segnalo anche che con lo stesso changeset hai aggiunto un tag
wikipedia usando un formato errato:
https://www.openstreetmap.org/way/298912981
Questo il modo corretto: https://wiki.openstreetmap.org/wiki/Key:wikipedia

Ciao,
Federico

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


Re: [Talk-it] aiuto con relazione

2019-01-05 Per discussione Daniele Forsi
Il giorno sab 5 gen 2019 alle ore 12:25 Marco ha scritto:

> 2) aver aggiunto il parcheggio come membro (inner)
> https://www.openstreetmap.org/way/228761854

il Validatore di JOSM segnala che quella way interseca l'outer (è per
il Validatore che uso principalmente JOSM!)

tra l'altro recentemente sono state cambiate le regole per disegnare i
multipoligoni che ora sono meno tolleranti agli errori

ma che senso ha avere una relazione forest così grande (201 percorsi e
11000+ nodi) e senza nome?

-- 
Daniele Forsi

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


Re: [talk-ph] Mapping private information in Lupang Arenda

2019-01-05 Per discussione Erwin Olario
Temporary block has been applied by DWG to affected accounts. Looking
forward to hear back from at least one of them.

DWG is requesting for feedback, and that we raise the following concerns:
* data privacy protection (family names, and information like number of
household members (including children) that they've been posting)
* quality of the building geometry
* wiki page for their project

FYI.


On Fri, Jan 4, 2019 at 9:25 PM maning sambale 
wrote:

> Hi everyone,
>
> Over the last couple of days we noticed several mappers in Lupang
> Arenda Taytay/Cainta are adding names of residents on buildings.
> We have been reviewing and fixing a lot of theses edits [0].  I
> believe Erwin also added comments in some changesets.
>
> We are not sure what is the purpose of these edits, our hunch is that
> the data is being used for a community based land tenure project.
> While using OSM for land rights is a commendable endeavor, private
> information such as names of residents should not be in OSM.
> We are requesting the Data Working Group to redact these data ASAP.
>
> If anyone knows about this initiative, we would love to talk to the
> organizers so that we can help them how to use OSM without
> compromising privacy.
>
>
> [0]
> https://osmcha.mapbox.com/?filters=%7B%22date__gte%22%3A%5B%7B%22label%22%3A%22%22%2C%22value%22%3A%22%22%7D%5D%2C%22geometry%22%3A%5B%7B%22label%22%3A%7B%22coordinates%22%3A%5B%5B%5B121.09267299103794%2C14.553205630453988%5D%2C%5B121.11572489832605%2C14.553431006907346%5D%2C%5B121.1203818492969%2C14.530554123541435%5D%2C%5B121.113473703%2C14.523466229286896%5D%2C%5B121.10683755375703%2C14.526171095636244%5D%2C%5B121.0964758378588%2C14.540145711273581%5D%2C%5B121.09426378614421%2C14.541836129052285%5D%2C%5B121.09267299103794%2C14.553205630453988%5D%5D%5D%2C%22type%22%3A%22Polygon%22%7D%2C%22value%22%3A%7B%22coordinates%22%3A%5B%5B%5B121.09267299103794%2C14.553205630453988%5D%2C%5B121.11572489832605%2C14.553431006907346%5D%2C%5B121.1203818492969%2C14.530554123541435%5D%2C%5B121.113473703%2C14.523466229286896%5D%2C%5B121.10683755375703%2C14.526171095636244%5D%2C%5B121.0964758378588%2C14.540145711273581%5D%2C%5B121.09426378614421%2C14.541836129052285%5D%2C%5B121.09267299103794%2C14.553205630453988%5D%5D%5D%2C%22type%22%3A%22Polygon%22%7D%7D%5D%2C%22is_suspect%22%3A%5B%7B%22label%22%3A%22Yes%22%2C%22value%22%3A%22True%22%7D%5D%2C%22harmful%22%3A%5B%7B%22label%22%3A%22Show%20Bad%20only%22%2C%22value%22%3A%22True%22%7D%5D%7D
> --
> cheers,
> maning
> --
> "Freedom is still the most radical idea of all" -N.Branden
> https://github.com/maning
> http://twitter.com/maningsambale
> --
>
> ___
> talk-ph mailing list
> talk-ph@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ph
>
-- 

/Erwin Olario

e: er...@ngnuity.xyz | v/m: https://t.me/GOwin | s: https://mstdn.io/@GOwin
___
talk-ph mailing list
talk-ph@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ph


[Talk-it] aiuto con relazione

2019-01-05 Per discussione Marco

Ciao a tutti.

Stavo risolvendo un po' di note in prossimità di questa relazione 
https://www.openstreetmap.org/relation/273948 e sembra che sia riuscito 
a "danneggiarla", in quanto su mapnik la foresta sta piano piano 
scomparendo.


Le uniche modifiche consapevoli alla relazione sono state:

1) aver rimosso un fantasioso highway=path da questa linea 
https://www.openstreetmap.org/way/140595473


2) aver aggiunto il parcheggio come membro (inner) 
https://www.openstreetmap.org/way/228761854


Il gruppo di modifiche incriminato è il 66043868

Qualcuno di buona volontà mi aiuta a capire dove ho sbagliato?

Grazie


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


Re: [Talk-is] Data improvements in Iceland

2019-01-05 Per discussione Morten Lange
Hi, Matt and Andrew
One area for improvement is the mapping of walking and cycling paths and 
routes. And a few bicycle lanes, bicycle parking, repair stations etc.It would 
be great if paths found on ja.is maps could be freely used on OpenStreetMap, 
and the other way around. I guess that depends on licensing clauses. 
-- Regards / Kveðja / Hilsen Morten Lange

  From: Matt Riggott 
 To: "talk-is@openstreetmap.org"  
 Sent: Thursday, 3 January 2019, 16:11
 Subject: Re: [Talk-is] Data improvements in Iceland
   
Hi Andrew,

This is good news. I work for Já (based in Reykjavík) and we also have an 
interest in improving OpenStreetMap data in Iceland, although our changes have 
been ad hoc rather than structured.

The OSM data we've used so far has focused on the road network and building 
geometries. As you say, from this perspective the data is mostly complete, but 
there are some things that could be fixed. Roughly, if we split the country 
into three parts we have Reykjavík and its surrounding municipalities, the 
rural areas and smaller towns that ring the coast, and the uninhabited central 
highlands. The data for Reykjavík is generally excellent, so I would think it's 
the rural/uninhabited areas where most improvements could be made. (Even this 
data is very good though.)

One example we've seen in the small towns and rural areas are misaligned roads. 
They might only be a few metres from their real position, but when you have 
parallel roads in close proximity to one another this can cause GPS coordinates 
to place you on the wrong road. Likewise with misaligned or inaccurate building 
outlines — important to us since we use them to decide which points along the 
road network are visible from a given location.

Then there's the central highlands. The gravel road network here is only 
accessible during the summer and many roads require a four-wheel drive if 
you're driving. I haven't looked much into the data here, but I have an inkling 
that very useful improvements could be made — surface tags especially, but also 
additional routes, accessibility, and road numbers. I'd love to see more detail 
added here.

As for external data, up-to-date imports from the Staðfangaskrá and LUKR 
datasets would be great. The latter is the land information system for 
Reykjavík and surrounding municipalities, and it's extraordinarily detailed 
(down to the road markings painted on roads). Both datasets were imported into 
OSM a long time ago and I don't think they've been revisited since.

I've tried and failed to keep this short, but if you want more information 
please get in touch via email or on this list.

M.

PS. While you're here, there's an error in the Reykjavík coastline in Apple 
Maps that's always irritated me. Compare these:

- https://maps.apple.com/?ll=64.1509,-21.9142
- https://www.openstreetmap.org/#map=15/64.1509/-21.9142

> On 23 Dec 2018, at 02:52, Andrew Wiseman   wrote:
> 
> Hello everyone,
> 
> I’m Andrew with Apple’s Maps team. We’re interested in doing some a few 
> improvements to the OSM data in Iceland, specifically adding some missing 
> buildings, making road network fixes like adding missing roads, making sure 
> intersections are correct, and the like, and some coastline fixes. It looks 
> like the data is mostly complete but I wanted to see if you had any 
> suggestions for places where things might be out of date or inaccurate, or 
> other suggestions or feedback. I also saw that some addresses had been 
> imported from a government dataset 
> (https://wiki.openstreetmap.org/wiki/Staðfangaskrá_Import), is that still 
> going on?
> 
> Here’s more information about our project: 
> https://github.com/osmlab/appledata/issues/134
> 
> 
> Please let me know if you have any questions or feedback. Also if there is a 
> forum, Telegram or WhatsApp group the community uses, I’d be happy to join 
> and talk there.
> 
> Thank you,
> 
> Andrew

-- 
Matt Riggott
Programmer / Forritari

https://ja.is/

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


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