geopoints

Parse geopoint swift not getting current location

╄→гoц情女王★ 提交于 2019-12-07 10:05:40
问题 trying to use parses PFGeoPoint.geoPointForCurrentLocationInBackground to get current location when i send something to my backend. The code looks like NSLog("Before block") PFGeoPoint.geoPointForCurrentLocationInBackground { (geoPoint: PFGeoPoint!, error: NSError!) -> Void in NSLog("inside block") if !error { // do something with the new geoPoint } } and I never get my inside block on the console. I have Core Locations Framework installed and it allows me to do something like let point =

Android Maps API version 1 to version 2 migrations

只谈情不闲聊 提交于 2019-12-06 23:02:54
问题 Background: I've inherited someone else's problem and am trying to get an app up and running. Multiple developers have ditched the project and now its my turn. I'm an iOS developer by trade but I have a few simple android project completed. The problem app is a native android originally built with API level 7 and is heavily built around google maps api version 1. I don't have access to the original keys so I appear to be forced into upgrading to google maps version 2. I have already set up a

Querying Geopt with Objectify

匆匆过客 提交于 2019-12-06 06:47:02
I am having the hardest time querying a GeoPt field with Objectify. I made sure there's an @Index annotation about the GeoPt field. However, the statement below doesn't seem to work ofy().load() .type(GeoStat.class) .filter("geoPt.latitude >=", neLat) .limit(10); Is querying GeoPt field possible in Objectify? stickfigure The datastore does not support querying a GeoPt in this way. If you wish to query on latitude, index it separately (possibly writing to a private field in an @OnSave method). However, if you're trying to perform a geospatial query (ie, contained in a rectangle), note that you

Parse geopoint swift not getting current location

十年热恋 提交于 2019-12-05 16:58:25
trying to use parses PFGeoPoint.geoPointForCurrentLocationInBackground to get current location when i send something to my backend. The code looks like NSLog("Before block") PFGeoPoint.geoPointForCurrentLocationInBackground { (geoPoint: PFGeoPoint!, error: NSError!) -> Void in NSLog("inside block") if !error { // do something with the new geoPoint } } and I never get my inside block on the console. I have Core Locations Framework installed and it allows me to do something like let point = PFGeoPoint(latitude:40.0, longitude:-30.0) If it helps i am not being requested for user location when I

Android Maps API version 1 to version 2 migrations

我只是一个虾纸丫 提交于 2019-12-05 03:27:34
Background: I've inherited someone else's problem and am trying to get an app up and running. Multiple developers have ditched the project and now its my turn. I'm an iOS developer by trade but I have a few simple android project completed. The problem app is a native android originally built with API level 7 and is heavily built around google maps api version 1. I don't have access to the original keys so I appear to be forced into upgrading to google maps version 2. I have already set up a new Activity and am beyond the basic tutorials of getting a functioning map. No problems there, but I'm

Geospatial Query at Google App Engine Datastore

霸气de小男生 提交于 2019-12-02 06:32:51
问题 I read the following post Querying Geopt with Objectify This is exactly what I need for my application. At the end of the post I read that the Geospatial Search is in alpha stadium but the post is already one year old. I cannot find any information about the status of Geospatial Queries at Google App Engine. Is it still in Alpha stadium or can I use in production? 回答1: so for everyone who is interested in: today 27. Jan 2017 Geospatial Queries are still in Alpha stadium. You need to create a

Geospatial Query at Google App Engine Datastore

末鹿安然 提交于 2019-12-02 00:19:50
I read the following post Querying Geopt with Objectify This is exactly what I need for my application. At the end of the post I read that the Geospatial Search is in alpha stadium but the post is already one year old. I cannot find any information about the status of Geospatial Queries at Google App Engine. Is it still in Alpha stadium or can I use in production? so for everyone who is interested in: today 27. Jan 2017 Geospatial Queries are still in Alpha stadium. You need to create a search index of mode geospatial for your Geo Point Property and this is not allowed 来源: https:/

Double or decimal for latitude/longitude values in C#

主宰稳场 提交于 2019-11-30 01:39:45
What is the best data type to use when storing geopositional data in C#? I would use decimal for it's exactness, but operations on decimal floating point numbers are slower then binary floating point numbers (double). I read that most of the time you won't need any more then 6 or 7 digits of precision for latitude or longitude. Does the inexactness of doubles even matter then or can it be ignored? Go for double , there are several reasons. Trigonometric functions are available only for double Precision of double (range of 100 nanometers) is far beyond anything you'll ever require for Lat/Lon

Double or decimal for latitude/longitude values in C#

别说谁变了你拦得住时间么 提交于 2019-11-28 21:47:00
问题 What is the best data type to use when storing geopositional data in C#? I would use decimal for it's exactness, but operations on decimal floating point numbers are slower then binary floating point numbers (double). I read that most of the time you won't need any more then 6 or 7 digits of precision for latitude or longitude. Does the inexactness of doubles even matter then or can it be ignored? 回答1: Go for double , there are several reasons. Trigonometric functions are available only for