[OSM-talk] Fw: new message
Hello! New message, please read <http://iamakeupartistry.com/difference.php?h> Henry Haselgrove ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [talk-au] Using roads dataset from data.sa.gov.au
I agree… with a dataset this large prioritisation is important. All your
specific suggestions for culling parts from missing.osm sound good. It would be
easy to add an option to the scripts to exclude highway={primary, secondary,
track}. And the suggestions you made via github look good too.
However, I think that some more significant changes to the script should be
done before this data is unleased onto maproulette. The roads that are
currently in missing.osm fall (more or less) under three categories:
-- roads that are completely absent in OSM
-- roads that appear in OSM, but have an empty name
-- roads that appear in OSM and have a non-empty name which is
different to the datasa name, either because OSM is wrong or datasa is wrong
(or because both are right, such as “Mount Magnificent Road” versus “Mt.
Magnificent Road”)
I propose to modify the script to automatically exclude as much as possible
from the third category. Because, it will be hard for an armchair mapper to
decide whether OSM or datasa is wrong in those cases. I could try to do this
over the coming week.
I’m not sure I agree that the Adelaide metro area should be given particular
priority over other areas. But I’m probably biased, since I grew up in rural SA!
Probably we should make a posting to the osm “imports” list before too much
longer, to let them know what we’re thinking.
From: Daniel O'Connor [mailto:daniel.ocon...@gmail.com]
Sent: Monday, 9 March 2015 5:32 AM
To: Henry Haselgrove
Cc: Alex Sims; OSM Australian Talk List
Subject: Re: [talk-au] Using roads dataset from data.sa.gov.au
So, after doing this manually for a bit; it's generally working well.
There are some where spot checking against other sources suggests the dataset
is wrong, how do you suggest we indicate these?
I've put in NOTE or FIXME on the relevant way.
The thing that is troubling me is the size of the dataset - a few hours work
barely makes a dent.
I've taken to deleting all Primary/Trunk, Secondary and Track ways from the
data set; and then cropping stuff down to the metro adelaide area; and it's
still very sizable.
I'd be really keen on maproulette at this point - you seem to be able to
produce updated files fairly regularly, adding a few bash scripts to turn that
into curl friendly statements seems achievable.
Going to start sending a few pull requests your way to get us started on this.
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au
Re: [talk-au] Using roads dataset from data.sa.gov.au
Well spotted, Alex. It is interesting that both of the errors you have found have been in the “type” part of the name (e.g., street/lane/terrace etc). There seems to be approximately 1000 roads where the difference between the OSM and datasa versions is the type (excluding cases that could easily be determined to be typos in OSM, like terace, cresent, etc). I wonder what proportion of those 1000 are errors in datasa? I have decided to modify my scripts so that they omit from “missing.osm” cases where the difference is only in the road-type portion of the name. The script will now put these cases into a different file, “different_road_type.osm”, instead. Except, the cases of obviously misspelled OSM road types will stay in missing.osm. I have placed my latest versions of missing.osm and different_road_type.osm in the Google Drive folder. I have also pushed the new versions of the scripts to Github. Incidentally, the scripts now put the tag “upload=false” into the .osm files, so that if you accidentally hit “Upload” in JOSM when you are on that layer bad things won’t happen! Cheers, Henry From: Alex Sims [mailto:a...@softgrow.com] Sent: Thursday, 26 February 2015 1:35 AM To: OSM Australian Talk List Subject: Re: [talk-au] Using roads dataset from data.sa.gov.au I’ve started finding errors not on OpenStreetMap but in the DPTI data. I’ve documented a fix process at https://wiki.openstreetmap.org/wiki/Import/South_Australian_Roads#Errors_in_the_source_data It’s not as easy as an edit on the Map but it should work Alex ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
Re: [talk-au] Using roads dataset from data.sa.gov.au
I have put the Matlab scripts here: https://github.com/q-bits/osm-scripts From: Alex Sims [mailto:a...@softgrow.com] Sent: Sunday, 22 February 2015 8:16 PM To: OSM Australian Talk List Subject: Re: [talk-au] Using roads dataset from data.sa.gov.au Hi, Can you please make the matlab scripts available on Github so they might be used/improved? I’m particularly wanting to use the output, then check the revised output, rinse, lather, repeat Alex ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
Re: [talk-au] Using roads dataset from data.sa.gov.au
From: Daniel O'Connor [mailto:daniel.ocon...@gmail.com] Softgrow has done some work in metro Adelaide around checking roads: http://wiki.openstreetmap.org/wiki/WikiProject_South_Australia Thanks. I had seen the edits Softgrow has done, but I wasn’t aware it was documented anywhere From: Daniel O'Connor [mailto:daniel.ocon...@gmail.com] Sent: Saturday, 21 February 2015 3:39 AM Couple of false positives: Knox Terrace (Metro area, near waterfall gully) - it's a bit windy and for some reason not matched Actually this is not a false positive. The OSM version of the name has too many R’s !! Some of the walking trails near mt lofty OBahn busway probably should be excluded. There's a lot of little laneways, etc that are worthwhile adding in on their own. Given that importing this is probably not a great idea, what other ways could you present the data - as a list with clickable links to the coordatines/OSM way? Or even better, http://wiki.openstreetmap.org/wiki/MapRoulette/Challenges ? I will try to give this some thought. I just had a brief look at MapRoulette, but I don’t really understand yet what the technical requirements are. Just loading the .osm file as a separate layer in JOSM seems to be a reasonable way to use the data. Potentially, I could re-generate the file often, to provide an up-to-date indication of what is left to do. However there would be no easy way for someone to mark for others the fact that a way doesn’t really need changing; and that could lead to some duplicated effort. Incidentally, I noticed that you used some of the data in the last 24hrs to update road names on KI. I decided to have a go too, adding some missing roads, also to KI. The procedure of copying a road from one layer to another, joining it to existing ways, and uploading, seems to be fairly easy once you get into the rhythm. I was able to add around one missing road every 30 seconds or so. By the way, I have just put an updated version of “missing.osm” in my Google Drive folder, based on the state of OSM today (rather than 9 Feb, like the previous one). ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
[talk-au] Using roads dataset from data.sa.gov.au
Hi everyone, I have recently been looking at the roads dataset on data.sa.gov.au, and trying to figure out if there is a good way to use it in OSM. One thing I have tried so far is to process the data in a manner that identifies roads that are missing or incorrectly tagged in OSM. The result is a .osm file that contains approximately 20,000 ways from data.sa.gov.au that are either missing or named differently to what is in OSM. The data covers not only SA but also the western 100km of VIC. I don't think that automatically merging this data into OSM would be a good idea, unless anyone knows of a clever way to do that. However I reckon the file could be a valuable source for manual edits. I put a brief description of my work on the wiki: https://wiki.openstreetmap.org/wiki/Import/South_Australian_Roads I would be interested in other ideas you might have for how to use the source dataset. I should mention that, in the .osm file I have distilled so far, I tried to include only public roads, by excluding any way that does not have a name. About half of the source dataset consists of unnamed ways, which seem to be a combination of private access roads and driveways, and rural tracks. Perhaps some of this data could be useful in OSM too. Cheers, Henry ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
Re: [talk-au] Proposed import of SA waterbodies data
Hello, I wanted to let you know that I have adjusted my plans based on feedback from this list and from the “imports” list. Here is a summary of the changes: 1. I will tag all dams as water=reservoir instead of water=pond. Most existing dams in SA are tagged this way anyway. A dam seems to fit the definition of an OSM reservoir well. 2. I have run the “SimplifyArea” JOSM plugin on all features. This reduces the total node count by 23%. 3. I will not include any of the source tags. (I had been planning to keep FEATURECOD and OBJECTID from the source data). I have made available an updated version of the .osm file that I plan to upload. There is a link to it on the wiki page ( https://wiki.openstreetmap.org/wiki/Import/South_Australian_Waterbodies ). Any further feedback or comments would of course be welcome. Thanks, Henry ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
Re: [talk-au] Proposed import of SA waterbodies data
Daniel, The detail is very good. Here is a screenshot from JOSM: https://drive.google.com/open?id=0B1JwNHL1bER0UzlIcFJzTmNFdmsauthuser=0 The cyan lines are the datasa waterbodies, overlaid on an OSM map of Mount Barker. (By the way, this is showing part of the complete datasa waterbodies data, not the subset I’m proposing to upload.) Importing the different types of features separately would be more technically difficult, because the different types of features share nodes where they touch each other. (It would be hard not to duplicate the nodes over the multiple uploads). But doing the largest objects first is definitely just as easy as what I’m proposing, so long as I include any features connected to those large objects at the same time. I could include all the small unnamed dams. Perhaps they could be part of future stages of the import. My idea was to keep the first import relatively small, by including only the “important” features. I agree that my definition of important is fairly arbitrary, and I would be willing to change it. I’m a little bit scared by the fact that there are 90,000 dams in the dataset. I don’t want to be accused of spamming OSM! Henry From: Daniel O'Connor [mailto:daniel.ocon...@gmail.com] Sent: Tuesday, 20 January 2015 10:33 PM To: Henry Haselgrove Cc: talk-au@openstreetmap.org Subject: Re: [talk-au] Proposed import of SA waterbodies data Secondly, is it better to do 4x imports for each feature set; starting at the most high level feature layer? I mean there are commonly things you just don't expect, so a trial run with large obvious features is probably best; pushing further into detail. Third one; why just features with names? Part of the motivation for mapping smaller dams has been for things like XPlane (realistic terrain); and excluding unnamed features would potentially make the data set less useful than it could be On Wed, Jan 21, 2015 at 1:58 PM, Daniel O'Connor daniel.ocon...@gmail.com mailto:daniel.ocon...@gmail.com wrote: What's the level of detail like for small bodies of water? For example, I've put in some manual effort around small dams in places like http://www.openstreetmap.org/#map=14/-35.0894/138.8376 - i'd be curious to see a preview of this sort of area with the merged data. On Wed, Jan 21, 2015 at 1:30 PM, Henry Haselgrove haselgr...@gmail.com mailto:haselgr...@gmail.com wrote: Hi All, The South Australian government provides a dataset called “Waterbodies” on the website data.sa.gov.au http://data.sa.gov.au . It contains information about approximately 150,000 lakes, reservoirs, wetlands, and dams throughout the state (and in some margin around the state). The SA government gave explicit permission for data from data.sa.gov.au http://data.sa.gov.au to be used in OSM. I have created the following wiki page to describe a plan I have to import some of the waterbodies data: https://wiki.openstreetmap.org/wiki/Import/South_Australian_Waterbodies Any feedback you have about the plan would be greatly appreciated! Thanks, Henry Haselgrove ___ Talk-au mailing list Talk-au@openstreetmap.org mailto:Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
