Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-24 Thread Yuchen Pei
On Tue 2023-10-24 07:04:34 +1100, Andrew Harvey wrote: > On Mon, 23 Oct 2023, 11:12 pm Andrew Harvey, > wrote: >>> Do they say that the data is supposed to be >>> updated weekly? >> That order was set as a weekly recurring order. > I just got the reccuring email for my orders, so this

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-23 Thread Andrew Harvey
On Mon, 23 Oct 2023, 11:12 pm Andrew Harvey, wrote: > > >> Do they say that the data is supposed to be >> updated weekly? >> > > That order was set as a weekly recurring order. > I just got the reccuring email for my orders, so this appears fixed now and they will be fresh.

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-23 Thread Andrew Harvey
On Mon, 23 Oct 2023 at 00:25, Yuchen Pei wrote: > This is the URL > > https://s3.ap-southeast-2.amazonaws.com/cl-isd-prd-datashare-s3-delivery/Order_FDBZT5.zip > > Is it from the DELWP? Yes > Do they say that the data is supposed to be > updated weekly? > That order was set as a weekly

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-23 Thread Yuchen Pei
On Mon 2023-10-23 00:25:21 +1100, Yuchen Pei wrote: > On Thu 2023-10-19 21:47:28 +1100, Andrew Harvey wrote: >> I found the process was only using Vicmap data from last year, so I've >> updated that. The URL it's using should be serving new data every week but >> I'm not sure it was not

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-22 Thread Yuchen Pei
On Thu 2023-10-19 21:47:28 +1100, Andrew Harvey wrote: > I found the process was only using Vicmap data from last year, so I've > updated that. The URL it's using should be serving new data every week but > I'm not sure it was not happening previously. This is the URL

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-19 Thread Andrew Harvey
I found the process was only using Vicmap data from last year, so I've updated that. The URL it's using should be serving new data every week but I'm not sure it was not happening previously. So we'll need to monitor this if the import is delayed further. On Sat, 7 Oct 2023 at 20:48, Yuchen Pei

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-16 Thread Andrew Harvey
On Tue, 17 Oct 2023 at 12:13, Phil Wyatt wrote: > Personally I think it should be suburb and postcode (drop the country) > https://gitlab.com/alantgeo/vicmap2osm#inclusion-of-addrsuburb-addrpostcode-and-addrstate It was noted that there is not a consensus within the community, therefore I

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-16 Thread Phil Wyatt
Personally I think it should be suburb and postcode (drop the country) From: Warin <61sundow...@gmail.com> Sent: Monday, October 16, 2023 5:53 PM To: Graeme Fitzpatrick ; Yuchen Pei Cc: talk-au@openstreetmap.org Subject: Re: [talk-au] How to efficiently improve AU address co

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-16 Thread Yuchen Pei
On Mon 2023-10-16 20:32:16 +1100, Yuchen Pei wrote: > On Mon 2023-10-16 17:01:23 +1100, Andrew Harvey wrote: >> That's okay. I created https://github.com/alantgeo/vicmap2osm as a mirror >> of the GitLab code, happy to collaborate via Issues and Pull Requests there. > Thanks, but Github is bad.

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-16 Thread Yuchen Pei
On Mon 2023-10-16 15:35:13 +1100, Andrew Harvey wrote: > On Mon, 16 Oct 2023 at 15:16, Yuchen Pei wrote: >> On Mon 2023-10-16 14:51:00 +1100, Andrew Harvey wrote: >> > On Sat, 7 Oct 2023 at 20:40, Yuchen Pei wrote: >> > [... 38 lines elided] >> > mr2osc.mjs is used in Stage 2 (replacing

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-16 Thread Yuchen Pei
On Mon 2023-10-16 17:01:23 +1100, Andrew Harvey wrote: > That's okay. I created https://github.com/alantgeo/vicmap2osm as a mirror > of the GitLab code, happy to collaborate via Issues and Pull Requests there. Thanks, but Github is bad. It requires running proprietary javascript[1] to create

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-16 Thread Warin
On 16/10/23 14:06, Graeme Fitzpatrick wrote: Do we need the country, city & post code fields? No. Thanks Graeme On Mon, 16 Oct 2023 at 12:23, Yuchen Pei wrote: On Tue 2023-10-03 19:51:13 +1100, Warin wrote: > On 3/10/23 14:27, Andrew Harvey wrote: > [... 12 lines

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-16 Thread Andrew Harvey
That's okay. I created https://github.com/alantgeo/vicmap2osm as a mirror of the GitLab code, happy to collaborate via Issues and Pull Requests there. On Mon, 16 Oct 2023 at 15:49, Yuchen Pei wrote: > On Mon 2023-10-16 15:35:13 +1100, Andrew Harvey wrote: > > > [... 86 lines elided] > > > Are

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-15 Thread Yuchen Pei
On Mon 2023-10-16 15:35:13 +1100, Andrew Harvey wrote: > [... 86 lines elided] > Are you on the OSM World Discord? I do not use Discord, because it is proprietary. I am on IRC, xmpp, mastodon and Signal - do you use any of these? If not can you suggest another free software option? Best,

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-15 Thread Andrew Harvey
On Mon, 16 Oct 2023 at 15:16, Yuchen Pei wrote: > On Mon 2023-10-16 14:51:00 +1100, Andrew Harvey wrote: > > > On Sat, 7 Oct 2023 at 20:40, Yuchen Pei wrote: > > > [... 38 lines elided] > > > mr2osc.mjs is used in Stage 2 (replacing street_number=x/y with > > unit_number=x &&

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-15 Thread Yuchen Pei
On Mon 2023-10-16 14:51:00 +1100, Andrew Harvey wrote: > On Sat, 7 Oct 2023 at 20:40, Yuchen Pei wrote: > [... 38 lines elided] > mr2osc.mjs is used in Stage 2 (replacing street_number=x/y with > unit_number=x && street_number=y). For example, the Makefile rule >

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-15 Thread Andrew Harvey
On Sat, 7 Oct 2023 at 20:40, Yuchen Pei wrote: > On Tue 2023-10-03 19:51:13 +1100, Warin wrote: > > > [... 14 lines elided] > > > OK, what is needed to be done for "Stage 2 - Set unit from > > housenumber"? > > > Further testing of the upload script. The changes themselves

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-15 Thread Graeme Fitzpatrick
Do we need the country, city & post code fields? Thanks Graeme On Mon, 16 Oct 2023 at 12:23, Yuchen Pei wrote: > On Tue 2023-10-03 19:51:13 +1100, Warin wrote: > > > On 3/10/23 14:27, Andrew Harvey wrote: > > > [... 12 lines elided] > > > OK, what is needed to be done for "Stage 2 -

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-15 Thread Yuchen Pei
On Tue 2023-10-03 19:51:13 +1100, Warin wrote: > On 3/10/23 14:27, Andrew Harvey wrote: > [... 12 lines elided] > OK, what is needed to be done for "Stage 2 - Set unit from > housenumber"? > Further testing of the upload script. The changes themselves are > pretty safe.

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-07 Thread Yuchen Pei
On Sat 2023-10-07 20:40:47 +1100, Yuchen Pei wrote: > [... 26 lines elided] > mr2osc.mjs is used in Stage 2 (replacing street_number=x/y with > unit_number=x && street_number=y). For example, the Makefile rule > dist/unitFromNumber.osc is generated using this script. I have generated > the osc

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-07 Thread Yuchen Pei
On Tue 2023-10-03 19:51:13 +1100, Warin wrote: > [... 14 lines elided] > OK, what is needed to be done for "Stage 2 - Set unit from > housenumber"? > Further testing of the upload script. The changes themselves are > pretty safe. It's using a custom uploader and if

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-03 Thread Warin
On 3/10/23 14:27, Andrew Harvey wrote: On Mon, 2 Oct 2023 at 23:48, Yuchen Pei wrote: On Mon 2023-10-02 21:42:01 +1100, Andrew Harvey wrote: > [... 15 lines elided] > It's been a while since I worked on this, but I believe it was the > matching of existing OSM addresses to

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-02 Thread Andrew Harvey
On Mon, 2 Oct 2023 at 23:48, Yuchen Pei wrote: > On Mon 2023-10-02 21:42:01 +1100, Andrew Harvey wrote: > > > [... 15 lines elided] > > > It's been a while since I worked on this, but I believe it was the > > matching of existing OSM addresses to Vicmap, and that matching > > affects most of the

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-02 Thread Andrew Harvey
On Tue, 3 Oct 2023 at 00:10, Yuchen Pei wrote: > On Mon 2023-10-02 21:35:10 +1030, Daniel O'Connor wrote: > > > While OSM doesn't have layers, https://openaddresses.io/ more or less > > acts as the address layer. The datasets there aren't all ODBL, but > > they are generally open. It includes

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-02 Thread Simon Poole
Except if something has massively changed, the GNAF data isn"t actually open. Am 2. Oktober 2023 13:05:10 MESZ schrieb Daniel O'Connor : >While OSM doesn't have layers, https://openaddresses.io/ more or less acts >as the address layer. The datasets there aren't all ODBL, but they are >generally

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-02 Thread Yuchen Pei
On Mon 2023-10-02 21:35:10 +1030, Daniel O'Connor wrote: > While OSM doesn't have layers, https://openaddresses.io/ more or less > acts as the address layer. The datasets there aren't all ODBL, but > they are generally open. It includes GNAF. Thanks, I didn't know of openaddresses, but I'm a bit

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-02 Thread Yuchen Pei
On Mon 2023-10-02 21:42:01 +1100, Andrew Harvey wrote: > [... 15 lines elided] > It's been a while since I worked on this, but I believe it was the > matching of existing OSM addresses to Vicmap, and that matching > affects most of the import stages. OK, what is needed to be done for "Stage 2 -

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-02 Thread Daniel O'Connor
While OSM doesn't have layers, https://openaddresses.io/ more or less acts as the address layer. The datasets there aren't all ODBL, but they are generally open. It includes GNAF. Given how frequently addresses update, to keep it in sync with OSM would be pretty significant and hard to reconcile

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-02 Thread Andrew Harvey
On Sun, 1 Oct 2023 at 23:16, Yuchen Pei wrote: > > The preparation and planning is well progressed in my view. There is > > always going to be a long tail of corner cases and I was attempting to > > handle more of these in the code and that never got finished. We > > probably would be better to

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-01 Thread Yuchen Pei
I am re-sending the following message without the attachment, as the original message is held in the moderation queue due to its size. Sorry for any duplication if that one is approved, but I might forget if I don't resend, and the delay could also be confusing to people because I already sent

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-01 Thread Graeme Fitzpatrick
On Sun, 1 Oct 2023 at 21:34, Warin <61sundow...@gmail.com> wrote: > Then simply the major cities of Brisbane Brisbane itself is already done via an import of BCC data a few years ago, but this is only "Brisbane" itself, not the surrounding "cities" Thanks Graeme

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-01 Thread Yuchen Pei
On Sun 2023-10-01 21:33:45 +1100, Warin wrote: > [... 25 lines elided] > --- > I have been adding addr:street to those places with addr:housenumber > where possible. If you are adding addr:housenumber then it is not much > more work to add the addr:street data. There are a few

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-01 Thread Yuchen Pei
On Sun 2023-10-01 21:20:38 +1100, Andrew Harvey wrote: > [... 23 lines elided] > Is there a way to efficiently improve the address coverage in > Australia? > What are the main roadblocks? > I don't have the numbers, but StreetComplete would already be helping > already to improve

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-01 Thread Warin
On 1/10/23 18:08, Yuchen Pei wrote: On 1 October 2023 12:56:20 GMT+11:00, Phil Wyatt wrote: but I also see that the VIC import is well progressed How is it well progressed, do you have a link showing the progress? From what I see it seems to be stalled. I'd take it that someone is

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-01 Thread Andrew Harvey
On Sun, 1 Oct 2023 at 12:34, Yuchen Pei wrote: > Hello, > > I read in a 6-year old post[1] that the Netherlands had an address > coverage of over 99%. This made me curious what would be the Australian > number. G-NAF boasts 15M addresses[2], whereas according to > metrics.improveosm.org there

Re: [talk-au] How to efficiently improve AU address coverage?

2023-10-01 Thread Yuchen Pei
On 1 October 2023 12:56:20 GMT+11:00, Phil Wyatt wrote: > but I also see that the VIC > import is well progressed How is it well progressed, do you have a link showing the progress? From what I see it seems to be stalled. -- Best, Yuchen Sent from a mobile device. Please excuse my

Re: [talk-au] How to efficiently improve AU address coverage?

2023-09-30 Thread Phil Wyatt
Pei Sent: Sunday, October 1, 2023 12:31 PM To: talk-au@openstreetmap.org Subject: [talk-au] How to efficiently improve AU address coverage? Hello, I read in a 6-year old post[1] that the Netherlands had an address coverage of over 99%. This made me curious what would be the Australian number. G

Re: [talk-au] How to efficiently improve AU address coverage?

2023-09-30 Thread Yuchen Pei
On Sun 2023-10-01 12:30:50 +1100, Yuchen Pei wrote: > [... 19 lines elided] > For Victoria there was an initiative to import vicmap addresses[4][5], > I wonder how many addresses it will add, Just noticed the wiki page, according to which it would increase the VIC address coverage to >95%:

[talk-au] How to efficiently improve AU address coverage?

2023-09-30 Thread Yuchen Pei
Hello, I read in a 6-year old post[1] that the Netherlands had an address coverage of over 99%. This made me curious what would be the Australian number. G-NAF boasts 15M addresses[2], whereas according to metrics.improveosm.org there are less than 1.2M address points mapped in AU[3], so that