Count Annotations on MapView in Swift
After completing a loop that places annotations on a map from an array, I want to count the number of annotations.
My code as follows:
let anCount = self.mapView.annotations?.count
if (anCount > 1) {
//do something
}
gives error:
Value of optional type 'Int?' must be unwrapped to a value of type
'Int'
The fixit suggestions yield other errors. What is the correct way to count the number of annotations for the map.
Thanks for any suggestions.
ios swift mapkit mkannotation
add a comment |
After completing a loop that places annotations on a map from an array, I want to count the number of annotations.
My code as follows:
let anCount = self.mapView.annotations?.count
if (anCount > 1) {
//do something
}
gives error:
Value of optional type 'Int?' must be unwrapped to a value of type
'Int'
The fixit suggestions yield other errors. What is the correct way to count the number of annotations for the map.
Thanks for any suggestions.
ios swift mapkit mkannotation
This has been asked and answered many times: stackoverflow.com/…
– Rob
Dec 31 '18 at 0:01
By the way, be careful of just counting atannotations
because there might be different types of annotations. E.g., including or excluding the user location on the map (which results in a system generatedMKUserLocation
to be added on your behalf) will suddenly change this logic. You really should filter the results for annotations of a particular type...
– Rob
Dec 31 '18 at 0:14
add a comment |
After completing a loop that places annotations on a map from an array, I want to count the number of annotations.
My code as follows:
let anCount = self.mapView.annotations?.count
if (anCount > 1) {
//do something
}
gives error:
Value of optional type 'Int?' must be unwrapped to a value of type
'Int'
The fixit suggestions yield other errors. What is the correct way to count the number of annotations for the map.
Thanks for any suggestions.
ios swift mapkit mkannotation
After completing a loop that places annotations on a map from an array, I want to count the number of annotations.
My code as follows:
let anCount = self.mapView.annotations?.count
if (anCount > 1) {
//do something
}
gives error:
Value of optional type 'Int?' must be unwrapped to a value of type
'Int'
The fixit suggestions yield other errors. What is the correct way to count the number of annotations for the map.
Thanks for any suggestions.
ios swift mapkit mkannotation
ios swift mapkit mkannotation
asked Dec 30 '18 at 23:55
user1904273user1904273
1,62482864
1,62482864
This has been asked and answered many times: stackoverflow.com/…
– Rob
Dec 31 '18 at 0:01
By the way, be careful of just counting atannotations
because there might be different types of annotations. E.g., including or excluding the user location on the map (which results in a system generatedMKUserLocation
to be added on your behalf) will suddenly change this logic. You really should filter the results for annotations of a particular type...
– Rob
Dec 31 '18 at 0:14
add a comment |
This has been asked and answered many times: stackoverflow.com/…
– Rob
Dec 31 '18 at 0:01
By the way, be careful of just counting atannotations
because there might be different types of annotations. E.g., including or excluding the user location on the map (which results in a system generatedMKUserLocation
to be added on your behalf) will suddenly change this logic. You really should filter the results for annotations of a particular type...
– Rob
Dec 31 '18 at 0:14
This has been asked and answered many times: stackoverflow.com/…
– Rob
Dec 31 '18 at 0:01
This has been asked and answered many times: stackoverflow.com/…
– Rob
Dec 31 '18 at 0:01
By the way, be careful of just counting at
annotations
because there might be different types of annotations. E.g., including or excluding the user location on the map (which results in a system generated MKUserLocation
to be added on your behalf) will suddenly change this logic. You really should filter the results for annotations of a particular type...– Rob
Dec 31 '18 at 0:14
By the way, be careful of just counting at
annotations
because there might be different types of annotations. E.g., including or excluding the user location on the map (which results in a system generated MKUserLocation
to be added on your behalf) will suddenly change this logic. You really should filter the results for annotations of a particular type...– Rob
Dec 31 '18 at 0:14
add a comment |
1 Answer
1
active
oldest
votes
You have to unwrap the optional, e.g. with if let
, which you can then combine with the > 1
test in a single if
statement:
if let anCount = mapView.annotations?.count, anCount > 1 {
//do something
}
But annotations
isn't an optional (at least in current iOS versions), so you'd probably just do:
let anCount = mapView.annotations.count
if anCount > 1 {
//do something
}
Thanks for the answer which worked but did you downvote my question cause I took too long to respond? I had a lot going on. In theory, optionals should be simple, but in practice if you are still learning them, each case can be different.
– user1904273
Dec 31 '18 at 15:38
No, I did not down vote. I was merely suggesting that you research more before posting a question. If you are going to post a question that has been asked before, it’s good to include references of a question or two to demonstrate that you did research it.
– Rob
Dec 31 '18 at 15:56
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53982410%2fcount-annotations-on-mapview-in-swift%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You have to unwrap the optional, e.g. with if let
, which you can then combine with the > 1
test in a single if
statement:
if let anCount = mapView.annotations?.count, anCount > 1 {
//do something
}
But annotations
isn't an optional (at least in current iOS versions), so you'd probably just do:
let anCount = mapView.annotations.count
if anCount > 1 {
//do something
}
Thanks for the answer which worked but did you downvote my question cause I took too long to respond? I had a lot going on. In theory, optionals should be simple, but in practice if you are still learning them, each case can be different.
– user1904273
Dec 31 '18 at 15:38
No, I did not down vote. I was merely suggesting that you research more before posting a question. If you are going to post a question that has been asked before, it’s good to include references of a question or two to demonstrate that you did research it.
– Rob
Dec 31 '18 at 15:56
add a comment |
You have to unwrap the optional, e.g. with if let
, which you can then combine with the > 1
test in a single if
statement:
if let anCount = mapView.annotations?.count, anCount > 1 {
//do something
}
But annotations
isn't an optional (at least in current iOS versions), so you'd probably just do:
let anCount = mapView.annotations.count
if anCount > 1 {
//do something
}
Thanks for the answer which worked but did you downvote my question cause I took too long to respond? I had a lot going on. In theory, optionals should be simple, but in practice if you are still learning them, each case can be different.
– user1904273
Dec 31 '18 at 15:38
No, I did not down vote. I was merely suggesting that you research more before posting a question. If you are going to post a question that has been asked before, it’s good to include references of a question or two to demonstrate that you did research it.
– Rob
Dec 31 '18 at 15:56
add a comment |
You have to unwrap the optional, e.g. with if let
, which you can then combine with the > 1
test in a single if
statement:
if let anCount = mapView.annotations?.count, anCount > 1 {
//do something
}
But annotations
isn't an optional (at least in current iOS versions), so you'd probably just do:
let anCount = mapView.annotations.count
if anCount > 1 {
//do something
}
You have to unwrap the optional, e.g. with if let
, which you can then combine with the > 1
test in a single if
statement:
if let anCount = mapView.annotations?.count, anCount > 1 {
//do something
}
But annotations
isn't an optional (at least in current iOS versions), so you'd probably just do:
let anCount = mapView.annotations.count
if anCount > 1 {
//do something
}
edited Dec 31 '18 at 0:12
answered Dec 31 '18 at 0:00
RobRob
299k49557726
299k49557726
Thanks for the answer which worked but did you downvote my question cause I took too long to respond? I had a lot going on. In theory, optionals should be simple, but in practice if you are still learning them, each case can be different.
– user1904273
Dec 31 '18 at 15:38
No, I did not down vote. I was merely suggesting that you research more before posting a question. If you are going to post a question that has been asked before, it’s good to include references of a question or two to demonstrate that you did research it.
– Rob
Dec 31 '18 at 15:56
add a comment |
Thanks for the answer which worked but did you downvote my question cause I took too long to respond? I had a lot going on. In theory, optionals should be simple, but in practice if you are still learning them, each case can be different.
– user1904273
Dec 31 '18 at 15:38
No, I did not down vote. I was merely suggesting that you research more before posting a question. If you are going to post a question that has been asked before, it’s good to include references of a question or two to demonstrate that you did research it.
– Rob
Dec 31 '18 at 15:56
Thanks for the answer which worked but did you downvote my question cause I took too long to respond? I had a lot going on. In theory, optionals should be simple, but in practice if you are still learning them, each case can be different.
– user1904273
Dec 31 '18 at 15:38
Thanks for the answer which worked but did you downvote my question cause I took too long to respond? I had a lot going on. In theory, optionals should be simple, but in practice if you are still learning them, each case can be different.
– user1904273
Dec 31 '18 at 15:38
No, I did not down vote. I was merely suggesting that you research more before posting a question. If you are going to post a question that has been asked before, it’s good to include references of a question or two to demonstrate that you did research it.
– Rob
Dec 31 '18 at 15:56
No, I did not down vote. I was merely suggesting that you research more before posting a question. If you are going to post a question that has been asked before, it’s good to include references of a question or two to demonstrate that you did research it.
– Rob
Dec 31 '18 at 15:56
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53982410%2fcount-annotations-on-mapview-in-swift%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This has been asked and answered many times: stackoverflow.com/…
– Rob
Dec 31 '18 at 0:01
By the way, be careful of just counting at
annotations
because there might be different types of annotations. E.g., including or excluding the user location on the map (which results in a system generatedMKUserLocation
to be added on your behalf) will suddenly change this logic. You really should filter the results for annotations of a particular type...– Rob
Dec 31 '18 at 0:14