piebro/osm-data huggingface dataset:
Minh Nguyen (2018-12-19 20:52:15+00:00): I moved a couple addresses from garages to nearby existing buildings in changeset 65623166.
viloan (2018-12-19 21:04:08+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
NunoCapeloCaldeira (2018-12-19 22:42:48+00:00): hi, thanks for improving data in Madeira. There's a lot of Mapillary imagery on that area if you want to add more details. If you have any doubts on how to use Mapillary on iD editor let me know. If you want to add new elements on OSM based on Mapillary, use Deriviste (which allows you to add POIs within the photo to OSM https://osm.cycle.travel/deriviste/
KartaKompass (2018-12-20 10:31:53+00:00): Olá Nuno,
Thanks for reaching out! Also thank you for helping me with the double naming issue the other day. So far I've used my own notes and images, but I'll have a look at Mapillary/Deriviste.

Some things are trickier and/or more time consuming than I thought. I struggle with the buses/bus stops and feel I need to discuss how to proceed.

What is the best way: Can I PM you or should I just do the edits and add a request for review on the changeset?

Best,
Erik
kleroux (2018-12-19 21:21:27+00:00): Mapillary street level imagery also used as a source.
user_1470980 (2018-12-21 06:22:17+00:00): Hallo _!Y!_, ich bitte Dich, künftig einen aussagekräftigen Hinweis auf Deine Mapping Grundlage anzuführen. Dass Du in Lilienfeld Gebäudeumrisse gezeichnet hast, das sehen wir bereits anhand der Daten. Die Frage ist hier, warst Du zum Mappen vorort, alternativ von welchem Luftbild hast Du hier abgezeichnet.

Grüße Johann Haag
Ehrenamtlicher Mapper
St. Johann in Tirol
mweper (2018-12-20 11:56:41+00:00): ¿Esto es un local que vende de todo o es un negocio de venta mayorista?
En el segundo caso, se debería usar https://wiki.openstreetmap.org/wiki/Tag:shop%3Dwholesale

Saludos.
nobbongnu (2018-12-20 12:02:49+00:00): Es como un importador donde venden de todo y su nombre es Mayorista San Luis, no averigüe pero creo que igual creo que también hacen venta minorista
muralito (2018-12-20 19:20:44+00:00): Yo no se como es ahi, pero a veces la venta "mayorista" tampoco es tan "mayorista" exclusivamente, es decir venden al publico pero los precios con descuento si empiezan a partir de cierta cantidad de unidades o packs.
mweper (2018-12-20 11:59:56+00:00): Si ese local vende ropa femenina, podrías especificarlo con clothes=women o clothes:women=yes (https://wiki.openstreetmap.org/wiki/ES:Key:clothes)

Saludos.
nobbongnu (2018-12-20 12:03:37+00:00): Perfecto, ahí lo agrego, gracias
muralito (2018-12-20 19:26:56+00:00): Sigo en modo sugerencias.

Si como la descripcion plantea, el "talle para todas" es talles grandes
tambien podria der
clothes=oversize

https://wiki.openstreetmap.org/wiki/Key:clothes
mweper (2018-12-20 21:00:54+00:00): Yo lo resolvería con:

clothes=women;oversize +
clothes:women=yes +
clothes:oversize=yes

Compatible con ambos métodos.
Trevor_1 (2018-12-19 22:00:39+00:00): *roads; not schools
manings (2018-12-26 12:05:08+00:00): Removed edits here: https://www.openstreetmap.org/changeset/65782549
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/65624720
abakus_uploader (2018-12-19 23:30:33+00:00): (Wiadomość automatyczna)
Cześć!
Otrzymujesz ten komentarz, ponieważ dodałeś lub zmodyfikowałeś adres, który jest niepełny lub błędny.
Adres powinien zawierać minimum trzy znaczniki: addr:city=[nazwa_miejscowosci] + addr:street=[nazwa_ulicy] + addr:housenumber=[numer_porządkowy].
Wyjątkiem są miejscowości bez nazwanych ulic - wtedy stosujemy znaczniki: addr:place=[nazwa_miejscowosci] + addr:housenumber=[numer_porządkowy].
Bez poprawnego oznaczenia adresów, nie będą one brane pod uwagę przez wyszukiwarki, dlatego warto je dostosować do ww. schematu (w zależności od sytuacji).
Więcej informacji na forum: https://forum.openstreetmap.org/viewtopic.php?id=5632 - a pytania najlepiej zadawać tu: https://forum.openstreetmap.org/viewtopic.php?pid=681873
Pozdrawiamy!
manings (2018-12-26 12:01:38+00:00): remove via this edit: https://www.openstreetmap.org/changeset/65782465
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/65624806
freebeer (2018-12-19 22:27:24+00:00): five standalone outlines in the Microsoft building dataset for this neighbourhood included what i believe to be three separate buildings each.

in addition, two more outlines encompassing three buildings were not simple outlines, but look to be multiple ones overlapping or something, but i don't see the highlighted co-positioned nodes i expect, so i'll have to examine those in detail in a later changeset.
oba510 (2019-01-02 03:32:26+00:00): I'm curious what your source for this name is. I can't find any reliable references to it.
freebeer (2018-12-19 22:56:19+00:00): here 16 2-buildings-in-one outlines - but worse, many more overlapping outlines as i described with my earlier 3-building delete, probably comparable in number to this.  aieee.

also saw one or two outlines i should have included in my 3-in-one deletion, this time using somewhat more recent mapbox imagery, which also shows several buildings that have (unsurprisingly) been razed since the Microsoft datagrab, which may well correspond with their overflight which i guess to be about five years old by now, and the mapbox imagery may be getting on to two years by now.  just wild-arse guessing.
Warin61 (2018-12-21 07:16:01+00:00): 1) Lambert Park ... is not all covered by trees. Suggest you use the tree area from Brush Farm Park to map the true extent of the trees. 

2) What evidence is there that Lambert Park connects to Brush Farm Park? The LPI base map shows a clear area between them that it does not name. 

3) the boundaries you have drawn do not agree with the base map. 

4) Relation outer ways should not touch. In this case if Lambert part is this total area then it should be drawn as one simple way. 

I had previously mapped this area before the LPI data was avalible. It is normally polite practice to edit the old entry if required... The changes you have done to the old entry covers a few change sets.
freebeer (2018-12-19 23:12:17+00:00): one outline deleted with four distinct building outlines within; one more to be analysed.

urgh, was hoping to use digitalglobe standard as possibly newer  than mapbox as determined elsewhere, but it is just too grotty for even me.
itineris (2019-01-31 16:10:52+00:00): Nem akarod élesíteni? A SmartCity kész, az 5G toronnyal együtt.
https://g7.hu/tech/20190131/elfelejtettek-mondani-de-a-telekom-5g-tesztjenek-szallitoja-a-fejlett-vilagbol-eppen-kiutalni-keszult-huawei/
GOwin (2018-12-22 08:42:44+00:00): Hello @Serdeeneil Merin, and welcome to OpenStreetMap (OSM). Thank you for these edits!

Kudos for helping make a better map of your favorite neighborhoods. OSM is a database of real-world features, used by many humanitarian and emergency service organizations. Fictional edits has no place in OSM. 

When you have a few minutes to spare, try the browser-based editor called iD, to edit the map of your community. You may find it quicker and easier if you need to update a lot of information on the map.

If you're keen to know more, there's this concise tips page for Philippine contributors: https://telegra.ph/Awesome-OSM-Tips--Tricks-01-28

Also, find out the latest happenings, or interact with local contributors through these community channels: https://wiki.osm.org/wiki/PH/channels

If you have any questions at all, please feel free to get in touch. You might be doubtful about a particular tag, or would like to clarify their use. Or perhaps, you have ideas you want to flesh out  to improve your neighbourhood map. Or maybe  just want to know more about OSM.  

Cheers,
freebeer (2018-12-19 23:37:14+00:00): while the roof of one of the buildings is intact in the Bing z20 overflight, it is seen to have collapsed in later Mapbox.  DG Standard does not show any difference...

This building outline consisted of three overlapping ways, all sharing the same points, but with differing address data, so there's a problem assigning addresses to polygons that incorrectly span multiple buildings.

Address 	4239
https://www.openstreetmap.org/way/654529367/history

Address 	4233
https://www.openstreetmap.org/way/654529374/history

Address 	4235
https://www.openstreetmap.org/way/654529370/history

I am pretty sure i will be seeing the same thing in the overlapping 2-in-1 and 3-in-1 and 4-in-1 outlines which i have not tried to delete yet.

am i having fun yet?

answers on a postcard, please
bagage (2018-12-22 11:13:58+00:00): Bonjour,

Je remarque que lors de l'import, les bâtiments segmentés n'ont pas été traités - par exemple ici (https://www.openstreetmap.org/way/656364210#map=18/49.41117/-1.26567). 

Est-ce qui serait possible de nettoyer ces imports svp ? 

Pour info, il y a aussi une page sur le wiki : https://wiki.openstreetmap.org/wiki/WikiProject_France/Cadastre/Import_semi-automatique_des_b%C3%A2timents#Utilisation_du_plugin_.C2.ABConflation.C2.BB_dans_JOSM

Merci ! :)
Gwenj (2018-12-22 11:37:43+00:00): Bonjour Gautrier,

Je dois bien avouer que je ne connaissais pas cette histoire de segmentation.
Merci pour votre message, je corrigerai ça d’ici la fin de la semaine prochaine, entre la bûche, 2 ou 3 relevés dans le froid et le traitement de quelques traces GPS :-)
bagage (2018-12-22 12:17:39+00:00): Pas de soucis Gwenj, merci pour les imports ;) Et bon courage pour survivre à travers les repas de fin d'année !
JJIglesias (2018-12-20 03:08:30+00:00): No se coloca informacion de indole personal en el Mapa. La "Casa a Comprar" la pusiste como un Spring y al "liset" como una atraccion Turistica. Por favor modificalos a algo de uso general. o Lamentablemente tendre q borrarlos. Gracias y Slds
JJ
Jakka (2018-12-20 09:39:27+00:00): Constate pour Rue du Coron du Gouffre differente type "highway=footway" et sigment après  "highway=path" ? Rue du Coron du Gouffre (108172536, v5) Rue du Coron du Gouffre (314700337, v2) sur le terrain indication du changement?
surveyor54 (2018-12-20 09:34:26+00:00): Hi benjamin1180,
 
das Krankenhaus wird nicht mehr dargestellt !

Gruß
surveyor54
benjamin1180 (2018-12-20 10:53:37+00:00): Hallo,
hatte zunächst gedacht, dass das Hinzufügen eines Lichthofs im neuen Bettenhaus bzw. der Übergang zwischen diesem und dem OP-Trakt (basierend auf Multi-Polygonen) vielleicht etwas Zeit zum Rendern benötigt. Nachdem allerdings das ganze "Gebäude" nicht mehr dargestellt wurde, habe ich diese Veränderungen wieder entfernt. Im Tagesverlauf schaue ich nochmal nach, ob das Krankenhaus in seinem Umriss wieder dargestellt wird.

Viele Grüße
surveyor54 (2018-12-20 11:27:02+00:00): Hi,
Wenn in einem Gebäude Lichthöfe vorhanden sind, wird ein MP angelegt, wie in diesem einfachen Beispiel:

https://www.openstreetmap.org/relation/2973431

Gruß
benjamin1180 (2018-12-20 15:54:36+00:00): Auf Basis dieses Beispiels scheint es jetzt auch am gegebenen Objekt geklappt zu haben. Allerdings geht der Lichthof nicht durch bis zum Erdboden, weshalb ich ihn wieder entfernen werde. Interessant wäre die Lösung mit den Multipolygonen aber beim Übergang vom OP- Trakt zum Aufwachraum / Bettenhaus, wo ich diese noch einsetzen wollte.

Für das genannte Beispiel (Fliegerhorst Erlensee) vielen Dank!
freebeer (2018-12-20 00:25:27+00:00): i suspect i overlooked one or two, but these are the outlines where i would draw two buildings, which have been assigned more than one address, resulting in multiple overlapping ways sharing the same nodes.

one might expect these to have two addresses, and in fact a few did.  but many had three or more -- up to ten or so, i actually lost count while deleting.

obviously trying to merge addresses with outlines here is destined to failure.

it;s hard to say how many locations were afflicted, without looking at the data -- 33 addresses, but only 60 nodes, so maximum 15 locations, probably 10 or 12 or so.

i guess next (or when i wake up) i will see how many of what i would trace as a single-building outline, has multiple addresses, purging them...
L'imaginaire (2021-05-26 07:00:03+00:00): image link is now broken
freebeer (2018-12-20 01:25:19+00:00): sure felt like i was deleting a hundred ways in the same place, all sharing the same points.  i *would* have lost count, and did take a break for a partial upload, moved on, then returned.  it was that bad, after i did count 19 ways at one white-roofed building.  overall, 144 ways slain, but only 90 nodes.  i know osm should strive for efficiency, but *this* is ridiculous.

the addresses at that one spot were from several different streets.  essentially, anything i deleted here is a bug not from the microsoft side, but in some cases, the addresses should have been left as nodes (where two or so apply to one building), but something is seriously pear-shaped in several other locations, like a church with quite a lot of address ways overlaid on themselves.

there's getting to be not much left to judge positional accuracy, as most of these were not errors in the outline data, but errors in assigning addresses, which really needs to be found and fixed before any further production upload.

i need a break, resolving spam notes or something, for a bit...
user_5359 (2019-10-21 19:38:22+00:00): Welcome to OSM! Short question to your maxspeed value: Roundup Road (https://www.openstreetmap.org/way/656373171) is a living_street and has 69 mph value for maxspeed? Can you please check this?
freebeer (2019-10-21 20:55:59+00:00): and no aerial imagery shows this as any sort of highway.  also, this is obviously not an urban area so there are no osm municipal parks here.  and it is very odd to rename a lake after yourself following earlier edit wars.
iandees (2019-10-21 21:21:29+00:00): Reverted in https://www.openstreetmap.org/changeset/76018858
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/65627435
mariotomo (2020-03-11 18:05:07+00:00): that was a questionable deletion.  it took me time to find this changeset, and in the meanwhile I have reconstructed the Lago Bayano relation.  the lake is there, the relation should stay in the database.
chachafish (2018-12-22 12:17:45+00:00): Good morning :) Thank you for your work on the OSM map. I see here you deleted the residential tag for the Pine Apartments. Are these no longer the Pine Apartments? Have they become something else? Thanks :)
GeoDave5280 (2018-12-28 14:56:51+00:00): A dwelling unit with its own street address, attached or detached, is considered to be a "house".  The Wiki recommends this over the more general "residential" tag.  See https://wiki.openstreetmap.org/wiki/Tag:building%3Dterrace and some others. In some cases, landuse= residential tags were also removed, because that tag generally applies to neighborhoods instead of individual buildings.  (I also drove by these "apartments" and added the individual addresses, where visible).
chachafish (2018-12-28 15:32:18+00:00): Hi, thanks for the reply :) I think we're talking about two different things. I totally agree these should be tagged as houses. I'm referring to the residential area that surrounded the 16 buildings here designating them as the Pine Apartments. It was deleted. https://www.openstreetmap.org/way/329978965/history
GeoDave5280 (2018-12-29 02:40:12+00:00): I have always thought of landuse=residential, commercial, etc. as designating a larger area (e.g. a whole neighborhood).  But I have restored the Pine Apartments tag. Wiki articles on this topic are rather confusing, and I can't think of a better way to designate a group of buildings such as this.
chachafish (2018-12-29 13:08:12+00:00): Thanks :) I went through the same thought process myself. If an apartment complex is just one building, it's easy. But, if there are numerous buildings, this would seem to be the best option. Cheers :)
ToniE (2018-12-21 15:18:23+00:00): Hallo Axel,

wir hatten uns, glaube ich, mal über die Reihenfolge der Route-Relationen eines Route-Masters bei PTNA:  DE-HE-NVV (oder anderswo) "unterhalten".
Ich habe den Code geändert. Die Reihenfolge der Ausgabe in PTNA entspricht nun der Reihenfolge im Route-Master - nicht mehr via name oder sort_name oder ref_trips ...

Viele Grüße
Toni
axelr (2018-12-31 17:23:20+00:00): Sieht gut aus, besten Dank und Guten Rutsch
AkuAnakTimur (2018-12-20 23:40:50+00:00): Hello! I don't think this particular stretch of this highway (https://www.openstreetmap.org/way/236001234) has a speed limit of 30 km/h.
a_run (2018-12-21 03:58:44+00:00): Hi AkuAnakTimur,

Existing data has two different way's for same stretch which were not combined(way 235993094, way 236001234). One of the way id(235993094)  had speed limit of 30 given by external mappers.

The speed limit got carry forward to the resultant way id(236001234) after i have combined the ways. 

Now with your suggestion we removed the speed limit. 

Thanks,
a_run.
dooley (2019-01-17 17:22:28+00:00): Hallo berjk,

kannst du bitte kurz erläutern, was "wg. FM: ->HNr. auf disused gesetzt." bedeutet?

Danke.
berjk (2019-01-17 19:15:52+00:00): OK hier die Langversion. Es wurde über ein OSM-Fehlermeldung gemeldet, dass es das Haus mit der Hausnummer 56 nicht mehr gibt. Folglich wurde das "tag" addr:housenumber auf disused:addr:housenumber gesetzt, so dass die Hausnummer nicht mehr in der OpenStreetMap-Karte erscheint.
dooley (2019-01-17 21:21:48+00:00): Ach so. Ich werde demnächst vorbeifahren und vor Ort prüfen.
jmapb (2018-12-20 16:21:04+00:00): Hi datbrahm -- To encode an exception to a turn restriction, add the except=* tag to the turn restriction relation (https://www.openstreetmap.org/relation/9130540) not the intersection node (https://www.openstreetmap.org/node/42466290). 

Also, there's no need to use the `conditional` syntax unless there are other restrictions such as time of day or weather. If the rule is simply "no left turn except busses", then except=bus on the relation is sufficient.

See:
https://wiki.openstreetmap.org/wiki/Relation:restriction
https://wiki.openstreetmap.org/wiki/Conditional_restrictions
datbrahm (2019-07-11 06:21:45+00:00): Hi,

Thanks for looking into the edit and apologies for the delayed response. Thanks for the updates. We will follow your suggestions going forward while adding restrictions at ramps/turn lanes.

Regards, 
Brahm Datt
datbrahm (2019-07-11 06:26:25+00:00): Hi jmapb, Thanks for reviewing the edit and apologies for the delayed response. I made the changes as soon as I received a comment from your end but missed to reply back. Thanks for the updates we will follow the same as per your suggestions going forward.

please ignore the previous comment.
Regards,
Brahm Datt
mavl (2019-07-21 13:10:25+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:10:28+00:00): This changeset was redacted. Reason: copyrighted data were used.
Ficky IRM-RV (2021-02-24 05:15:35+00:00): Hi bhavani1,
I've modified this road (https://pewu.github.io/osm-history/#/way/656401716) based on maxar premium. I also made some changes around this changeset.
Thank you, happy mapping!
mavl (2019-07-21 13:10:32+00:00): This changeset was redacted. Reason: copyrighted data were used.
pyram (2019-01-11 20:19:43+00:00): rewiew:

Hello kalpna,

thank you for trying to help, but you changed a highway to a "tree row": See https://www.openstreetmap.org/way/479146146/history
(Now it's a highway again)

Best regards
pyram
mavl (2019-07-21 13:10:35+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:10:38+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:10:41+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:10:45+00:00): This changeset was redacted. Reason: copyrighted data were used.
tim32fly (2018-12-20 05:10:45+00:00): Added Green? Trail. Will update name once found.
mavl (2019-07-21 13:10:48+00:00): This changeset was redacted. Reason: copyrighted data were used.
viloan (2018-12-20 05:05:32+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
mavl (2019-07-21 13:10:51+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:10:55+00:00): This changeset was redacted. Reason: copyrighted data were used.
tim32fly (2018-12-20 05:08:15+00:00): Corrected spelling error of "Hertiage" to "Heritage"
mavl (2019-07-21 13:10:58+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:02+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:05+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:08+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:11+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:15+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:18+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:21+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:25+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:28+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:11:31+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:20:59+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:20:53+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:21:03+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:21:06+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:21:10+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:21:13+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:21:16+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 13:21:20+00:00): This changeset was redacted. Reason: copyrighted data were used.