I too suggest categorization first, with more time to weigh whether the requirements are needed or how they should be defined.

Decentraland POIs: Categorization and Guidelines This proposal is now in status: PASSED. Voting Results: * Yes 80% 5,561,512 VP (39 votes) * No 19% 1,330,675 VP (7 votes) * Abstain 1% 17,635 VP (6 votes)

I like categorizing POIs. It's one of those "it just makes sense" implementations. I like this without the guidelines feature. I would recommend implementing categories first, see how our system goes, then some level of POI guideline if necessary. I believe the categorizing of the POI will help remove clutter from the map and drill down into more targeted discoveries for users.

I like the concept of categories and better clarity about requirements. I'll be curious how a number of venues that I operate in the Conference Center, VRS District, and Aetheria may or may not qualify (in other words what the metrics will actually be). I generally have not submitted POIs on them but would like to. I hope that the bar isn't set too high, especially if categorized where having somewhat more POIs wouild be fine, but too high of a bar means venue operators would too often fail. I have some traffic stats I could discuss with you about most of those venues to help you refine the specifics about thresholds.

Sounds good. Thank you for your feedback.

@web3nit Personally I like this idea, I think there is a lot of room for improving the Map experience inside DCL and it would be nice if POIs had more metadata associated to empower the Foundation, or anyone building a client to provide an engaging and guided experience when exploring Decentraland for the first time. However, I think that for the first iteration, we could use the scene categorization metadata that is currently available to enrich POIs without having to go through an entire development of this feature. WDYT? On a side note, from the Governance experience and the platform itself, this would be doable without too much effort.

Hi Folks. Could you please explain the rationale behind your 'NO' vote ? @mazafaka @nwiz

Hi Nikki. - The purpose of this proposal is to confirm community sentiment and gather feedback. Once we have that, I plan to engage with the Foundation to discuss all the technical details. Additionally, I'm waiting for feedback from @ginoct to gain further insights on this matter. - I like the idea of using different colors for each category. It seems reasonable and beneficial to introduce them to bring clarity. - Initially, the idea was to assign one category per parcel. However, we can remain flexible and consider implementing applications that allow parcels to qualify for multiple categories. - IMO we need feedback from the Foundation to determine the most effective way to work out reasonable activity levels. Maybe we can start without this feature and consider it for future implementation. - Ideally, the Foundation would handle the development and integration of this system. However, the DAO also has a bidding and tendering process that could be utilized as an alternative if necessary.

Although I think this extremely overcomplicates the POI system, I do have some questions since I'm sure it's going to get passed through no matter what. 1. Do we know the technical feasibility to develop/integrate this "system"? 2. Since there are now categories does this mean each category POI will still be the same icon color? (yellow currently) Or will there be new colors introduced associated with each category? 3. Can a parcel qualify for more than one category? What if a parcel is both a gaming and venue parcel? 4. How is the "automated" system going to gauge what is reasonable "activity"? Especially when the platforms player base fluxuates? 5. Who is going to build/integrate this "system"?

Hi DAO. Thank you all who participated in this topic. :handshake: Please Vote and Leave your feedback. Also here is doc file for comments: [https://docs.google.com/document/d/17Gvjw1HG_bYmbaxG9dnzggV80fzmBobmIqa4kT7rKbk/](https://docs.google.com/document/d/17Gvjw1HG_bYmbaxG9dnzggV80fzmBobmIqa4kT7rKbk/)