4,121 reputation
11839
bio website blog.geoprocessamento.net
location Sao Paulo, Brazil
age 28
visits member for 4 years
seen Jul 10 at 21:06

This is just me. Geographer, interested in GIS.


6h
awarded  Yearling
Jul
3
answered How to handle updates to pgRouting network in webmapping environment?
Jul
2
awarded  Inquisitive
Jul
2
awarded  Curious
Jun
19
awarded  Good Answer
Mar
24
awarded  Popular Question
Jan
13
accepted Cannot use a SnapAgent alone?
Dec
10
answered Unit testing with postgis 1.5 and django
Nov
30
answered How integrated can an IDE get for arcpy scripting?
Nov
20
awarded  Necromancer
Nov
5
comment Openlayer is very slow when using WKT Multipolygon with a large number of Points
There is something MapBox is working on that could help, but I think for now only works with TileMill2 (not production ready, if I'm not mistaken). They created the concept of Vector Tiles that seems to work well. Another issue is that the serialization between actual geometries and text (geojson) is always slow. If you can precache these geojson representations, it would me somewhat faster to draw, but that doesn't help in the client.
Jul
22
awarded  Yearling
Jul
19
awarded  Popular Question
Jul
8
awarded  Notable Question
Mar
27
awarded  Notable Question
Mar
19
comment Strange ArcSDE error inserting null into state_locks
Hi travis! Well, the logs do not show anything, but it's weird. We moved back to service connection and we've been getting a few Network IO errors, typical of that issue. i'm still investigating.
Mar
15
comment Strange ArcSDE error inserting null into state_locks
Master Kirk! THank you for answering the question. Unfortunately, this has nothing to do with the locks itself, since I can compress the database to state zero. :(
Mar
14
revised Strange ArcSDE error inserting null into state_locks
added 123 characters in body
Mar
14
asked Strange ArcSDE error inserting null into state_locks
Mar
5
comment Naming conventions PostGIS Database
This is a valid method, but I really don't like abbreviations. This is of course a matter of personal taste, but specially if you are on a international team, these abbreviations may confuse everyone and one will always need a data dictionary whenever he needs to use the database. PostgreSQL allows, if I'm not mistaken, 64 letter object names. Make good use of that space and create the most descriptive names you can find, in a language everyone can understand.