2009/12/18 Ross Scanlon :
> Likewise it's not necessary to have multiple nodes on a straight section of
> road (unless it's really long). As an example I just came across one
> straight road that was 150m long. It had 6 nodes on it where it could have
> been drawn with three. One at each end of
On Fri, Dec 18, 2009 at 4:31 PM, John Smith wrote:
> Technically all it does is introduce it to the map features page, but
> that doesn't mean you can't use it anyway, it doesn't mean you can't
> document it's usage on other pages, although some people say that map
> features shouldn't be updated
On Fri, Dec 18, 2009 at 7:12 PM, Ross Scanlon wrote:
> Likewise it's not necessary to have multiple nodes on a straight section of
> road (unless it's really long). As an example I just came across one
> straight road that was 150m long. It had 6 nodes on it where it could have
> been drawn with
2009/12/18 Steve Bennett :
> In that case, the voting means nothing at all? Weird.
It's a left over practise from a time it would have been more
appropriate/useful, but since the number of users have increased by
several orders of magnitude it has become a much less efficient way to
do things.
>
2009/12/18 Steve Bennett :
> I'm guilty of this sometimes. One reason for me comes from the method of
> tracing: zoom in, mark points along the longest straight stretch you can
> see, then pan the map, repeat, etc. If you're very zoomed in, you can't tell
> that the road will be straight off the sc
As per email below, intersection_simple.jpg is the method I have adopted.
Agree with multiple nodes on straight roads, I have been fixing them up as I
find them.
Separated ways is an interesting one and people do it differently. I am of
the opinion that they have to be 'physically separate' ie ther
On Fri, 18 Dec 2009 21:13:44 +1100
Steve Bennett wrote:
> On Fri, Dec 18, 2009 at 7:12 PM, Ross Scanlon wrote:
>
> > Likewise it's not necessary to have multiple nodes on a straight section of
> > road (unless it's really long). As an example I just came across one
> > straight road that was 1
> Separated ways is an interesting one and people do it differently. I am of
> the opinion that they have to be 'physically separate' ie there must be some
> barrier (island) between them (other than a solid white line - which can be
> seen in the link to the OSM map of the intersection under curre
On Fri, Dec 18, 2009 at 11:43 PM, Ross Scanlon wrote:
> Better way to do it is zoomed out so you can see the whole section you want
> to trace. Mark an end point then mark the other end. Then zoom and
> accurately adjust the end points, once they are in the correct place then
> add extra points
2009/12/18 Steve Bennett :
> Yeah but then if there are curvy bits – which I want to be maximally zoomed
> in for – that doesn't work. Personally I'm not seeing a lot of harm in
> excess nodes. Of all the things you could do wrong, it ranks pretty low in
> harm.
You're right, there is no harm in i
> > Better way to do it is zoomed out so you can see the whole section you want
> > to trace. Mark an end point then mark the other end. Then zoom and
> > accurately adjust the end points, once they are in the correct place then
> > add extra points if necessary.
> >
>
> Yeah but then if there a
There is also Vic police locations as part of the
data.australia.gov.au release, it's under cc-by:
http://data.australia.gov.au/406
Even has lat/lon, but isn't listed under the geography section...
Makes me wonder if there are other similar datasets that aren't listed
under geography but have lat
I just took a look at a few in JOSM and they must have used some other
datum, if anyone call tell me which one and/or how to convert to WGS84
I'll update the osm file.
___
Talk-au mailing list
Talk-au@openstreetmap.org
http://lists.openstreetmap.org/list
Or just another case of bad geocoding...
___
Talk-au mailing list
Talk-au@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-au
I've been looking over the data.australia.gov.au site some more, so
far there is a kml file for vic hospitals, as a result most of the
useful information is in html type formating and seems to include a
lot of disclaimers about the information being best effort/use at own
risk...
00clampToGround14
I should have included a direct link to the page:
http://data.australia.gov.au/404
___
Talk-au mailing list
Talk-au@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-au
Another document with lat/lon data, but this one will need to be dealt
with manually, contains locations and types of projects money is being
spent on, seems to be useful for extracting school and park locations,
and locations of rail way crossings/bridges that are being upgraded,
among other thing
Yet another document with lat/lon that wasn't in the Geography category:
http://data.australia.gov.au/80
I've converted this to an osm file:
http://map-data.bigtincan.com/data/centrelink.osm.bz2
Wasn't sure how to tag these so came up with the following:
The opening hours could be
Department of Planning and Infrastructure (NT) has a bunch of data
uploaded to data.australia.gov.au which includes lat/lon:
http://data.australia.gov.au/76
This spread sheet includes schools, parks, fire/ambulence stations,
libraries, museums and aboriginal communities.
Majority of the data is
2009/12/19 Aun Johnsen :
> For changing roads, I think the future of changesets will allow us to revert
> changes as well as have a way to retrieve historical data. I guess that a
> future API version will allow you to see "how the world looked in 2009", so
> that non-existing roads doesn't need to
Why wouldn't the address be entered using the Karlsruhe system?
Is the data all in one line and it would need more processing?
I normally enter urls using the url tag.
Keep up the great work!
Evan
On Friday 18 Dec 2009 16:59:01 John Smith wrote:
> Yet another document with lat/lon that wasn't in
On Sat, 19 Dec 2009, John Smith wrote:
> I should have included a direct link to the page:
>
> http://data.australia.gov.au/404
>
There are other interesting ones
South Australian Boat Ramp Locations
http://data.australia.gov.au/99
Medicare Offices is Just addresses
There is a link to
http://www.a
On Fri, Dec 18, 2009 at 6:12 PM, Ross Scanlon wrote:
>
> I have not changed the current intersection in osm but here are two screen
> shots of the intersection in josm.
>
> http://www.4x4falcon.com/osm/junctions/intersection_messy.jpg
> http://www.4x4falcon.com/osm/junctions/intersection_simple.j
On Sat, Dec 19, 2009 at 1:03 AM, John Smith wrote:
>
> ... seems to include a
> lot of disclaimers about the information being best effort/use at own
> risk...
Probably just covering their back - because people looking for a
hospital do tend to be "at risk" if the data's off...
_
On Fri, Dec 18, 2009 at 8:10 PM, Steve Bennett wrote:
>
> In that case, the voting means nothing at all? Weird.
>From my perspective, voting's similar to asking for opinions on an
email list, just with the added benefit of yes/no responses and
documentation of results.
__
Roy Wallace wrote:
> +1. A problem with the router requires a simple ROUTER fix. The router
> just needs to be told that when entering a junction with a roundabout,
> that also happens to have an exit, that exit counts as the "first
> exit".
I can just see the people at Garmin falling over themse
On Sat, Dec 19, 2009 at 8:31 AM, Roy Wallace wrote:
> The real issue here is "what are we mapping" - and with the
> intersection example, the issue seems to be whether the ways should
> accurately correspond to geographic reality (_messy), or not
> (_simple).
>
IMHO, it's quite simple: we proba
On Sat, Dec 19, 2009 at 2:22 AM, John Smith wrote:
> Another document with lat/lon data, but this one will need to be dealt
> with manually, contains locations and types of projects money is being
> spent on, seems to be useful for extracting school and park locations,
> and locations of rail way
Yeah, good work. Should the name be "Bairnsdale Centrelink" or just
"Centrelink"?
___
Talk-au mailing list
Talk-au@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-au
Steve Bennett wrote:
> Yeah, good work. Should the name be "Bairnsdale Centrelink" or just
> "Centrelink"?
I'm all for putting town/suburb names in as well. One place where it
matters is looking up POIs on GPS units.
These are sorted by proximity to current location. And when using the
featu
On Sat, Dec 19, 2009 at 9:46 AM, John Henderson wrote:
>
> I thought long and hard about this issue before I make the first
> "correction" to a local roundabout. I came to the conclusion that
> roundabout entry and exit points should be separate.
Sure, and I see the logic - but the fact you need
On Sat, Dec 19, 2009 at 10:28 AM, John Henderson wrote:
> Steve Bennett wrote:
>> Yeah, good work. Should the name be "Bairnsdale Centrelink" or just
>> "Centrelink"?
>
> I'm all for putting town/suburb names in as well. One place where it
> matters is looking up POIs on GPS units.
>
> These are
On Sat, Dec 19, 2009 at 11:54 AM, Roy Wallace wrote:
> Sure, and I see the logic - but the fact you needed to "think long and
> hard" means it's probably better if the routing can be fixed to cope
> with either kind of mapping.
>
Yes. Although if we're trying to make our map data work with route
2009/12/19 Roy Wallace :
> On Sat, Dec 19, 2009 at 1:03 AM, John Smith wrote:
>>
>> ... seems to include a
>> lot of disclaimers about the information being best effort/use at own
>> risk...
>
> Probably just covering their back - because people looking for a
> hospital do tend to be "at risk" if
On Sat, Dec 19, 2009 at 12:00 PM, Roy Wallace wrote:
> But isn't this a problem with the user i.e. the GPS unit software?
> I.e. shouldn't the suburb be retrieved from an admin boundary if
> required? IMHO the name=* value should be the name. If it's actually
> called "Bairnsdale Centrelink" then
2009/12/19 Liz :
> On Sat, 19 Dec 2009, John Smith wrote:
>> I should have included a direct link to the page:
>>
>> http://data.australia.gov.au/404
>>
> There are other interesting ones
> South Australian Boat Ramp Locations
> http://data.australia.gov.au/99
Yea, the boat ramps and boating hazar
On Sat, 19 Dec 2009, John Smith wrote:
> 2009/12/19 Liz :
> > On Sat, 19 Dec 2009, John Smith wrote:
> >> I should have included a direct link to the page:
> >>
> >> http://data.australia.gov.au/404
> >
> > There are other interesting ones
> > South Australian Boat Ramp Locations
> > http://data.au
2009/12/19 Evan Sebire :
> Why wouldn't the address be entered using the Karlsruhe system?
I did it this way because I think we should be verifying the
information, not just entering it. Although if people think it should
be dealt with differently I'm happy to update the uploaded files to be
somet
2009/12/19 Steve Bennett :
> Yeah, good work. Should the name be "Bairnsdale Centrelink" or just
> "Centrelink"?
Generally places like this are in context when you are there but on
maps the context is lost a little so I think it's best to have the
suburb as part of the name.
_
2009/12/19 John Henderson :
> Steve Bennett wrote:
>> Yeah, good work. Should the name be "Bairnsdale Centrelink" or just
>> "Centrelink"?
>
> I'm all for putting town/suburb names in as well. One place where it
> matters is looking up POIs on GPS units.
+1
The BP locations, imported the other d
2009/12/19 Steve Bennett :
> IMHO, the tag "name" is really not enough. I've often wanted at least three
> tags:
> 1) The genuine most official name of the place - in this case, Bairnsdale
> Centrelink
Should I switch the order on the names from 'Centrelink Bairnsdale' to
'Bairnsdale Centrelink' ?
On Sat, Dec 19, 2009 at 11:07 AM, Steve Bennett wrote:
>
> I feel weird tagging "name=Bowls Club" - that's clearly not the name
I would feel weird too! If you don't know the name, PLEASE don't enter a name=*.
___
Talk-au mailing list
Talk-au@openstreet
> Automatically inserting extra ways? Could work. Would be good to decide once
> and for all how to map these things rather than letting the current
> ambiguity reign.
>
> Not that "deciding" means we have to immediately go out and fix every
> roundabout, but a clear "preferred" and "deprecated" d
2009/12/19 Roy Wallace :
> But isn't this a problem with the user i.e. the GPS unit software?
> I.e. shouldn't the suburb be retrieved from an admin boundary if
> required? IMHO the name=* value should be the name. If it's actually
> called "Bairnsdale Centrelink" then fine, but I wouldn't add it j
2009/12/19 Steve Bennett :
> Good stuff. Worth making a wiki page to collect all this information.
Volunteering? :)
___
Talk-au mailing list
Talk-au@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-au
2009/12/19 Elizabeth Dodd :
> Operating mines had lat and long
> Mineral processing plants didn't
> any of these things should be big enough to see on satellite imagery with a
> rough idea of where to start looking
Hmmm I must have missed that dataset...
__
2009/12/19 Ross Scanlon :
> The first is easy, is quick to implement and brings the roundabouts into line
> with the wiki, the second may take some time.
As I stated some time ago it might be good to document this on the
wiki as to how not to do a roundabout, I wasn't aware and even when I
explai
2009/12/19 Steve Bennett :
> Yes. Although if we're trying to make our map data work with routers we
> can't fix (eg, Garmin), then we're in an interesting situation.
Depends how much control the preprocessing software has over garmin
devices, I don't have a garmin so I can't test etc.
> ("Don't
On Sat, 19 Dec 2009 07:31:59 +1000
Roy Wallace wrote:
> This is an interesting example. The "_messy" and "_simple" techniques,
> of course, could just as well be described as "_complete" and
> "_approximate", etc.
No _messy is over mapped and _simple is accurate.
> The real issue here is "what
On Sat, Dec 19, 2009 at 12:24 PM, Ross Scanlon wrote:
>
>> This is an interesting example. The "_messy" and "_simple" techniques,
>> of course, could just as well be described as "_complete" and
>> "_approximate", etc.
>
> No _messy is over mapped and _simple is accurate.
This is subjective and,
2009/12/19 Roy Wallace :
> This is subjective and, as I said, depends on "what we are mapping".
> E.g. IF we are mapping the "centrelines of paths of travel" in terms
> of geographic location, clearly _messy is more accurate/complete. But
> that's a big IF. I'm not saying _messy is better, I'm just
On Sat, 19 Dec 2009 11:31:45 +1000
John Smith wrote:
> 2009/12/19 Ross Scanlon :
> > The first is easy, is quick to implement and brings the roundabouts into
> > line with the wiki, the second may take some time.
>
> As I stated some time ago it might be good to document this on the
> wiki as t
> As I keep advocating, we should be able to map lanes, but it makes no
> sense to try and use ways to do this because as Ross keeps pointing
> out it just looks messy.
And becomes unusable on small screens.
> > Yes, fair enough. But what if someone wants to mark the geographic
> > locations of t
2009/12/19 Ross Scanlon :
>> As I keep advocating, we should be able to map lanes, but it makes no
>> sense to try and use ways to do this because as Ross keeps pointing
>> out it just looks messy.
>
> And becomes unusable on small screens.
My advocacy is to treat ways like relations, you group th
I think I've finally finished NSW, ACT and the NT... 3 down 5 to go...
___
Talk-au mailing list
Talk-au@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-au
> My advocacy is to treat ways like relations, you group the lanes into
> a way and the tags from the way cascade to the lanes or can be
> overriden, however for small screens you only use ways and ignore
> lanes, although the lanes could be used for routing/turning even if
> not displayed.
This i
On Sat, Dec 19, 2009 at 12:23 PM, John Smith wrote:
> 2009/12/19 Steve Bennett :
> > Good stuff. Worth making a wiki page to collect all this information.
>
> Volunteering? :)
>
If you really want, email me the list of URLs.
___
Talk-au mailing list
Tal
On Sat, Dec 19, 2009 at 12:19 PM, Roy Wallace wrote:
> On Sat, Dec 19, 2009 at 11:07 AM, Steve Bennett
> wrote:
> >
> > I feel weird tagging "name=Bowls Club" - that's clearly not the name
>
> I would feel weird too! If you don't know the name, PLEASE don't enter a
> name=*.
>
This must be impo
On Sat, Dec 19, 2009 at 4:01 PM, Ross Scanlon wrote:
>
> http://wiki.openstreetmap.org/wiki/User:Santiago1504/MultiLane
>
> http://wiki.openstreetmap.org/wiki/Proposed_features/lane_and_lane_group
>
>
I should have a read before commenting further. But I won't.
> In the meantime I suggest the
On Sat, Dec 19, 2009 at 3:50 PM, Steve Bennett wrote:
>> >
>> > I feel weird tagging "name=Bowls Club" - that's clearly not the name
>>
>> I would feel weird too! If you don't know the name, PLEASE don't enter a
>> name=*.
>
> This must be important to you. Why so?
People tag "A=B" when they know
On Sat, Dec 19, 2009 at 6:15 PM, Roy Wallace wrote:
> People tag "A=B" when they know A does not equal B. Do you really want
> me to explain why this isn't a good idea?
>
You want steak. I only have chicken. I want you to explain why you prefer to
starve.
More prosaically, many maps use descrip
2009/12/19 Steve Bennett :
> On Sat, Dec 19, 2009 at 12:23 PM, John Smith
> wrote:
>>
>> 2009/12/19 Steve Bennett :
>> > Good stuff. Worth making a wiki page to collect all this information.
>>
>> Volunteering? :)
>
> If you really want, email me the list of URLs.
I thought you meant for the sti
2009/12/19 Steve Bennett :
> The right solution would probably include a way to automatically subdivide a
> road into lanes, but seamlessly allow individually mapped lanes where
> appropriate.
That's the general idea, the implementation is the sticking point :)
___
2009/12/19 Ross Scanlon :
> Which is what the lanes_group relation would do as the relation is attached
> to the way.
As I said, it'd be nice to cascade the tags from ways to lanes, but it
seems at this point in time some sort of relation hack is the only
feasible solution unless we want to spend
64 matches
Mail list logo
