Yeah I'm trying to get GeoDjango set up as we speak. GeoDjango sounds awesome.
I have postgresql and Im trying to install postgis but im getting this: jjz@jjz-Laptop:~$ wget http://postgis.refractions.net/download/postgis-1.5.2.tar.gz --2012-07-15 19:40:12-- http://postgis.refractions.net/download/postgis-1.5.2.tar.gz Resolving postgis.refractions.net (postgis.refractions.net)... 199.103.56.11 Connecting to postgis.refractions.net (postgis.refractions.net)|199.103.56.11|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3749293 (3.6M) [application/x-gzip] Saving to: `postgis-1.5.2.tar.gz' 100%[======================================>] 3,749,293 345K/s in 7.1s 2012-07-15 19:40:20 (516 KB/s) - `postgis-1.5.2.tar.gz' saved [3749293/3749293] jjz@jjz-Laptop:~$ tar xzf postgis-1.5.2.tar.gz jjz@jjz-Laptop:~$ cd postgis-1.52 bash: cd: postgis-1.52: No such file or directory jjz@jjz-Laptop:~$ cd postgis-1.5.2 jjz@jjz-Laptop:~/postgis-1.5.2$ ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking how to run the C preprocessor... gcc -E checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl.exe... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking whether we are using the GNU C++ compiler... (cached) no checking whether g++ accepts -g... (cached) no checking if gcc supports -Wall... yes checking if gcc supports -Wmissing-prototypes... yes checking if gcc supports -ffloat-store... yes checking for flex... no checking for lex... no checking for bison... no checking for byacc... no checking ieeefp.h usability... no checking ieeefp.h presence... no checking for ieeefp.h... no checking for convert... no configure: WARNING: ImageMagick does not seem to be installed. Documentation cannot be built checking for xsltproc... no configure: WARNING: xsltproc is not installed so documentation cannot be built checking for dblatex... no configure: WARNING: dblatex is not installed so PDF documentation cannot be built configure: WARNING: could not locate Docbook stylesheets required to build the documentation checking CUnit/CUnit.h usability... no checking CUnit/CUnit.h presence... no checking for CUnit/CUnit.h... no configure: WARNING: could not locate CUnit required for liblwgeom unit tests checking iconv.h usability... yes checking iconv.h presence... yes checking for iconv.h... yes checking for libiconv_open in -liconv... no checking for iconv_open in -lc... yes checking for iconvctl... no checking for libiconvctl... no checking for pg_config... /usr/bin/pg_config checking PostgreSQL version... PostgreSQL 9.1.4 checking libpq-fe.h usability... yes checking libpq-fe.h presence... yes checking for libpq-fe.h... yes checking for PQserverVersion in -lpq... yes checking for xml2-config... no configure: error: could not find xml2-config from libxml2 within the current path. You may need to try re-running configure with a --with-xml2config parameter. jjz@jjz-Laptop:~/postgis-1.5.2$ make make -C liblwgeom make[1]: Entering directory `/home/jjz/postgis-1.5.2/liblwgeom' gcc -g -O2 -fno-common -DPIC -Wall -Wmissing-prototypes -c -o measures.o measures.c In file included from measures.h:16:0, from measures.c:18: liblwgeom.h:18:31: fatal error: ../postgis_config.h: No such file or directory compilation terminated. make[1]: *** [measures.o] Error 1 make[1]: Leaving directory `/home/jjz/postgis-1.5.2/liblwgeom' make: *** [liblwgeom] Error 2 jjz@jjz-Laptop:~/postgis-1.5.2$ sudo make install [sudo] password for jjz: make -C liblwgeom make[1]: Entering directory `/home/jjz/postgis-1.5.2/liblwgeom' gcc -g -O2 -fno-common -DPIC -Wall -Wmissing-prototypes -c -o measures.o measures.c In file included from measures.h:16:0, from measures.c:18: liblwgeom.h:18:31: fatal error: ../postgis_config.h: No such file or directory compilation terminated. make[1]: *** [measures.o] Error 1 make[1]: Leaving directory `/home/jjz/postgis-1.5.2/liblwgeom' make: *** [liblwgeom] Error 2 jjz@jjz-Laptop:~/postgis-1.5.2$ cd .. jjz@jjz-Laptop:~$ Which I feel like is an error? Wow really that sounds too good to be true haha its sounding better already! On Sunday, July 15, 2012 7:20:45 PM UTC-4, Jani Tiainen wrote: > > Or if your database backend supports spatial fields, you can let the > database to do the hard work and use Geodjango (built-in GIS extension) > which supports spatial operations like query by distance within. > > I think most standard databases can do that (mysql, postgresql, sqlite, > oracle) but I would recommend postgres + postgis if possible. > > Then everything is just matter of taste, you can pick pretty much any > coordinate system and you get the results you want. No math involved. > > On Mon, Jul 16, 2012 at 2:12 AM, JJ Zolper <codinga...@gmail.com> wrote: > >> I'm also thinking since Northern VA is so big in terms of people if I get >> a good thing going here I can port that to other major cities but if I find >> a less server heavy method I can use that for smaller areas possibly. Not >> sure, I'll see. >> >> JJ >> >> >> On Sunday, July 15, 2012 1:22:10 PM UTC-4, Nicolas Emiliani wrote: >>> >>> >>> >>> What you have just explained seems to be a good option! Is the option to >>>> use latitude and longitude a very common one? I'm not >>>> as familiar as to which options of calculation have known to be the >>>> most stable, usable, fast, or efficient. Or there is any common >>>> knowledge about the such thing. >>>> >>> >>> Well with (lat, long) you can point to any place on earth, it's like >>> having an (x,y) point on a cartesian plane. >>> And yes, it is the standard method. >>> >>> >>>> >>>> Here's what I'm thinking. First the user enters their town for example >>>> so Vienna, VA. Then they choose how far from their location so 25 miles. >>>> But then they also have an advanced search option where they can refine >>>> their request even more. They are able to play around with a Google Map on >>>> the side and zoom into their physical house location on the map and put a >>>> marker/point there of some sort. This could be lat/long I don't know yet. >>>> This way if that data checks out they get and even more accurate >>>> representation of the artists in their area. Any thoughts or opinions on >>>> how you think I >>>> should go about this? >>>> >>>> >>> With the (lat,long) that belongs to the user position yo can then ask >>> for a radius in blocks, meters o whatever. >>> So, now you can get the surface of a circle and with some basic math you >>> go through your db checking if any artist >>> are inside the limit of that circle. >>> >>> >>>> Thanks so much! >>>> >>>> JJ >>>> >>>> On Sunday, July 15, 2012 10:22:53 AM UTC-4, Nicolas Emiliani wrote: >>>>> >>>>> >>>>> >>>>> On Sun, Jul 15, 2012 at 1:58 AM, JJ Zolper <codinga...@gmail.com>wrote: >>>>> >>>>>> So heres my goal: >>>>>> >>>>>> The user logins in and goes to a discover page. They enter a distance >>>>>> from their location as the requested results scope. Lets say 25 miles >>>>>> from >>>>>> where I live for example. Additionally they could pick like a genre or >>>>>> music but not as important. >>>>>> >>>>>> So they hit seach and see in a 25 mile spanse in all directions in a >>>>>> circle form the closest artists to their location. From there they can >>>>>> see >>>>>> the top result and click that and step through the top results from 1 to >>>>>> 2 >>>>>> to 3.... To top 10 and so on as much as their heart desires. >>>>>> >>>>>> So i was thinking maybe GeoIP might be good because it will use the >>>>>> users location and last known GeoIP of the artist for example. >>>>>> >>>>>> >>>>> I'm currently developing a project based on google maps, and it sounds >>>>> that you might want to take a look at their API, >>>>> You could use markers (latitude and longitude) for your artists, ask >>>>> the user to place themselves on the map and then >>>>> calculate if they are on the wanted area or not. >>>>> >>>>> https://developers.google.com/**maps/<https://developers.google.com/maps/> >>>>> >>>>> I was curious if anyone had any ideas or better ideas then I had. >>>>>> >>>>>> Thanks so much, >>>>>> >>>>>> JJ Zolper >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Django users" group. >>>>>> To view this discussion on the web visit https://groups.google.com/d/ >>>>>> **msg/django-users/-/_**ERIIZrolmUJ<https://groups.google.com/d/msg/django-users/-/_ERIIZrolmUJ> >>>>>> . >>>>>> To post to this group, send email to django-users@googlegroups.com. >>>>>> To unsubscribe from this group, send email to >>>>>> django-users+unsubscribe@**googlegroups.com<django-users%2bunsubscr...@googlegroups.com> >>>>>> . >>>>>> For more options, visit this group at http://groups.google.com/** >>>>>> group/django-users?hl=en<http://groups.google.com/group/django-users?hl=en> >>>>>> . >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Nicolas Emiliani >>>>> >>>>> Lo unico instantaneo en la vida es el cafe, y es bien feo. >>>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/django-users/-/xqKHuCVictIJ. >> >> To post to this group, send email to django-users@googlegroups.com. >> To unsubscribe from this group, send email to >> django-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-users?hl=en. >> > > > > -- > Jani Tiainen > > - Well planned is half done, and a half done has been sufficient before... > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/W-SrqDO5vxMJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
