Zero Waste Upgrade of Empire State Building Windows

First of all, Jagan outlined a fascinating story about upgrading all the windows in the Empire State Building. To improve  energy efficiency all of the Empire State Building's 6,500 R2 windows were replaced with higher insulation R8 windows, which will enable the Empire State Building to reduce its energy bill by 40%.  But what is even more interesting is that replacing the 26,000 panes of glass did not involve carting the old glass out to the landfill, and then carting in the new ones. Instead a small factory was setup on one of the floors where the the old R2 windows were converted to R8 windows - minimal waste, no transportation costs and smaller carbon footprint for manufacturing these windows.

Autodesk Cleantech Partner Program

Secondly, Jagan pointed to Autodesk's Cleantech partner program which he saw as "a win-win for the early stage startups as well as Autodesk."  In July of last year Autodesk setup the Autodesk Cleantech Partner Program, which grants free design and engineering software to early-stage clean technology companies in North America who are working to solve some of the world’s environmental challenges.

China’s run to become Cleantech Leader

Finally, Jagan discussed China's very ambitious cleantech initiative.  According to Jagan, one of the panelist in the forum said “China is going to kick our (US) butt in cleantech industry if we do not act quickly”. Jagan "was amazed by the speed with which China is moving into the cleantech space, both in terms of developing green cities as well as building products for the cleantech industry. Mayors of China’s cities have the authority to approve green city projects within weeks, if right type of financing, project plan and technologies are presented to them. China has plans to pilot smart grid in 4 cities over the next 4 years, as well as plans to build many more green cities."

One thing that Shapely has lacked is one or two dirt simple example programs to keep the API real and help explain its use. I did something about this over the past couple of nights: 1.2a6 includes two easy to understand, easy to run scripts. I hope users profit from them. Myself, I found that they demanded a new and improved API feature. I'll explain.

First, here's an example of using Shapely to construct patches by growing buffer regions out from a set of points and dissolving those regions together as they intersect, and plotting the results with Matplotlib. This is run-of-the-mill GIS stuff, yes, but done in style.

A plate of blue-speckled brains splattered on the floor, or is it just me?

The interesting part of the complete, amply-documented dissolve.py script is here:

import pylab
from shapely.ops import cascaded_union
patches = cascaded_union(spots)
pylab.figure(num=None, figsize=(4, 4), dpi=180)
for patch in patches.geoms:
    x, y = patch.exterior.xy
    pylab.fill(x, y, color='#cccccc', aa=True)
    pylab.plot(x, y, color='#666666', aa=True, lw=1.0)
    for hole in patch.interiors:
        x, y = hole.xy
        pylab.fill(x, y, color='#ffffff', aa=True)
        pylab.plot(x, y, color='#999999', aa=True, lw=1.0)
pylab.text(-25, 25,
    "Patches: %d, total area: %.2f" % (len(patches.geoms), patches.area))
pylab.savefig('dissolve.png')

The xy property is completely new in 1.2a6, inspired by how awkwardly I had to slice and dice coordinates when writing this example against 1.2a5. It provides two Python arrays that are immediately usable with Numpy or Matplotlib. Speaking of Matplotlib: I'd love to know how to fill a patch but not its holes (you'll notice that I'm faking the emptiness of the holes in this example).

What would would you have to go through to pyplot ArcGIS scripting results?

Shapely doesn't just make grey matter go splat, it can also toss brains in the air and pierce them with lasers:

Or make a fair facsimile thereof. What's really going on in intersect.py is an analysis of a HTML5 geolocation (latitude, longitude, heading, and speed) trajectory's intersection with a cluster of patches. The intercepted patches are plotted in red and the intersecting segments of the trajectory itself are also plotted in red. Finally, scalar properties of different geometries are used in a text label:

import pylab
from shapely.geometry import LineString
# Represent the following geolocation parameters
#
# initial position: -25, -25
# heading: 45.0
# speed: 50*sqrt(2)
#
# as a line
vector = LineString(((-25.0, -25.0), (25.0, 25.0)))
# Find intercepted and missed patches. List the former so we can count them
intercepts = [patch for patch in patches.geoms if vector.intersects(patch)]
misses = (patch for patch in patches.geoms if not vector.intersects(patch))
pylab.figure(num=None, figsize=(4, 4), dpi=180)
for spot in misses:
    x, y = spot.exterior.xy
    pylab.fill(x, y, color='#cccccc', aa=True)
    pylab.plot(x, y, color='#999999', aa=True, lw=1.0)
    for hole in spot.interiors:
        x, y = hole.xy
        pylab.fill(x, y, color='#ffffff', aa=True)
        pylab.plot(x, y, color='#999999', aa=True, lw=1.0)
for spot in intercepts:
    x, y = spot.exterior.xy
    pylab.fill(x, y, color='red', alpha=0.25, aa=True)
    pylab.plot(x, y, color='red', alpha=0.5, aa=True, lw=1.0)
    for hole in spot.interiors:
        x, y = hole.xy
        pylab.fill(x, y, color='#ffffff', aa=True)
        pylab.plot(x, y, color='red', alpha=0.5, aa=True, lw=1.0)
pylab.arrow(-25, -25, 50, 50, color='#999999', aa=True,
    head_width=1.0, head_length=1.0)
intersection = vector.intersection(patches)
for segment in intersection.geoms:
    x, y = segment.xy
    pylab.plot(x, y, color='red', aa=True, lw=1.5)
pylab.text(-28, 25,
    "Patches: %d/%d (%d), total length: %.1f" \
     % (len(intercepts), len(patches.geoms),
        len(intersection.geoms), intersection.length))
pylab.savefig('intersect.png')

Grab the new distribution with easy_install or pip (as well as Numpy and matplotlib) and give them a try:

$ python /usr/local/bin/dissolve.py
$ python /usr/local/bin/intersect.py

I think this is pretty much the last 1.2 alpha.

The National Institute of Standards and Technology (NIST) has released the Framework and Roadmap for Smart Grid Interoperability Standards 1.0.  The NIST sees an urgent need to establish standards for the smart grid because without standards, there is the potential for technologies developed or implemented with sizable public and private investments to become obsolete prematurely or to be implemented without ensuring security. The Energy Independence and Security Act of 2007 (EISA) designated development of a Smart Grid as a national policy goal and specifically said that the interoperability framework should be “flexible, uniform, and technology neutral” while at the same time encouraging new, innovative smart grid technologies.

The Framework and Roadmap for Smart Grid Interoperability Standards 1.0 describes a conceptual reference model for the smart grid, identifies existing standards that are applicable to the development of the smart grid, identifies high-priority gaps for which new or revised standards are necessary, outlines action plans with timelines and standards organizations for addressing these gaps, and addresses smart grid cybersecurity.

NIST chose to focus initially on standards identified by the Federal Energy Regulatory Commission (FERC) plus additional areas identified by NIST. The priority areas are:

• Demand Response and Consumer Energy Efficiency
• Wide-Area Situational Awareness
• Energy Storage
• Electric Transportation
• Advanced Metering Infrastructure
• Distribution Grid Management
• Cyber Security
• Network Communications

For each priority area, Priority Action Plans (PAP) and targets for completion have been identified.  One, the smart meter upgradeability standard, has already been completed.

1. Common specification for price and product definition (early 2010)
2. Common scheduling mechanism for energy transactions (early 2010)
3. Common information model for distribution grid management (year-end 2010)
4. Standard demand response signals (early 2010)
5. Standards for energy use information (mid 2010)
6. DNP3 Mapping to IEC 61850 Objects (2010)3
7. Harmonization of IEEE C37.118 with IEC 61850 and precision time synchronization (mid 2010)
8. Transmission and distribution power systems models mapping (year-end 2010)
9. Guidelines for use of IP protocol suite in the Smart Grid (mid 2010)
10. Guidelines for use of wireless communications in the Smart Grid (mid 2010)
11. Energy storage interconnection guidelines (mid 2010)
12. Interoperability standards to support plug-in electric vehicles (year-end 2010)
13. Standard meter data profiles (year-end 2010)
14. Harmonize power line carrier standards for appliance communications in the home (year-end 2010)
15. Cyber Security

The reference model, standards, gaps and action plans in the Framework are designed to create an initial foundation for a secure, interoperable smart grid and were achieved through participatory workshops and webinars, a formal public review process, and the involvement of more than 20 standards organizations.

The second phase of the NIST plan involves an ongoing organization and consensus process that is being formalized under a new virtual organization, the Smart Grid Interoperability Panel (SGIP). The SGIP is a public-private partnership that provides a more permanent organizational structure to support the continuing evolution of the framework and is open to international participation. SGIP membership already includes over 500 organizations.  The objective is to create a robust standards process that supports smart grid innovation for at least the next two decades.

Autodesk has acquired Dynamite VSP and Dynamite SIM visualization software products from 3AM Solutions in the UK.  Dynamite VSP and Dynamite SIM help automate the process of creating visualizations for civil engineering projects designed with AutoCAD Civil 3D by providing simple and efficient ways to bring Civil 3D designs into Autodesk 3ds Max Design. 

3D visualization helps communicate engineering designs with technical and non-technical people and is especially helpful for processes involving public consultation and approval.  Autodesk intends to integrate core technology from the Dynamite VSP and Dynamite SIM products into 3ds Max Design and other existing Autodesk architecture, civil engineering and visual communication applications.  The applications are specifically optimized for road design and corridor modeling for transportation networks, but there are plans to extend this capability into other domains.

Ever had the need to format some text in SLD, or to perform complex filter in WFS, and noticed that the basic elements of the OGC Filter specification left you wanting for more?

If so, welcome to the club. One thing few people know is that both SLD and WFS filtering capabilities can be extended by using filter functions. A filter function is just like a programming language function, it’s something that takes arguments and returns some result. For example, “sin(toRadians(45))” will compute the mathematical sin of 45 degrees, and “strSubstring(”hippopotamus”, 0,  5)” will return “hippo”.

The concept of filter function is standardized, but functions themselves are not, so once you start using them you’re tied to a specific server. However they often provide the level of flexibility that you just need in order to get some work done. The good news is that GeoServer already contains tens of them, from number and date formatting, to geometry manipulation, math, string wrangling. So far we just never found the time to document them, but things have changed and we have now quite a complete reference along with some examples.

Let me show you a simple example of using functions. Say we have a contour map, each isoline has an elevation, and we want to show it on the map. Unfortunately the elevation is stored as a floating point, resulting in a less than pleasing output of “150.0″ or sometimes “149.999999″ when we know the elevation accuracy does not go beyond the meter. To get nice labelling we can use the “numberFormat” filter function to force an integer representation instead (along with some VendorOptions):

<TextSymbolizer>
  <Label>
    <ogc:Function name="numberFormat">
       <ogc:Literal>#</ogc:Literal>
       <ogc:PropertyName>ELEVATION</ogc:PropertyName>
    </ogc:Function>
   </Label>

  ....

   <VendorOption name="followLine">true</VendorOption>
   <VendorOption name="repeat">250</VendorOption>
   <VendorOption name="maxDisplacement">150</VendorOption>
   <VendorOption name="maxAngleDelta">30</VendorOption>
</TextSymbolizer>

Notice how the the ELEVATION field is formatted as an integer number following the simple formatting pattern provided (for a full reference see the the Java DecimalFormat documentation):

I hope you’ll find interesting and clever uses of the existing filter functions to improve the way you work with GeoServer. Next time I’ll show you my favourite one, which is also a new feature in GeoServer 2.0.1, called “geometry transformations”. Stay tuned to learn more about it.

The report suggests that a significant worldwide expansion is unlikely before 2030, and that a window of opportunity exists to fix the currently inadequate global governance system to avoid nuclear accidents and weapons proliferation. The report says that since the 1986 Chernobyl accident, nuclear safety has improved around the world, but that a safety culture around nuclear power does not exist in all countries. 

President Obama will host a special summit on nuclear security in April, Nuclear Nonproliferation Treaty signatories will meet in New York for a review conference in May and it looks like nuclear issues will be high on the agenda at the G8 summit in Huntsville, Ontario in June. 

The report makes several recommendations to improve global nuclear global governance and make the world safer for nuclear energy.  It also argues that Canada, with experience in nuclear technology and a history of engagement in the construction of effective global governance in this area, is particularly well placed to promote such an agenda.

In a joint project with the World Bank, USAID, and numerous other partners, there are now 6 TB hard drives on the ground in Haiti with mapping tools and satellite and remote imagery data being shared with the Haitian government. Read more about the project on the FortiusOne blog.

Schuyler Erle and Tom Buckley will be heading down on Tuesday to provide on the ground support between the government agencies and the community.

A tremendous thank you to the numerous individuals and groups that helped and provided tools or data: World Bank, San Diego State University / Calit2, Internet2, Georgetown University, DigitalGlobe, Delta State University, Sahaha, Crisis Mappers, OpenStreetMap, NOAA, Ushahidi, DevelopmentSeed, TelaScience, STAR-TIDES, CrisisCommons, USAID, GeoCommons, OpenSGI, GeoEye.

I’ve just started writing Boost.Geometry (aka GGL) documentation in Quickbook. It is a lightweight format and parser being developed by Boost used to prepare technical documentation for software, mainly for for Boost C++ Libraries. Quickbook files (.qbk) are used as input for BoostDoc which in turn is an extension of DocBook.

Quickbook is a textual format, it feels quite similar to AsciiDoc or some sort of Wiki dialect but dedicated for documenting C++ programming. It is extremely easy to grasp while drinking a single short coffee.

Anyway, it seems it is going to be a quite a book after all elements of Boost.Geometry are documented. One of the challenge I’ve found is to collect all bits necessary to document C++ concepts defined by Boost.Geometry. Unfortunately, Doxygen is not an ideal tool for this purpose, so current version of the documentation lacks of some sections of concepts description. So, I have to dig the source code to find out formal definitions and details of valid expressions and semantics.

Another challenge related to concepts is to find best way to structure their documentation. I started to browse documentation of existing Boost libraries looking for examples and what I found is that there is no best example. Various libraries document concepts in very different way.

A concept is a set of requirements consisting of valid expressions, associated types, invariants, and complexity guarantees

– David Abrahams, Generic Programming Techniques

For example, neatly Boost.Fusion documents concepts with Quickbook, though some elements seem to be omitted. Boost.Graph doesn’t document with Quickbook, looks good, but some details are missing to me, for instance, titles in headers of tables saying what is what is return type and pre-/post-condition for valid expressions, etc. Documentation of Boost.IOStreams concepts sound well. On the other hand, Boost.GIL is an example of why Doxygen should not be used to document concepts of a C++ library.

It looks to me the old good Standard Template Library Programmer’s Guide at SGI is still a best and most complete example of how C++ concepts should be documented.

Given these experiences, I started to think of a way to improve the way concepts are documented within Boost. I believe it would be a good idea to have predefined block for concept in Quickbook. Something along these lines:

[concepttype [Point Concept]
  [this is a concept for 0-dimensional geometry]
  [notation
    [term 1] [description 1]
  ]
  [refinement [concept 1] [concept 2]]
  [associated
    [type 1] [description 1]
  ]
  [expressions
    [name 1 [expr 1]
      [type requirement 1] [return type 1]
  ]
  [semantics
    [name 1 [expr 1]
      [precondition 1] [semantic 1] [postcondition 1]
  ]
  [complexity [...]]
  [invariants
    [invariant 1] [description 1]
  ]
  [models [model 1] [model 2]]
  [notes
    [ note 1] [ note 1]
  ]
  [seealso ...]
]

I posted my proposal to boost-docs list explaining the motivation in details. It’s an interesting experience of a C++ documentation craftsman, anyway. (BTW, Daniel James just announced Quickbook port to Spirit 2.)

Regina Obe has just announced that PostGIS in Action book website launched. It is http://postgis.us

The Boost 1.42 was released a week ago, however this release does not include Boost.Geometry (aka GGL) which was accepted 2 months ago. It is nothing uncommon, though many people have been asking obvious question, why Boost.Geometry is not there and when it will be there.

Boost.Geometry is accepted but with a sticky note attached with a list of issues that need to be solved before the library can be included in official Boost release. It means there is still plenty of work necessary to be done and as soon as they are done and confirmed, we’re in.

Hartmut Kaiser, the review manager, included compete and detailed list of all the issues that need to be addressed in the GGL review results report. Shortly, the contingencies are:

• Robustness: complete review of all elements of the library to assure it allows to instantiate all algorithms with arbitrary number types. By design, it is possible to specialise types and algorithms of Boost.Geometry with GMP or CLN, so it computes with arbitrary-precision arithmetic. This feature is possible thanks to numeric_adaptor developed by Bruno and Barend. Also, details of computational complexity per algorithms shall be updated.
• Concepts: during the review, a few problems have been revealed with adapting custom geometries for Boost.Geometry. The concepts are a moral backbone of the library, so they need to be sound making the adaptation process simpler as that’s what the whole idea of concepts in C++ is for.
• Boolean operations: robustness and coping with different coordinate orders of polygons should be improved.
• Documentation: currently only Doxygen-based documentation is available. This system does not work well for Boost, so migration to Quickbook system is to be done.
• Testing: simply, a collection of basic unit tests is not enough and verification of the correctness of the algorithms in a wide range of use cases is necessary along with high volume and random tests.

There are also a few minor issues specified as non-contingencies, however.

It is quite a list and plenty of work that needs to be done and Barend replied on the list:

We’re working on the library, I don’t hope it will take us that long, but 1.42 was not feasable at all. I hope 1.43 but even that is already coming soon.

Tasks dispatched. Fingers crossed.

Over the last two years, Landgate has invited proposals for Developer Innovation Grants to build innovative applications that utilises the Shared Land Information Platform (SLIP). SLIP delivers web data services for a wide range of Western Australian and national geospatial data though a standards-based Spatial Data Infrastructure.

The SLIP Innovation Grants are awarded for innovative ideas in the development of commercial applications and new uses of SLIP datasets. LISAsoft is proud to be awarded three of five of this year’s grants.

“LISAsoft’s proposals fitted very closely with our users needs, and we see them providing significant value to the future of SLIP.” Darren Mottolini, Landgate Business Consultant.

Winning Ideas:

PostGIS Shapefile Loader GUI

The current process for appending a shapefile to an existing PostGIS table involves command line tools and scripts. This project will produce a GUI interface for loading a shapefile to a PostGIS database.

Automated Layer Creation

By streamlining the current manual process of metadata collection, agencies will be able to leverage SLIP for high currency data services.

Big Red Basemap Feedback

“Big Red” provides the ability to markup base map information with instructions to create, update and delete features and review update history from a web page. Crowd sourcing will be used to clean and improve datasets.

Would you like to work on innovative projects, using Geospatial Standards, Open Source, and Geospatial Technologies? LISAsoft is hiring. Contact me if interested.

Since tiles from different sources are being stored in the application cache with a common namespace, you can move tiles from one folder to another to get funny, revealing combinations:

And here is a nice screenshot in full-screen mode (click to expand):

Read more of this story at Slashgeo.

Read more of this story at Slashgeo.

Read more of this story at Slashgeo.

President Obama's request in the 2011 Budget for additional funds for nuclear power reminded me of a post I made last July. At that time there were 436 operable nuclear power plants (373 GW) in about 30 countries generating about 15% of the world's power, 45 new plants were under construction, 131 were planned, and 282 had been proposed.  Since then the worldwide development of new nuclear power has increased.   As of February 1, 53 new plants (51 GW) are under construction, 142 (156 GW) are on order or planned, and 327 (343 GW) have been proposed.  One of the major drivers for nuclear power is that it is non-emitting and does not contribute to world CO₂ emissions.

About 60 per cent of the world's production of uranium from mines is from Canada, Australia and Kazakhstan. Canada produces the largest share of uranium from mines, 20.5 per cent of world supply. In 2008 Canada generated about 88.6 billion kWh from 18 nuclear power plants with a total capacity of 13 GW, about 15% of total power generation.

Australia has the world's largest uranium reserves, 23% of the total. Only three mines are currently operating, but more are proposed. It looks like the government of Western Australia is about to approve its first uranium mine in three decades. There are no nuclear power plants in Australia, all uranium production is exported.

The rapid increase in demand for uranium has led to predictions of worldwide shortages in supply.

select ID, GEOM from T1 as t
inner join
HATBOX_MBR_INTERSECTS_ENV('PUBLIC','T1',145.05,145.25,-37.25,-37.05) as i
on t.ID = i.HATBOX_JOIN_ID

The RES Alliance for Jobs is a coalition of renewable energy companies in wind, solar and biomass.  The Alliance argues that a strong Renewable Energy Standard (RES) would provide the national commitment to renewable energy enabling manufacturers to invest billions of dollars in the U.S. economy and job creation.

The Alliance hired Navigant Consulting Inc. to study the impact of a national mandate for 25 percent renewables by 2025.  The study concluded that

• A national RES of 25% by 2025 would result in 274,000 more jobs than without a national RES.
• A national RES will lead to job growth in all states, especially those currently without state-level renewable electricity standards (RPS).

A equipe de desenvolvimento tem PostGIS, depois de um longo período de reflexão e um auto-exame de vários erros, decidiu lançar PostGIS 1.5.0 para o público. Esta nova versão do PostGIS inclui o novo tipo Geography para de gestão dos dados geodésicos (latitude / longitude), além da melhora no desempenho dos cálculos de distância, GML e KML.

O tipo Geography vai tornar mais fácil para novos usuários armazenarem seus dados no PostGIS (sem ter que aprender sobre projeções e sistemas de coordenadas) e também permitir que os gestores de dados armazenar e consultar seus dados com uma maior eficácia.

http://postgis.org/download/postgis-1.5.0.tar.gz

Fonte: OpenGEO Blog

Posts Relacionados

• Editando uma tabela do PostGIS utilizando o Open Mobile IS
• PostGIS WKT Raster
• PostGIS 1.4.0 Released
• PostGIS versus MySQL Spatial
• Livro: PostGIS in Action
• Cuidado: PostGIS 1.3.4 e MapServer
• GeoServer Developers Map
• Candidato usa Geotecnologia Livre em Campanha
• Preparando ambiente SIG com MapServer e C#
• GeoServer-BR alcança a marca de 350 membros

Enrico Zini, author of Meteosatlib, posted to his blog an interesting example in C++ language which uses, still quite mysterious for many, GDAL C++ API class VRTDataset and GDAL VRT machinery and illustrates how to crop images with GDAL.

In the US buildings are responsible for 40% of primary energy consumption and 39% of CO₂ emissions.  It is estimated that 150 billion square feet or about half of the existing building stock in the US will be remodeled over the next 30 years and most of it will require energy modeling to conserve energy and reduce emissions.

Autodesk developed a workflow for rapid energy modeling (REM) that streamlines capturing building exteriors, creating a building simulation and performing a building energy analysis. To assess the practicability of the process, Autodesk applied the process to six Autodesk buildings on three continents.  The results, which are available in a report, suggest that rapid energy modeling enables building energy assessments with a smaller budget and shorter time frame, and can thereby help increase the number of existing buildings that undergo assessment and energy upgrades. 

 The first Canadian Geomatics Conference will take place   June 15 to 18, 2010 at the Telus Convention Centre in Calgary, Alberta.  Pre-Conference Workshops will be offered June 14. 

The Organizers, a partnership of groups from within the Geomatics Community, are presenting the conference in association with Commission I of the International Society for Photogrammtery and of Remote Sensing.

The conference will focus on the potential of Intelligent Mapping and the critical role Geomatics can play in bolstering Canada’s productivity, innovation, global competitiveness and overall socio-economic well-being.  The Conference is designed to attract decision-makers, the general public and non-traditional users of spatial information, as well as those deeply involved within the Geomatics community: educators, developers, government, industry, and scientists. ISPRS Commission I will present a concurrent program focused on sensors and platforms. This will provide insight into the role space and satellites play in developing the ability to observe, detect and capture accurate data from great distances.

Texas now requires building information modeling (BIM) on state projects.  You can find the new standards at the Texas Facilities Commission web site.  Follow the link and download #23 for BIM guidelines and standards that go with the new TFC contracts. Thanks to Mob Middlebrooks for pointing me to this.

"A. TFC has adopted Building Information Modeling (BIM) as a standard for producing the design and documentation for all projects developed under TFC authority.

"B. TFC-adopted BIM software versions are listed in the “BIM Standards - Overview” section of this document.

"C. CADD software may be used only in isolated circumstances as indicated in the “CADD Standards” section of this document"

I have blogged previously about Singapore, which is encouraging e-submission of building information models (BIM).  Right now I believe that Singapore accepts architectural, structural and MEP BIMs.

Ontem a comunidade GeoServer-BR chegou a marca de 350 membros, isso em menos de 3 anos de vida. É muito gratificante ver como esta comunidade tem crescido aqui no Brasil, somos hoje a segunda maior comunidade GeoServer no mundo, só perdendo para a comunidade americana.

O números tem surpreendido não só a mim, como também ao Core do GeoServer, pois só no ano de 2009 foram 166 novos membros, e 1068 mensagens, criando uma média de 89 por mês.

Gostaria de agradecer a todos que tem ajudado de alguma forma essa comunidade a crescer. Se você não participa desta comunidade ainda, cadastre-se no link abaixo:

– http://tech.groups.yahoo.com/group/geoserver/

Posts Relacionados

• Atualização do RESTful no GeoServer 1.7.x
• Serviços RESTful com o GeoServer 2.0.1
• GeoServer 2.0.1 Released
• GeoServer Japanese Group
• GeoServer agora é um projeto da OSGeo
• Workshop de GeoServer com Jody Garnett
• GeoServer 2.0 Released
• Resultado do WMS Performance Shootout 2009
• Apostila de GeoServer para Iniciantes
• GeoServer 2.0 RC2 Released

Speaking of the open web, here's Mark Pilgrim's take on HTML5 geolocation:

Geolocation is the art of figuring out where you are in the world and (optionally) sharing that information with people you trust. There are many ways to figure out where you are — your IP address, your wireless network connection, which cell tower your phone is talking to, or dedicated GPS hardware that receives latitude and longitude information from satellites in the sky.

You can also pick your location, or any other location at all that suits your needs, from a map using René-Luc's Firefox Geolocater.

• Alternativa Geologica


• ESRIdipendente


• Faccio Cose Vedo Gente


• GeoBI


• freeGIS-Italia


• Il Blog italiano di AutoCAD Map e Civil 3D


• inDiritto.it


• JGrass Tech Tips


• map freely


• massimozotti.it


• OpenStreetMap Italia


• Simone Cortesi


• TANTO


• Thinking in GIS


• Sistemi Informativi Territoriali in Sicilia

I may be a gonzo or it’s just that today I didn’t have my notorious 4th coffee in my favourite Winnie The Pooh cup I got from Pantera on our 14th (or 15th?) anniversary we celebrated a month ago, so…

Apparently, there are situations in which PostGIS could be an affordable anti-GML vaccine jab. It seems there is a potential market for PostGIS to conquer. Perhaps it wouldn’t be estimated as profitable as the H1N1 but who knows what will happen if no one takes a brave stand and stop GML designers! Here I’d eagerly conclude with one of the famous Scottish sentences :-)

Back to the subject matter. Today, I spotted an interesting question on the StackOverflow archives: Is it possible to export spatial data from Sql Server 2008 in gml2 format?. Natively? No, there is no such solution. Presumably, Microsoft thinks forward and thinks GML 2 is a legacy standard. Fair enough, someone has to draw a line between prehistoric and modern, somewhere. Why Microsoft? Again?

Facing such a tremendous suffer Microsoft exposed SQL Server users to, I suggested to visit the “underworld” for a while and hire PostGIS to do the dirty job.

Paraphrasing Andrei Alexan­dres­cu’s, hysterically famous recently, sentence: SQL Server should go!.

Autodesk has announced the release of Topobase 2010 Update 2 for Topobase 2010 Client and Topobase 2010 Web.  Topobase is infrastructure asset management software built on AutoCAD Map 3D and MapGuide Enterprise.