Aea adt using the latest MAXAR imagery?

also the surrounidngs need to use uppercase

Should be BPP

sorry, I mean Esri

Sure, these are some of the areas with new MAXAR imagery but no road traced.
1.4837031, 103.8459759
1.4848281, 103.8976705
1.5015220, 103.9547236
1.5741503, 103.7866953
1.5813598, 103.7749734
1.5781079, 103.7685048
1.5708935, 103.7363673
1.5464270, 103.7663068
1.5565948, 103.6821252
1.4863399, 103.6278633
1.5004977, 103.5833720
1.50315,103.56996
1.4382,103.6256
1.3885,103.6402
1.6230736, 103.8131908

Large box due to wrongly drag a road in Pulau Sebang🥲

Why upper case?

Hello, I do hope Apple Data Team can help the local community to map out some of the new roads in Johor Bahru and Kulai District. From the latest Esri imagery, there are thousands of road need to be map or rectify for neighbourhoods in these areas. I had also marked up some of the area with note. Really appreciate if Apple can help to trace it.

× Tanjung Berembang update

hello, can I know how you add these POIs?

own visit

I will follow the community opinion, since most of here do want a revert.

For me, I am deleteing (and duplicating ) those who already have the bus stop previously, for the others I think the best way is to delete via filter the tagging. If you want to let DWG to wipe out, I think please only wipe out these nodes who in the first version, as some of them already replace the existing bus stop. so if just simply delete all the new bus stop will also coincidencely delete some previous bus stop data.

I try to resolve in capital letter data and also duplication with existing data, but seems like it only can be resolve manually (and it is time consuming), currently I dont have a method to convert all into Totle case in one. But thank you for your sharing about this. I acknowledge that this is not an easy task. But honestly telling, although this data are mostly accurate and is open data but seems like going through process like what you list is needed.

Per AkuAnakTimur's opinion, I will apologize for not considered it rather then this edit as an import, because I also do some comparision with the existing data, and can be say that most of them are tally with the current bus stop location. I think we may further discuss on this in our Telegram group, if you wish to have more indept discussion regarding those bus stop data.

Ok, I understand your consideration, but the code i do not directly put in the route_ref section, I will try to trun all what you say in hidden caveat into the route_ref listed in the normal passenger system.

(and some Rapid KL bus stop in the system are display as smth like Spg or Apt, actually we can use Simpang or Apartment insetad of using short name in OSM.

Yes, need to split it.

The route number for U is still using now just that now we only display 123, instead of U1230 (Like U7700 actuallly is route 770, T1230 actually is T123). All the route numbers mostly are relevant unless Rapid KL amend the route recently. The duplicate bus stop will be merge, but take a lot of time. I will do some housecleaning to merge with the existing bus stop, just give some times will do.

Yes ia lso do some duplication, the data is filtered, and actually you can use the coordinate for a more accurate bus stop location, Personally, I use the route_ref from the data to add for the bus stop, just remove U for trunk ine in most case, if there are S I think is DBKL/Smart Selangor route. The data is quite accurate for now, but I admit need to do a lot of integration with the current data. What I do is I use the new coordinate (unless it is clearly located at wrong space e.g. middle of road or shift of bus stop location, I will use the original coordinate) and use the old bus stop data. The bus reference also avaiable for most bus stop in the name, so can add at the ref site also.