StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18368614
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-08-21T22:15:16.700
FavoriteCount
0
LastActivityDate
2013-08-21T22:15:16.700
LastEditDate
LastEditorUserId
0
OwnerUserId
2574249
ParentId
18061728
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Boost.Geometry requires that your Point type is adapted to the Point Concept described here: <a href="http://www.boost.org/doc/libs/1_54_0/libs/geometry/doc/html/geometry/reference/concepts/concept_point.html" rel="nofollow">http://www.boost.org/doc/libs/1_54_0/libs/geometry/doc/html/geometry/reference/concepts/concept_point.html</a> Your derived type myPoint must also be adapted because it's a different type than your base type, model::pointer<>. The reason for this is that the library allows to adapt legacy classes and use them as Geometries without the need for modification. To adapt it you must either use one of the registration macros or specialize all required traits by yourself. Besides the exmaple mentioned in the comment, see those: <a href="http://www.boost.org/doc/libs/1_54_0/libs/geometry/doc/html/geometry/examples.html" rel="nofollow">http://www.boost.org/doc/libs/1_54_0/libs/geometry/doc/html/geometry/examples.html</a> In the second one the Point type is adapted by manual specialization of all required traits, which is the most flexible approach. In your case this would look like this: <pre><code>namespace boost { namespace geometry { namespace traits { template <typename C, std::size_t D, typename S> struct tag< myPoint<C, D, S> > { typedef point_tag type; }; template <typename C, std::size_t D, typename S> struct coordinate_type< myPoint<C, D, S> > { typedef C type; }; template <typename C, std::size_t D, typename S> struct coordinate_system< myPoint<C, D, S> > { typedef S type; }; template <typename C, std::size_t D, typename S> struct dimension< myPoint<C, D, S> > { static const std::size_t value = D; }; template <typename C, std::size_t D, typename S, std::size_t I> struct access<myPoint<C, D, S>, I> { static inline C get(myPoint<C, D, S> const& p) { return p.template get(); } static inline void set(myPoint<C, D, S> & p, C const& v) { p.template set(v); } }; }}} </code></pre> Just paste it after your Point definition and you're done.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to inherit from boost::geometry::model::point?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAdam Wulkiewicz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to inherit from boost::geometry::model::point?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.