To learn how to do this using the REST API directly or using the ArcGIS Python API or ArcGIS REST, go to: https://www.postman.com/esridevs/workspace/authentication-in-arcgis/collection/15786767-04f0cd88-1d89-42ce-af76-529987cd5a9a

Does this means that it is the new default style?

This link is pointing to Places API, I guess it should point to https://developers.arcgis.com/documentation/mapping-apis-and-services/maps/basemap-layers/#basemap-styles-service-v2-beta

Please, let me know if you find relevant channels missing! 😊🙏

I have been wondering this during the whole article... are there any rules/guidelines to better understand when to use them vs regular geometries?. Here you have Chat GPT recommendation to when to use multipart geometries:

1. Complex and Overlapping Features: Multipart geometries are useful when you need to represent complex features that consist of multiple non-contiguous parts or features that overlap with each other. Examples include a river system with multiple branches or a collection of islands within a single polygon.

2. Preserving Topological Relationships: Multipart geometries maintain topological relationships between the different parts. This means that the relationships between the individual parts, such as connectivity or adjacency, are preserved. If you need to perform spatial operations that rely on topological relationships, multipart geometries are necessary.

3. Flexibility and Future Extensibility: Using multipart geometries allows for greater flexibility and extensibility in your data model. It accommodates the representation of more complex and varied spatial phenomena, and it provides room for future additions or modifications to the dataset.

I also would consider to link to this page to learn more about geometries: https://developers.arcgis.com/documentation/common-data-types/geometry-objects.htm

100% agree, but it made me think. in the blog article you show code that construct these geometries manually (not loaded from a persisted database) and you are not explaining how these databases needs to be created to support these geometries, do you need to set a spatial set of geometry? or is it a regular geometry, similar to "CREATE TABLE geometries (name varchar, geom geometry);" ?

This can be done without multipoint geometries too. Or do you mean you can do it with ArcGIS Pro?

To me this is the best example. If you have a database with countries, you will find situations (and not only on islands) where you just want to have a complex geometry associated to a set of attributes.

I struggle with this example. I mean, multipart geometries are a benefit for a developer because it is a better way to structure and manage data, but from a functional perspective, a developer will be able to achieve the same result with and without multipart geometries, right?

I guess I would remove this part (redundancy) and all are vector data types (but we haven't explained what a vector data type is; a regular developer will better understand "alphanumberic value"). Even the word "vector" is sometimes confusing to me because it has several meanings (vector data type, vector layer, vector tile layer, ...)

Are you not adding the attributes on purpose?

I understand the efficient management (less duplicate data), but I don't get the efficient analysis.

I had no idea what this was xD, I had to use the translator xD

Same with this: https://developers.arcgis.com/documentation/glossary/geometry/

Is it better than the Developer Glossary?: https://developers.arcgis.com/documentation/glossary/feature/ ? If so we should consider sending feedback to that definition 🙂

but you don't know which is the best way to store and manage them?

I would like to the hosted tables which I think are easier to understand for a developer. https://developers.arcgis.com/documentation/mapping-apis-and-services/data-hosting/hosted-tables/

I would also say that an attribute table is a relational table in a database.

Really neat article!

I wonder how many people will get this statement 😁