More4me2do

I misunderstood what you wrote our setup is identical except we enabled 6 buttons while you enabled 5 buttons. The 6th button is labeled "Infirm" to reserve an address that is suitable for the elderly and infirm to approach. Sometimes it is like driving territory or a flat approach to the door. We mark those either before or during the ministry. This way the elderly and infirm are also enjoying the ministry especially during campaigns.

We have almost the same but why did you use a 2nd button for Not Home? When I press the Not Home button I get a choice to tick 1st or 2nd. When ticked 1st it becomes orange, when ticked 2nd it become grey and now is part of the phone/letter writing territory. Button 6 we use to reserve houses for "Infirm"

Thanks that was my thinking with the Data Protection Laws in the EU. Well still will have a VPN on the Surface Pro just in case.

Question for anyone who knows what happens when you travel with NWS. My Surface Pro 11 running Win 11 is registered and connected to the North American server. I am traveling to Australia will I have problem accessing and working with the North American server while being in the Southern hemisphere? Is using a VPN and logging into a North American server before connecting to the NWS servers a requirement to work with NWS while being away from the home country? Thanks for any help.

That would be another explanation that the connectivity between NWS and the mapping services were disrupted in whatever form that would be. In addition when comparing Google, Bing and Here there were always slight differences, however, all three of NWS map services showed the same results when I took the screenshots, now there is a slight difference at least in the satellite views.

Well guess what, the very screenshots that I posted and that @foghorn confirmed, can no longer be reproduced. So, in the last 22 hours this was fixed. As I quoted in my earlier comments that when they replaced Bing with the present map service providers several months ago, I tested their accuracy and it was fine. Therefore somewhere in the bowels of the code maybe something was corrected that did not require a NWS update.

Your explanation makes perfect sense and that is what I was afraid of. In my initial digitizing project I sampled some addresses using Google, Bing and Here to make sure the addresses were correct and all three were giving the same results. Then I used the Bing Satellite view in NWS to finish our digitizing. Now the only thing left is boots on the ground verifying that the maps are correct and delete or add addresses according to what is really there in the territory using Google and Bing. I posted this just to make anyone aware of the fact that the creating of addresses at the moment in NWS is broken and unusable as either you get wrong street names, wrong numbers or "unnamed road". Google, Bing and Here give you the correct addresses but all the map providers in the NWS are unusable. If you want to experiment that is fine and may give us an answer to the question do Mapbox and ThinkGeo use OSM as it looks right now that they do? But my situation is that our territory is finished and only corrections from boots on the ground is now needed. Thank you so much for putting a perspective on this problem.

Thank for replying and I do value your contributions in this thread. Since you are an editor for OpenStreetMap I have included an image using OpenStreetMap that makes my point. The correct address is 11337 Teakwood Ct and it was created using Bing in March 2025. According to the taxation department the primary structure of this residence was built in 2000 the first sale of this house was in 2008. There should be no time factor since 25 years have passed to get this in the maps. In March 2025 I created this territory and Bing was spot on NONE of the providers listed in NWS now get this correct and ALL of them show unnamed Road. Something is rotten in the state of Denmark. The only explanation I have is something quite serious has happened in the Territory Module with the map providers. None of the points you make are applicable in this case. Since these errors did not appear after they replaced Bing with Mapbox and added ThinkGeo satellite view, I did a spot check to see if they can be used for adding addresses and they were the same as the ones Bing entered. So if you have access to the developers, pass on the thought that they have a serious problem with creating new addresses unless this is just the case in the US.

HOUSTON we have a PROBLEM in the NWS Territory Module! To set the stage I have finished early in 2025 digitizing all our territory in NWS using as map service provider the Bing Satellite view when it was still available. In addition I compared its results for accuracy with the Google Map service plus consulted the Department of Assessments and Taxation to ensure that the address is a residence and not just a plot belonging to some developer. Since the change of dropping Bing and replacing it with the Map Service providers OpenStreetMap, MapBox and ThinkGeo in the territory module ALL the map service providers are now faulty and incorrect. When clicking in the satellite view on a clearly visible dwelling place some will now show "unnamed Road" while others will have an incorrect or erroneous address. When correcting addresses in any given territory by right clicking on the address ALL the map service providers now show the same results either an address which is not existing in the Department of Assessments and Taxation data base or an incorrect street address number. This will now be a problem or lengthy process for adding addresses of newly build homes to territories. For finished digitized territories the Google and Bing map services will help with the maintenance. A plea to the developers please either bring back the Bing Map Service provider or correct the present ones. Something is VERY fishy here, I have never seen Map Services to agree and show the same results for a particular address. It almost looks like as if NWS's 3 different Map Service providers are all working from the same data base which is either corrupt, outdated or faulty in some other way. Please bring back Bing.

1. The DNCs are a hot topic and it would be a disadvantage to automatically notify the territory servant who then enters any DNCs since the majority of publisher have no idea what a DNC is. For example some have marked extensive No Soliciting descriptions as a DNC since it stated no Religion. A DNC is when the householder tells you directly face to face please Do Not Call at this door again. It creates additional work as now the Elders have to check in a year is this still a DNC. If there is an extensive No Soliciting sign you have to address the white elephant in the room FIRST. I have knocked on a door that was for 12 years listed as a DNC because no one did a follow up. After doing my introduction, come to find out the owner has lived there for 30 years and the DNC was not from him, and we had an excellent discussion starting with complaining about our HOAs. You have to educate the territory holders and the publishers of what a DNC is. If someone marks a door as a DNC while I am in the territory, I quiz them why do you say this is a DNC? Well the person answered the ring bell and said he doesn't want to be disturbed. How do you know he was not indisposed while being in the bathroom and used the first excuse that came to his mind. This whole DNC marking is a mega educational job. So don't take the publishers word for it when included in a returned territory find out why this was marked DNC. And don't get me even started on those that did telephone witnessing and marked houses as DNCs because they wanted to be taken of OUR list.

When I digitized our territories I came across the limitation of 300 addresses however, once I started entering the addresses it allowed me to surpass the threshold of 300 as some of the territories had new homes added and now exceeded 300. We have 3 territories out of 80 that exceed 300 with 310, 345 and 351. It allowed me to enter these as it would be an absolute pain to divide up the subdivision of those territories. I assume that the developers had the foresight to realize what if there are some additional houses in access of 300 to complete an area that is a subdivision let us give them some additional room to finish the digitizing of a specific territory. It is just a guess of mine but each territory most likely has an upper limit of total size including the map image, number of streets entries and this may also be a factor in when you reach the limit because I have reached the limit at 330 but was surprised to be able to get to 351. Finally a word of advice, once you finished the address entries export those address entries as a CSV file because if anything goes wrong in your NWS setup, you just import the CSV file and spare yourself the time consuming entry of addresses.

Excellent Good News, with the latest update of NWS the Satellite view of territories is working again. The best map service is the MapBox Satellite as the other map service ThinkGeo Satellite is not as clear and sharp, plus my first quick check shows in one territory finished homes in an undeveloped area. So, it looks like that an update for the ThinkGeo Satellite map service is needed. Thanks to the Devs for getting such a quick fix for the territory module.

Just installed the minor update this morning and I noticed that the Bing Satellite map as well as the Bing map dark was removed from the available map providers. That is a real concern as it basically makes the assigning of new addresses now more guess work as to where the residences are. I understand that there may be an additional expense for map services, but if at all make it an option to add for an additional fee the Bing Satellite map.

I could now add an address to the territory, but the Bing Satellite map is not displaying and you sort of have to guess where the home is. Does that have to do with any API or paid service for the satellite map to be displayed?

I updated to the latest version and everything is working as it is supposed to except when trying to add an address to a territory I get this error message and this has been for a few hours now. Request: System.Net.WebException: The remote server returned an error: (429) Too Many Requests. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result) at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at JW_Scheduler.Helpers.HelperMethods.<PerformReverseGeocodingQueryLocationIQAsync>d__83.MoveNext() Result: https://us1.locationiq.com/v1/reverse?key=pk.00eaaac3ec9aeda0701ef179d10ac280&lat=38.6257851145725&lon=-76.9406257339515&format=json