[talk-au] Qld topo map usable?

[Graeme Fitzpatrick]

G'day all

I've just come across an online Qld topo map, published by Dept of Natural
Resources.

Map is at http://qtopo.dnrm.qld.gov.au/Mobile/

Also makes reference to copyright being licensed under CC BY 4.0:
https://www.dnrm.qld.gov.au/legal/copyright, & includes

"Under this licence you are free to use this information in accordance with
the licence terms without having to seek permission from our department.
You must keep the copyright notice intact and attribute the State of
Queensland as the source of the material."

Does that mean we can use it?

Thanks

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

Re: [OSM-talk] Adding wikidata tags to the remaining objects with only wikipedia tag

[Yuri Astrakhan]

Verifiability is critical to OSM success, but it does not mean it must only
be  verifiable by visiting the physical location. Tags like "wikipedia",
"wikidata", "url", "website" and some IDs cannot be verified that way.  You
must visit some external website to validate. Stopping by Yellowstone
National Park or a statue in the middle of a city may tell you its national
registration number, but most likely you will have to visit some government
website. Seeing some complex URL tells you nothing about its correctness
unless you visit that web site.

Yet, we are not talking about the last two examples.  Node 153699914 has
wikipedia="Eureka, Wisconsin".  It looks fine to a casual examiner, but in
reality is a garbage link to a disambiguation place - a list of 3 different
places, which you wouldn't know unless you visit the external site -
Wikipedia.  I have uncovered many thousands of such cases, and many of them
have already been fixed thanks to a stronger IDing system.  Yet, every day
there is more of them - because Wikipedia keeps renaming things, and
several people refuse to allow Wikidata IDs.

Wikipedia created a stable ID system for these pages. Its called Wikidata.
Please view Wikidata as first and foremost a linking system to Wikipedia
articles.  It is NOT perfect. It has many issues. But it is simply much
better than linking to Wikipedia articles by their names because they don't
break as often.

Andy, you keep saying Wikidata is not verifiable data - but that's because
you keep insisting on separating it from Wikipedia. We can already make it
so that when you click on Wikidata link, you are taken directly to
Wikipedia. The statements on Wikidata entries are a major bonus for
automated verification and other things, but it should be viewed in
addition to the redirecting capability, not as a replacement to Wikipedia
pages.
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk-ie] DIT study of Balbriggan

[Colm Moore]

Hi,


Over time, Stabilo_boss, others and I have added a fair bit of detail to 
Balbriggan, such that the map there is generally in a better condition than the 
surrounding towns, the big difference being that the the other towns generally 
have a higher percentage (but still low) of individual houses mapped than 
Balbriggan. As a mapping exercise, Balbriggan would therefore be of less use 
than the other towns. There will of course be extendable data.


That said, from a town planning point of view, Balbriggan is probably more 
interesting than the other towns.


I wouldn't overly worry about third-party mappers interfering.


Features that could be added by the students:

* Individual houses and other buildings (landmark buildings fairly well mapped).
* Retail and other service businesses;
* Non-roadway street features, including paths and street furniture;
* Confirm street names (there's the usual fuzziness with unsigned legacy roads);
* Addresses;
* Bus routes
* Update construction;
* Rural features;
* Local road numbers, if available.

If the students are to be assessed on their work, then each should be given two 
tasks (a) surveying, recording and mapping everything in one neighbourhood to 
get experience at mapping different keys / tags and (b) doing the same for one 
type of key / tag over a wider area to understand differences between areas.


Colm


---
Never doubt that a small group of thoughtful, committed citizens can change the 
world. Indeed, it is the only thing that ever has. Margaret Mead
___
Talk-ie mailing list
Talk-ie@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ie

Re: [OSM-talk-ie] DIT study of Balbriggan

[Ciarán Staunton]

DIT Study of Balbriggan

Thanks for the suggestions Donal, Ruairi and Dave, these give me a few
things to explore with the class and teachers.

On using HOTOSM, generally you need some sort of humanitarian/environmental
call to action that is urgent and I don't think Balbriggan has that.
Mapcraft can be explored, and if there are other things that are simpler
now is the time to suggest them.

Now on the big one from Rory (yes it is helpful).

   - The mappers will first identify a theme or focus, and map according to
   achieving a level of completeness defined by themselves and within a
   boundary defined by themselves. At this stage I have suggested (before you
   did) they join this mailing list and seek volunteer OSM users to consult on
   what tagging might be best
   - Students are not paid to map, nor are they instructed to map any
   particular way, so they are utterly open to feedback. They are encouraged
   to find out what conventional tagging is in use and learn about OSM. The
   project hasn't got here yet but my feeling was they would document what
   they wanted to do once they start and do it ahead of time so the interested
   members of the community could comment
   - I will take the suggestion to them that a teacher or class nominee
   posts as much as possible up (and what they feel comfortable with) so that
   the project is as transparent as possible. However, I would stop well short
   of assuming that new users need higher forms of visibility because they are
   a class group or because they are new users
   - I will be explaining the general principles of OSM to them in a couple
   of meetings, it will be made clear that the mapping in Balbriggan is osm
   data and not their personal geodatabase


I think we need to focus here, as you did, on the massive shot in the arm
that groups working in particular areas can be to the OSM project overall,
especially if there is a local community link. They will be working with
both the political and community interests in the town, which may give a
further exposure to the fact that there is a big free database called OSM.

Ciaran




On Thu, Sep 28, 2017 at 2:45 PM, Rory McCann  wrote:

> Hi,
>
> That's a great idea, some minor thoughts and a big one:
>
> If the students use Mapillary that would be great, because it means
> other people can check the "source" in case someone made a mistake. And
> we can use the mapillary images ourselves to map things the students
> might have missed.
>
> JOSM is good, but iD has a new feature where someone can "request
> review" which could allow the community to help the mapper¹.
>
> So the big bit:
>
> This is now referred to as "Organized Editing"², and the OSM Data
> Working Group is requesting feedback on any Policy that should be
> created, similar to the Import Guidelines³ (which you all should fill
> out!). It's to cover paid mapping, and (since elitist Germans want to
> bash HOT & Missing Maps) any "organised mapathon".
>
> The main question is: Who is telling the mapper what to map? How much
> freedom does the mapper have?
>
> If I see a dodgy/bad edit, the OSM approach is to contact the mapper and
> talk to them. But if the person who uploaded it is being paid to map it,
> then they don't have any freedom to act differently, they're just doing
> their job. I can't suggest that someone not add a certain thing, if the
> would get fired for not adding it! I should really be talking to their
> manager.
>
> Some classes (etc) are designed for the students to learn about OSM, and
> the students are only required to map /something/. In which case I have
> to talk to the student. It sounds like this is where the mappers will be
> told what to map.
>
> I suggest that the person in charge of the project post a diary entry
> (they do already have an OSM account, right??) explaining their project,
> what their experience with OSM is, where they'll be mapping, what they
> will be adding, what the source is, who the team members will be, etc.
> All of the team members should probably have a separate OSM account for
> the mapping, and in their OSM user profile mention that they are working
> on a certain project, and include a link to the person in charge of the
> project. Perhaps they should also details in changeset comments/tags
> about the project. This way, if anyone sees a dodgy edit, we know who to
> ask about it.
>
> It's also important that the people running this project know about OSM.
> Sometimes people think it's a generic geo-data-store, where you have
> private layers, and can just store whatever you need to there. Nope,
> we're all in one database. So other mappers might come along and
> fix/change/improve/delete something you add, if appropriate. This may or
> not affect your project. Sometimes people react to this with "We need
> the data in this form for our project, stop changing/deleting it". But
> if the data is "wrong" (by OSM standards) then tough. This could be a
> 

Re: [OSM-talk] All the subway systems in the world

[Daniel Koć]

W dniu 30.09.2017 o 18:35, Ilya Zverev pisze:


usable, I've compiled a list of practices on this page:

https://wiki.openstreetmap.org/wiki/Proposed_features/Metro_Mapping

Some questions are answered on the Talk page there. Next week I'll open a 
voting, so that tagging schema could be made official. The validator of course 
expects that kind of tagging, though it allows for some omissions.


Nice to see another unification effort, but I have a specific question: 
we have an interchange station in Warsaw called "Świętokrzyska". I 
marked it as one station some time ago in the middle of lines crossing.


Lately somebody (namely https://www.openstreetmap.org/user/IraSergeeva ) 
made it two different points in the middle of each line's waiting area:


- https://www.openstreetmap.org/node/3390253994 (M1)
- https://www.openstreetmap.org/node/5117464830 (M2)

How do you think it should be tagged properly?

Plus there is additional error reported about duplication and I'm also 
unsure what to do with public_transport=stop_position:


https://www.openstreetmap.org/node/3208963714 (M2)

--
"My method is uncertain/ It's a mess but it's working" [F. Apple]


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

Re: [Talk-us] guidelines regarding roads access

[Greg Morgan]

On Sep 24, 2017 8:33 AM, "Greg Troxel"  wrote:


Adam Franco  writes:

> One additional note is that at least in my area, the TIGER import
> incorrectly added access=private to many driveways and privately
maintained
> residential roads. Upon surveying these I've found that they are signed
> "Private" or "PVT" on the street-name sign to indicate
> private-maintenance/ownership (don't complain to the town about a lack of
> snow-plowing/grading), but do not in reality have an access restriction.


https://www.mapillary.com/app/?focus=photo=oyEdoFPUg3yayTv1deHZUQ=33.567826=-112.016051=17

I initially marked a street like this as access=private.  Then I found out
that this definition of private is more like Adam's experience. However, I
did not experience the issue with the TIGER import. I am not sure that an
HOA is a good thing.  I stay away from them for a number of reasons
including the leftovers of the subprime rate debacle.

http://www.azcentral.com/story/news/local/arizona-investigations/2017/09/14/phoenix-area-homeowners-associations-foreclosing-record-number-homeowners/595816001/


For a "private way" (legal term in my state for what I think you refer
to as "privately maintained residential road"), I agree that there
shouldn't be access=private.

For a driveway to someone's house, access=private seems right, in that
it's generally at least impolite to use that road other than as
visitor/delivery/etc.

...

But, that tends to lead to pink blobs in rendering, and I'm not sure
that's the right thing, as service roads having the status "you should
use these only when dealing with the adjacent entities" seems to be the
default/normal case.  We should adjust rendering, not access, to make
this pleasing.


The rendering has been changed to a gray dashed center line.

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

Re: [Talk-at] Wochennotiz Nr. 374 12.09.2017–18.09.2017

[Peter Barth]

Hallo Manfred,

Manfred Brandl schrieb:

> Ich habe die Wochennotiz Nr. 375 nicht per Email bekommen, bisher war das 
> ausgenommen Nr. 368 sehr zuverlässig. Wurde die Notiz nicht verschickt oder 
> gab es auf meiner Seite ein Empfangsproblem?

ohne das jetzt größer auszuführen: Durch interne Umstellungen gab es
diese Woche keinen der das Skript hätte ausführen können. Es sollte ab
nächster Woche aber wieder wie gewohnt laufen.

Gruß,
Peda


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

Re: [Talk-us] dubious church node

[Max Erickson]

>One more thing to know about GNIS: entries are never deleted.

One minor exception to this is if they determine that a given feature
has 2 IDs, one of the IDs will often be removed.


Max

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

Re: [OSM-talk] All the subway systems in the world

[Milo van der Linden]

Nice! I like the detail you guys are applying. Keep up the good work!

2017-09-30 18:35 GMT+02:00 Ilya Zverev :
> Hi,
>
> I have made a script that parses and validates subway systems. It prints the 
> number of subway lines and stations that an automated system can extract from 
> the OpenStreetMap data. See the latest report here (these are updated 
> manually for now):
>
> http://osmz.ru/subways/
>
> It is still in beta: it doesn't use networks and omits many non-european 
> cities. We plan to employ it for maps.me, so it would be the first app that 
> does world-wide subway routing using only OSM data. To make tagging subway 
> systems uniform and usable, I've compiled a list of practices on this page:
>
> https://wiki.openstreetmap.org/wiki/Proposed_features/Metro_Mapping
>
> Some questions are answered on the Talk page there. Next week I'll open a 
> voting, so that tagging schema could be made official. The validator of 
> course expects that kind of tagging, though it allows for some omissions.
>
> Ilya
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk



-- 
Milo van der Linden
web: dogodigi
tel: +31-6-16598808

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

Re: [Talk-us] dubious church node

[Martijn van Exel]

I sense a topic for the next Many Mappy Minutes or a BOF at State of the Map US 
—> cleaning up old imports.
I sure appreciate all the knowledge shared here! So much I didn’t know about 
GNIS data.
Martijn

> On Sep 30, 2017, at 11:54 AM, Wolfgang Zenker  
> wrote:
> 
> * Carl Anderson > 
> [170930 17:21]:
>> ​A little history on GNIS data, and the Board of Geographic Names.
> 
>> The US Board of Geographic Names manages names for places and features
>> shown on US govt maps.  They have been using a database to manage the names
>> across maps and map scales. That database is the GNIS.
> 
>> The ​original GNIS data was populated from all text labels shown on USGS
>> maps.  The most common source was 1:24,000 scale topo quarter quads.  Text
>> from 1:100,000, 1:250,000 and 1:1,000,000 scale maps and larger were
>> included.
> 
>> The stated map accuracy of these scales  (
>> https://nationalmap.gov/standards/nmas.html ) is approximately
> 
>> 1:24:00040 feet
>> 1:250,000 416 feet
>> 1:500,000 833 feet
>> 1:1,000,000   1666 feet
> 
>> The GNIS dataset includes the most precise location for text, when the text
>> appears on maps of different scales.
> 
> You can look at the full database entry for an individual GNIS feature
> if you search for the GNIS Feature ID at geonames.usgs.gov/apex/f?p=gnispq 
> 
> 
> This will give you the source of the database entry, possibly a list of
> alternate names, sometimes a note like "location approximate", and
> sometimes the history of the decision process if more than one name
> had been proposed for the feature. Also documentation of official
> name changes.
> 
> One more thing to know about GNIS: entries are never deleted. If a
> feature no longer exists, the name gets "(historical)" appended to
> it. This may have happened after the feature was imported to OSM,
> so it may not show in the OSM database.
> 
> Unfortunately the GNIS database is no longer fully maintained due to
> budget constraints, so you can't be sure if features still exist even
> if they are not flagged as "(historical)".
> 
> As to mapping in OSM: I usually remove any "(historical)" feature.
> For the others, I improve the location if possible, and if the feature
> can be represented as an area, I draw that area/polygon.
> Instead of deleting the original POI, I now reuse that node as part
> of the outline of the feature and only move the tags to the area, so
> someone looking at the object details can notice that one of the nodes
> is a lot older than the others and still find the osm history of the
> feature on that node.
> 
> Wolfgang
> ( lyx @ OSM )
> 
> ___
> 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: [OSM-talk] All the subway systems in the world

[Fredrik]

Cool stuff.
I was clicking around and the link to the github repo is either dead or 
to a private repo. Not sure if this was intentional?


\FredrikLindseth


On 30. sep. 2017 19:06, Ilya Zverev wrote:

My definition of a subway is a network of lines that are marked "subway" on 
official subway maps.

Though validator also processes light rail lines (with obviously similar 
definition).

Ilya


30 сент. 2017 г., в 19:59, john whelan  написал(а):

Silly question but what is your definition of a subway?

Is it different to commuter rail?

Thanks John

On 30 Sep 2017 12:38 pm, "Ilya Zverev"  wrote:
Hi,

I have made a script that parses and validates subway systems. It prints the 
number of subway lines and stations that an automated system can extract from 
the OpenStreetMap data. See the latest report here (these are updated manually 
for now):

http://osmz.ru/subways/

It is still in beta: it doesn't use networks and omits many non-european 
cities. We plan to employ it for maps.me, so it would be the first app that 
does world-wide subway routing using only OSM data. To make tagging subway 
systems uniform and usable, I've compiled a list of practices on this page:

https://wiki.openstreetmap.org/wiki/Proposed_features/Metro_Mapping

Some questions are answered on the Talk page there. Next week I'll open a 
voting, so that tagging schema could be made official. The validator of course 
expects that kind of tagging, though it allows for some omissions.

Ilya
___
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-be] Do you Tag those as cycleway?

[marc marc]

Hello,

Le 30. 09. 17 à 18:36, joost schouppe a écrit :
> I think everyone agreed that this is nothing more than "maquillage"
not me, not always :)

> https://www.google.be/maps/@50.8674422,4.3297542,3a,60y,141.06h,86.52t/data=!3m6!1e1!3m4!1srWr6HwmC8P9LgEfOSk2Xpg!2e0!7i13312!8i6656
this traffic sign is not a "maquillage".
It is the traffic sign that tells you that another traffic sign at the 
other end of the street allows a cyclist to take the one-way street.
If this mark did not exist, you do not know it when going forward
in this street in the "one-way" direction.

> https://www.google.be/maps/@50.8676849,4.3295925,3a,75y,183.24h,93.62t/data=!3m6!1e1!3m4!1sLOB7wV_P3Sqi3kbypjpQcw!2e0!7i13312!8i6656
here is the second traffic sign.

> https://www.touring.be/fr/articles/regles-de-circulation-pour-les-cyclistes
Without any sign, a cyclist can not go backward in a "one-way" street.

maybe the regionalization of the road code has * the situation but 
that is, as far as I know, the rule in Brussels where is the street of 
the first photo.

So this street should be tagged with cycleway=opposite. see wiki :
https://wiki.openstreetmap.org/wiki/Key:cycleway
Use cycleway=opposite for situations where cyclists are permitted to 
travel in both directions on a road which is one-way for normal traffic, 
in situations where there is no dedicated contra-flow lane marked for 
cyclists.

Regards,
Marc
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [Talk-us] dubious church node

[Wolfgang Zenker]

* Carl Anderson  [170930 17:21]:
> ​A little history on GNIS data, and the Board of Geographic Names.

> The US Board of Geographic Names manages names for places and features
> shown on US govt maps.  They have been using a database to manage the names
> across maps and map scales. That database is the GNIS.

> The ​original GNIS data was populated from all text labels shown on USGS
> maps.  The most common source was 1:24,000 scale topo quarter quads.  Text
> from 1:100,000, 1:250,000 and 1:1,000,000 scale maps and larger were
> included.

> The stated map accuracy of these scales  (
> https://nationalmap.gov/standards/nmas.html ) is approximately

> 1:24:00040 feet
> 1:250,000 416 feet
> 1:500,000 833 feet
> 1:1,000,000   1666 feet

> The GNIS dataset includes the most precise location for text, when the text
> appears on maps of different scales.

You can look at the full database entry for an individual GNIS feature
if you search for the GNIS Feature ID at geonames.usgs.gov/apex/f?p=gnispq

This will give you the source of the database entry, possibly a list of
alternate names, sometimes a note like "location approximate", and
sometimes the history of the decision process if more than one name
had been proposed for the feature. Also documentation of official
name changes.

One more thing to know about GNIS: entries are never deleted. If a
feature no longer exists, the name gets "(historical)" appended to
it. This may have happened after the feature was imported to OSM,
so it may not show in the OSM database.

Unfortunately the GNIS database is no longer fully maintained due to
budget constraints, so you can't be sure if features still exist even
if they are not flagged as "(historical)".

As to mapping in OSM: I usually remove any "(historical)" feature.
For the others, I improve the location if possible, and if the feature
can be represented as an area, I draw that area/polygon.
Instead of deleting the original POI, I now reuse that node as part
of the outline of the feature and only move the tags to the area, so
someone looking at the object details can notice that one of the nodes
is a lot older than the others and still find the osm history of the
feature on that node.

Wolfgang
( lyx @ OSM )

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

Re: [Talk-us] dubious church node

[Jesse B. Crawford]

I also seem to have observed that, at least in rural New Mexico where I
do most of my mapping, GNIS features like historic places seem to have
only been entered to the resolution of what town they were in, and then
all ended up at something like the centroid of the town or county
limits. The result can be rather odd - before I moved them all to more
correct locations, the parking lot of a particular bank in Socorro, NM
contained over a half dozen historic homes. What an amazing place to
visit!

So this is another thing to keep in mind, it seems like the GNIS
locations may be quite a bit less granular for certain types of
features. The historic features are a good example as they were
presumably all taken from the registry and so they *do* exist, but it
can take a lot of legwork to figure out where.

-- 
Jesse B. Crawford

https://jbcrawford.us
je...@jbcrawford.us
GPG 0x4085BDC1

On Sat, Sep 30, 2017, at 11:05 AM, Mark Wagner wrote:
> On Sat, 30 Sep 2017 15:11:06 +0700
> Dave Swarthout  wrote:
> 
> > "Second, many entries have their coordinates specified using the old
> > NAD 27 datum, but somewhere along the line, that fact was lost and the
> > coordinates were assumed to be in either NAD 83 or WGS 84.  This
> > results in an offset that increases the further you go from central
> > Indiana; the offset in Alaska is upwards of a hundred meters to the
> > west."
> > 
> > Wow, thanks for that. If I understand what you're saying, this means
> > many of the old GNIS nodes will be positioned about 100 meters east
> > of where they should be? Or do I have your statement turned around?
> 
> Depending on where in the process the error was made, it could go
> either way, but in my experience, the nodes are usually positioned too
> far to the east.
> 
> -- 
> Mark
> 
> ___
> 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: [OSM-talk] All the subway systems in the world

[Ilya Zverev]

My definition of a subway is a network of lines that are marked "subway" on 
official subway maps.

Though validator also processes light rail lines (with obviously similar 
definition).

Ilya

> 30 сент. 2017 г., в 19:59, john whelan  написал(а):
> 
> Silly question but what is your definition of a subway?
> 
> Is it different to commuter rail?
> 
> Thanks John
> 
> On 30 Sep 2017 12:38 pm, "Ilya Zverev"  wrote:
> Hi,
> 
> I have made a script that parses and validates subway systems. It prints the 
> number of subway lines and stations that an automated system can extract from 
> the OpenStreetMap data. See the latest report here (these are updated 
> manually for now):
> 
> http://osmz.ru/subways/
> 
> It is still in beta: it doesn't use networks and omits many non-european 
> cities. We plan to employ it for maps.me, so it would be the first app that 
> does world-wide subway routing using only OSM data. To make tagging subway 
> systems uniform and usable, I've compiled a list of practices on this page:
> 
> https://wiki.openstreetmap.org/wiki/Proposed_features/Metro_Mapping
> 
> Some questions are answered on the Talk page there. Next week I'll open a 
> voting, so that tagging schema could be made official. The validator of 
> course expects that kind of tagging, though it allows for some omissions.
> 
> Ilya
> ___
> 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: [Talk-us] dubious church node

[Mark Wagner]

On Sat, 30 Sep 2017 15:11:06 +0700
Dave Swarthout  wrote:

> "Second, many entries have their coordinates specified using the old
> NAD 27 datum, but somewhere along the line, that fact was lost and the
> coordinates were assumed to be in either NAD 83 or WGS 84.  This
> results in an offset that increases the further you go from central
> Indiana; the offset in Alaska is upwards of a hundred meters to the
> west."
> 
> Wow, thanks for that. If I understand what you're saying, this means
> many of the old GNIS nodes will be positioned about 100 meters east
> of where they should be? Or do I have your statement turned around?

Depending on where in the process the error was made, it could go
either way, but in my experience, the nodes are usually positioned too
far to the east.

-- 
Mark

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

Re: [Talk-it] Import numeri civici Trento

[Andrea Musuruane]

Ciao,

2017-09-30 17:52 GMT+02:00 Martin Koppenhoefer :

>
>
> sent from a phone
>
> > On 30. Sep 2017, at 11:02, Andrea Musuruane  wrote:
> >
> > civici associati a un edificio mentre in Italia sono sempre associati a
> un'entrata
>
>
> non è necessariamente un errore. È vero che ogni ingresso dovrebbe avere
> un civico, ma quando non c’è più di un ingresso/civico per un edificio non
> è un problema associare il civico ad un area
>

Invece è un problema, ad esempio per il routing perché si perde
l'informazione sull'ingresso. Quindi non puoi sapere da dove si entra (gli
edifici hanno più lati e non sono necessariamente posizionati vicino
all'accesso stradale).

Ciao,

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

Re: [OSM-talk] All the subway systems in the world

[john whelan]

Silly question but what is your definition of a subway?

Is it different to commuter rail?

Thanks John

On 30 Sep 2017 12:38 pm, "Ilya Zverev"  wrote:

> Hi,
>
> I have made a script that parses and validates subway systems. It prints
> the number of subway lines and stations that an automated system can
> extract from the OpenStreetMap data. See the latest report here (these are
> updated manually for now):
>
> http://osmz.ru/subways/
>
> It is still in beta: it doesn't use networks and omits many non-european
> cities. We plan to employ it for maps.me, so it would be the first app
> that does world-wide subway routing using only OSM data. To make tagging
> subway systems uniform and usable, I've compiled a list of practices on
> this page:
>
> https://wiki.openstreetmap.org/wiki/Proposed_features/Metro_Mapping
>
> Some questions are answered on the Talk page there. Next week I'll open a
> voting, so that tagging schema could be made official. The validator of
> course expects that kind of tagging, though it allows for some omissions.
>
> Ilya
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

hebdoOSM Nº 375 2017-09-19-2017-09-25

[weeklyteam]

Bonjour,

Le résumé hebdomadaire n° 375 de l'actualité OpenStreetMap vient de paraître 
*en français*. Un condensé à retrouver sur :

http://www.weeklyosm.eu/fr/archives/9500/

Bonne lecture !

hebdoOSM ? 
Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où : 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[Talk-it] Fwd: [OSM-talk] All the subway systems in the world

[Martin Koppenhoefer]

Ilya ha pubblicato i risultati di un nuovo sistema per verificare le metro del 
mondo in osm. Questo è il link per lItalia:
http://osmz.ru/subways/italy.html

Ciao, Martin 

sent from a phone

Begin forwarded message:

> From: Ilya Zverev 
> Date: 30. September 2017 at 18:35:18 CEST
> To: t...@openstreetmap.org
> Subject: [OSM-talk] All the subway systems in the world
> 
> Hi,
> 
> I have made a script that parses and validates subway systems. It prints the 
> number of subway lines and stations that an automated system can extract from 
> the OpenStreetMap data. See the latest report here (these are updated 
> manually for now):
> 
> http://osmz.ru/subways/
> 
> It is still in beta: it doesn't use networks and omits many non-european 
> cities. We plan to employ it for maps.me, so it would be the first app that 
> does world-wide subway routing using only OSM data. To make tagging subway 
> systems uniform and usable, I've compiled a list of practices on this page:
> 
> https://wiki.openstreetmap.org/wiki/Proposed_features/Metro_Mapping
> 
> Some questions are answered on the Talk page there. Next week I'll open a 
> voting, so that tagging schema could be made official. The validator of 
> course expects that kind of tagging, though it allows for some omissions.
> 
> Ilya
> ___
> talk mailing list
> t...@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

hebdoOSM Nº 375 2017-09-19-2017-09-25

[weeklyteam]

Bonjour,

Le résumé hebdomadaire n° 375 de l'actualité OpenStreetMap vient de paraître 
*en français*. Un condensé à retrouver sur :

http://www.weeklyosm.eu/fr/archives/9500/

Bonne lecture !

hebdoOSM ? 
Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où : 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

hebdoOSM Nº 375 2017-09-19-2017-09-25

[weeklyteam]

Bonjour,

Le résumé hebdomadaire n° 375 de l'actualité OpenStreetMap vient de paraître 
*en français*. Un condensé à retrouver sur :

http://www.weeklyosm.eu/fr/archives/9500/

Bonne lecture !

hebdoOSM ? 
Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où : 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-ht mailing list
Talk-ht@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ht
Notez! Vous pouvez utiliser Google Translate (http://translate.google.com) pour 
traduire les messages.

hebdoOSM Nº 375 2017-09-19-2017-09-25

[weeklyteam]

Bonjour,

Le résumé hebdomadaire n° 375 de l'actualité OpenStreetMap vient de paraître 
*en français*. Un condensé à retrouver sur :

http://www.weeklyosm.eu/fr/archives/9500/

Bonne lecture !

hebdoOSM ? 
Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où : 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-africa mailing list
Talk-africa@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-africa

[OSM-talk] All the subway systems in the world

[Ilya Zverev]

Hi,

I have made a script that parses and validates subway systems. It prints the 
number of subway lines and stations that an automated system can extract from 
the OpenStreetMap data. See the latest report here (these are updated manually 
for now):

http://osmz.ru/subways/

It is still in beta: it doesn't use networks and omits many non-european 
cities. We plan to employ it for maps.me, so it would be the first app that 
does world-wide subway routing using only OSM data. To make tagging subway 
systems uniform and usable, I've compiled a list of practices on this page:

https://wiki.openstreetmap.org/wiki/Proposed_features/Metro_Mapping

Some questions are answered on the Talk page there. Next week I'll open a 
voting, so that tagging schema could be made official. The validator of course 
expects that kind of tagging, though it allows for some omissions.

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

Re: [OSM-talk-be] Do you Tag those as cycleway?

[joost schouppe]

We also discussed this quite extensively on Riot. I think everyone agreed
that this is nothing more than "maquillage", but that the proper tag for
this maquillage is in fact shared_lane.

> Jo: we could use shared_lane, but then we either have to do that on all
highways where bicycles aren't banned, or we go on with that as the de
facto standard.

I don't think this is a correct conclusion, as the explanation of
shared_lane on the wiki is quite clear: only tag it when there is
waste-of-paint.

I think it does make sense to tag them, even if only to be able to see
which roads to avoid when biking - as they indicate the road manager was
aware of the problem, but didn't find a proper solution :)
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [Talk-it] Import numeri civici Trento

[Martin Koppenhoefer]

sent from a phone

> On 30. Sep 2017, at 11:02, Andrea Musuruane  wrote:
> 
> civici associati a un edificio mentre in Italia sono sempre associati a 
> un'entrata


non è necessariamente un errore. È vero che ogni ingresso dovrebbe avere un 
civico, ma quando non c’è più di un ingresso/civico per un edificio non è un 
problema associare il civico ad un area


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

Re: [Talk-us] dubious church node

[Brian May]

On 9/29/2017 11:06 PM, Kevin Kenny wrote:
On Fri, Sep 29, 2017 at 9:33 PM, Mark Bradley 
> wrote:



In the course of my mapping in the American Midwest, I have come
across several small country churches of GNIS origin that no
longer exist.  Often there will be a nearby cemetery, but the
church facility is gone.  I simply delete the node.  In one case I
know of, the church building was converted into a home, so I
remapped it accordingly.


Of course, if the cemetery is there on the ground, then it should be 
mapped. But deleting the node for a demolished church is entirely 
appropriate. For a church converted to a private home, consider:


building=detached historic:amenity=place_of_worship historic:name=* etc.

if the building still resembles a church.


For any arm-chair mappers out there, you cannot assume the location of 
the original GNIS point is accurate at all, unless you have up to date 
evidence it is. So if you see a church point sitting on what looks like 
a house in a residential neighborhood on the aerial, then either delete 
it,  mark it as a FIXME or leave it alone. The person working for the 
Feds who originally mapped the point may have been miles off.


A few thoughts:

Churches from GNIS seem to be one of the biggest "map noise" features 
for areas I look at. Sometimes the locational accuracy is spot on, 
church is still there and everything is great. Sometimes the church is a 
mile and half down the road on a different block. Sometimes its in the 
middle of the highway. Sometimes in the water, etc. When I am quickly 
reviewing an area and I see a church point in the water or on a road, I 
usually just move it to a halfway plausible location without doing more 
research. It would be nice to have a fairly solid process for reviewing 
these with external data that is of known high quality.


I did a little playing around with the new USGS Map VIewer [1] and it 
has a Structures layer.  This appears to be part of the volunteer corps 
thing w/ USGS, which was (is?) a national program to provide higher 
accuracy points focused on buildings and structures.  I found this [2] 
from 2012 that provides an overview. Looks like they intended to 
contribute back to OSM - but no word on that in the doc. Found this site 
as well [3], but out of time to dig into it for now. Anyone know more 
about this Structures layer?


In the USGS Map Viewer, you can click on a structure and see details 
about it. Some say source=centroid - to me this means parcel centroid. 
Many have addresses as well. The map viewer allows you to switch the 
base map to OSM. So then you get a nice QA tool to check OSM features in 
an area. The structures layer doesn't include churches, but cemeteries 
are included. Other features include Post Offices, State Capitol 
Buildings, Hospitals / Medical Centers, Police Stations, Prisons, 
Colleges, Technical Schools, Schools, Campgrounds, Trailheads and 
Visitor Information Centers.


I have a statewide parcels layer that just shows church polygons and 
labels that I use sometimes use as well for checking churches - others 
are welcome to use it if interested.


[1] https://viewer.nationalmap.gov/advanced-viewer/
[2] https://pubs.usgs.gov/of/2012/1209/pdf/ofr2012-1209.pdf
[3] https://nationalmap.gov/TheNationalMapCorps/#

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

Re: [OSM-talk-be] Do you Tag those as cycleway?

[Glenn Plas]

On 30-09-17 08:13, Jo wrote:
> True, we could use shared_lane, but then we either have to do that on
> all highways where bicycles aren't banned, or we go on with that as the
> de facto standard.
> 
> The fact that a bicycle is drawn, doesn't make it 'more' of a shared
> lane than it would be without the wasted paint.
> 
> All it does is make motorists aware that there might be bicycles sharing
> their lane. Something they should have been aware of anyway.

It also confirms for sure what Marc suggests for tagging, that this is
indeed a shared_lane.

I support tagging this as he proposes.  But so far for legality, this is
just suggestive painting.  Traffic signs should also be taken into
account as they override whatever is painted.

Glenn



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

Re: [Talk-us] dubious church node

[Brian May]

On 9/30/2017 3:19 AM, Mark Wagner wrote:

Second, many entries have their coordinates specified using the old NAD
27 datum, but somewhere along the line, that fact was lost and the
coordinates were assumed to be in either NAD 83 or WGS 84.  This
results in an offset that increases the further you go from central
Indiana; the offset in Alaska is upwards of a hundred meters to the
west.


I found this [1] page that says:.



9. What datum applies to the geographic coordinates in the GNIS Database?
All coordinates in the database are in NAD 83. They were converted from 
NAD 27 in September 2005.




And this page [2] which appears to be official metadata that doesn't 
mention a datum - but it was written in 1994 (see very bottom of page).


[1] https://geonames.usgs.gov/domestic/faqs.htm
[2] https://geonames.usgs.gov/metadata.html

Brian


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

Re: [Talk-it] Import numeri civici Trento

[Dario Zontini]

Benvenuto Daniele e complimenti per la proposta di importare i numeri civici


Il 29 Set 2017 16:46, "Maurizio Napolitano"  ha scritto:


Come Daniele ha già spiegato il Comune di Trento georefernzia ogni
etichetta che  rappresenta un numero civico.
Questo fa sì che una abitazione si trova ad avere da uno ad un massimo di 4
punti che riportano la stessa informazione ma su coordinate diverse.
Esempio:
- ingresso del cancello
- ingresso della porta dell'abitazione
- ingresso secondario
- ingresso dal garage
Ciascuno riporta lo stesso numero civico e via anche nel caso in cui il
cartellino è appeso su un lato della casa che si affaccia su un altra strada

Dire di valutare bene cosa importare dei possibili 4 punti perché per ISTAT
il civico è solo quello sulla pubblica via. L'ingresso secondario è del
garage non dovrebbero essere un numero civico  diverso?

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

Re: [OSM-talk-fr] Importation des hauteurs de bâtiments sur Nice

[Vincent Frison]

Le 27 septembre 2017 à 23:25, Philippe Verdy  a écrit :

> Un problème entre Cantaron et Falicon, le MNT ne semble pas correct (plat
> là où il y a des montagnes) du coup, on a des tas de "tours":
>

Pour info j'ai corrigé cette zone, merci pour le report.

A priori c'était la seule zone qui posait problème...

J'ai fait la correction manuellement mais savez vous si avec l'Overpass API
j'aurais pu faire une petite requête remontant tous les bâtiments dont la
hauteur est supérieur à X mètres ? Le problème c'est que les tags ne sont
que des champs textes et j'ai pas l'impression qu'on puisse utiliser des
opérateurs genre inférieur ou supérieur sur les tags. Mais bon je connais
pas vraiment l'API...
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-it] Task incompleto, da me bloccato.

[liste DOT girarsi AT posteo DOT eu]

Il 29/09/2017 21:40, Alessandro Palmas ha scritto:
> 
> Il tsk è stato terminato.
>
> Sbiribizio ha dato una mano al server a tirarsi su.
>
> 


Ok, grazie, comunque per il quadrato in questione quando saranno sul
posto verificheranno meglio.

Grazie ancora.



-- 
Simone Girardelli
_|_|_|_|_|_|_|_|_|_
|_|_|_|_|_|_|_|_|_|_|

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

Re: [OSM-talk-be] Do you Tag those as cycleway?

[Jo]

It definitely is not always permitted to ride a bicycle against the flow of
traffic on oneway streets.

The law was changed at some point to allow administrations to create oneway
streets where bicycles are allowed in both directions, but it's not for all
oneway strees.

Jo

2017-09-30 11:56 GMT+02:00 Marc Gemis :

> I thought was always allowed to drive in the opposite direction under
> Belgian law. What does not mean that a sign to remind car drivers  is
> welcome.
>
> m.
>
> On Sat, Sep 30, 2017 at 9:19 AM, marc marc 
> wrote:
> > Hello,
> >
> > Le 29. 09. 17 à 22:42, eMerzh a écrit :
> >> https://www.google.be/maps/@50.8674422,4.3297542,3a,60y,
> 141.06h,86.52t/data=!3m6!1e1!3m4!1srWr6HwmC8P9LgEfOSk2Xpg!
> 2e0!7i13312!8i6656
> >
> > imho the bike painted in the opposite direction to what appears to be a
> > one-way street is intended to warn that bike is allowed in the reverse
> > direction (a traffic sign should exist under the one-way traffic sign
> > but no traffic sign exist at the other end of the street)
> >
> > Regards,
> > Marc
> > ___
> > Talk-be mailing list
> > Talk-be@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-be
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [Talk-us] dubious church node

[Marc Gemis]

> Another point is that if you have the outline for something that GNIS shows
> as a node, please conflate! I've done that with a lot of buildings and parks
> locally - just copy-and-paste the GNIS tags from the node to the polygon and
> then delete the node.

The utilsplugin2 [1] for JOSM and it's replace geometry is another way
to do this quickly.

m.

[1] https://wiki.openstreetmap.org/wiki/JOSM/Plugins/utilsplugin2

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

Re: [OSM-talk-be] Do you Tag those as cycleway?

[Marc Gemis]

I thought was always allowed to drive in the opposite direction under
Belgian law. What does not mean that a sign to remind car drivers  is
welcome.

m.

On Sat, Sep 30, 2017 at 9:19 AM, marc marc  wrote:
> Hello,
>
> Le 29. 09. 17 à 22:42, eMerzh a écrit :
>> https://www.google.be/maps/@50.8674422,4.3297542,3a,60y,141.06h,86.52t/data=!3m6!1e1!3m4!1srWr6HwmC8P9LgEfOSk2Xpg!2e0!7i13312!8i6656
>
> imho the bike painted in the opposite direction to what appears to be a
> one-way street is intended to warn that bike is allowed in the reverse
> direction (a traffic sign should exist under the one-way traffic sign
> but no traffic sign exist at the other end of the street)
>
> Regards,
> Marc
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be

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

Re: [OSM-talk-fr] Centre commercial déplacé

[Lionel Allorge]

Bonjour,

> Ok. Du coup, le plus simple est d'utiliser les imageries Cadastre pour
> les bâtiments et BDOrtho IGN pour le reste visible du ciel.
> C'est ce que je viens de faire (j'avais trop envie, c'est une vraie
> drogue ce projet !). ;-)
Super ! Merci.

Librement.

-- 
Lionel Allorge
April : http://www.april.org
Lune Rouge : http://www.lunerouge.org
Wikimedia France : http://wikimedia.fr
OpenStreetMap France : http://www.openstreetmap.fr/

« Si vous m'avez compris c'est que je me suis mal exprimé »
Alan Greenspan

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

Re: [Talk-it] Import numeri civici Trento

[Andrea Musuruane]

Ciao,

2017-09-30 0:40 GMT+02:00 Maurizio Napolitano :

> > La pagina wiki deve essere in inglese perché poi deve essere commentata
> > nella ML di import e il parere della ML di import è vincolante.
>
> Certo.
> Per la discussione in italiano però è meglio l'italiano :)
> In ogni caso il percorso è ancora lungo.
>

Vi consiglio di seguire il seguente template perché contiene molte delle
cose che devono essere discusse per un import.
https://wiki.openstreetmap.org/wiki/Import/Plan_Outline

Per compilarlo, usate come esempio le pagine di altri import.


> > Attendo il resto della documentazione prevista per potere capire meglio.
> > Inoltre, chi parteciperà all'import? Quali sono i loro account di import?
>
> L'idea è avere un account dal nome trento_import.
> In effetti questo Daniele non lo ha scritto.
>

OK. Servirebbe anche un elenco di persone che partecipa all'import.


> > Qual è la pianificazione?
>
> appena arriva l'ok lancia lo script
>
> > E' possibile vedere i dati che verranno importati
> > (già trasformati)?
>
> Lo script il cui codice è stato reso pubblico usa le API di OSM.
> Se serve convertirlo in .osm allora si può fare
>

Sarebbe meglio per verificare il risultato della trasformazione.


> > Come verrà fatta la fase di QA?
>
> è già stata fatta tutta una analisi - documentata su github (che poi
> era il lavoro di stage di Daniele) - di confronto fra i dati erogati
> dal comune di trento e quelli presenti in openstreetmap.
> Fra le azioni sono state fatte anche le verifiche in merito ai nomi
> delle vie visto che, il dataset del comune usa nomi "compressi" mentre
> osm nomi "estesi".
> Daniele, con la sua serie di script e di pulizie con openrefine ha
> individuato:
> - i dati già presenti in osm e comparato con quelli del comune
> - dove ha trovato corrispondenza di contenuto ed una distanza fra i
> punti ragionevole (= larghezza di un edifico che contiene un civico)
> ha marcato i dati del comune come già presenti in osm (ergo cancellati
> dal potenziale dataset di importazione)
> - dove ha trovato corrispondenza geografica (o comunque in un intorno)
> è andato a verificare cosa mancava e, nei casi più complessi, è andato
> sul posto
> Dopo queste impostazioni ha isolato i dati.
> Tutto il codice è la procedura è rilasciata su github con
> documentazione in inglese -
> https://github.com/danielezotta/osm_civici_trento .
> Fra le verifiche ha controllato anche l'esistenza della strada oltre
> che del civico (il risultato ha dato
> completa copertura delle strade).
> Probabilmente questi passaggi ti erano sfuggiti o, molto più
> probabilmente, non sono coerenti con le linee guida.
> In tal caso l'invito è a segnalare cosa non va.
>

No, non mi è sfuggito. Tralasciando il modus operandi (che è interessante e
vorrei analizzarlo meglio appena ho tempo), il modo migliore per valutare
la bontà dei dati è analizzare il file OSM risultante.

Inoltre, è altamente improbabile che questo sia il primo import che non
necessiti di una fase di QA successiva, perché tutto è stato importato
benissimo, i dati sorgente non contenevano errori e anche i dati
precedentemente inseriti in OSM erano perfetti.

Alcuni dei problemi che possono capitare sono: strade mancanti in OSM (ma
ricavabili dai civici e dalle foto satellitari), strade scritte con nomi
differenti nei civici e nella strada (già oggi ce ne sono molti a Trento),
civici duplicati, civici formalmente corretti (ovvero associati a una
strada esistente) ma molto distanti da questa, civici associati a un
edificio mentre in Italia sono sempre associati a un'entrata (a Trento ce
ne sono diversi come si vede dalla seguente query overpass o tramite osm
inspector)


  


  
  
  

 
  
  
  
  



http://tools.geofabrik.de/osmi/?view=addresses=8.10563=45.56110=10=street_not_found

Prova a vedere quali strumenti sono stati usati per gli altri import (es:
osm inspector, no name map, ecc).

Ciao,

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

Re: [Talk-us] dubious church node

[Dave Swarthout]

"Second, many entries have their coordinates specified using the old NAD
27 datum, but somewhere along the line, that fact was lost and the
coordinates were assumed to be in either NAD 83 or WGS 84.  This
results in an offset that increases the further you go from central
Indiana; the offset in Alaska is upwards of a hundred meters to the

west."

Wow, thanks for that. If I understand what you're saying, this means many
of the old GNIS nodes will be positioned about 100 meters east of where
they should be? Or do I have your statement turned around?

The mine whose position I last adjusted, the Case Mine in the Chugach
Mountains on the Kenai Peninsula, was quite a distance from an area of bare
ground (visible only in ESRI) where an old mine site might have been. The
original position was to the east of that bare area. I didn't measure the
distance but will do that next time I come across such a mine.  The bare
spot also happens to be where the USGS Topo places the mine, consequently,
I felt moving it was justified.

I'm also guessing that the other Case Mine node,  the"duplicate" I
mentioned earlier, represents perhaps a second mine_entrance on the same
mining claim. However, there is nothing west of that node to provide any
clue to guide a repositioning, nor does it appear on theUSGS Topo map, so I
left it where it was.

On Sat, Sep 30, 2017 at 2:19 PM, Mark Wagner  wrote:

> On Sat, 30 Sep 2017 06:56:31 +0700
> Dave Swarthout  wrote:
>
> > Glad you mentioned that GNIS import, Ian.
> >
> > This isn't a pressing issue but I've been doing considerable mapping
> > in Alaska and encounter GNIS features constantly. Many of them are
> > nodes and refer to mines, usually abandoned mines, and contain
> > tagging that JOSM complains about, for example, using landuse=quarry
> > on a node. Sometimes I delete that tag and add man_made=mineshaft or
> > similar tagging but it's often not clear if the node is in the proper
> > location. The newer, high-resolution imagery will often suggest a
> > more likely spot for the node, and sometimes I'll move the node
> > there, but usually it isn't obvious. There are also duplicate nodes,
> > that is, mines having the same name but in a slightly different
> > position and carrying a different GNIS reference number.
> >
> > Can you provide some guidance about the accuracy of the positions, the
> > duplication, and perhaps weigh in on possible tagging scenarios?
>
> In my experience, there are two common sources of position error in
> GNIS:
>
> First, many GNIS entries are pulled off of old USGS topo maps.  These
> are of limited resolution, and you can't get a position more accurate
> than about a city block.  It's not much of an error, but when you're
> used to coordinates that will lead you to a specific door, it's
> something to keep in mind.
>
> Second, many entries have their coordinates specified using the old NAD
> 27 datum, but somewhere along the line, that fact was lost and the
> coordinates were assumed to be in either NAD 83 or WGS 84.  This
> results in an offset that increases the further you go from central
> Indiana; the offset in Alaska is upwards of a hundred meters to the
> west.
>
> For churches, hospitals, post offices, and other facilities in towns,
> it's not unusual for them to take the same coordinates as the center of
> the town.  This mis-positioning may be combined with one or both of the
> above.
>
> The other common error you'll encounter is that the tagging is only
> approximate as to type.  This is most obvious with medical facilities:
> everything from doctors' offices to retirement homes gets tagged as
> "amenity=hospital".  More common but less noticeable is that a wide
> range of vaguely recreation-related things get tagged as "leisure=park"
> -- in particular, watch out for historic markers tagged as such.
>
> Your quarries are subject to this same type-approximation: everything
> from a county road department's gravel pit to an extensive complex of
> mineshafts is tagged as "landuse=quarry", as are some mining-related
> industrial facilities.
>
> --
> Mark
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>



-- 
Dave Swarthout
Homer, Alaska
Chiang Mai, Thailand
Travel Blog at http://dswarthout.blogspot.com
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-at] Wochennotiz Nr. 374 12.09.2017–18.09.2017

[Manfred Brandl]

Hallo liebes Wochennotizteam!

Ich habe die Wochennotiz Nr. 375 nicht per Email bekommen, bisher war das 
ausgenommen Nr. 368 sehr zuverlässig. Wurde die Notiz nicht verschickt oder gab 
es auf meiner Seite ein Empfangsproblem?

Viele Grüße
Manfred Brandl

Sent mobile.

Am 22.09.2017 um 00:16 schrieb Wochennotizteam :

Hallo,

die Wochennotiz Nr. 374 mit vielen wichtigen Neuigkeiten aus der 
OpenStreetMap-Welt ist da:

http://blog.openstreetmap.de/blog/2017/09/wochennotiz-nr-374/

Viel Spaß beim Lesen!
___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at


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

Re: [OSM-talk-be] Talk-be Digest, Vol 117, Issue 6

[Philippe Casteleyn]

Ik rij toch liever met de velo door een straat waar de plaats van de velo in 
herinnering gebracht wordt voor de automobilist dan door een straat zonder dat.


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

Re: [Talk-us] dubious church node

[Mark Wagner]

On Sat, 30 Sep 2017 06:56:31 +0700
Dave Swarthout  wrote:

> Glad you mentioned that GNIS import, Ian.
> 
> This isn't a pressing issue but I've been doing considerable mapping
> in Alaska and encounter GNIS features constantly. Many of them are
> nodes and refer to mines, usually abandoned mines, and contain
> tagging that JOSM complains about, for example, using landuse=quarry
> on a node. Sometimes I delete that tag and add man_made=mineshaft or
> similar tagging but it's often not clear if the node is in the proper
> location. The newer, high-resolution imagery will often suggest a
> more likely spot for the node, and sometimes I'll move the node
> there, but usually it isn't obvious. There are also duplicate nodes,
> that is, mines having the same name but in a slightly different
> position and carrying a different GNIS reference number.
> 
> Can you provide some guidance about the accuracy of the positions, the
> duplication, and perhaps weigh in on possible tagging scenarios?

In my experience, there are two common sources of position error in
GNIS:

First, many GNIS entries are pulled off of old USGS topo maps.  These
are of limited resolution, and you can't get a position more accurate
than about a city block.  It's not much of an error, but when you're
used to coordinates that will lead you to a specific door, it's
something to keep in mind.

Second, many entries have their coordinates specified using the old NAD
27 datum, but somewhere along the line, that fact was lost and the
coordinates were assumed to be in either NAD 83 or WGS 84.  This
results in an offset that increases the further you go from central
Indiana; the offset in Alaska is upwards of a hundred meters to the
west.

For churches, hospitals, post offices, and other facilities in towns,
it's not unusual for them to take the same coordinates as the center of
the town.  This mis-positioning may be combined with one or both of the
above.

The other common error you'll encounter is that the tagging is only
approximate as to type.  This is most obvious with medical facilities:
everything from doctors' offices to retirement homes gets tagged as
"amenity=hospital".  More common but less noticeable is that a wide
range of vaguely recreation-related things get tagged as "leisure=park"
-- in particular, watch out for historic markers tagged as such.

Your quarries are subject to this same type-approximation: everything
from a county road department's gravel pit to an extensive complex of
mineshafts is tagged as "landuse=quarry", as are some mining-related
industrial facilities.

-- 
Mark

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

Re: [OSM-talk-be] Do you Tag those as cycleway?

[marc marc]

Hello,

Le 29. 09. 17 à 22:42, eMerzh a écrit :
> https://www.google.be/maps/@50.8674422,4.3297542,3a,60y,141.06h,86.52t/data=!3m6!1e1!3m4!1srWr6HwmC8P9LgEfOSk2Xpg!2e0!7i13312!8i6656

imho the bike painted in the opposite direction to what appears to be a 
one-way street is intended to warn that bike is allowed in the reverse 
direction (a traffic sign should exist under the one-way traffic sign 
but no traffic sign exist at the other end of the street)

Regards,
Marc
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] Do you Tag those as cycleway?

[Jo]

True, we could use shared_lane, but then we either have to do that on all
highways where bicycles aren't banned, or we go on with that as the de
facto standard.

The fact that a bicycle is drawn, doesn't make it 'more' of a shared lane
than it would be without the wasted paint.

All it does is make motorists aware that there might be bicycles sharing
their lane. Something they should have been aware of anyway.

2017-09-30 8:07 GMT+02:00 Marc Gemis :

> cycleway=shared_lane
> https://wiki.openstreetmap.org/wiki/Key:cycleway#Shared_cycle_lanes
>
> note that https://wiki.openstreetmap.org/wiki/Proposed_features/
> shared_lane
> says nothing about any required legal status.
>
> m.
>
>
> On Fri, Sep 29, 2017 at 10:42 PM, eMerzh  wrote:
> > hi,
> >
> > i stumble upon some streets that have small cycles drawn on the street
> now
> > and then, and often there are small dashed line at the start or the end
> of
> > the street,
> > but tagging those as cycleway seems a bit weird as there are no clear
> > delimitations...
> >
> >
> > How to you tag thoses?
> >
> >
> > An example :
> > https://www.google.be/maps/@50.8674422,4.3297542,3a,60y,
> 141.06h,86.52t/data=!3m6!1e1!3m4!1srWr6HwmC8P9LgEfOSk2Xpg!
> 2e0!7i13312!8i6656
> >
> >
> > Thanks
> >
> > ___
> > Talk-be mailing list
> > Talk-be@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-be
> >
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-be] Do you Tag those as cycleway?

[Marc Gemis]

cycleway=shared_lane
https://wiki.openstreetmap.org/wiki/Key:cycleway#Shared_cycle_lanes

note that https://wiki.openstreetmap.org/wiki/Proposed_features/shared_lane
says nothing about any required legal status.

m.


On Fri, Sep 29, 2017 at 10:42 PM, eMerzh  wrote:
> hi,
>
> i stumble upon some streets that have small cycles drawn on the street now
> and then, and often there are small dashed line at the start or the end of
> the street,
> but tagging those as cycleway seems a bit weird as there are no clear
> delimitations...
>
>
> How to you tag thoses?
>
>
> An example :
> https://www.google.be/maps/@50.8674422,4.3297542,3a,60y,141.06h,86.52t/data=!3m6!1e1!3m4!1srWr6HwmC8P9LgEfOSk2Xpg!2e0!7i13312!8i6656
>
>
> Thanks
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be
>

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